SAP Note 23863 - MEMORY MANAGEMENT 3.0

Symptom:

Storage problems.

Cause and prerequisites

Insufficient profile settings.

Solution
In Release 3.0 there are 3 storage areas which must be set by profile parameters so that the respective applications run with optimal performance. In addition to the classical roll area, 3.0 also contains the EM storage area (Extended memory area), which accesses the 'shared memory' resources, as well as the 'heap' memory which uses operating system storage areas (malloc).

Relevant parameters:

ROLL:
ztta/roll_area Size of the entire roll / internal mode
ztta/roll_first Size of the 1st roll area segment
(from 3.0C)
rdisp/ROLL_SHM Roll buffer in 8KB blocks

EM:
ztta/roll_extension Quota of one user in EM (bytes)
em/blocksize_KB EM Block size in KB, 1024 to n
em/initial_size_MB Created on the install date
em/max_size_MB ... NN
em/address_space_MB Reserved address space (only NT)

HEAP:
abap/heaplimit Limit in the heap (bytes), beyond which the WP is restarted.
Storage is then available again
for other processes.
abap/heap_area_dia Heap / user online
abap/heap_area_nondia Heap / user in background processes + update
abap/heap_area_total Sum of all heap storage / Application servers
Restrictions and special features of the storage classes:
The EM resource in shared memory is limited to approx. 1 GB per UNIX machine. The total of all processes must not exceed this quantity. In contrast to the heap, however, a user with a WP in EM can move to another one. This is not possible for the process-specific heap memory.

This is a temporary recommendation with the request to update the information here:
Smaller transactions should take their storage requirement purely from the ROLL. It is therefore recommended that you use a roll of 1 MB (standard). The entire roll area can be set to 16MB - it is only required if the EM area is used up.
The EM area replaces the old SAP paging. The larger EM/initial_size_MB is, the more SWAP must be configured on a machine. 1 GB of memory is ideal.
HEAP:
Background, update and spool processes take their memory from the ROLL and HEAP. Only if these areas are exhausted, is the remaining EM used.
Important for the installation: The operating system must generally be recompiled so that sbrk (malloc) is not limited to a few MB per process. As the amount of storage required for background processing can be very considerable, the value must be set correspondingly. The swap space on the machines should be increased.

Note: The 3.0 MM is released with 3.0A.
With the report RSMEMORY, the apportionment of individual areas can be checked in the current system. Display according to users is available under the menu option Goto ..
Moreover, you can use System -> Utilities -> Resource usage to check the storage usage of individual transactions.
From Release 3.0C, you can use transactions RZ03 and ST02 to display the occupancy level of the storage types. This display forms the basis of tuning measures.
RZ03 -> Additional views > Storage management: Shows the current usage of all R/3 instances.
ST02 shows the current usage and history of an R/3 instance.

SAP Note 23862 - Line items: Double items / 2nd search incorrect

Symptom:

1. Items are displayed twice in the line item display in the following cases:

• The line layout is a special variant

• The line layout was changed (the initial transaction was with a different line layout).

2. Contents of special fields are no longer displayed (for example, after sorting) if the line layout variant popup was not processed beforehand.
3. During the second search in the list by placing the cursor, the system does not search for the value you select with the cursor but searches for the corresponding value in the first line of the list.
(This error especially occurs in 22F and 30A.)
Key words: RFEPOS00 FBL1 FBL3 FBL5

Cause and prerequisites

Error.

Solution
Corrected for 2.2F/3.0A.
Preliminary correction as follows:
1. /NSE38 - RFPOSFZ0


FORM ZVZEILE_SETZEN.
...
SPOSTAB = POSTAB. <-- insert
IF POSTAB IS INITIAL. <-- delete
READ TABLE POSTAB INDEX 1.
SF-TABIX = 1.
ELSE. <-- delete
DESCRIBE TABLE POSTAB LINES SF-TABIX. <-- delete
ENDIF. <-- delete
...
POSTAB = SPOSTAB. <-- insert
ZVZEILE = ZEILE.
ENDFORM.
...

2. /NSE38 - RFPOSFS0

FORM SONDERVARIANTE_ANALYSIEREN.
PERFORM NACHLESEN_VARNR. <-- insert
CLEAR: CSF-XBKPF, CSF-XBSEG, CSF-XBSEC, CSF-XBSED, CSF-XPAYR.

SAP Note 23860 - Informix: Access rights on SAP Informix tables

Symptom:

Some SAP/Informix tables have public access.

Cause and prerequisites

When the R/3-System is delivered, the rights on the database tables are assigned in such a way that all permissions were deleted on the R/3 Informix tables (except for the table "SAPUSER" from 2.1J/2.2D). On the other hand, new tables created by the R/3-System are given public access as a default by Informix.

Solution
The system is currently set up in such a way that only the sapr3 user as owner of the database, as well as the adm user, can access the informix database. The database is locked to all other users, as they have no CONNECT privileges.
If the adm user's rights to these newly created tables are also removed, these rights at present can only be deleted manually by the user "sapr3": $ su - adm
$ su sapr3
$ dbaccess << !
REVOKE ALL ON FROM PUBLIC;
As of SAP Release 3.0, for all tables created via the R/3 Dictionary, a "REVOKE ALL ..." is executed after every "CREATE TABLE ...".

SAP Note 23858 - E: Transaction SM53 is unknown

Symptom:

When you start the transaction to open a remote connection to SAP using the menu path 'System -> Services -> X.25 Service' the following error message appears:
E: Transaction SM53 is unknown.

Cause and prerequisites

Transaction code SM53 not delivered.

Solution
The ABAP/4 'SAPSERVR' with the transaction SA38 can be started as an alternative way of opening a remote connection to SAP.

SAP Note 23851 - SAPF040: Problem with ROLLBACK segments

Symptom:

ROLLBACK segments overflow during deletion of large datasets.
Key words: SAPF040 SAPF040D F040

Cause and prerequisites

a) Offline redo logs overflow (database archiving)
b) Online redo logs overflow

Solution

If case a) has occurred, either

• Split up the documents to reduce the quantity for archiving in a single run

• and/or deactivate the writing of offline redo logs

• and/or provide more disk space for the offline redo logs
  

If case b) has occurred, either

• Provide more disk space for the online redo logs (recommended)

• Reduce the COMMIT counter for deletion
  

To implement the latter:

Release 2.1 or 2.2, change program SAPF040D:
...
*
* Systemvariablen
*
"DATA: MAX_DEL TYPE I VALUE 5000, "<<<---- delete
"DATA: MAX_DEL TYPE I VALUE 1000, "<<<---- insert
X_CLUSTER TYPE C VALUE 'X'. "Löschen des Belegs im Cluster
*
INCLUDE F040TOP .
*
...

Starting in Release 3.0A: The COMMIT counter can be maintained in Customizing for archiving object "FI_DOCUMNT" using transaction SAR3.

SAP Note 23850 - Payment history not updated

Symptom:

Payment history is not updated.
Key words: SAPFF007, KNB4, FD11, FD32

Solution

The payment history is updated if

• the update is activated for the customer (select KNB1-XZVER)

• the posting keys is selected as relevant for payment (OB41)

If the update was not carried out, there is no program for the subsequent creation of the data.

SAP Note 23845 - MMIM: Single picking list for reservations

Symptom:

A single picking list for reservations (transaction TL20 does not exist in the R/2 System.

Cause and prerequisites

Such a list has not been programmed yet.

Solution
Currently not available.

SAPNote 23841 - Picking reqst/ext.procsd activity:non-existent item

Symptom:

1. The picking request refers via schedule - procurement to an item in a purchase requisition which does not exist.

2. A released and already deleted externally processed activity refers with a temporary number (e.g. # 1) to a purchase requisition that does not exist.

Cause and prerequisites

Transfer of export parameters, although these should have been cleared.

Solution
The repair report ZREPAFVC mentioned below may be used to repair incorrect externally processed operations. Run this report in test mode in order to establish the correctness of the selected orders. You can then run it normally to implement the repairs.
In addition, the following source code corrections must also be implemented.

Additional key words

CO01, CO40, External processing, CO472

SAP Note 23840 - Translate retained earnings w. hist.curr.

Symptom:

How is the currency translation method to be set up if the retained earnings are to be translated using the historical currency ?

Cause and prerequisites

Missing documentation

Solution
Procedure A -----------

This procedure can ONLY be applied if the FS item profit/loss carried forward in the current year in local currency (LC) AND reporting currency (RC) states exactly the correct values of the retained earnings of the previous year. If one of the two conditions are not met, procedure B must be applied.

1. Changes in equity table (T871)
Item Year LC Ex.rate RC
--------------------------------------
Retained earn. 1994 1000 2.0 2000
1995 1000 1.5 1500

Consequently, the balance carried forward item in the current year has the value
1000- in LC and in 2000- in RC.

2. Translation method contains the following translation entries
(maintenance by means of transaction GC31, storage in T884):
Item LC Transl. 1995 RC
---------------------------------------------------------------------
BALANCE SHEET
Fixed assets 2000 S-rate = 1.5 3000
Retained earnings 2000- T871 3500- (Sel.item BG)
Curr.transl.diff. 0 500+

INCOME STATEMENT
Sales 10000- D rate = 1.8 18000-
Expenses 9000 D rate = 1.8 16200+
Curr.trans.diff P+L 0 300+
-------------------------------------------------
Net income for yr 1000- 1500- (Totals item)
Bal. carried forward 1000- no new transl. 2000-
Retained earnings 2000+ S rate = 1.5 3000 (Sel.item ERG)
500 (from bal.)

A translation set with precisely that carry-forward item exists. It is not translated again. The currency translation difference is posted to the FS item ERG. This then automatically has its correct historical value which, if at all, deviates from the value of the BG item on the balance sheet due to roundoff.

3. Roundings between balance sheet and P+L
Example: Amortization in the P+L equals the total of the amortizations on the balance sheet. Differential item in the balance sheet or P+L.

4. Rounding balance sheet
Summary of all balance sheet items in a set and posting of the difference to a rounding difference item on the balance sheet.

5. Rounding P+L
Summary of all P&L account items in a set and posting of the difference to a rounding difference item in the P+L. This can, but must not lie "above" the annual net profit.


Procedure B -----------

Procedure is ALWAYS applicable. In particular, it is needed when no historical values for the profit carried forward are available yet due to a first consolidation in FI-LC.

1. Changes in equity table (T871)
- similar to procedure A

2. The translation method contains the following translation entries
(maintenance by means of transaction GC31, storage in T884):
Item LC Transl. 1995 RC
---------------------------------------------------------------------
BALANCE SHEET
Fixed assets 2000 S rate = 1.5 3000
Retained earnings 2000- T871 3500- (Sel. item BG)
Curr.transl.diff. 0 500+

INCOME STATEMENT
Sales 10000- D rate = 1.8 18000-
Expenses 9000 D rate = 1.8 16200+
Curr.trans.diff P+L 0 300+
-------------------------------------------------
Net income for yr 1000- 1500- (Totals item)
Bla. carried forward 1000- S-Kurs = 1.5 1500-
Retained earnings 2000+ S-Kurs = 1.5 3000 (Sel.item ERG)

Contrary to procedure A, the balance carried forward is translated by means of the spot exchange rate.

3. Roundings between balance sheet and P+L
- similar to procedure A

4. Rounding balance sheet
- similar to procedure A

5. Rounding P+L
- similar to procedure A

6. Rounding retained earnings:
The retained earnings on the balance sheet (BG) and in the P+L (ERG) must always correspond in local and reporting currency. At first, this is not the case in the described example, that is, after processing the translation entries of step 2.

By means of a rounding, the difference between both FS items is added to the retained earnings in the P+L. A set is created for this, which includes both FS items and supports the FS item ERG as differential item.

7. Rounding P+L for correct profit carried forward
After processing the translation entries (step 2), the FS item Profit carried forward still displays an incorrect value, namely 1500- instead of historically correct 2000- in RC.

On the other hand, a balance across all P+L account items was created by means of rounding off the retained earnings in step 6.

Both aspects are now cleared by repeating the rounding of the P+L (all P+L and appropriations of net income items including ERG) with the profit carried forward (!) as differential item.

Rounding differences of 500 will now appear in the audit trail for translation; however, these are not roundings in the actual sense but a temporary measure.

SAP Note 23835 - Buffering RV_BELEG / Number assignment in SD

Symptom:

RV_BELEG Number assignment Buffering

SD is serialized with number range object RV_BELEG:

CAUTION: On Okt/8th/97, an important component was added to this note. If you have already implemented the note, note the following addition:
To ensure that there are no gaps in invoice lists, change Include LV60AU11 as described below.

Cause and prerequisites

The number range object RV_BELEG is not buffered (as delivered) and, normally, should not be buffered for a billing document, or, in Italy, for the delivery note (for completeness reasons).

Solution

For releases up to 3.0: apply Note 23698 and then proceed as follows:

Buffer object 'RV_BELEG' but not for the number intervals of the
billing document and delivery note.

Call Transaction SNRO -> Object name 'RV_BELEG' -> Change -> Edit -> Set-up buffering -> Main memory
Number of numbers in buffer 100.

Development requests 26219 and 26233 were submitted in 1996 to solve the problem.
As of Release 4.5A, in the delivery for delivery documents you can separately deactivate the buffering of the number range object RV_BELEG. To do this in Customizing maintain the corresponding parameter under 'Global shipping settings' (Table TVSHP).
For Releases earlier than 4.5A, in the delivery and for the other sales document categories if necessary transfer the following modifications into your system:

1. Prevent buffering for the billing document

------------------------------------------ Include LV60AU02:
----------------
...
...
...
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
NR_RANGE_NR = DA_NUMKI
OBJECT = 'RV_BELEG'
IGNORE_BUFFER = 'X' "<--- MOD
IMPORTING
NUMBER = XVBRK-VBELN.
...
...
...

2. Prevent buffering for billing documents (invoice lists)

----------------------------------------
Include LV60AU11:
---------------------------------------
...
... CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
NR_RANGE_NR = DA_NUMKI
OBJECT = 'RV_BELEG'
IGNORE_BUFFER = 'X' "<--- MOD
IMPORTING
NUMBER = XVBRK-VBELN.

...
...

3. Prevent buffering for delivery note

4. (Releases up to and including 3.1I): ----------------------------------------
Include FV50XF0B, Routine BELEG_SICHERN:
---------------------------------------
...
...
...
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING

NR_RANGE_NR = TMP_NUMKI
OBJECT = 'RV_BELEG'
IGNORE_BUFFER = 'X' "<--- MOD
IMPORTING
NUMBER = XLIKP-VBELN.
RETURNCODE = RETC
...
...
...

(Releases as of 4.0)
---------------------------------------
Include FV50XF0B, Routine NUMMERNVERGABE_LIEFERUNG:
As of Release 4.5B, the indicator 'IGNBF' 'No doc.number buffering' of table TVSHP is evaluated. If this global setting is not made, buffering can be carried out, as in Release 4.0B, by means of the following program change.
---------------------------------------
...
...
...
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
NR_RANGE_NR = TMP_NUMKI
OBJECT = 'RV_BELEG'
IGNORE_BUFFER = 'X' "<--- MOD
IMPORTING
NUMBER = XLIKP-VBELN.
...
...
...


Additional key words

NRIV, VL04, locks

SAP Note 23833 - Valuation difference in 2nd local currency

Symptom:

The fields BDIF2 / RDIF2 (valuation difference and realized exchange rate difference) are not displayed according to the currency key of the 2nd local currency but according to teh currency key of local currency.
Key words: FB03 SAPMF05L RFEPOS00 FBL1 FBL3 FBL5

Cause and prerequisites

Error.

Solution

Corrected in Release 22F/30A.
Advance correction:
/NSE11 - Change - BSEG - check that status is 'active - saved' and only then continue -
Fields - search for 'BDIF2' - F2 on field name,

• Reference table: incorrect: T001, correct: BKPF

• Reference field: incorrect: WAERS, correct: HWAE2.

Similar for field RDIF2.

Save and activate.

SAP Note 23830 - PC config. recommendation for FI LC PC data entry

Symptom:

Only the blue initial screen appears when starting the PC data entry (dBASE-Clipper application), the program does not start.
Other problems: not enough storage available, to open a further file, or similar things

Cause and prerequisites

Configuration of the PC.

Solution

Concerning the configuration of the PC, the following can be pointed out:
REM CONFIG.SYS e.g: for Windows for Workgroups !
REM =============================================================
DEVICE=C:\DOS\HIMEM.SYS/testmem:off
FILES=81
REM FILES should be set to the highest possible value! We
REM recommend an odd (!) value!!!

DEVICE=C:\DOS\EMM386.EXE 512 RAM X=D800-DBFF X=CC00-CDFF
REM For a network card, you must reserve an area
REM e.g: X=D800-DBFF a.X=CC00-CDFF. In addition, we recommend to
REM have at least 512 KB RAM available!

DOS=HIGH,UMB
COUNTRY=049,850,C:\DOS\COUNTRY.SYS
SHELL=C:\COMMAND.COM /E:1024 /p
STACKS=9,256
DEVICEHIGH =C:\DOS\ANSI.SYS
DEVICE=C:\WINDOWS\IFSHLP.SYS
REM Network driver for Windows

L/(TDRIVE=Z


REM AUTOEXEC.BAT e.g: for Windows for Workgroups !
REM =============================================================

ho off LH C:\WINDOWS\SMARTDRV A- B-
REM SMARTDRV.EXE uses the storage more effectively than BUFFERS !

C:\WINDOWS\NET START
REM Starting the WFW network

PROMPT $p$g
PATH C:\WINDOWS;C:\DOS;D:\BAT;C:\;
SET TEMP=C:\TMP
LH C:\DOS\KEYB GR,,C:\DOS\KEYBOARD.SYS

Problems can also occur with: =============================

• loaded SHARE.EXE. This program is no longer needed with Windows 3.11 anyway and should be deleted when problems occur!

• Activated video or system cache. Then the BIOS settings are to be checked and changed. Normally "disable" or switching off video cache or system cache helps!!!

SAP Note 23826 - Error in the ZLIT fct. when OUTZL oper. is used

Symptom:

If operation OUTZL is used in a cycle accessed by function ZLIT, then
the correct results are not achieved for all parameters.

Cause and prerequisites

This is caused by a program error.

Solution
If you run the payroll with RPCALCU0 (USA), RPCALK0 (Canada) or RPCALCJ0 (Japan), make the changes in RPCMAS09. All other country versions are based on the RPCMAS00 program. Make the following changes in the 'Fuzlit' routine in program RPCMAS00 or RPCMAS09:
form fuzlit
ccycl = as-parm1.
* XIT-KENN1 = SPACE.
perform fubzl-init-natio.
* OLDZLPOSID = SPACE.
oldzldate = space.
refresh zh. "<--insert
loop at zl. zh = zl. append zh. endloop. "<--insert
clear loopnr. "<--insert
* loop at zl. "<--deactivate
loop at zh. "<--insert
loopnr = sy-tabix. "<--insert
at first.
if ccycl gt space. perform phase-heading. endif.
endat.
* check as-parm4 ca zl-iftyp. "<--deactivate
check as-parm4 ca zh-iftyp. "<--insert
it = it0.
if ccycl gt space. "Regeleverarbeitung?
* ZL = ZH wird in znn-regel durchgeführt
* zh = zl. "<--deactivate perform znn-regel.
.
.
.
else.
* cdatum = zl-datum. "<--deactivate
cdatum = zh-datum. "<--insert
perform pos-wpbp.
it-abart = wpbp-abart.
it-apznr = wpbp-apznr.
perform pos-cntr.
move-corresponding split-natio to it.
* it-c1znr = zl-c1znr. "<--deactivate
* it-abznr = zl-abznr. "<--deactivate
* it-alznr = zl-alznr. "<--deactivate
* it-lgart = zl-lgart. "<--deactivate
* it-anzhl = zl-anzhl. "<--deactivate
it-c1znr = zh-c1znr. "<--insert
it-abznr = zh-abznr. "<--insert
it-alznr = zh-alznr. "<--insert
it-lgart = zh-lgart. "<--insert
it-anzhl = zh-anzhl. "<--insert
collect it.
endif. "Regelverarbeitung?
endloop. "at ZL

Afterwards, please check to ensure that the payroll program does not
contain any errors.

SAP Note 23820 - RFAWVZ5A: Data from T001Z does not drag

Symptom:

The company data which is maintained in T001Z for the Z5A message for the German foreign trade and payments ordinance are not used.
Key words: RFAVWZ5A T001Z T001M Z5A

Cause and prerequisites

Data is expected in T001M.

Solution

Maintain data in T001M:

• SM31 - T001M or

• OBA2 or

• Closing - Month end reports - General ledger - FTPS: Company data

SAP Note 23816 - Procedures (PL/SQL) in Oracle

Symptom:

PL/SQL export import

Cause and prerequisites

Procedures invalid after import.

Solution
Stored procedures are exported on export in the user mode, set to import invalid and must be recomplied after the import with COMPILE ALL. Once this has been done, they have the status 'valid'.

SAP Note 23814 - Retirement of capital inv. measure -> error AK005

Symptom:

You cannot post a retirement on an asset under construction (AuC), which is created for a capital investment measure (order / WBS element), when an investment profile with line item allocation is used. The following error message is displayed:
AK005 'Asset is capital investment measure, transaction type not allowed'.

Other terms

ABAV, ABAD, ABAO, ABAVN, line item settlement

Reason and Prerequisites

If you use an investment profile with line item apportionment in the investment measure, and the investment profile is thereby settled based on the CO line items, you must assign a retirement to the CO line item that you want to dispatch. You cannot use the usual retirement transaction for this assignment.
It is not possible to post the respective asset under construction directly, since settlement information must be updated for every CO line item through the retirement (otherwise there would be differences between asset under construction values and CO line items that are to be settled in Transaction KOB5 or CJ70 / CJIC).

Solution

Up to Release 3.0E or release-independent workaround:
The CO line items, to which the retirement refers, must be finally settled using Transaction KOB5 and KO88 (order) or CJ70 and CJ88 (WBS element) to an asset under construction that is managed in totals. You can then post the retirement from this asset. The AuC managed in totals is used as a type of clearing account.
Alternatively, you can carry out the affected asset under construction line items to other receivers (GL account or CO receiver, for example, cost center) and not to an asset.

As of Release 3.0E:
For investment measures with line item apportionment, transactions are delivered that allow you to mark line items of the investment measure for a retirement and to post a retirement from the asset under construction for these items by means of a special settlement run.
The following steps are necessary:

1. Extending a display variant:

• Extending a display variant up to Release 3.1:

• Add the ABGKZ field "Retirement ID" to a display variant for the line item distribution transaction.

• Generate the display variant.

• You can also enter the ABGKZ field for a display variant as an allowed additional field.

• Extending a display variant (layout) as of Release 4.0:
  Use the layout management in the line item list (ALV list) to add the field 'Retirement indicator' to the display variant used. The field 'Retirement indicator' is only available in the transaction described below.

2. Marking line items for retirement:

• If your investment measure is an order, call Transaction KOB7. If it is a WBS element, call Transaction CJ7N.

• Enter the object and display the line items.

• Select the line items that are to be posted as retirement by the asset under construction. For the selected items, set the retirement ID by choosing "Edit -> Outflow -> Set Indicator".

• Save your selection.

3. Carrying out the settlement:

• Call Transaction KO8A for the order or CJ8A for the WBS element to carry out the retirment settlement. Internally, these settlements use processing type "R".

• Note that you can only carry out a retirement for line items, for which a periodic settlement to the asset under construction has already been made. You may have to carry out a periodic settlement to the asset under construction first. In this case, you can however check, whether the affected line item cannot simply be reversed in CO or retired by a preliminary settlement of the order or WBS element to the CO receiver or GL account.

• Up to Release 3.1I, you must give the asset value date. In a higher release, the asset value date is optional.

• First, carry out a test run and check the output values.

SAP Note 23810 - Matchcode object VMSK

Symptom:

When the system makes an INSERT in table VBSK, the system log entry occurs because an UPDATE should be carried out for matchcode object VMSK from the database interface.

Cause and prerequisites

The matchcode object VMSK is obsolete and could not be deleted by the transport system. In Release 3.0/3.1, it is used neither in the programs nor in the screens for input help.

Solution

Deactivate the matchcode object by changing all the IDs of the matchcode object to the asynchronous update type 'A'.Proceed as follows:

1. Call the transaction to maintain the Data Dictionary (SE11).

2. Enter VMSK as the object name, select sub-object 'Matchcode object' and choose 'Display'.

3. Select 'Goto--> Matchcode IDs', and select ID A or B on the dialog box.

4. Call the change mode and change the update type from 'S' to 'A'.

5. Activate the matchcode ID at the end of your changes.

6. Execute steps 1-5 for both matchcode IDs A and B.

After the change to asynchronous update, the matchcode tables M_VMSKA and M_VMSKB are only supplied in case of an explicit generation via report SAPMACO.Since however the matchcode tables are not needed anywhere in the R/3 System, you can omit this, this virtually deactivates the matchcode.
To ease the workload of the database, you can also completely delete the contents of the matchcode tables. Use report SAPMACO to do this - with the option 'DEL'.

Note 21046 contains information on the F4 help in Transaction VG02 for field 'Group number'.

SAP Note 23808 - Vendor during GR for stock transport order

Symptom:

Field 'Vendor' (MSEG-LIFNR) is initial during the goods receipt for stock transport order. Prior to Release 2.2, this field contained the delivering plant.

Cause and prerequisites

This program error was corrected in Release 2.2.

Solution
If you need the former contents of field MSEG-LIFNR for your own analyses, you would have to refer to the field 'Delivering plant' (EKKO-RESWK) by reading the respective stock transport order (MSEG-EBELN).

SAP Note 23801 - Create product groups: DUPREC

Symptom:

Update termination when creating product groups with DUPREC.

Cause and prerequisites

When creating a product group, a record is also written into table S076E. This table has an unique index to field PLOBJ.
If the status of the number range (object MCLIS) is that existing numbers of the object are reassigned, a DUPREC occurs.

Solution
Raise the number range status.

SAP Note 23794 - RFZALI00 - Incorrect number of zero balances

Symptom:

If items balanced to zero during a payment run, these items are output in the payment proposal list or payment list with the payment method . The number of these zero balances is randomly specified with the number of payments for another payment method and does not match the control figure on the form summary section of RFFOAVIS.

Cause and prerequisites

Incorrect read access in an internal table.

Solution
Error in the company code list is corrected in Release 2.2F, the same error is solved in Release 2.2H/3.0D for the client list.
An interim correction is possible.

Additional key words

RFZALI00

SAP Note 23787 - Update term. during goods receipt for purchase order

Symptom:

During the goods receipt for the purchase order with transaction MB01, the update in function module MB_UPDATE_MATERIAL_VALUES terminates, if a valuation type (EKPO-BWTAR) is entered in the unassigned order item in question although the material in question is not valuated separately (the valuation category of material MBEW-BWTTY is initial).

Cause and prerequisites

The valuation category was cancelled in the material master although a purchase order exists. This, however, must not be allowed by the system.

Solution
Please make the following changes in FORM routine MATERIAL_LESEN in program FM07MFM0:
...
IF MBEFU-BWTTY IS INITIAL.
IF NOT MBEFU-BWTAR IS INITIAL.
MESSAGE E051 WITH M-MATNR M-WERKS.
ENDIF.
IF NOT M-BWTAR IS INITIAL AND NOT MBEFU-WERTU IS INITIAL. <--- new
MTCOM-KENNG = 'MBEW '. <--- new
CLEAR MTCOM-BWTAR. <--- new
CALL FUNCTION 'MATERIAL_READ' <--- new
EXPORTING <--- new
SCHLUESSEL = MTCOM <--- new
IMPORTING <--- new
MATDATEN = MBEW <--- new
RETURN = MTCOR <--- new
TABLES <--- new
SEQMAT01 = DUMMY. <--- new
IF NOT MTCOR-RMBEW IS INITIAL. <--- new
MESSAGE E077 WITH MTCOM-MATNR MTCOM-BWKEY MTCOM-BWTAR. <--- new
ENDIF. <--- new
XMTCOR-RMBEW = MTCOR-RMBEW. <--- new
MOVE-CORRESPONDING MBEW TO MBEFU. <--- new
CLEAR M-BWTAR.
ENDIF. <--- new
ELSE.
...

SAP Note 23782 - Order confirmation: Material determination

Symptom:

Key word: Material determination/order confirmation
When printing order confirmation, the found material is printed although (material substitution: reason) is set in table TVSU, so that the entered material should be printed.

Cause and prerequisites

Function has not yet been implemented in Release 2.2.

Solution
Correction S11K143672
This can be used as an advance correction as of Release 2.2:

1. Program LV05DTOP:
FUNCTION-POOL V05D MESSAGE-ID VD.
....
....
TABLES: VBDKAZ, VBDPAZ.
TABLES: TVSU. <== NEW

2. Program LV05DFMO:
Insert routine MAKT_ERMITTELN at the beginning of the program:
*----------------------------------------------------------------------*
* FORM MAKT_ERMITTELN *
*----------------------------------------------------------------------*
* Bereitstellen des Materialkurztextes *
*----------------------------------------------------------------------*
* --> US_MATNR Materialnummer *
* <-- CH_KURZTEXT Materialkuztext *
*----------------------------------------------------------------------*
FORM MAKT_ERMITTELN USING US_MATNR CH_KURZTEXT.
TABLES: MAKT, MTCOR.
DATA: BEGIN OF MAKT_MTCOM.
INCLUDE STRUCTURE MTCOM.
DATA: END OF MAKT_MTCOM.
DATA: BEGIN OF XDUMMY OCCURS 1,
FELD,
END OF XDUMMY.

MAKT_MTCOM-KENNG = 'MAKT'.
MAKT_MTCOM-SPRAS = VBCO3-SPRAS.
IF MAKT_MTCOM-SPRAS = SPACE.
MAKT_MTCOM-SPRAS = SY-LANGU.
ENDIF.

MAKT_MTCOM-MATNR = US_MATNR.
MAKT_MTCOM-MAXTZ = 5.

CALL FUNCTION 'MATERIAL_READ'
EXPORTING
SCHLUESSEL = MAKT_MTCOM
IMPORTING
MATDATEN = MAKT
RETURN = MTCOR
TABLES
SEQMAT01 = XDUMMY.
CH_KURZTEXT = MAKT-MAKTX.

ENDFORM.
....
....
FORM MOVE_VBAP_TO_LVBDPA.
MOVE VBAP-ARKTX TO LVBDPA-ARKTX .
....
....
IF LVBDPA-KWMENG = 0.
LVBDPA-KWMENG = VBAP-ZMENG.
ENDIF.
MOVE VBAP-MATNR TO LVBDPA-MATNR .
* MATNR ggfs. mit eingegebenem Material füllen <== NEW
IF NOT VBAP-MATWA IS INITIAL AND <== NEW
NOT VBAP-SUGRD IS INITIAL. <== NEW
SELECT SINGLE * FROM TVSU <== NEW
WHERE SUGRD = VBAP-SUGRD. <== NEW
IF SY-SUBRC EQ 0 AND <== NEW
NOT TVSU-SUDRU IS INITIAL. <== NEW
MOVE VBAP-MATWA TO LVBDPA-MATNR. <== NEW
*... Materialkurztext nachlesen <== NEW
PERFORM MAKT_ERMITTELN USING VBAP-MATWA LVBDPA-ARKTX. <== NEW
ENDIF. <== NEW
ENDIF. <== NEW
MOVE VBAP-NETPR TO LVBDPA-NETPR .
======================== End of correction ============================

SAP Note 23780 - RFDKLI40: Selection by credit limit used

Symptom:

When selecting by credit limit used in the credit overview RFDKLI40, the accounts that manage their credit data with another account are always displayed as well, even if this other account is not selected.
Example:
Credit limit Account A - 0 DM, limit for account B, credit limit used 0 %
Credit limit Account B - 1000 DM, credit limit used 20 %.
Account A is also issued if you select the parameter 'Display all with credit limit used > 50 %'.

Cause and prerequisites

*

Solution
None, since the data is not sorted internally in a way that allows you to make the decision for account A dependent on account B.

The following change may enable you to suppress output of the dependent accounts (such as A) by selecting the parameter 'Credit limit used':



First make sure that you have implemented Note 100320 for releases up to and including Release 4.0B.


Insert the following lines for Releases 3.0A - 3.1I:

/NSE38 - RFDKLI40, FIND CHECK_KNKK
IF KNKK-KUNNR = KNKK-KNKLI.
...
ELSE.
CLEAR: S067-OLIKW, S067-OFAKW, S066-OEIKW, RF021-OBLIG,
RF02L-KLPRZ.
CHECK: KLPRZ.
IF NOT KLPRZ IS INITIAL. <--- insert
CHECK 1 = 2. <--- insert
ENDIF. <--- insert
ENDIF.
IF NOT WAERS IS INITIAL.



Insert the following lines as of Release 4.0A:
/NSE38 - RFDKLI40, FIND CHECK_KNKK
IF KNKK-KUNNR = KNKK-KNKLI.
...
ELSE.
CLEAR: S067-OLIKW, S067-OFAKW, S066-OEIKW, RF021-OBLIG,
RF02L-DELTA, RF02L-KLPRZ.
PERFORM CLEAR_HORDA.
RF02L-HORDA = HORDA.
CHECK KLPRZ, DELTA.
IF NOT KLPRZ IS INITIAL. <--- insert
CHECK 1 = 2. <--- insert
ENDIF. <--- insert
ENDIF.
IF NOT WAERS IS INITIAL.

SAP Note 23775 - Release strategy in company code currency

Symptom:

If you specify a plant when determining a release strategy, a currency entered in field V_161I-WAERS is possibly overwritten.

Cause and prerequisites

If the plant is allocated to a company code, the currency of this company code is determined from table T001 and this value is entered into the currency field of the strategy determination. There is no conversion at quoted value.

Solution
None. It is defined this way.

SAP Note 23771 - Quantity conversion with non-metric units

Symptom:

The quantity conversion between metric (meters, kilos, liters) and non-metric (yard, pound, gallon) units of measure is often only possible with big conversion errors.
When quantity units are being customized with factory that have more then five positions, the message "Field overflow ..." (BM398) or message V1384 is output.

Cause and prerequisites

In many applications, the conversion factors can only be represented as an integral decimal fraction with a maximum of 5 positions.

Solution
The following tables contain the conversion factors for some conversions from non-metric into metric units of measure which cause the least conversion error. The table specifies the conversion factor resulting in each case from the decimal fraction so that the conversion error can be judged.

Length:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 inch = 0,0254 Meter | 254/10000 = 0,0254
1 foot = 0,3048 Meter | 3048/10000 = 0,3048
1 yard = 0,9144 Meter | 9144/10000 = 0,9144
1 mile = 1,609344 Kilometer | 75438/46875 = 1,6093440000
------------------------------------------------------------------------
Surface:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 square inch = 6,4516 Square centimeter| 16129/2500 = 6,4516
1 square foot = 0,09290304 Square meters| 7099/76413 = 0,0929030401
1 square yard = 0,83612736 Square meters| 70325/84108 = 0,8361273601
------------------------------------------------------------------------
Volume:
Exact conversion | SAP conversion ----------------------------------------|-------------------------------
1 minimum = 0,06161152 Milliliter | 4009/65069 = 0,616115201
1 cubic inch = 16,387064 Milliliter | 48391/2953 = 16,3870640027
1 cubic foot = 28,316846592 Liter | 94465/3336 = 28,3168465228
1 cubic yard = 0,764554857984 Cubicmeter| 41393/54140 = 0,7645548578
1 dry pint = 0,5506105 Liter | 46493/84439 = 0,5506104999
1 liquid pint = 0,473176473 Liter | 47038/99409 = 0,4731764730
1 gallon = 3,785411784 Liter | 92065/24321 = 3,7854117841
------------------------------------------------------------------------
Weight:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 avdp. ounce = 28,349523125 Grams | 32687/1153 = 28,3495229835
1 avdp. pound = 0,45359237 Kilograms | 24445/53892 = 0,4535923699
1 short ton = 0,90718474 Tons | 24445/26946 = 0,9071847399
1 long ton = 1,016046909 Tons | 61861/60884 = 1,0160469089
------------------------------------------------------------------------

Further notes to avoid conversion errors:
- From several alternative units of measure always choose the smallest one as a base unit of measure for a material.
Example: If the units of measure grams, ounce, pound and kilos are useful for a material, gram should be chosen as a base unit of measure.
Since the inventory management is always carried out in base unit of measure and quantities are managed with exactly 3 places behind the decimal point, you can thus avoid conversion errors for small quantities moved.
- If conversion factors are maintained centrally in Customizing of the units of measure, the conversion is always maintained for the respective SI unit. If the unit of measure to be maintained has a dimension other than the SI unit (for example, 1 minimum << 1 cubic meter), you can only specify a very inaccurate decimal fraction.
Solution: Define non-metric units of measurem as without dimensions.
Advantage: You can define the conversion factors with maximum accuracy in the material master.
Disadvantage: You have to make sure organizationally that materials with the same units of measure also use the same conversion factors.
- Many conversion factors that are not listed in table can be determined by a corresponding multiplication since the relationship between two non-metric units of measure can often be represented with a decimal fraction (for example, 1 gallon = 4 liquid quarts).
- If you define special conversion factors, you have to consider that an exact conversion factor can often be represented simply by reducing the decimal fraction.
Example:
1 Unit1 = 0.10476 Unit2
100000 Unit1 = 10476 Unit2 (conversion factor is too large)
99999 Unit1 = 10476 Unit2 (big conversion error)
25000 Unit1 = 2619 Unit2 (reduced by 4, precise conversion factor)

Additional key words

imperial

SAP Note 23771 - Quantity conversion with non-metric units

Symptom:

The quantity conversion between metric (meters, kilos, liters) and non-metric (yard, pound, gallon) units of measure is often only possible with big conversion errors.
When quantity units are being customized with factory that have more then five positions, the message "Field overflow ..." (BM398) or message V1384 is output.

Cause and prerequisites

In many applications, the conversion factors can only be represented as an integral decimal fraction with a maximum of 5 positions.

Solution
The following tables contain the conversion factors for some conversions from non-metric into metric units of measure which cause the least conversion error. The table specifies the conversion factor resulting in each case from the decimal fraction so that the conversion error can be judged.

Length:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 inch = 0,0254 Meter | 254/10000 = 0,0254
1 foot = 0,3048 Meter | 3048/10000 = 0,3048
1 yard = 0,9144 Meter | 9144/10000 = 0,9144
1 mile = 1,609344 Kilometer | 75438/46875 = 1,6093440000
------------------------------------------------------------------------
Surface:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 square inch = 6,4516 Square centimeter| 16129/2500 = 6,4516
1 square foot = 0,09290304 Square meters| 7099/76413 = 0,0929030401
1 square yard = 0,83612736 Square meters| 70325/84108 = 0,8361273601
------------------------------------------------------------------------
Volume:
Exact conversion | SAP conversion ----------------------------------------|-------------------------------
1 minimum = 0,06161152 Milliliter | 4009/65069 = 0,616115201
1 cubic inch = 16,387064 Milliliter | 48391/2953 = 16,3870640027
1 cubic foot = 28,316846592 Liter | 94465/3336 = 28,3168465228
1 cubic yard = 0,764554857984 Cubicmeter| 41393/54140 = 0,7645548578
1 dry pint = 0,5506105 Liter | 46493/84439 = 0,5506104999
1 liquid pint = 0,473176473 Liter | 47038/99409 = 0,4731764730
1 gallon = 3,785411784 Liter | 92065/24321 = 3,7854117841
------------------------------------------------------------------------
Weight:
Exact conversion | SAP conversion ----------------------------------------+-------------------------------
1 avdp. ounce = 28,349523125 Grams | 32687/1153 = 28,3495229835
1 avdp. pound = 0,45359237 Kilograms | 24445/53892 = 0,4535923699
1 short ton = 0,90718474 Tons | 24445/26946 = 0,9071847399
1 long ton = 1,016046909 Tons | 61861/60884 = 1,0160469089
------------------------------------------------------------------------

Further notes to avoid conversion errors:
- From several alternative units of measure always choose the smallest one as a base unit of measure for a material.
Example: If the units of measure grams, ounce, pound and kilos are useful for a material, gram should be chosen as a base unit of measure.
Since the inventory management is always carried out in base unit of measure and quantities are managed with exactly 3 places behind the decimal point, you can thus avoid conversion errors for small quantities moved.
- If conversion factors are maintained centrally in Customizing of the units of measure, the conversion is always maintained for the respective SI unit. If the unit of measure to be maintained has a dimension other than the SI unit (for example, 1 minimum << 1 cubic meter), you can only specify a very inaccurate decimal fraction.
Solution: Define non-metric units of measurem as without dimensions.
Advantage: You can define the conversion factors with maximum accuracy in the material master.
Disadvantage: You have to make sure organizationally that materials with the same units of measure also use the same conversion factors.
- Many conversion factors that are not listed in table can be determined by a corresponding multiplication since the relationship between two non-metric units of measure can often be represented with a decimal fraction (for example, 1 gallon = 4 liquid quarts).
- If you define special conversion factors, you have to consider that an exact conversion factor can often be represented simply by reducing the decimal fraction.
Example:
1 Unit1 = 0.10476 Unit2
100000 Unit1 = 10476 Unit2 (conversion factor is too large)
99999 Unit1 = 10476 Unit2 (big conversion error)
25000 Unit1 = 2619 Unit2 (reduced by 4, precise conversion factor)

Additional key words

imperial

SAP Note 23768 - Negative list : Different valuation for GR / IR

Symptom:

A different valuation of fixed assets per depreciation area with acquisitions from Materials Management (goods receipt / invoice receipt) is not possible.

Cause and prerequisites

This is caused by the program design.

Solution
The different valuation can be achieved later within Asset Accounting by means of special transaction types.

SAP Note 23766 - SOP: Create product group: Batch input error 1

Symptom:

Create product groups: Termination with batch input error 1.

Cause and prerequisites

The customer has maintained table T134 incorrectly.

Solution
Table T134 in the standard system contains material type 'ROH' as screen reference for material type 'PROD' (used for product groups). The customer had entered 'PROD' here. Reset the table to the status of the standard system to correct the error.

SAP Note 23762 - FD11: Unearned/earned deductions

Symptom:

For payments with cash discount which indeed exceeded the cash discount period, but are still within the tolerance ranges, the deductions are not managed with the earned deductions but with the unearned deductions.
Example:
Payment 18 days after base date, cash discount line 14 days 3 %, 30 days 2 %, 40 days net. Tolerance 6 days. Invoice 100 DM, payment 97 DM.
The earned deductions now do not increase by 3 DM (because 18 <> 14, 18 < 30), and the unearned deductions increase by 1 DM.
Key words: FD11 SAPMF42B Payment history SAPFF007 BABZG UABZG T043G

SAP Note 23760 - Incorrect audit trail for commercial law

Symptom:

Audit trail, Depreciation run
The end of the log shows the planned total, the posting total for the previous months, and the postings for this depreciation run. A summation error then occurs, as the depreciation posting total for the previous months is wrong.
Example: actually posted in January: 2'095'051.58
actually posted in February: 2'102'830.35
results in a total of 4'197'881.93
The audit trail for March reports 'posted so far': 4'178'014.93.

Cause and prerequisites

Problems in understanding the system.

Solution
Only those fixed assets are included in each depreciation posting run which contain depreciation that has still to be posted. Assets without depreciation in the period in question, either because they have been deactivated, or whose depreciation calculation had been closed with the end of their useful life (for example, during the fiscal year, in which case the depreciation for past periods in a lump sum was defined in the depreciation posting rules), are no longer contained in the next posting run. As a result, the depreciation posted so far for these fixed assets is not displayed in the RABUCH list. Therefore, you cannot expect that the depreciation for these fixed assets to be posted in the previous period will be displayed in the next period as 'depreciation posted so far'. From Release 3.0A this procedure has been re-arranged
to agree better with Financial Accounting. In the log for Rabuch00 from
Release 3.0A, those fixed assests are also posted for which depreciation
was to be posted in the previous period, but not, however, in the
present period. (You should compare Note 82541)

Additional key words

RABUCH00

SAP Note 23759 - Field overflow in SOP - transfer to Demand Management

Symptom:

When data is transferred from SOP to master production scheduling, terminations can occur if large key figures are to be transferred. These terminations occur in the area indicated k004125 below of Include LMCP2U01. In release 3.0, it is in includes LMCP2U40 and LMCP2U41 instead.
This program code rounds off places after the decimal point according to the specifications in the unit table (field: T006-ANDEC).
Transactions concerned: MC74 and MC75.

Cause and prerequisites

1. The auxiliary fields were defined too small.
2. The value in field T006-ANDEC of table T006 is too large (for example, 99).

Solution
1. Korrektur P22K007632:
*k004125***********************Rundung der Übergabewerte
DATA: PT_HLP_MENGE_MIN_REST(16) TYPE P, "change
PT_HLP_MENGE_RUNDUNG(16) TYPE P DECIMALS 0, "change
PT_HLP_MENGE_GERUND(16) TYPE P, "change
PT_HLP_FAKTOR TYPE I,
PT_HLP_REST(16) TYPE P, "change
...
2. Change the unit table

26.2.11

SAP Note 23759 - Field overflow in SOP - transfer to Demand Management

Symptom:

When data is transferred from SOP to master production scheduling, terminations can occur if large key figures are to be transferred. These terminations occur in the area indicated k004125 below of Include LMCP2U01. In release 3.0, it is in includes LMCP2U40 and LMCP2U41 instead.
This program code rounds off places after the decimal point according to the specifications in the unit table (field: T006-ANDEC).
Transactions concerned: MC74 and MC75.
If the field overflows, rounding errors may occur in the transferred data.

Cause and prerequisites

1. The auxiliary fields were defined too small.
2. The value in field T006-ANDEC of table T006 is too large (for example, 99).

Solution
1. Korrektur P22K007632:
*k004125***********************Rundung der Übergabewerte
DATA: PT_HLP_MENGE_MIN_REST(16) TYPE P, "change
PT_HLP_MENGE_RUNDUNG(16) TYPE P DECIMALS 0, "change
PT_HLP_MENGE_GERUND(16) TYPE P, "change
PT_HLP_FAKTOR TYPE I,
PT_HLP_REST(16) TYPE P, "change
...
2. Change the unit table

SAP Note 23758 - Docu error: Obj. type 'ORH' only for PP order header

Symptom:

When allocating a status profile defined by the user to the object types of the general status management (transactions OIBS and BS13), it is not clear whether the object type ORI = 'Maintenance order' or the object type ORH = 'PP, PM: Order header' is to be used for the maintenance order.

Cause and prerequisites

Documentation error

Solution
Object type ORH only applies to the PP order. Thus, ORI is to be used for the maintenance order/plant maintenance order.

SAP Note 23754 - Exclusive lockwaits for table display SE16

Symptom:

If several users in the SAP system want to display the contents of a table (for example BSEG) via transaction SE16, exclusive lockwaits can occur on table D010LINF, with the result that one user has to wait for another. This can also occur if two users want to display different tables at the same time.

Cause and prerequisites

When you execute transaction SE16, an update lock is set up in table D010LINF on the generic ABAP/4 programs 'RSLOCK01', 'RSLOCK02' and so on. Due to an index access to table D010LINF that is not fully classified when executing transaction SE16, wait situations (exclusive lockwaits) can occur, so that one session must wait until the other one releases the update lock again.

Solution
Download the newest version of the script 'D010LINF.SH.23754' from sapservX.

This script is stored on sapservX in the directory '/general/3rdparty/informix/ddic', with the name 'D010LINF.SH.23754'.

Stop the R/3 System (stopsap r3) and execute the script; An informix specific index is created on table D010LINF.

SAP Note 23753 - Copy plan versions without orders for the project

Symptom:

In Project system, when you perform the functions
"Copy plan version--> costs" (CJ9B) and
"Copy plan version--> revenues" (CJ9C)
only the values planned directly on the WBS elements are copied.
The planning values of orders or networks for the project are not taken into account when copying.

Cause and prerequisites

Function not supported in R/3-3.0.

Solution
This function is planned for a later release.
If only CO orders are allocated to the project, the corresponding copy function in the CO orders application can be used in R/3-3.0.

SAP Note 23751 - GEN_STRUCTURE_STACK_OVERFLOW for posting

Symptom:

1. The runtime error GEN_STRUCTURE_STACK_OVERFLOW occurs in the case of a posting.

2. When you maintain a validation, a substitution or rule, the error GB018 ('Boolean statement not complete') is generated.

Cause and prerequisites

1. The name of the program that caused the runtime error is:

a) up to Release 3.0: FGBB2mmm and FGBB3mmm where mmm stands for the client.

b) as of Release 3.0: GBTmmaa0 where mm stands for a two-digit encryption of the client and aa for the respective component (for example, FI, CO, AM, PC, GS, GL). To identify the client, use Transaction SE37. Enter 'G_CLIENT_DECODE' as function module and press the 'Sngl.test' pushbutton. In the following screen, enter the two-digit encryption of the client in input field 'MM' and choose 'Execute' (F8). In the following screen, the system displays the unencrypted client in export parameter 'MMM'.

Too many conditions linked by logical operators (AND, OR, --> or <-->) were used in a substitution, validation or rule. The generated source code thus has a too deep IF ... ENDIF nesting.

2. The condition, which you try to maintain is too long. There is a defined limit which is about 33 lines. The program disregards everything which exceeds this limit.

Solution
Try to group several conditions together to a rule since this reduces the nesting depth of the IF ... ENDIF structures.

Example:

original rule: OR OR AND AND AND
( ... are placeholders for simple conditions)

This can be split into two or morel rules:

splited rule : &SR1 AND &SR2
where : SR1 = OR OR
SR2 = AND AND

Rules SR1 and SR2 are maintained with Transaction GCVZ.

If the complex condition contains field literal comparisons like those the following, it can be simplified by using sets:

$Field = 'Constant_1' or
$Field = 'Constant_2' or
$Field = 'Constant_3' or ... (Release < 4.0A)

Table-Field = 'Constant_1' or
Table-Field = 'Constant_2' or
Table-Field = 'Constant_3' or ... (Release >= 4.0A)

In this case, you can create a set in Transaction GS01 for the field 'Table field' that contains the values 'Constant_1', 'Constant_2', 'Constant_3' and so on. The sequence can then be replaced by an easy set validation - this also improves the performance.

If runtime error GEN_STRUCTURE_STACK_OVERFLOW occurs after you replace or split all complex conditions, execute program RGUGBR00. Check all parameters except for 'Gen.substn routns in all clnts'.

Additional key words

FB01, GGB0, GGB1, GBT

SAP Note 23743 - Negat. list decl. bal. of asset acct det. grp asset

Symptom:

The group asset became available with Release 3.0.
At present, the depreciation determined on the group asset cannot be distributed onto the allocated individual assets.

Solution
A solution within reporting is planned with Release 3.0.

SAP Note 23741 - Quantity management negative list in fixed assets

Symptom:

In Asset Accounting, the following functions are not possible with reference to a quantity management:

• Settlement of orders or projects with quantity for investment measure with line item settlement. As of Release 4.5, a quantity settlement is possible for summary settlement (see Note 337476)

• Asset balance update from Materials Management

• Quantity grid

• For negative assets, the quantity is not updated during the first acquisition posting in the asset master record.

Solution
Use transaction AS02 to maintain the quantity manually in the fixed asset.

SAP Note 23740 - Negative list: Variable lease payments

Symptom:

You cannot manage non-periodic lease payments (such as special payments) or changes to lease payments during the life of the leasing agreement.

Further negative points include:

• No flexible installments.

• Down payments/final settlements are not taken into account.

• Posting to vendor account occurs for area 01 only.

• Opening entries with affiliated company are not possible.

• Posting the interest paid occurs for area 01 only.

• Tax is not taken into account when the posting to vendor account is created.

• The installment allocation to interest and repayment portions is executed using the depreciation key.

• No different capitalization amounts (capitalization with the present value).

• The useful life and contract duration must correspond. Changes during the life of the leasing agreement are not possible.

• The contract start date, depreciation start date and interest start date must correspond and must not be in a future fiscal year.

• The purchase price option is taken into account for the calculation of the present value.

• The scrap value is not taken into account for the calculation of the present value.

• Shutdown periods are not taken into account.

• The "new depreciation calculation" is not used in combination with the leasing function. If the present value is determined in the asset master record, the logic of the old depreciation calculation is used.

• The leasing start date must be at the start of the month. The system calculates from the start of the month even if another leasing start date is selected.

• Partial transfer of a leased asset

In general, no value adjustment is determined for interest for intracompany transfers. For the issuing fixed asset, this means that interest on the retirement is determined from the relationship of the transfer posting amount to the entire APC. No prior year acquisitions are determined for interest.

However, the proportion of interest for target assets is newly determined according to the settings of the depreciation key. In almost all cases, there may therefore be differences when comparing the interest for the issuing transfer with the interest for the acquiring transfer.

SAP does not recommend partial transfers, but instead canceling the original acquisition, and activating the individual assets separately.

Other terms

Leasing, LEAS, negative list, LZINS

Reason and Prerequisites

*

Solution
You can use a new fixed asset for changes to regular payments during the life of the leasing agreement. In the case of fixed assets with the capital lease method, you must perform a retirement on the previous fixed asset beforehand (this procedure is described in the user guide).
Important: There may be differences between the cash value calculations and the display on a fixed asset (which is not possible).

SAP Note 23736 - Negative list : Indexing during the fiscal year

Symptom:

The indexing within Asset Accounting presently only works on an annual basis, that is, a monthly or quarterly indexing is not possible.

Solution
Up to now, this indexing was only implemented for the Argentinian version. The indexing was determined with a specific table in an additional program and reported as manual revaluation to Asset Accounting.
At this time no plans exist for additional coutry-specific versions.

SAP Note 23735 - WBS proposal from header, no profit center

Symptom:

If a WBS element is entered in the order header in account assignment, this is taken into account during the account assignment of items entered afterwards. However, the profit center is not extended. The profit center is only updated if you "access" the WBS number in the individual items.

Cause and prerequisites

Missing proposal

Solution
The following advance correction can be made as of 2.2B:
Program fv45pfap, form vbap_fuellen:

...
* Bedarfsdaten ermitteln
PERFORM VBAP_FUELLEN_T459K.
* Daten aus der Hauptposition, auch Kontierung
PERFORM VBAP_FUELLEN_HVBAP.

>>>> Begin of correction, insert the following lines:
* Bei Projektkontierung wird das Profitcenter aus dem PSP vorgeschlagen
if vbap-kzvbr = kzvbr_p and
not vbap-ps_psp_pnr is initial.

call function 'CJPN_PROJECT_ACCOUNT'
exporting
int_num = vbap-ps_psp_pnr
importing
e_prctr = vbap-prctr
exceptions
others = 1.
endif.
>>>> not changed: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

* Bei Bedarfserfassung kommt die Mengeneinheit aus MT61D(MAEPV),
* weil MAAPV nicht genutzt wird.
PERFORM VBAP-UMZIZ_ERMITTELN.
PERFORM VBAP-UMVKZ_ERMITTELN.
...
...

SAP Note 23734 - Negative list : Subdivision of acquisition costs

Symptom:

A subdivision of acquisition and production costs (APC), for example, according to acquisition years or original costs is not possible.

Solution
You can use subnumbers in the system for the subdivision according acquisition years.
In this case, you can use a depreciation key for the fixed assets in question which does not allow an acquisition according to the acquisition year.

SAP Note 23732 - Negative list : Different period versions

Symptom:

Can a fiscal year variant (other than the one in the General Ledger) be used in one or more depreciation areas?

Cause and prerequisites

The reasons for this might include:

• The company is a member of a corporate group: the group has a different fisal year.

• Fixed tax year: the tax year is the calendar year (for example) and is different from the fiscal year of the company code.

Solution

The fundamental rule is, you specify the fiscal year variant for the company code centrally in the FI General Ledger. In Asset Accounting, you can define an alternative fiscal year variant (version) for all depreciation areas. However, the first and last day of the fiscal year for this fiscal year variant must be the same as the first and last day of the fiscal year variant in the General Ledger.
You can define and use your own fiscal year variant in depreciation areas starting in maintenance level 3.0C, but the first and last day of your fiscal year variant must agree with the General Ledger variant.
Reports for a specific date (for example, an asset list) are possible with this functionality, but not reports on a period of time (for example, an asset history sheet).
There are two possible workaround solutions. Use the follwing as an example: Assume that the fiscal year in depreciation area 01 goes from January 1 to December 31. The desired fiscal year for reporting goes from October 1 of year X to September 30 of year X+1.

1. Solution using additional reports:

a) Run a report for September 30 of year X (for example, 1997).

b) Run a report for December 31 of year X (for example, 1997).

c) Run a report for September 30 of year X+1 (for example, 1998).

d) Load all of these reports into EXCEL or a similar tool and calculate the differences using that tool.

2. Solution using a copy of the data in a dummy company code:
Create an additional company code that has the different fiscal year version. Using a program you create yourself, copy the master data and transactions to the new company code. Then run the reports in the new company code.

Additional key words

Period version

SAPNote 23731 - CJ40: Only one WBS element in cost element planning

Symptom:

When you access cost element planning (primary costs KPP2 and activity input KPR2) via the work breakdown structure (CJ40/CJ41), and after executing function 'Swap dimensions...', only one element is displayed the 'Dimension WBS elements' screen, even though you selected several WBS elements in the structure.

Cause and prerequisites

The branch from the WBS to cost element planning always refers to the
first of the selected WBS elements, since groups of WBS elements cannot
be set up. Consequently, only the one WBS element is displayed when you execute 'Swap dimensions...'.

Solution
You need to plan the WBS elements of a WBS separately.

SAP Note 23729 - FB01/FBZ1/FB05: Mess. KI235, e.g. for bank charges

Symptom:

The message KI235 appears for incoming payment with bank charges (account does not contain a cost center-relevant account assignment).
Key words: FBZ1 KI235 SAPLRKIP K_COBL_CHECK

Cause and prerequisites

No default account assignments maintained in tables TKA3A, TKA3B.

Solution
Configuration menu Controlling - Cost center accounting - actual postings - Autom. account assignment (transaction OKB9): Define default account assignments.

SAP Note 23727 - Incomplete transfer of default values T159B

Symptom:

When creating batch input sessions BTCI, the default value 'Including inventoried batches' from table T159B is not transferred for the following transactions/reports:

MI31 / RM07II31
MIK1 / RM07IK31
MIE1 / RM07IE31
MIO1 / RM07IO31
MIV1 / RM07IV31 -> RM07IVW1
MIW1 / RM07IW31 -> RM07IVW1
MIQ1 / RM07IQ31 (only > 2.1)
MIM1 / RM07IM31 (only > 2.1)

Cause and prerequisites

The transfer of field T159B-XICHA is missing in module RM07IBDC.

Solution
Editor SE38 -> MODUL RM07Ixxx -> for Release 2.1* where xxx stands for the respective program under 'Sysmtom'.
Editor SE38 -> MODUL RM07IBDC -> approx. line 2190 for Release 2.2*/3.0*

SAP Note 23723 - Creating WBS from a ref. does not copy plan.values

Symptom:

When you create a work breakdown structure (WBS) from a reference (CJ01), in other words by copying a WBS, the cost/revenue plan values of the reference are not copied.

Cause and prerequisites

This function is not available in R/3-3.0.

Solution
The created WBS must be planned again.

SAP Note 23718 - Generation of an incorrect matchcode

Symptom:

After an information structure generation, the required matchcode is not created on the selection screen of the respective standard analysis. Instead, a different matchcode is generated. For example, in some cases, the matchcode for quotations is processed instead of the matchcode for orders, if the sales order number is a characteristic of the information structure.

Other terms

Matchcode, info structure, F4, input help, search help, standard analysis

Reason and Prerequisites

The matchcode object is not always unique, a dialog to choose the required matchcode object is not supported.

Solution
You can force the required matchcode object by the following modification in the module for determining the matchcode object. Please note that this matchcode object then becomes effective for all information structure fields with this check table (in the above example VBAK). That is, in the example, the matchcode is also processed for orders, if quotations are meant.
Insert an entry in the include LV12BU02 in the CASE query:
CONDENSE TAB_FELD NO-GAPS.
CASE TAB_FELD.
WHEN 'XXXXYYYYY'. "<------ new
MATCHCODE_FOUND = 'X'. "<------ new
MCD_MATCHCODE = 'ZZZZ'. "<------ new
WHEN 'MARAMATNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MAT1'.
WHEN 'KNA1KUNNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'DEBI'.
WHEN 'MCHACHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'MCH1CHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'LFA1LIFNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'KRED'.
WHEN OTHERS.
* MC-Datei finden
SELECT * FROM DD27S
Where: 'XXXX' is the name of the check table (example: VBAK)
'YYYYY' is the name of the check table field against which the checks are run (example: VBELN)
'ZZZZ' is the name of the matchcode object which should be forced (example: VMVA)
Generate program SAPLV12B.
Regenerate the standard analyses and planning screens using the report RMCSISGE (or RMCSISGN).

SAP Note 23716 - Missing fields in transfer structure BALTD

Symptom:

Depending on the Release, asset table fields (for example, the tax jurisdiction TXJCD) are missing in the internal structure BALTD.
Key words: Transfer structure, RAALTD01, RAALTD11

Cause and prerequisites

Incorrect delivery.

Solution
How can these fields be included in the structure?
Program RAALTD01 or RAALTD11 (as of Release 2.2) can generally process enhancements or reductions in the interface structure.
The customer can therefore insert a missing field at any appropriate position without requiring a program change.
You cannot tranfer the fields of ANLU.

SAP Note 23704 - No standard F4 help on 'Reason of movement'

Symptom:

There is no standard F4 help available for field 'Reason of movement'.

Cause and prerequisites

There is still an old help function module implement for the event .

Solution
Make the following changes to the flow logic of screens SAPMM07M 0210, 0310 and 0410 with SE51 and regenerate the screens:
PROCESS ON VALUE-REQUEST.
FIELD MSEG-GRUND MODULE GRUND_HILFE. 'OLD
* FIELD MSEG-GRUND MODULE GRUND_HILFE. 'NEW
*eject
As a result, MODUL GRUND_HILFE is no longer called and the standard F4 help is available.

SAP Note 23697 - Problem with ABAP/4 statement "call system"

Symptom:

ABAP/4 statement "call 'SYSTEM'" supplied in version 2.2D+ Status -1 in SYST-SUBRC.

Cause and prerequisites

Oracle libraries use 'SIGCHLD'.

Solution

In some Oracle releases, the runtime environment supports the signal 'SIGCHLD' and clears the exit status of all scheduled processes.
On the other hand, the pclose called by the kernel for the ABAP/4 statement "call 'SYSTEM'" expects the process to deliver its exit code. Pclose provides an error (-1) which is returned by the kernel to ABAP/4. Errno ECHILD occurs internally. The problem appears in different versions on different platforms. It also depends on the access mode in the database (in one system, it can sometimes occur only on a couple of application servers).

A general solution is not possible. "call system" should not be used and is not released by SAP for customer applications.

The following implementation approaches are possible:

1. Avoid supported and documented calls, as, for example, CPIC, RFC and external batch.

2. Furthermore, if "call system" should be used: Do not call up the return code and document the successful exit in the standard output.

3. Since the problem occurs only when connections to BEQUEATH are made, doing the work in TWO_TASK mode (TCP/IP) creates the possibility of limiting the creation of 'ZOMBIE' processes.

SAP Note 23694 - RFVBER00: Termination CONNE_IMPORT_WRONG_COMP_LENG

Symptom:

RFVBER00 terminates with runtime error CONNE_IMPORT_WRONG_COMP_LENG.

Cause and prerequisites

Update terminations from former releases are still in the system, the document structures have been extended in the meantime (BSEG was extended) so that the IMPORT of the old data no longer fits to the new structures.

Solution
None.
In RFVBER00, only select the data from the current release in RFVBER00.
Generally, update terminations should be checked, updated and deleted on a daily basis using transaction SM13.

SAP Note 23690 - Special characters in keys (names)

Symptom:

When you use unsuited special characters in keys, problems can occur during the database access or matchcode search. This particularly applies to the project numbers of the work breakdown structure (WBS), project definition and WBS element. However, you should also avoid the special characters in other keys, for example, network (during external number assignment) or PS text.

Cause and prerequisites

The special characters are interpreted by the database system or basis system and have a special meaning there (see "Solution")

Solution

Please avoid the following special characters in keys:

• . Period is used as a field separation character during the matchcode search.

• * Asterisk is in certain cases interpreted as a mask (wildcard).

• ? Question mark is in certain cases interpreted as a mask (wildcard).

• % Percent is interpreted as a mask (wildcard) by the DB system for as many characters as desired.

• _ Underscore is interpreted as a mask (wildcard) by the DB system for an individual character.

SAP Note 23688 - PA-TRV: customer enhancement screen, user data

Symptom:

In PR01 (Maintain trip data) a customer wants to use the user data
screen. However, there is no documentation on this.

Cause and prerequisites

In 2.1 and 2.2, the documentation can be called up using 'Extended
help'. As of 3.0, you should read CHAP.REIS9999 in RPDSYS00.

Solution
The documentation reads as follows:

Customer enhancement screen
-------------------------
In HR-TRV, it is easy to create an individual screen which meets the
specific requirements of your company.

The internal table USER can be used for this purpose. This table is
written to the database by the standard SAP programs and read there.
This table can be modified by users: it has been specially devised for
applications particular to individual customers.

To do this, you will need to have basic knowledge of the SAP
development environment. This includes knowledge of ABAP/4, DDIC,
Screenpainter.
In this way, you can enter information which can be used again and again (ranging from the reports of sales reps. in the pharmaceutical and insurance industries) to facts determined with regard to customer- specific subsequent systems.

Example: services that can be billed to customers.

SAP Note 23687 - MMBE: GR blocked stock

Symptom:

The stock overview (transaction MMBE) displays the GR blocked stock. This stock is calculated from the total of all goods receipts for purchase orders into GR blocked stock of this material (movement types 103 and 106) for which the transfer into the own stock or the return delivery to the vendor (movement types 105 and 104) was not yet entered. In this case, only those order items are considered whose goods receipt to the stock is to be posted to the material master. No special stocks are considered except for the vendor consignment stock.

Cause and prerequisites

This function is defined this way. The GR blocked stock should contain the stock quantity which can be used without restrictions after its release.

Solution
If the GR blocked stock is to be calculated differently, a modification is required.

SAPNote 23676 - Terms of payment in billing document: Output your own texts

Symptom:

With this modification, it is possible to output your own texts instead of the terms of payment texts generated from table T052.

Cause and prerequisites

Modification
Consider attached Note 170183.

Solution

1. Entering your own text:

• Transaction SO10

• Text name z.B. ZB01 (Text name should be 'TermsOfPaymentKey')

• Text ID SDTP

• Language, for example D

• Create function key

• Enter and save text

2. Form for billing document printout (standard: RVINVOICE01) change:

• Transaction SE71

• Form, for example, RVINVOICE01

• Language, for example D

• Change function key

• Goto - Window

• Choose TERMS

• Edit - Text elements

• CN requirements /: IF NE 'O'. (*)
  AS
  /
  /
  /: ELSE. "neu
  /: INCLUDE OBJECT TEXT ID SDTP PARAGRAPH AS "neu
  /: ENDIF.
  AS ,,

--> The IF Statement in line (*) must be adjusted in such a way that the program reaches the ELSE statement and consequently prints the term of payment you entered.

SAP Note 23667 - Account no. print wrong with summarization 3

Symptom:

When summarization level 3 is used in the balance interest calculation for G/L accounts, only one account number is displayed per page.

Cause and prerequisites

Program error

Solution
Insert the lines marked with "S11KQQQQ below in progrma RFSZIS00
.
.
.
AT NEW SKA1-SAKNR.
*---------------------------------------------------------------------*
* Gruppenanfangsverarbeitung: Konto *
* Initialisierungen pro Konto *
*---------------------------------------------------------------------*
CHECK GUELTIGER-BUKR-FLAG = 'X'.
CHECK GUELTIGES-VZSKZ-FLAG = 'X'.
FORMAT RESET.
IF VD-STUFE < '3'.
NEW-PAGE.
BLATTNRP = 0.
ELSE. "S11KQQQQ
FORMAT COLOR COL_NORMAL INTENSIFIED. "S11KQQQQ
WRITE: / SY-VLINE, 2 SKB1-BUKRS, "S11KQQQQ
7 WAVZSKZ, "S11KQQQQ
18 WAWAERS, "S11KQQQQ
24 SKA1-SAKNR, "S11KQQQQ
36 SKAT-TXT20, 81 SY-VLINE. "S11KQQQQ
WRITE: / SY-VLINE, TEXT-036, PRINTVZUNTER DD/MM/YYYY, "S11KQQQQ

TEXT-002, PRINTVZOBER DD/MM/YYYY, 81 SY-VLINE. "S11KQQQQ
SKIP 1. "S11KQQQQ
WRITE: / SY-VLINE, 81 SY-VLINE."S11KQQQQ
"S11KQQQQ

ENDIF.


PERFORM DEBUGGING-CHECK1. "pruefen ob Konto zu debuggen ist
PERFORM DEBUGGING-MODE USING '0490'. "Konto wird bearbeitet
.
.
.
Insert the lines marked with "S11KQQQQ below in program RFSZIS01, subroutine UEBERSCHRIFT_FZ
FORM UEBERSCHRIFT_FZ.
.
.
.
CASE PRINT_STATUS.
WHEN '1'. " POSTENUEBERSCHRIFTEN
FORMAT COLOR COL_HEADING INTENSIFIED.
WRITE: / TEXT-100.
ULINE.
IF VD-STUFE < '3'. "S11KQQQQ
FORMAT COLOR COL_NORMAL INTENSIFIED.
WRITE: / SY-VLINE, 2 SKB1-BUKRS,
7 WAVZSKZ,
18 WAWAERS,
24 SKA1-SAKNR,
36 SKAT-TXT20, 81 SY-VLINE.
WRITE: / SY-VLINE, TEXT-036, PRINTVZUNTER DD/MM/YYYY,
TEXT-002, PRINTVZOBER DD/MM/YYYY, 81 SY-VLINE.
SKIP 1.
WRITE: / SY-VLINE, 81 SY-VLINE.
ULINE.
ENDIF. "S11KQQQQ
FORMAT COLOR COL_HEADING INTENSIFIED OFF.
.
.
.

25.2.11

SAP Note 23666 - Negative list: Asset types/classification

Symptom:

Fixed assets are currently classified in asset classes from a business point-of-view. Classification from a technical point-of-view (for example, according to types of objects) or an interface to the SAP classification is not provided.

Additional key words

Class, asset, material class

Cause and prerequisites

*

Solution
*

SAP Note 23663 - Negative list: Takeover of historical transactions

Symptom:

During old assets data takeover into Asset Accounting, no historical transactions can be entered.

Cause and prerequisites
Solution

There are no current development plans for this.

Additional key words

AS91, RAALTD01, RAALTD11, negative list

SAP Note 23656 - No transport connection for condition records

Symptom:

The transactions for condition record maintainance have no transport connection although they are called from some Customizing applications.

Cause and prerequisites

The condition records have the characteristics from the administration master data or message master data rather than the characteristics from the customizing data.

Solution
Manually unite condition records in the target system.

SAP Note 23649 - Cost comp. on main and lower lvl in costing reports

Symptom:

The cost elements of the main level and lower level are 'incorrectly' displayed in the costing reports 7EOE_002 and 7EOE_003. The lower level displays the total of the raw materials from the lower level and main level, however, the display of the raw materials is completely missing on the main level.

Cause and prerequisites

This is defined that way.

Solution
According to logic in R/3, only those costs are added to the main level which result directly from the value added (for example, indirect costs and external costs). Therefore, the entire raw material costs are displayed on the lower level.
If you require a distinction between the raw materials and the semi-finished products/assemblies, you can recognize the distinction via the cost element report in itemization (7U0E_004).

SAP Note 23642 - Description of pxanew and pxastat

Symptom:

There are two files are in the directory /usr/sap//D*/work with the names "pxanew" and "pxastat". The names of ABAP/4 programs which are loaded into the program buffer (the so-called PXA buffer) when the system is next started are listed in these files.
The programs listed in "pxastat" are loaded first, then those in "pxanew". "pxanew" is then copied to "pxastat" and "pxanew" is deleted. When shutting down the system normally, the names of all programs in the buffer are entered in the file "pxanew".
Thus, the programs listed in "pxanew" are those that were used in the last system instance. The files listed in "pxastat" are from the previous instance. This prevents the PXA statistics being lost if the system is started and then immediately stopped again.

Cause and prerequisites

Without this "preload" process, system response time would be initially very slow until the relevant programs were loaded back into the buffer.

Solution
*

SAP Note 23635 - T510J: values of Value column 100 times too small

Symptom:

After importing the FCS 3.0, the values of the column Value in table T510J are 100 times too small.
This applies to all clients except client 0.

Cause and prerequisites

It is possible that XPRA RPU30009 ran twice in the FCS System

Solution
You can partially restore the table entries using the following report:
Report chT510j.

tables: t510j.

select * from t510j
client specified
where mandt <> '000'
order by primary key.

t510j-wert1 = t510j-wert1 * 100.
update t510j client specified from t510j.

endselect.

Please remember that the previous division might have rounded values off, and that these cannot, therefore, be restored with the above report. This is always the case if the value is not a whole number. These fractions disappear after the two divisions by 100.
This means that you should check the table entries manually after running the report!

SAP Note 23633 - Carry Forward Budget for Projects/Orders Not Allowed

Symptom:

In Release 3.0, you cannot automatically transfer remaining budgets that were not used within the year-end closing into the new year.

Cause and prerequisites

This is caused by missing functions in Release 3.0.

Solution

If a budget is transferred into the following year for a few orders or WBS elements only, you can carry out the carry forward manually as return/supplement, original budget change or (only for WBS elements) as a transfer, if necessary.

In Release 3.1G, two new transactions in the standard R/3 System allow a carry forward budget for projects and orders:

1. Transaction KOCO: Carry Forward Order Budget

The carry forward budget is available for CO internal orders and maintenance orders.

Budgets of a closed fiscal year that are not used up can be transferred into the following year.

The carry forward budget can be executed repeatedly in succession and it can run in the test run and in the production run. The differences to the last run are posted in each case. A detail list is issued optionally.

Selecting the orders is carried out via selection variants.

The budget of an order that is not used up results from the annual budget minus the actual costs. Commitments and sales revenues are not considered. Credits from settlements are only considered if the order in question was settled to another order, WBS element, network or network activity (elimination of internal business volume).

If the calculated value is negative, the program checks whether a carry forward run has already occurred before and writes the possibly existing carry forward amounting to the calculated value back into the initial year. The budget already transferred is retrieved as a maximum in this case. It is not possible to transfer a newly assigned budget into a previous year. With this an "actual" negative carry forward budgets are not possible.

An error log is issued in the case of an error. No carry forward occurs for the order in question.

For reasons of performance, you should execute the program in the background if the used selection variant contains many orders.

No active availability control occurs.

2. Transaction CJCO: Project Carryover Funds

Budgets of a closed fiscal year that are not used up can be transferred into the following year.

The carry forward budget can be carried out repeatedly in succession and it can run in the test and in the production run. The differences to the last run are posted in each case. A detail list is issued optionally.

Selecting the projects is carried out via the logical database of the Project System. The selection criteria can be restricted as desired using dynamic selections. However, the database profile is predefined for technical reasons and it cannot be changed.

The budget of a WBS element that is not used up results as follows:

Budget not used up = Annual budget
- Distributed value
- Actual costs

The actual costs contain the costs of the WBS element with budget and the actual costs of all assigned orders, all networks and all network activities as well as the actual costs of the lower-level WBS elements without budget.

Sales revenues and commitments are not taken into account. In contrast to the availability control, planned costs of apportioned orders and networks are also not included in the calculation of the carry forward. Reductions from settlements are only taken into account if the WBS element in question (or order, network or network activity) was settled to a WBS element, an order, a network or network activity (elimination of internal business volume).

If the calculated value is negative, the program checks whether a carry forward run has already occurred previously and it transfers the possibly available carry forward that amounts to the calculated value back into the initial year, if necessary. The budget already transferred is retrieved as a maximum in this case. It is not possible to transfer a newly assigned budget into a previous year. With this an "actual" negativ carry forward budgets are not possible.

An error log is issued in the case of an error. No carry forward occurs for the affected WBS element.

If a carry forward budget is carried out on a WBS element of a lower level, the corresponding value is also transferred into the following year on the higher-level WBS elements to ensure that the distributed values of the higher-level WBS elements are not higher than the budget available there.

Since the balance of the carry forward (budget minus distributed value) resulting from it is equal to zero on the higher-level WBS elements, only the carry forward of the lower WBS element is displayed in the detail list. For the same reason, a status validation is also only carried out for the lower WBS element in this case: it is checked whether the activities "Carry forward budget sender (GJA)" and "Carry forward budget receiver (GJA)" are permitted.

If the projects for which a carry forward is carried out contain many WBS elements or if you want to edit a large number of projects, you should execute the program in the background, due to reasons of performance.

No active availability control occurs.

As of Release 3.0D, the function described above is available via SAPSERV3 as a preliminary delivery.
The required files for transport request P30K160981 (old: P30K160981) are available in the directory /general/R3server/abap/note.0023633. See Note 13719 on how to pick up the files.

In addition, execute the following actions in your system manually:

a) Create a message for message class BP with number 595 using Transaction SE91:

Short text: 'Live run only possible for closed financial years'

Long text:
Cause
You tried to close the current fiscal year, or a future one, in the production run.
As you cannot reverse the activity, you may only close a fiscal year which has elapsed.
System response
The system switches automatically to the test mode.
What to do
Start the transaction again, if required, for a fiscal year which has elapsed.

b) Call Transaction SE37 and choose 'Utilities -> Repair funct. group -> Compare funct. group'. Enter AIPA as function group. Select the two top items (AIPA_CHECK_MEAS_YRCHG and AIPA_CHECK_MEAS_YRCHG_PREREAD) and choose 'Repair'. (If your logon language is not German, you must maintain in the *original* language).

c) Activate the two function modules AIPA_CHECK_MEAS_YRCHG and AIPA_CHECK_MEAS_YRCHG_PREREAD. You must first change the source code of function module AIPA_CHECK_MEAS_YRCHG_PREREAD as specified under "Corrections" (see also the next point). If in doing so problems with the editor lock occur proceed according to related Note 112111.

d) Make the source code changes specified under "Corrections".

Insert the lines marked with "<=== INSERT and delete those marked with "<=== DELETE.

Note the specified Releases to which the corrections apply in each case.

e) For Releases 3.0D and 3.0E implement Note 50457 first.

Note that these corrections are modifications which may be overwriten by applying Hot Packages and have to be edited afterwards to avoid syntax errors.

If you work with releases and do not want to adjust them manually, you must implement Note 93841 (Release 3.0D - 3.0F, 3.1G - 3.1H, 4.0A) in addition, which ensures that releases of the old year are reduced according to the budget during carry forward budget. However, no carry forward of the releases to the new year takes place. The note is required to avoid error messages caused by too high releases in the old year within budgeting.

Additional key words

budget forwarded, fiscal year change, fiscal year end, budgeting, budget

Subscribe to: Posts (Atom)

Search

Top 10 SAP OSS Notes

• SAP OSS Notes

  Get the SAP OSS Notes widget and many other great free widgets at Widgetbox ! Not seeing a widget? ( More info )
• SAP Note 22640 - ABAP/4 query: Add. structures in logical databases

  Symptom: Question: How can structures which are connected to logical databases as an extension be used by ABAP/4 query? Some logical databa...
• SAP Note 16083 - Standard jobs, reorganization jobs

  Symptom: There are a number of jobs that must periodically run in a live R/3 installation, for example, to delete outdated jobs or spool o...
• SAP Note 24832 - Pricing rules / TVCPF

  Symptom: Depending on the situation, the system should redetermine conditions or not. For this, a differentiated control is required, for ex...
• SAP Note 18023 - Jobs EU_INIT, EU_REORG, EU_PUT

  Symptom: What are the jobs EU_INIT (program SAPRSEUC), EU_REORG (program SAPRSLOG), and EU_PUT (program SAPRSEUT), which are automatically...
• SAP Note 11162 - Invoice split criteria in billing document .

  Symptom From a number of deliveries or sales orders more than one billing document is created. Cause and prerequisites The invoice split ma...
• SAP Note 25528 - Parameter rdisp/max_wprun_time

  Symptom: The meaning of parameter rdisp/max_wprun_time is not clear. Other terms TIME_OUT, timeout, SY 098, Time limit exceeded, instance p...
• SAP Note 22559 - BTCI material - Add. costing functions are impossible

  Symptom: Basic data transfer for the material master with standard batch input program RMMMBIM0. The field contents for the additional cos...
• SAP Note 28869 - Printout of changes although field not print-relevant

  Symptom: When a field (item or header) is changed in a purchasing document, a change message is generated although the field is non-print-...
• SAP Note 11104 - PPPR: General note on printing production orders.

  Symptom Lack of knowledge about the general printing procedure in PPSFC. Other terms Print, production order, CO04, CO04N, shop paper printi...

Labels

\ abap account assignment Allocation authorization book books certification CO controlling areas CPIC download free GA715 help view Help view prior index series javascript:void(0) LIST_ILLEGAL_PAGE Master data ME51 Number Ranges pdf rapidshare release strategy RKCORR01 SAP SAPcomm SAPFAX.DLL SAPLPD.EXE Service submit T800 table unknown

• ABAP
• SAP
• Help View
• Certification
• Books

Latest Posts

Subscribe Enter your email address: Delivered to your inbox instantly

Articles

• Home
• Where to find SAP OSS NOTES?
• How to implement SAP OSS NOTES?
• What is SAP OSS NOTES?
• How to create new SAP OSS Note?
• Top SAP Downloads