SAP OSS Notes: 1/9/11

12.1.11

SAP Note 17698 - Line item: Fast selection via allocation

Symptom:

Summary

Symptom

The selection of open and cleared items in the line item display via the allocation number is to be speeded up.

Additional key words

RFEPOS00, FBL1, FBL3, FBL5, ZUONR, allocation, TZUN, performance

Cause and prerequisites

Large number of items on an account.

Solution

Difficult, since the field can contain upper/lower case and only the selection conditions existing in upper case are passed on.
An advance correction is possible, but is only useful if only numeric characters ('numbers') or CAPITAL letters are contained in the allocation number. 1. /NSE38 - RFPOSTOP - FIND RANGES
...
RANGES: XBLNR FOR BSID-XBLNR.
RANGES: ZUONR FOR BSID-ZUONR. <-- Insert

2. /NSE38 - RFPOSFS0 - FIND BLDAT
FORM SELEKTION_AUSFUEHREN.
...
REFRESH: BLDAT.
LOOP AT SELTAB WHERE KTEXT = 'BLDAT'.
CHECK SELTAB-XINIT = SPACE.
PERFORM SELTAB_RANGE_FUELLEN
USING BLDAT-LOW BLDAT-HIGH BLDAT-OPTION BLDAT-SIGN.
APPEND BLDAT.
ENDLOOP.
REFRESH: ZUONR. <-- insert
LOOP AT SELTAB WHERE KTEXT = 'ZUONR'. <-- insert
CHECK SELTAB-XINIT = SPACE. <-- insert
PERFORM SELTAB_RANGE_FUELLEN <-- insert
USING ZUONR-LOW ZUONR-HIGH ZUONR-OPTION ZUONR-SIGN. <- insert
APPEND ZUONR. <-- insert
ENDLOOP. <-- insert
(These 7 statements are best copied from the above statements for BLDAT and then replace BLDAT by ZUONR.) 3. /NSE38 - RFPOSFB0, FORM routine BSID_LESEN and BSAD_LESEN
(Example only for customers! Other account types analogously):
FORM BSID_LESEN USING KONTO VBUKR.
...
CLEAR: BSID-AUGDT. <-- insert
SELECT * INTO BSID
FROM BSID
WHERE BUKRS = VBUKR
AND KUNNR = KONTO
AND UMSKS BETWEEN VVSHB AND BVSHB
AND UMSKZ BETWEEN VONUM AND BISUM
AND AUGDT EQ BSID-AUGDT <-- insert: 3.0A - 3.1H!
AND AUGBL EQ SPACE <-- insert: 3.0A - 3.1H!
AND BELNR IN BELNR
...
AND XBLNR IN XBLNR
AND ZUONR IN ZUONR <-- insert
...
ORDER BY PRIMARY KEY.
PERFORM POSTAB_BSID_FUELLEN.
ENDSELECT.
Providing, fields AUGDT and AUGBL have already been supplied
in the WHERE condition (as of Release 3.1I), do not change
these lines.

FORM BSAD_LESEN USING KONTO VBUKR.
...
SELECT * INTO BSID
FROM BSAD
WHERE BUKRS = VBUKR
AND KUNNR = KONTO
AND UMSKS BETWEEN VVSHB AND BVSHB
AND UMSKZ BETWEEN VONUM AND BISUM
...
AND XBLNR IN XBLNR
AND ZUONR IN ZUONR <-- insert
...
ORDER BY PRIMARY KEY.
PERFORM POSTAB_BSID_FUELLEN.
ENDSELECT.
ENDFORM.

4. As from release 4.0A: Analogous enhancement of the SELECT statements
in include RFPOSFT1, form routines BSID_LESEN_HIGHPERFORMANCE and
BSAD_LESEN_HIGHPERFORMANCE (Example for customers only! Other
account types in analogy):

FORM BSAD_LESEN_HIGHPERFORMANCE USING KONTO VBUKR.
SELECT (TRATAB)
FROM BSAD
INTO CORRESPONDING FIELDS OF BSID
WHERE BUKRS = VBUKR
...
AND XBLNR IN XBLNR
AND ZUONR IN ZUONR <-- insert
...
ENDSELECT.
ENDFORM.
...
FORM BSID_LESEN_HIGHPERFORMANCE USING KONTO VBUKR.
SELECT (TRATAB)
FROM BSID
INTO CORRESPONDING FIELDS OF BSID
WHERE BUKRS = VBUKR
...
AND XBLNR IN XBLNR
AND ZUONR IN ZUONR <-- insert
...
ENDSELECT.
ENDFORM.

Header Data


Release Status:	Released for Customer
Released on:	26.06.2001 22:00:00
Master Language:	German
Priority:	Recommendations/additional info
Category:	Performance
Primary Component:	FI Financial Accounting

Affected Releases

Release-Independent

Related Notes

194842 - Poor performance when you display line items

Print Selected Notes (PDF)

SAP Note 17694 - TIME_OUT

Symptom:

Runtime error during long-lasting evaluations: TIME_OUT

Cause and prerequisites

The time slice parameter has been defined too small.

Solution
Increase abap/timeout in the system profile (check with RSPARAM1). An 'endless' time slice can be set up by using value '0' for the parameter.

SAP Note 17692 - Matchcode in HR, infotype, configuration

Symptom:

Matchcodes in HR

Cause and prerequisites

Consulting problems

Solution
The following questions arise regarding the topic of matchcodes in HR:
What activities are required to configure and maintain matchcodes?
The description of configuration and maintenance of MC's is contained in the Guide "BC: SAP Data Dictionary", Chap. 4, Item no. 50007392
What Matchcode ID can be used?
HR recommends the MC ID's from 1 - 9.
Can MC's be set over more than one infotype?
Yes, see the example "Matchcode PREM -> ID 'Q'".
Can the MC be configured at a later stage?
The MC can also be configured at a later stage, even online.
Is there an alternative to the missing option of starting reports via MC?
As of Rel. 2.1D, a utility (RPUJOB00) exists which can be used to start any personnel report via Matchcode 'W'. This utility can be used to start reports both online and in the background.

Remember the following when you are configuring an MC:
- always define MC's via the master data for the object PREM.
- new MC fields must first be attached to table PREM.
- use the MC ID's from 1 - 9.
- copy new MC ID's from a standard ID.
- if a defined ID is modified, the MC must be converted prior to activation, that is, after being saved, by means of auxiliary tools.
- the list screen is affected by the sequence of field definitions in the ID and should be initially configured without modificiation features.
- an ID should always be linked to condition INFTY = 'xxxx' and should, therefore, contain the INFTY field.

SAP Note 17679 - Lot created for wrong stor.loc. during stock transfer

Symptom:

During the stock transfer, an inspection lot is generated for the original storage location and plant and not for the destination storage location or destination plant.

Cause and prerequisites

Program error.

Solution
Please modify program MM07MQSS as follows:
(Only in Releases 2.1 and 2.2)
In addition replace the following strings in FORM routine QSS_PRUEFEN in all lines containing a MESSAGE statement:
Replace MSEG-MATNR by L_MATNR.
Replace MSEG-WERKS by L_WERKS.
Also replace the string MSEG-MATNR by L_MATNR and MSEG-WERKS by L_WERKS in the statement CALL FUNCTION QBCK_QM_GR_CHECK.

Additional key words

MB11

SAP Note 17677 - Key date is not printed

Symptom:

In the reports SAPF100 SAPF101 and RFSBEW00, the key date is not output in the header line. The literal DD.MM.YY appears.

Cause and prerequisites

Translation error.

Solution
Up to Release 3.0:
The programs replace the string TT.MM.JJ in the header by the current key date.
Change the header line, for example, for the English translation from DD.MM.YY to TT.MM.JJ.

As of Rel. 3.0
The programs replace the string '.......' in the header with the
current key date.
Change the header line, for example, for the English translation from
from 'DD.MM.YY' to '........'.

SAP Note 17669 - Print: Text element "xxxx" not in window "MAIN"

Symptom:

Text element "xxxx" in window "yyyy" is not defined for layout set "zzzz".
ERROR MESSAGE: TD 427.

Cause and prerequisites

Text element translation does not match German text, or was damaged during transport.
OR, the user has defined his own Layout sets or Print ABAPS.

If this error occurs in Original GERMAN then the Layout set or Program contains an error.
I.e. WRITE_FORM function does not match Layset being used.

Solution
The Text element needs to be retranslated to match the original string.
A Text element is defined by the paragraph type /E in Sapscript Layout sets.
For example: Layout set PM_GOODS_ISSUE (Trans SE71)
Page Window -> Text elements:
/E MATERIAL describes the section printed from ABAP when section "MATERIAL" is called.
Should /E translation somehow be damaged or missing, then a message similar to the one above may appear.

Additional key words

td427

SAPNote 17665 - Performance in sales (e.g. VA01)

Symptom:

Wait times occur on the database when you enter sales documents and customer orders, resulting in poor response times.

Cause and prerequisites

When many users are working at the same time, bottlenecks occur in number assignment because the number range in the database remains locked between the assignment of the number and the COMMIT.

Solution
The number range objects can also be buffered; no lock is then used,
e.g. buffering 10 numbers .
Object KONV for the internal condition number.
This number is only used internally, no possible consequences. Object
RV_BELEG for all sales documents, deliveries, and billing documents.
You must consider here that buffering may cause gaps in the number
assignment. This is often not satisfactory, especially for billing
documents. An alternative to buffering is to use several order types
to split the number ranges of the orders, as the database lock is placed
at number range level.
Please refer to Note 23835 for information on avoiding the buffering of
invoices.
Use transaction SNRO to maintain the number range objects mentioned above.

SAP Note 17663 - Check info from doc.display if cross-company code

Symptom:

For cross-company code transactions, displaying check information from the document display can cause an incorrect message that no check information was found.

Additional problem: if the document in the paying company code only contains the bank item and the company code clearing item, then the "Check information" menu option is not active.

Cause and prerequisites

Displaying check information for the payment document:
The search is carried out using the paying company code of the automatic payment transaction. This company code deviates from the one in which the check was created in the case described.

Displaying check information for the invoice document:
In this case, the error message was always issued in the case of cross-company code transactions since the search routine did not analyze whether the accompanying payment document contained a cross-company code number.

Solution
Error eliminated in Release 2.2G and 3.0B. Interim correction is possible.

Subsequent problem eliminated in Release 3.0B. In Release 2.2, you should implement the correction in MF05LO00 described below.

Additional key words

Check information, FB03, error message F5241.

SAP Note 17649 - Selected items are inactive for FB05

Symptom:

When posting with clearing ( FB05, FBZ1, etc. ), the selected items are inactive, and the error message F5263 is generated under certain conditions "The difference is too large for a clearing".
They can be activated by doppel-clicking on them.

The problem often occurs when testing data transfer with batch input.
Especially with:

RFBIBL00

eletronic or manual account statement ( RFEBKA00, RFEBBU00, FF67 )

check deposit list ( FF68 )

Cause and prerequisites

1. The editing options for 'Open items' during posting are set so that the selected items are initially inactive.
2. The posting date of the selected items is in the future, from the point of view of the posting date of the document which is to be used for clearing.

Solution
ad 1.:
Start posting any document so that you can access the first screen for posting.
There, choose the menu option Options -> Editing options and click on the pushbutton 'Open items'.
If you deselect the field 'Selected items initially inactive', all selected items are active when posting with clearing.

ad 2.:
Adapt the posting date of the transaction which is to be used for clearing.
If the postings are in a batch input session, it can be processed online and the posting date can be changed manually.

SAP Note 17640 - Report Writer reports over several years and periods

Symptom:

If you choose a report for orders or projects (for example, report group 6pp2 or 6P01) with the report parameters,

From fiscal year 1993,
To fiscal year 1995,
From period 001,
To period 006,

the user might get the impression that the report would select the periods 1 to 12 for the fiscal years 1993 to 1994 and the periods 001 to 006 for the fiscal year 1995.
In this case, however, only the periods 001 to 006 are selected for all fiscal years.

Cause and prerequisites

The Report Writer deals separately with the report selections "Fiscal year" and "Period". All records whose for the fields "Fiscal year" and "Period" are within the specified interval are selected from the database.

The reports were defined this way to report with the same report
* over a period,
* over a period interval within a fiscal year,
* over several years (with all periods), or
* over the aggregate period (that is, over all years and all periods)

Solution
As the customers are using the reports since Release 2.0A in basically unchanged form, it is impossible to change their logic.
Sample report 6O06 reports over the duration of an order up to the current point in time.
We recommend to use this report or to adapt this report according to your own requirements.
For projects, you have to create a corresponding report yourself.

Additional key words

----- SUPPORTGUIDE 20010208103353 -----
REPORTWRITER, SGRW_AMOUNT, SGRW_RC_STRUCTURE, SGRW_DATA, SGRW_DOCU_CONS_NOTE
SGRW_PS

SAP Note 17636 - Syntax error in MKGALT8T

Symptom:

Controlling transactions abend with a syntax error in Include MKGALT8T.

Cause and prerequisites

There are operating concerns for which no active version of Table CE7xxxx (xxxx - operating concern) exists in the Data Dictionary. ABAP Include MKGALT8T is consequently generated incorrectly.

Solution
Check whether Tables CE7xxxx exist and are active in the Data Dictionary for the entries in Table T811T. If the tables are not active, proceed as follows:
if you use the operating concern, generate it again. Use transaction KE02 in Release 2.2 and
transaction KEA0 in Release 3.0
or
if you do not use it, delete the entries CE7xxxx from Table T811T.
Then execute Transaction KEUG once more for an operating concern to regenerate the Include.
To eliminate the problem quickly, you can use the second option first, and generate the operating concerns later.

SAP Note 17626 - Reports RFDSHS00 and RFKSHS00 deleted

Symptom:

For Release 3.0A, the special G/L balance lists for customers and vendors (RFDSHS00, RFKSHS00) were deleted.

Cause and prerequisites

The functionality of this list was completely implemented in the standard balance lists (RFDSLD00, RFKSLD00).

Solution
Please use the reports RFDSLD00 or RFKSLD00 to display the special G/L balances. Via the parameters
- 'Standard balances' and
- 'Special G/L balances'
you can determine which balances are to be displayed.

11.1.11

SAP Note 17626 - Reports RFDSHS00 and RFKSHS00 deleted

Symptom:

For Release 3.0A, the special G/L balance lists for customers and vendors (RFDSHS00, RFKSHS00) were deleted.

Cause and prerequisites

The functionality of this list was completely implemented in the standard balance lists (RFDSLD00, RFKSLD00).

SAP Note 17622 - No stock fields at plant level for previous period

Symptom:

In the material master, stocks at plant level (table MARC) are only managed for the current period, but not for the previous period and the previous year. Consequently, they are not displayed, when you use the relevant transactions of the material master record.

Cause and prerequisites

Managing the described stocks for previous periods is not supported.

Solution
Not applicable

SAP Note 17621 - Transaction SE01 or SE09 freezes

Symptom:

When you call transaction SE01 or SE09, the work process freezes. The user only sees the egg timer.
In the process overview (transaction SM50), you can see that the program where the process froze is SAPLSTRF.

Cause and prerequisites

Only in Release 3.0A:
Programming error in the operating system interface
Specifically in Windows NT in maintenance levels 3.00 to 3.0E:
Blockade by database lock
General:
Network problem accessing the files on the transport server.
Network problems can have various causes. In each case, they are not caused by the transaction call; they existed beforehand.

1. Shutdown of individual network components

2. Transport server overloaded. Solution
Only in Release 3.0A:
See Note 31227.
Specifically in Windows NT in maintenance levels 3.00 to 3.0E:
See Note 49242.
General:
Correct the network problems.
Please inform your network and/or transport administrator.

SAP Note 17619 - Transferring a payroll account

Symptom:

Consulting

Cause and prerequisites

Transfer payroll account

Solution
Table T558A contains sample entries for transferring a payroll account. Depending on the time of transfer (on January 1, or during the year), sample entries are available for period 1 or 4 of a given year.
Due to the large number of these sample entries, it is clear that users need to know when to use which entries.
If the account is transferred on January 1, the answer is easy: simply transfer the income threshold deficits and bases for calculating average values.
/340 PR diff. AAT HI curr.year
/341 PR diff. AAT PI curr.year
/342 PR diff. AAT UI curr.year
/3P8 PR diff.AAT NI curr.year
/431 cum. exemption comp.
You might also include customer-specific bases for calculating averages.
If, however, the account is transferred during the year, you need to know what has to be supplied with data from the payroll account transfer.
In the following list, the wage types are marked:
1 for payroll accounting/annual tax declaration/DUEVO
2 for employment tax statement
3 for the payroll account
4 for reallocation of trade tax base
5 for workers' compensation association list
/101 Total gross amount 1
/102 Current remuneration SI 1
/103 One-time SI payment 1
/106 Current gross tax amount 1
/111 Other gross tax amount 1
/113 M.gross tax amount 1
/114 1/2 gross tax amount 1
/118 Current ins.ind. 1
/120 Other insurance ind. 1
/122 1/2 insurance ind. 1
/124 M.insurance ind. 1
/126 Tax-free DBA 2
/127 Tax-free ATE 2
/159 Gross trade tax 4
/160 Mutual indem.soc. - gross 5
/261 Employee SI shares 3
/264 tax-free ER HI allowance 2
/265 taxable EE SI shares 2
/310 HI est.gross curr.remun. 1,3
/311 PI est.gross curr.remun. 1,3
/312 UI est.gross curr.remun. 1,3
/313 HI est.gross curr.total 1,3
/314 PI est.gross curr.total 1,3
/315 UI est.gross curr.total 1,3
/316 PI GrAssessAmtIncrease ER 1,3
/317 PIGrAssessAmtIncrease EE 1,3
/31A RWH PI est.gr.PH day(cur) 1,3
/31B BWP HI est.gr.PH day(cur) 1,3
/31C RWH HI est.gross (curr) 1,3
/31D BWP HI est.gross (curr) 1,3
/31E RWH PI est.gr.PH day(cur) 1,3
/31F BWP PI est.gr.PH day(cur) 1,3
/31I RWH UI est.gr.PH day(cur) 1,3
/31J BWP UI est.gr.PH day(cur) 1,3
/31M RWH PI est.gross DUEVO 1,3
/31N BWP PI est.gross DUEVO 1,3
/31O RWH UI est.gross DUEVO 1,3
/31P BWP UI est.gross DUEVO 1,3
/320 HI est.gross 1-time paym. 1,3
/321 PI est.gross 1-time paym. 1,3
/322 UI est.gross 1-time paym. 1,3
/323 HI est.gross 1-time total 1,3
/324 PI est.gross 1-time total 1,3
/325 UI est.gross 1-time total 1,3
/340 PR diff. AAT HI curr.year 1 If started in January, these are
/341 PR diff. AAT PI curr.year 1 passed on to the following 4 wage
/342 PR diff. AAT UI curr.year 1 types accordingly.
/346 PR diff. AAT HI prev.year 1 Only if started in Feb. or March
/347 PR diff. AAT PI prev.year 1 Only if started in Feb. or March
/348 PR diff. AAT UI prev.year 1 Only if started in Feb. or March
/350 HI EE share, curr.remun. 3
/351 HI ER share, curr.remun. 3
/352 HI EE share, 1-time paym. 3
/353 HI ER share, 1-time paym. 3
/356 HI EE share, prev.year 3
/357 HI ER share, prev.year 3
/358 ER HI allowance 3
/359 ER allow.HI private supp. 3
/35A RWH HI ER share pub.hol. 3
/35B BWP HI ER share pub.hol. 3
/35C RWH HI ER share (curr.) 3
/35D BWP HI ER share (curr.) 3
/35E RWH ER HI allowance 3
/35F BWP ER HI allowance 3
/35G HI permanence compensat. 3
/35J ded.contrib.HI addit. 1 3
/35K ded.contrib.HI addit. 2 3
/35L ded.contrib.HI addit. 3 3
/35M ded.contrib.HI addit. 4 3
/35N ded.contrib.HI addit. 5 3
/360 PI EE share curr.remun. 3
/361 PI ER share curr.remun. 3
/362 PI EE share 1-time paym. 3
/363 PI ER share 1-time paym. 3
/366 PI EE share prev.year 3
/367 PI ER share prev.year 3
/368 ER PI allowance 3
/369 ER allowance, limited PI 3
/36A RWH PI ER share pub.hol. 3
/36B BWP PI ER share pub.hol. 3
/36C RWH PI ER share (curr) 3
/36D BWP PI ER share (curr) 3
/36E RWH ER PI allowance 3
/36F BWP ER PI allowance 3
/36G PI permanence comp. 3
/36J ded.contrib. PI supp. 1 3
/36K ded.contrib. PI supp. 2 3
/36L ded.contrib. PI supp. 3 3
/36M ded.contrib. PI supp. 4 3
/36N ded.contrib. PI supp. 5 3
/36P PI increase share ER 1,3
/36Q Increase supplement ER 1,3
/370 UI EE share curr.remun. 3
/371 UI ER share curr.remun. 3
/372 UI EE share 1-time paym. 3
/373 UI ER share 1-time paym. 3
/376 UI EE share prev.year 3
/377 UI ER share prev.year 3
/378 ER UI allowance 3
/37A RWH UI ER share pub.hol. 3
/37B BWP UI ER share pub.hol. 3
/381 Ded.contrib.voluntary HI 3
/389 EE expenses for PI 3
/399 PI ER liable share limit. 3
/3P8 PR diff.AAT NI curr.year 1
/3P9 PR diff.AAT NI prev.year 1 Only if started in Feb. or March
/3PA NI est.gross curr.remun. 3
/3PC NI est.gross 1-time paym. 3
/3Q0 NI EE share curr.remun. 3
/3Q1 NI ER share curr.remun. 3
/3Q2 NI EE share one-time pay. 3
/3Q3 NI ER share one-time pay. 3
/3Q6 NI EE share prev.year 3
/3Q7 NI ER share prev.year 3
/3Q8 ER NI allowance 3
/3Q9 ER NI allow.private supp. 3
/3QR Ded.contrib./voluntary NI 3
/401 current employment tax 1
/402 other employment tax 1
/404 m.employment tax 2
/405 1/2 employment tax 2
/408 Lump-sum employ tax/ER 3
/409 Lump-sum employ tax/EE 3
/40B curr.reunification tax 1
/40C m.reunification tax 2
/40D Lump-sum reunif.tax/EE 3
/40E Lump-sum reunif.tax/ER 3
/40F other reunification tax 1
/40G 1/2 reunification tax 2
/411 Compensation lock 1
/412 Number of interruptions 2
/414 Supplementary table 2 /
/41C BMG §40(2) S.2 2
/431 cum. exemption comp. 1 You can put the actual exemption
amount still open into IT 0014,
this wage type then no longer
applies.
/441 tax-free transport allow. 2
/447 cum.EE discounts 1
/448 cum.exemption/car 1
/449 cum.exemption/cap.form. 1
/491 CTax EE (current+other) 2
/492 CT/spouse (current+other) 2
/493 CTax EE (m.+half) 2
/494 CT/spouse (m.+half) 2
/4KG Child allowance 3
/521 current church tax 1
/522 other church tax 1
/524 m.church tax 1
/525 1/2 church tax 1
/528 CTax lump-sum ER 3
/529 CTax lump-sum EE 3
/611 Increase #1 PTW 1
/692 RHC payment effected 2
/693 BWP payment effected 2

Once again, you must maintain customer-specific averages.
If the old system allows it, all other sample wage types 'can' be supplied to enable users to represent the payroll account for the whole year.
If necessary (and very often in practice), customers must authenticate the first payroll period for which the payroll was run using a non-SAP HR system with the payroll account of the old system.
Master data can be transferred as of the times from which it is valid in the old system. Before the first productive SAP payroll run, the only thing to be done is set the earliest personal retroactive accounting date for every employee in infotype 0003. (Normally this is one day earlier than the transfer date. Therefore, if transfer is on April 1, the earliest personal retroactive accounting date is usually March 31.) However, if payroll cannot be run any earlier for the entire payroll area, you can also set the earliest possible retroactive accounting period to the transfer month in the control record.
Of course, incorrect payroll runs in the old system cannot be corrected by the HR Payroll Accounting System. Furthermore, a deregistration and registration must be generated for DUEVO on the transfer date (see RPDSYS: CONX.DDUFD). Any incorrect entries must be corrected using a new record.
Caution: Please check personnel calculation rule DCOP. In some systems that were delivered, a RESET R is executed. This causes all wage types to be stored with an employee subgroup grouping for personnel calculation rules. Wage types that were read in payroll accounting without an employee subgroup grouping for personnel calculation rules (income threshold deficits, for example) will not be found. Please remove this operation.

SAP Note 17617 - Performance problems with matchcode F4 help

Symptom:

Long response times for matchcode F4 help

Cause and prerequisites

Case 1: a non-transparent matchcode ID is used (update type "A", "P", or "S").
Non-standard use of matchcodes: In the matchcodes used by SAP, we normally assume that the end user specifies a search sample in the first field of the "Restrict value range" dialog box. If this does not occur, all the records of the table must be read.
Case 2: a transparent matchcode ID is used (update type "I").
Missing index for the table field for which the enduser specified a sample in the "Restrict value range" screen. All the records must be read in this case, as well.

Solution
For case 1:
Copy the required matchcode ID to a new ID (customer name range "0" through "9"); assign the field sequence so that the main search field is the first field after the client; activate the matchcode ID; construct the matchcode data for the ID.
For case 2:
Create the corresponding index in the Data Dictionary (Transaction SE11) and in the database (function DB utility).
Additional note for ORACLE:
If the matchcode ID consists of fields of several client dependent tables, it is important that you enter the search field directly after
the client field.

SAP Note 17615 - Processing status of requisition "N", although orde

Symptom:

An externally created purchase requisition (e.g. from a PM order) has processing status "N" (not processed", although it has already been (partially or completely) converted into a purchase order.
(Transactions in environment: ME52, ME53, IW31, IW32, VA01, VA02).
One further consequence is, for example, that the requisition appears
as still open in MD04.

Cause and prerequisites

When the order is changed (e.g. quantity change for a component), function module ME_REQUISITION_EXT is processed, and this module always (wrongly) sets the processing status to "N".

Solution
See correction numbers in this note.
Advance correction possible as follows:
Function module ME_REQUISITION_EXT in Program LEBNEU01:

*- Setzen Initialwerte ------------
EBAN-BSTYP = 'B'.
EBAN-MANDT = SY-MANDT.
EBAN-ERDAT = SY-DATUM.
EBAN-ERNAM = SY-UNAME.
IF EBAN-STATU IS INITIAL. "<---- new
EBAN-STATU = 'N'.
ENDIF. "<---- new

Existing requisitions can be repaired with the following report

REPORT TKMIST10 .

TABLES: EBAN.
DATA: COUNTER LIKE SY-TABIX.

WRITE: / 'The following requisitions are changed from',
/ 'not processed to processed'.

SELECT * FROM EBAN WHERE BSMNG GT 0
AND BSAKZ EQ SPACE
AND ( STATU EQ 'N' OR STATU EQ 'A' ).
WRITE: / EBAN-BANFN, EBAN-BNFPO, EBAN-ESTKZ.
UPDATE EBAN
SET STATU = 'B'
WHERE BANFN EQ EBAN-BANFN
AND BNFPO EQ EBAN-BNFPO.
ADD 1 TO COUNTER.
ENDSELECT.

WRITE: / 'Summary:', COUNTER, 'requisitions'.

SAP Note 17612 - Info about rules

Symptom:

How to get information about Defining rules of validation ?

Cause and prerequisites

Solution
Menu path: Accounting -> Financial Accounting -> Consolidation -> Master records -> Configuration menu -> Fin.Data input -> Validations -> Checks
Cursor on input-field Check formulas
Then press PF1
Doubleclick on word "Check formula"
Now you are in the hypertext.

9.1.11

SAP Note 17593 - Runtime error CONVERT_NO_NUMBER in SAPFGSB0

Symptom:

Field TVAR-TO instead of TVAR-FROM

Contents start with '3'

Cause and prerequisites

Incorrect entries exit in table T802G (generated by a program error).

Solution
Run ABAP/4 program RMCS802G in any client (the entries will be repaired in all clients).

SAP Note 17591 - Logistics Controlling with conditions

Symptom:

Error messages and documents (for example, training material) refer to an SAP name range for conditions (1nn - 5nn of the formula or condition number) and in this case to standard conditions. There are no such standard conditions in the information system.
Key words: Conditions, formula; information system

Cause and prerequisites

Misleading expression

Solution
There are no such standard conditions, that is, the standard system does not contain any conditions. The user has to create them himself.

SAP Note 17577 - Extension coding block / BSEG

Symptom:

Table BSEG is to be extended by customer fields, the total number of fields exceeds 255. Then fields are to deleted or field lengths or types are to be changed. When activating, a database conversion is required but cannot be carried out.

Cause and prerequisites

During the database conversion, a transparent table is created, in which the document data is stored temporarily. Transparent tables, however, only allow a maximum of 255 fields.

Solution
An extension of table BSEG beyond 255 fields cannot be reversed just like that. New fields can only be added on at the end. Each table extension should be very well thought-out and not be done just for test purposes. If fields with incorrect length and incorrect type have been added on, you can proceed as follows: leave those fields as they are and add on the fields at the end with correct length and correct type under a new name arektem Typ unter neuem Namen hinten
A conversion of the table is not necessary if no documents exist. ( e.g. after a DROP and CREATE on the cluster RFBLG ). This requirement, however, is to be set in test systems or prior to going productive, if need be.

SAP Note 17563 - FB01, batch input and optical archiving

Symptom:

If optical archiving is active, the batch input for FB01 does not run through automatically because the user is asked to enter a bar-code number in a pop up.

Cause and prerequisites

For the user who created the batch input session or processes the session, the setting that the bar-code number has to be entered was made in the table for the bar-code entry of original documents.

Solution
Either change the setting for this user or create a separate user with which the sessions can be created and who must not enter the bar-code number.
If the session is being processed in the 'Process online' mode, the pop up can be exited with CANCEL without having to enter the bar-code number.

The table for entering barcodes can be changed using transaction /nOAC5.

Make the settings for the object type BKPF there.
By selecting the B-Erf field (bar-code entry), you can control that this user must enter the bar code when posting with FB01.
An entry with user ID BLANK is valid for all users that are not explicitly specified.

SAP Note 17562 - Inaccurate result during formula evaluation

Symptom:

A report displays statistical data that resulted from the average across the period. It seems that formulas that refer to such figures are not calculated correctly. There seem to be deviations of some percent from the correct value.
Key word: ReportWriter

Cause and prerequisites

When the Report Writer averages statistical data across periods, the exact result with the places behind the decimal points is used internally. When printing, however, the amount is rounded up/down according to the assigned quantity unit.
Example: the statistical key figure 'Employee' is averaged across periods but is always printed with zero places behind the decimal point. Internally, the Report Writer uses the exact value for the calculation of formulas. Therefore, there can be a discrepancy between the formula result from the printed figures and the exact figures used internally.

Solution
Allow the values behind the decimal point to be in the printed version of the report. Make sure that the maximum number of decimal places for each quantity unit is defined in quantity unit customizing. If required, change the number of decimal places to be printed for the relevant units.

Additional key words

----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_FORMULA, SGRW_AMOUNT, SGRW_DATA, SGRW_DOCU_CONS_NOTE
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

SAP Note 17560 - Allocation: Deletion report for plan alloc. CO-CCA

Symptom:

Deletion report for plan assessments/distributions in cost center accounting CO-CCA for a fiscal year within a client for ALL controlling areas!!!!!

Cause and prerequisites

Solution
If you have already run planned assessment or distribution for cost centers and cannot fully reverse it, you can delete ALL CO transaction data generated during distribution/assessment by fiscal year within a client using the RKALLOCD report. If you have any questions, contact the CO section of the SAP hotline.
Afterwards - after deleting the movement datas - you must run all the PLAN assessments, PLAN distributions again.

ATTENTION: You can't use this deletion report if profit center accouting CO-PCA or extended general ledger FI-GLX is active in your system. In this case please contact again SAP hotline.

REPORT RKALLOCD NO STANDARD PAGE HEADING.
TABLES: COSS,
COSP,
COBK,
COEJ,
T811C,
T811D.

PARAMETERS: GJAHR LIKE COSS-GJAHR.
*--------------------------------------------------------------
START-OF-SELECTION.
*--------------------------------------------------------------
DO.
SELECT * FROM COSS UP TO 1000 ROWS
WHERE VRGNG IN ('RKPU','RKPV')
AND GJAHR = GJAHR.
DELETE COSS.
ENDSELECT.
IF SY-SUBRC > 0.
EXIT.
ENDIF.
COMMIT WORK.
ENDDO.
DO.
SELECT * FROM COSP UP TO 1000 ROWS
WHERE VRGNG = 'RKPB'
AND GJAHR = GJAHR.
DELETE COSP.
ENDSELECT.
IF SY-SUBRC > 0.
EXIT.
ENDIF.
COMMIT WORK.
ENDDO.
DO.
SELECT * FROM COEJ UP TO 1000 ROWS
WHERE VRGNG IN ('RKPU','RKPV','RKPB')
AND GJAHR = GJAHR.
DELETE COEJ.
ENDSELECT.
IF SY-SUBRC > 0.
EXIT.
ENDIF.
COMMIT WORK.
ENDDO.
DO.
SELECT * FROM COBK UP TO 1000 ROWS
WHERE VRGNG IN ('RKPU','RKPV','RKPB')
AND GJAHR = GJAHR.
DELETE COBK.
ENDSELECT.
IF SY-SUBRC > 0.
EXIT.
ENDIF.
COMMIT WORK.
ENDDO.

SELECT * FROM T811D WHERE TAB = 'CCSS'
AND GJAHR = GJAHR.
IF T811C-CYCLE NE T811D-CYCLE
OR T811C-SDATE NE T811D-SDATE.
SELECT SINGLE * FROM T811C WHERE TAB = 'CCSS'
AND CYCLE = T811D-CYCLE
AND SDATE = T811D-SDATE.
ENDIF.
CHECK T811C-IPKNZ = 'P'.
DELETE T811D.
ENDSELECT.
COMMIT WORK.
SKIP.
WRITE: /2 'Trans. data for plan assessment, plan distribution '(001).
WRITE: /2 'have been deleted for fiscal year:'(002), GJAHR.
Additional key words

Allocation

SAP Note 17559 - SP01 error log: unknown print control...

Symptom:

A SAPscript print request terminates with the status "incorrect". The error log in transaction SP01 contains the following message:
OTF module: Unknown print control xxxxx should be output. xxxx stands for the name of the print control (for example, SLINE), but may also be missing.

Other terms

Print control, SP01, OTF

Reason and Prerequisites

The SAPscript print request contains the name of print controls that have not been maintained for the device type. Alternatively, the device type definition may be incorrect. The output does not normally contain errors. It is only the status of the print request that is set to "Error" or "Problem" in transaction SP01.

Solution

You can normally suppress this message by defining the print control (for example, S1150) for the device type you use for printing (for example, HPLJIIID) in spool administration (transaction SPAD). Do not change any of the SAP standard device types when you do so. Instead, copy the standard device type to the customer name space (Zxxx) (see Note 3166). Refer also to Note 11214.

The following causes may be the reason for the message, depending on the print control named in the log:

Print controls S0120, S1100, S8000, S8400, and so on:

This behavior is incorrect because these print controls are normally empty at the time the character sets are selected (that is, they do not contain any print commands) in the case of the device types in the SAP standard system. If one of these print controls is not defined, a message appears in the output log.

Print control not named (name ):

Every SAPscript spool request contains the names of the print controls used to activate all possible printer fonts (such as COURIER 120 normal) and printer barcodes (such as MBBARC). Print controls for printer fonts are named SFxxx, while those for printer barcodes are named SBPxx and SBSyy. You use the SAPscript font maintenance transaction to manage the assignments between fonts/barcodes and print controls.
The printer fonts may contain the following entry, for example:
KYOF1200 COURIER 120 _ _ SF001 SF017
This means that font COURIER 120 normal is set to portrait mode with SF001 on KYOF1200; landscape mode is set with SF017.
Only the first print control is maintained for line printers, which cannot print in landscape mode.
SNI9014 COURIER 120 _ _ SF001
The printer barcodes may contain the following entry, for example:
KYOF1000 ARTNR SBP01 SBS01
This means that print control SBP01 activates barcode ARTNR for KYOF1000, while SBS01 deactivates it.

The print request contains a page format in landscape mode (for example, DINA4 L), but was printed on a device type defined as a line printer with printer driver STN2 and does not have any print controls for printer fonts in landscape mode (since line printers cannot print in landscape mode). In this case, the name of the print control is not included in the error message. Solution: If you have to print on this printer type, define the form in portrait mode.

The print request contains barcodes that are not maintained for the device type used. In this case, as above, the name of the print control does not appear in the error message. Note 5196 lists the printer types in the SAP standard standard for which barcodes have been maintained. Solution: if you need to print the barcode, you should use a device with a device type for which the barcodes have been maintained. Otherwise, you should delete the barcode string in the application form. You can easily find out whether barcodes appear in the application form by checking the list of strings defined for it to see whether one of them has the attribute "Barcode" (for example, barcode MBBARC).

Print controls SCxxx (for example, SC125) or SLyyy (for example, SL080):

The printer driver STN2 for line printing has to set the default line spacing (LPI = Lines per inch) and the default character spacing (CPI = Characters per inch) at the beginning of each new page. This is done with the print controls SLxxx (for example, SL060 = 06.0 LPI) and SCyyy (for example, SC120 = 12.0 CPI). The values for line and character spacing are derived from the header data of the SAPscript form with which the print request was generated and the selection of their setting is optional. If the form header data contains LPI and CPI values, for which there are no corresponding SLxxx or SCyyy print controls for the device type used (for example, IBM6408), the error message specified above is displayed. In this case, the form is not printed with the correct line or character spacing.
Solution: The SAPscript form must only use "established" values or CPI and LPI values supported for the individual device type (for example, CPI and 6 LPI) in the header data.
Device types for line printers only support very specific LPI and CPI values and the corresponding print controls:
6 LPI (6 lines per inch) = print control SL060 (all device types)
8 LPI (8 lines per inch) = print control SL080 (many device types)
4 LPI (4 lines per inch) = print control SL040 (few device types)
10 LPI (10 lines per inch) = print control SL100 (few device types)
12 LPI (12 lines per inch) = print control SL120 (few device types)

10 CPI (10 lines per inch) = print control SC100 (all device types)
12 CPI (12 lines per inch) = print control SC120 (many device types)
15 CPI (15 lines per inch) = print control SC150 (some device types)
5 CPI (5 lines per inch) = print control SC050 (few device types)
6 CPI (6 lines per inch) = print control SC060 (few device types)

Other print controls:
Some printer drivers require other print controls in addition to those for the fonts/barcodes. If these have not been maintained for the device type, the error message is output. Examples include:
S<<<<, S>>>>, SLINE, SPAGE, SPORT, SLAND, SUL<<, SUL>>, SUB<<, SUB>>, SUP<<, SUP>>
The R/3 online printer installation documentation ("Printer manual") tells you which print controls are required by which printer drivers.

SAP Note 17552 - Syntax error during a cycle in special periods

Symptom:

Keyword : Allocation
Description : When performing allocations (assessment, distribution,
periodic transfer posting) in a special period, you get
the following syntax error:
Source text ALxxyyyS: "Field "SAVE-SHARE0000" is unknown"
or "ABAP/4 packed field does not contain a correct
BCD format."
Transactions : KSW5, KSU5, KSUB, KSV5, KSVB, KEU5, GA15, GA35,
GA2B, GA4B
Program names: ALxxyyyR, ALxxyyyS, SAPMKGAL

Cause and prerequisites

Program error.

Conditions under which this error occurs:
1. The start period of the allocation is a special period.
2. This special period is not the first special period in the controlling area.

Solution
1. The syntax error can be avoided by always using a period interval when performing the allocation, so that the start period is the first special period.
2. You can completely eliminate the error by installing the following change:

************************************************************************
* Program: FKGA2F50
* FORM Routine: GEN-READDATA_RC ************************************************************************

FORM GEN-READDATA_RC USING
*--------------------------------
OLDTAB
FROM
TO
NORMAL_FLAG.
*--------------------------------
:
:
*...varying for save
WL = 'VARYING SSHA FROM SAVE-SHARE$1 NEXT SAVE-SHARE$2.'.
POS = FROM - RKGA2U-FROM + 1.
IF POS < 1. <-----INSERT
POS = 1. <-----INSERT
ENDIF. <-----INSERT
REPLACE '$1' WITH POS INTO WL.
ADD 1 TO POS.
REPLACE '$2' WITH POS INTO WL.
CONDENSE WL.
PERFORM APPEND-WL.

*...move
WL = 'ADD $1 TO SSHA.'.
:
:
:

************************************************************************ * Programm: FKGA2F50
* FORM-Routine: GEN-READ_RC
************************************************************************

*-------------------------------
form gen-read_rc using
*-------------------------------
index.
*-------------------------------

:
:
*.......generate oldkeys move
if index > 1.
clear old.
move space to o.
o-field = datas-field.
read table o.
if sy-subrc = 0.
old = true.
perform a_c using 0 'IF DBTYPE = DT-OLDKEYS.' 0 2 0.
if rkga2u-anzbp = nil.
*.............only normal
perform gen-readdata_rc using oldtab
rkga2u-from
rkga2u-to
'X'.
else.
*.............at first normal
if rkga2u-from <= rkga2u-anzbp. <<<< perform gen-readdata_rc using oldtab
rkga2u-from
rkga2u-anzbp
'X'.
xper_from = rkga2u-anzbp + 1. <<<< else. <<<< xper_from = rkga2u-from. <<<< endif. <<<<*.............then extra periods
* xper_from = rkga2u-anzbp + 1. <<<< perform gen-readdata_rc using oldtab
xper_from
rkga2u-to
space.
endif.
perform a_c using 0 'ELSE. ' -2 2 0.
endif.
endif.
*.......generate standard move
if rkga2u-anzbp = nil.
*.........only normal
perform gen-readdata_rc using space
rkga2u-from
rkga2u-to
'X'.
else.
*.........at first normal
if rkga2u-from <= rkga2u-anzbp. <<<<<< perform gen-readdata_rc using space
rkga2u-from
rkga2u-anzbp
'X'.
xper_from = rkga2u-anzbp + 1. <<<<<< else. <<<<<< xper_from = rkga2u-from. <<<<<< endif. <<<<<<*.........then extra periods
* xper_from = rkga2u-anzbp + 1. <<<<<< perform gen-readdata_rc using space
xper_from
rkga2u-to
space.
endif.

SAP Note 17550 - Customer master: update termination

Symptom:

Update termination in the customer master.

Cause and prerequisites

Inactive database tables.

Solution
When updating customer master records, terminations can occur if one of the database tables is inactive (DDIC). This status is generally caused by DDIC manipulations (for example, field length changes) and can only be corrected by converting or activating the table in question.

SAP Note 17548 - AA328 Posting yr.earlier than capitalization yr.

Symptom:

The posting date of a purchasing document which contains an item assigned to an asset is earlier than capitalization date of the asset. When posting the purchasing document (purchase order, PReq), you get the messsage:
AA328 Posting yr.earlier than capitalization yr.

Reason and Prerequisites

The posting year must not be earlier than the the capitalization year.

Solution
Either set the posting date of the purchasing document to a date after the capitalization date or set the capitalization date in the asset master record to an earlier date.

SAP Note 17539 - Runtime error when deleting transaction data

Symptom:

You delete transaction data using Report SAPF020. Runtime error "CONNE_IMPORT_WRONG_STRUCTURE" occurs.

Other terms

Program "SAPF020", Form "READ_RFDT",
Exception "CX_SY_IMPORT_MISMATCH_ERROR",
Error when importing object "T_BKPF".

Reason and Prerequisites

With the new Release, the structure of held documents in the index file "RFDT" has been changed and they have not yet been appropriately converted.

Solution
Before holding new documents or processing held documents, the documents previously held have to be converted.

Conversion of the held documents is carried out by Report "RFTMPBLU". In case of a large data volume (more than several hundred held documents), the report should be scheduled as batch job.

In general, conversion of held documents is supported for documents entered in Release 1.3A or later.

A conversion of older held documents is impossible. You have to delete those documents using Report "RFTMPBLD". Afterwards, run Report "RFTMPBLU" to activate version management for held documents.

If only small data sets need to be converted or deleted, you can carry out the action in another window and continue the current processing after finishing the action.

SAP Note 17537 - ABAP/4 runtime error SNAP_NO_NEW_ENTRY

Symptom:

The short dump to be displayed contains the message "SNAP_NO_NEW_ENTRY" but no other data.

Reason and Prerequisites

This error means that the short dump could not be found in the database.
The error may be caused by the following:
- Table SNAP is full,
- short dump was not written due to database problems,
- short dump has already been solved by reorganization.

Solution
When the SNAP Table is full: Reorganize the table e.g. via Transaction ST22->Go to->Reorganize. Please also refer to Note 16083. This may lead to other errors of this kind since not all dumps e.g. from SM21 can be displayed.

In case of database problems, the errors should no longer occur with new short dumps after correcting the database error. Here, other errors of this kind may occur in SM21 as well.

SAP Note 17520 - ISHCM Receiver data is shifted in the batch session

Symptom:

Data is not processed correctly for data transfer with the SAP R/3 Communications Module (also known by the name HCM Transceiver). The created batch input sessions hold the data somewhat shifted. It would appear that some offset is incorrect. The original file (transfer file) contains the correct data in the correct format.

The receiver program (RNCGET00, RNCGET01, RNCGET02, ...) may work through the transfer file despite this. However, you may then find no receiver logs appear in the corresponding log file NCI0. The program does not recognize the error.

Cause and prerequisites

There are several possibilities:

1. The data is not actually correct: check whether the correct message format has been stored for the partner in IS-H, and whether the data corresponds exactly to this format.

2. The ISHCM rule of thumb "one message equals one file line" is not taken into account in the file. The only exception to this rule: if the line is longer than 4096 (4K) characters, it is terminated after this number of characters.

3. An incorrect line end in the transfer file (hexadecimal '0d' + '0a' mandatory). Solution

1. Check whether the correct message format is stored for this partner in IS-H, and whether the data corresponds exactly to this format. Correct if necessary.

2. Check whether several messages are in one line, or whether one message is divided over several lines. This is only allowed if the message contains more than 4096 (4K) characters. In this case, the line end must be inserted after exactly 4096 characters (hexadecimal '0d' + '0a'; see 3).

(possibly link with 'more' or 'pg'). The file is displayed character by character, both as characters (c) and as hexadecimal codes (x).
You can analyse some of these points using program RNCCHK02. The results of this analysis can possibly play a decisive role in detecting the type and location of the error.

Additional key words

HCM, incoming, data transfer, transceiver, RNCGET*, data record, offset, consultation

SAP Note 17498 - Display variant for billing due list

Symptom:

In Customizing, you can create a display variant for the billing due list (VF04) with the fields 'Distribution channel' VTWEG and 'Division' SPART. These values are not filled in, however.

Cause and prerequisites

The fields 'Distribution channel' and 'Division' are mistakenly proposed in the field list for Customizing the billing due work list. This is because they are not entered in the corresponding table VKDFS (billing index).

Solution
The only solution is by means of a modification. Contact your consultant for this. Also refer to the attached Note 170183.
Attention: This impairs the performance !!!
A possible solution (for the division) would be to:
Attention: In release 3.0E there has been some enlargements in function
group SAPLV05H, so that you should take care about that.

1. Create Include ZZSPARTE

Attributes:
Type 'I' Include program
Status
Application 'V' Sales/distribution

Source text: ***INCLUDE ZZSPARTE .

FORM SPARTE_LESEN.

>>>>>>> These lines should be used only until release 3.0D
TABLES: VBAK,
LIPS,
VBRK.
>>>>>>>

>>>>>>> From release 3.0E is only valid this line
TABLES: VBRK.
>>>>>>>

IF LVKDFI-VBTYP CA VBTYP_VERK.
SELECT SINGLE * FROM VBAK WHERE VBELN = LVKDFI-VBELN.
IF SY-SUBRC = 0.
LVKDFI-SPART = VBAK-SPART.
MODIFY LVKDFI.
ENDIF.
ENDIF.

IF LVKDFI-VBTYP CA VBTYP_LIEF.
SELECT * FROM LIPS WHERE VBELN = LVKDFI-VBELN.
EXIT.
ENDSELECT.
IF SY-SUBRC = 0.
SELECT SINGLE * FROM VBAK WHERE VBELN = LIPS-VGBEL.
IF SY-SUBRC = 0.
LVKDFI-SPART = VBAK-SPART.
MODIFY LVKDFI.
ENDIF.
MODIFY LVKDFI.
ENDIF.
ENDIF.

IF LVKDFI-VBTYP CA VBTYP_FAKT.
SELECT SINGLE * FROM VBRK WHERE VBELN = LIPS-VGBEL.
IF SY-SUBRC = 0.
LVKDFI-SPART = VBRK-SPART.
MODIFY LVKDFI.
ENDIF.
MODIFY LVKDFI.
ENDIF.

ENDFORM.
2. Include Include ZZSPARTE in Report LV05HU01: LV05HU01:

>>>>>>>> This line should be inserted only until release 3.0D
INCLUDE RVVBTYP. <--- insert
>>>>>>>>

FUNCTION RV_READ_INVOICE_INDEX.
.
.
PERFORM VKDFS_INIT.
PERFORM LESEN_VKDFI_VKDFS_01.

LOOP AT LVKDFI.

PERFORM BERECHTIGUNG_PRUEFEN USING LVKDFI-FKART.
IF OK = ' '.
DELETE LVKDFI.
BERECHTIGUNGEN_FEHLEN = 'X'.
CHECK 1 = 2. <--- insert
ELSE.
PERFORM BERECHTIGUNG_VKORG_PRUEFEN USING LVKDFI-VKORG.
IF OK = ' '.
DELETE LVKDFI.
BERECHTIGUNGEN_FEHLEN = 'X'.
CHECK 1 = 2. <--- insert
ENDIF.
ENDIF

PERFORM SPARTE_LESEN. <--- insert

ENDLOOP.
.
.
>>>>>>> This line should be inserted this way until release 3.0D
ENDFUNCTION.

INCLUDE ZZSPARTE. <--- insert
>>>>>>>

>>>>>>> From release 3.0E the line should be inserted this way
ENDFUNCTION.

*---------------------------------------------------------------------*
* FORM AUSDUENNEN_XVKDFS *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
FORM AUSDUENNEN_XVKDFS.
.
.
.
ENDFORM.

INCLUDE ZZSPARTE. <--- insert
>>>>>>>

SAP Note 17491 - CO reports: elimination of internal business volume

Symptom:

1. As of Release 3.0:
1.a) General way of processing elimination of internal business volume with the characteristic BUEKZ when you use the variation:
The internal business volume is eliminated making use of the characteristic BUEKZ or is controlled explicitly in a line or column. The internal business volume is displayed for all subareas of the cost center hierarchy from the point of view of the upper node, that is, all allocations for the internal business volume which flowed within the group entered on the selection screen are explained for a subarea in a report.

1.b) Elimination of internal business volume in report group 1SBU:
4 reports are contained in report group 1SBU. The reports 1SBU-003 (Cost centers: Gross/net) and 1SBU-004 (Int.Bus. volume in lines) use the characteristic BUEKZ (Internal Business Volume Indicator) for the elimination of the internal business volume. As a result, the internal business volumes in these reports are only displayed referring to the upper node when you use the variation. On the lower nodes of variation or on the individual cost centers, other values than expected are therefore displayed.

2. Releases 2.1 and 2.2:
Simultaneous use of variation of the selection and the elimination of internal business volume in a Report Writer report: The internal business volume is displayed for all subareas of the cost center hierarchy from the point of view of the upper node, that is, all allocations for the internal business volume which flowed within the group entered on the selection screen are explained for a subarea in a report.

3. Releases 2.1 and 2.2:
Internal business volume which resulted from allocation to order and subsequent settlement of the order back to the area is not recognized.

Additional key words

BUEKZ elimination of internal business volume, internal business volume, variation, GR55, 1SBU. ----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_AMOUNT, SGRW_RC_STRUCTURE, SGRW_DATA, SGRW_IBV, SGRW_DOCU_CONS_NOTE
SGRW_OM

Cause and prerequisites

Cause:
There is no other technical solution available at the moment.

Preconditions:
This affects reports which use the Internal Business Volume Indicator characteristic (BUEKZ).
This does not affect reports with which the indicator 'Eliminate internal business volume' in the general selections is used for the elimination of internal business volume in the Report Painter.
Nor does this affect Report Writer reports with which the indicator 'Eliminate internal business volume' in the report definition causes the elimination of the internal business volume.

Solution

re 1.a)
If this is not desired, you can use the indicator 'Eliminate internal business volume' in the general selections instead; however, then you cannot display the internal business volume in the report.

re 1.b)
Change the definition of the reports 1SBU-003 (Cost centers: Gross/net) and 1SBU-004 (Int.Bus. volume in lines). In the definition of the general selections, set the variation parameter for the characteristic 'Cost center' to 'Do not explode'. Make this change in client 000 and afterwards copy the report group 1SBU from the source client 000 to the current client.

re 2.)
Instead of the variation of the selection, use varying, if indispensable. Nonetheless, this takes a lot more CPU time since the reports are created for all subareas independently from each other. Enhanced functions of the variation of selection are only available as of Release 3.0.

re 3.)
This is contained in the standard system as of Release 3.0. You can implement an advance correction in Release 2.2. See Note 33161.

SAP Note 17486 - ORA997 "Illegal Use of Long Datatype"

Symptom:

Access of a transparent database table terminates with ORACLE erro message ORA997: "Illegal Use of Long Datatype"

Cause and prerequisites

Attempt was made to query a field in a WHERE condition that has been defined in the database as LONG (RAW). This is not possible for fields with this data type, however.

Solution
The corresponding application program must be reprogrammed.

SAP Note 17483 - Business area for inventory postings

Symptom:

The inventory posting is assigned to a wrong business area during goods movements.

Cause and prerequisites

Before Release 3.0: Table T134G is maintained incorrectly.
As of Release 3.0: Table T134H is maintained incorrectly.

Solution
Please maintain table T134G (or T134H) - via the corresponding Customizing transaction. The business area you have to enter in this table for plant (or valuation area) and division of the material is transferred by the system into inventory posting. (transaction/event key BSX).
The same applies especially to stock transfers and transfer postings, regardless of whether they are executed with or without stock transport order. The business area for the isssuing material-plant (or valuation area) is set in inventory posting for the issuing stock and in inventory posting for the receiving stock, the business area of the receiving material-plant (or valuation area) is set.

SAP Note 17481 - RFBIBL00 and special G/L transactions

`Symptom:

Which special G/L transactions are supported by RFBIBL00 (document transfer of the R/3 System).

Other terms

UMSKZ, NEWUM, down payment, bill of exchange, payment advice note, special G/L transaction

Reason and Prerequisites

Solution

1. Direct input

The following special G/L transactions are not supported:

Prior to Release 4.0B: all except statistical postings (other special G/L transaction)

As of Release 4.0B: bills of exchange, noted items (down payment requests, payment requests)

2. Batch input and Call Transaction

As of Release 2. 2A, all special G/L transactions, except for bills of exchange and down payments, are supported. This also applies to Release 3.0*.

As of Release 4. 0C, down payments are also supported.

Prior to Release 2. 2A, special G/L accounts are not supported.

SAP Note 17479 - TemSe message: Can't convert "data" to "text type"

Symptom:

The following message appears in the TemSe administration:
Can't convert "data" to "text type"

Cause and prerequisites

The selected file with the "data" format cannot be displayed in the TemSe administration.

Solution
No solution.

The problem occurs especially when customers with Release 2.2A and later write the data carrier into the TemSe instead of the file system. These are stored in the "data" format.
For Release 3.0, the function "Display DME contents" in the FDTA transaction will be available to display or print DME data from the TemSe.
There is no function for displaying or printing generated TemSe files in Release 2.2A. In this case, you only have the option of carrying out a download and processing the generated file further by means of the operating system used, for example:
MS-DOS: type or print
UniX : cat or lp

SAP Note 17464 - V1331 Internal error. Item ... missing.

Symptom:

If a sales document is to be changed or displayed, the above error message appears. VA02 or VA03.
Caution: If the error occurs during delivery processing, Note 21397
applies.

Cause and prerequisites

An item has been deleted. The schedule line for the item, however, still exists.

Solution
The following program enables you to display the document again:

REPORT ZZVBEP .
* Document number with leading zeroes.
PARAMETERS: NUMBER LIKE VBAK-VBELN.
TABLES: VBEP, VBUP.

SELECT * FROM VBEP WHERE VBELN = NUMBER.
SELECT SINGLE * FROM VBUP WHERE VBELN = VBEP-VBELN
AND POSNR = VBEP-POSNR.
IF SY-SUBRC NE 0.
DELETE VBEP.
WRITE:/ VBEP.
ENDIF.
ENDSELECT.

If the item has reduced requirements, the requirements must then be recreated using Program SDRQCR21. The program cannot be run when the system is online.
Note 8376 may remove the cause in 2.1.

SAP Note 17457 - Transfer posting mat. to material with same sender

Symptom:

During a transfer posting material to material with movement type 309, you need to enter the receiving material (receiver) only once in the list entry screen if several materials (sender) are to be transferred to this material.
If, however, you want to transfer one sender to several receivers, there is no option for entering the sender only once.

Cause and prerequisites

If you enter a goods movement, the receiver is dealt with as an account assignment (for example, a cost center, order, ...). List entries for the account assignment are defined.
Entries for which one material is moved for several account assignments, on the other hand, are not defined.

Solution
1. With movement type 310 you can reverse transfer postings of movement type 309. Since the meaning of sender and receiver is reversed for this movement type, you can enter several receivers for one sender with movement type 310. Here, you have to keep in mind, however, that the sender is positioned as account assignment. As a result, the transfer posting is valuated in this case according to the valuation control of the receiver. Possible costs, price differences, or changes of the valuation price are assigned to the sender.
2. If you cannot use the option described under 1., enter the transfer postings separately for each item by entering sender and receiver in each case.

SAP Note 17449 - Payment program error FZ511: breakdown not possible

Symptom:

The log of the payment program contains error FZ511:
A breakdown of the line items on the payment forms was not possible

Cause and prerequisites

Example:
The payment program is started with a method of payment for bank transfers. 5 items @ $100.00 are to be paid. In addition, a credit memo of $300.00 is to be cleared.
2 items per form were specified in Customizing for the payment program; if the form overflows, an additional form is to be created.
Because only two items can be used per form, and only bank transfers are created, the credit memo cannot be cleared.
Error message FZ511 is issued.

Solution
First verify that the correct number of items per form was specified in Customizing for the payment program.

Then perform step a) and b) below when necessary (see below):

a) In Customizing for the payment program, select the setting "Payment advice upon form overflow" instead of "Additional forms". This will cause the items in the above example to be grouped together to a bank transfer of $200.00 The line item information is output on a separate payment advice form.

b) Perform an internal transfer posting by grouping the 5 items @ $100.00 together in one bank transfer of $500.00.

SAP Note 17410 - Posting credit memos; payments and dunning

Symptom:

Payment terms for credit memos not functioning as expected:

1. When credit memos are posted, the payment terms are not taken from the customer or vendor master record as is the case with invoices.

Cause and prerequisites

Works as designed.

1. Credit memos are either referenced to an invoice or not. A credit memo with an invoice reference (field BSEG-REBZG) has exactly the same payment terms as the invoice.

Solution
Credit memos that have a reference to an invoice should be posted using this reference (when processing in the background, you must fill field BSEG-REBZG accordingly).
Credit memos that refer to an inoice or have had other terms explicitly specified for them should be posted as credit memos with a fixed value date (with batch input processing, put a "V" next to the payment term in field BSEG-REBZG).

Additional key words

F110, payment programm, SAPF110V, SAPF110S, F150, dunning program, SAPF150V, due date

SAP Note 17406 - Text maintenance causes unjustified warning popup

Symptom:

Text maintenance causes an unjustified warning popup to be issued:
Text elem. were changed. Save
the changes?
even when you were working only in display mode.

Cause and prerequisites

The following change was implemented with corr. no. B20K010603 / transport no. B20K015602:
All text elements are assigned a length. Internal text symbols could previously be saved without any text (that is, only a text number). These texts were saved with an internal length 0, which caused difficulties in later processing (e.g. termination due to ASSIGN with length 0). For this reason, a default length of 1 was assumed in such cases (text symbol with assigned number but without text). Due to this change, which is invisible for the user, the system reacts correctly by displaying the change popup.
Change with correction B20K034289:
According to correction B20K034289, a change popup will not be sent after a pure length- correction. The confirmation message:
"Text elements for Program ... in Language . accepted"
will continue to be issued even after this correction.
A further reason for issuing the change Popup is solved with
correcttion B20K035301 - Inserting a Text symbol with Text=Space without default length definiton 1 from the Inconsistency cleanup program.

Solution
Confirm the query with "Yes". This will change the text symbols with length 0 to length 1 (one-time action).

SAP Note 17399 - MB1B ME_UPDATE_GOODS_RECEIPT termination AME803

Symptom:

When cancelling a goods issue for a stock transport scheduling agreement, the described termination occurs in ME_UPDATE_GOODS_RECEIPT.

Cause and prerequisites

The issued quantity (EKET-WAMNG) in a scheduling agreement was 50 ST below the quantity specified in the corresponding purchase order history record. The reason for this discrepancy is not clear. The scheduling agreement for this specific case was generated in a planning run.

Solution
You can correct the issued quantity in the scheduling agreement with a report. The report can be as follows:

REPORT TKTEST10.

TABLES: EKET.

SELECT SINGLE * FROM EKET WHERE EBELN EQ '..........' "<- number
AND EBELP EQ '.....' "<- item
AND ETENR EQ '....'. "<- schedule line

IF SY-SUBRC EQ 0.
WRITE: / EKET-EBELN, EKET-EBELP, EKET-ETENR, EKET-WAMNG.
EKET-WAMNG = EKET-WAMNG + 50.
WRITE: / EKET-EBELN, EKET-EBELP, EKET-ETENR, EKET-WAMNG.
UPDATE EKET.
ENDIF.

SAP Note 17388 - ME21 ME31 'Please enter net price'

Symptom:

During creation of a contract, the error message "Please enter net price" (error message ME 083 or 06 215) or 'Net price must be greater
than 0' (error message 06218) 'is issued for each item,
although a price was in fact entered. The error can also occur during the creation of POs. The message can also appear during the changing of contracts or POs (Transactions: ME21, ME22, ME31, ME32).

Cause and prerequisites

Missing authorization or wrong calculation schema (pricing procedure) assigned.

Solution

1. Please check whether the user has the authorization V_KONH_VKS. It was previously missing in the standard profile for Purchasing, M_EINK_ALL. The authorization is only important with regard to contracts.

3. The error can also be due to switching to a new calculation schema. If the new schema and the old one use different condition types for the price, and the conditions for a material were copied from the last PO, the price disappears because the old condition type is now no longer defined.

4. A further possible reason for the error may is that an access sequence has been assigned to condition type PBXX (price to be entered manually). If such an assignment exists, it should be cancelled.

5. Check whether the user exits LMEKO0001 (INCLUDE ZXM06U14) or LEMKO002 (INCLUDE ZXM06U15) cause the error (Note 80338:

a) the user exits are active, but the corresponding Includes are empty

b) the user exits return export structure E_KOMK or E_KOMP empty; the input structure I_KOMK or I_KOMP must be assigned at the beginning of the export structure (E_KOM? = I_KOM?).

Additional key words

ME47

SAP Note 17387 - YES, NO, CANCEL buttons for batch input SAPLSPO1

Symptom:

During the batch input of program SAPLSPO1, screens 100 or 300, the YES, NO, CANCEL buttons are not activated. This problem occurs in all programs with similar screens.

Cause and prerequisites

This was programmed this way in batch input.

Solution
Complete the batch input as follows:
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPLSPO1'.
BDC_TAB-DYNPRO = '0100'.
BDC_TAB-DYNBEGIN = 'X'.
BDC_TAB-FNAM = 'BDC_CURSOR'.
BDC_TAB-FVAL = 'SPOP-OPTION1'. 1 = JA, 2 = NEIN, 3 = ABBRUCH