SAP OSS Notes: 10/9/11

13.10.11

SAP Note 28463 - SE06 Setting up the Workbench Organizer

Symptom:

Operational ambiguities

Cause and prerequisites

The system is not initialized for the Workbench Organizer

Solution

Using SE06:
This transaction, for setting up the system for the Workbench Organizer has a few preconditions:

What is the system status (depends on the past) ?

Was the system freshly installed ?

Was the system created by a database copy ?
This option has more far-reaching consequences than the installation or the option: "modified with the Workbench Organizer". In addition, all repairs are completed and the tasks and requests which did not originate in the current system are also completed. The requests that can be transported are not exported.
Furthermore, the control tables for the upgrade and transport are initialized.

Has the Workbench Organizer already been used ?
By 'use', we mean objects have been changed with the Workbench Organizer. Tasks or requests have been created.

Which configuration of the systems is to be created (where are the objects created/changed and where are they to be transported to) ?

Individual system
Only 1 system is installed from which no objects should be exported. Everything required to import a new maintenance level or release is generated.

Test and production system
A system group should be created which consists of a test system (create, change and test objects) and a production system.

Any configuration
You can define another system group here. In this case, the tables for the definition of the system group must be individually maintained. A consultant should be brought in to model any non-standard system environment. A check function exists to aid the correct definition. A message log is generated and the long texts can be displayed using help.

3 system group (from Release 3.0C)
The system group consists of a development system (create, change objects), a quality assurance system (test objects) and a production system.
The requests from the development system should first be imported into the quality assurance system before they are imported into the production system.

After entering the configuration and the respective systems, a list of the table entries that need to be generated is displayed. You can save the settings with the function Continue.
If this changes the consolidation methods of the system, a corresponding information popup appears.
Typical problems when using SE06

The creation of a transport layer is refused because at least one of the specified systems is not listed in TSYST.
Enter the required systems in the maintenance of TSYST and save the newly entered systems.

When maintaining TASYS - Do you allow non-standard transports or not?
Generally, they should not be allowed.

Problems with the requests
No requests are deleted. All requests are retained. Repairs and external requests are completed when using "Database copy".
Note that problems occur with the number range of the requests if frequent database copies are made. If, for example, you imported a request from a system E11 and then rename the system E11, then the usable number range begins with the highest E11 request.

SAP Note 28461 - FI-SL: Client copy between systems

Symptom:

The client transport between systems in Release 3.0 and 3.0A is incomplete for the component FI SL (previously FI GLX). In extreme cases, syntax errors occur in programs (for example, in SAPLGLIN, SAPLGIV1 and so on).

Cause and prerequisites

Generated objects (missing entries in table CCCEXIT).

Solution
Start the programs RGBCFL01 and RGUGVTR0 in the target system.
Caution: These programs generate program code. This program code is client-independent. The programs must therefore not be started in a currently productive system, not even if the current client is not being used productively but there is another productive client within the same system.
It is therefore best to start both programs in the evening or at night when there are no online or background update runs being executed.

Additional key words

Client transport between systems, FI-SL, FI-GLX, SCC0, SCC1, SCC2, RSCLICOP

SAP Note 28460 - Termination KD039 object type is not supported

Symptom:

When creating a production order, error message KD039 "Object type is not supported" is issued.

Cause and prerequisites

A collective order contained a co-product.

Solution
A collective order together with manufacture of co-products on subordinate manufacturing levels is not supported.
Correction in the ABAP Include LCOSDFB1 and new message in table T100 for the message ID 'CO' with message number 647. The text reads: 'Manufacture of co-products is not permitted in the collective order'

Additional key words

CO01

SAP Note 28457 - DBIF_RSQL_INVALID_REQUEST during cluster access

Symptom:

An ABAP runtime error DBIF_RSQL_INVALID_REQUEST occurs within an R/3 application (for example SE16, when copying clients with RSCLXCOP). The last edited table was a logical cluster table (for example, BSEG or BSET). An entry is found in the system log:
Errors ??? on compression/decompression (c2_mk)
In the respective dev file (dev_db for releases prior to 3.0, dev_w for releases >= 3.0) there is a line
db_rclu2: damaged cluster record, TDE(name BSET, len 14, entrycnt 0)

R3trans terminates when accessing a logical cluster table (for example, BSEG), in the log file (trans.log) you find the text:
db_rclu2: damaged cluster record, TDE(name BSET, len 14,entrycnt 0)
[FILE dbrclu2, LINE ....]
cluster: RFBLG key: .......... [FILE dbrclu2, LINE
....]
DBI LOG (BZW): error ??? on compression/decompression using c2_mkdir
[FILE dbrclu2, LINE ....]
2EETW150 sap_dext called with msgnr "900":
2EETW000 Internal error in DB interface
4 ETW000
2EETW000 ---- db call info ----
2EETW000 function: db_setget
2EETW000 fcode: RT_GET
2EETW000 tabname: BSEG
2EETW000 keylen: 0
2EETW000 key:
2EETW000 ok fetches: 0
2EETW000 last entry:
4 ETW000
4 ETW000 ROLLBACK (...).

There are various other errors whose have the same symptom - the error message "Error on compression / decompression". Specific to this problem is that the error occurs when executing the dbrclu2.c function c2_mkdir() and that it appears as ???:
Error ??? on compression/decompression(c2_mk)
or
error ??? on compression/decompression using c2_mkdir
A further important indication is the specification
db_rclu2: damaged cluster record, TDE(name .., len 14, entrycnt 0)
in dev file or in the R3trans log file.

In contrast to other decompression errors, the data is correct in the database, the error is in the cluster interface. Also, the error is not destructive!

Cause and prerequisites

The record to be read (for example, BSEG-) was written to one update level but in the meantime, a newer release was installed and the number of fields in the table (BSEG) has been increased.
Logical cluster tables have the advantage that appending new fields takes place without problems, no immediate conversion is executed. The conversion is carried out 'on-the-fly' during the first access to physical cluster records which contain old logical records.
Up to and including Release 3.0A, this conversion (within the cluster interface) contains an error which causes the above error in certain cases.

Solution
Corrected in Release 3.0B. If necessary, a patch can be created (R3trans and disp+work must then be exchanged).

For releasse 30A, dw.CAR (contains disp+work and rsyn.bin) and r3trans.Z are available on sapserv3 and sapserv4 in the patch directories
~ftp/permanent/patch/30A/.
See note 19466 about transferring patches.

Additional key words

R3trans, SE16, SE17, clusters, BSEG, BSET, DBIF_RSQL_INVALIDREQUEST

SAP Note 28456 - Credit memos for billing plan

Symptom:

Summary

Symptom

A credit memo request was created for the billing plan with reference to a billing document. This uses pricing procedure PSER01.
However, the credit memo that is created later works with pricing procedure RVAA01. The pricing is incorrect for this reason.

Cause and prerequisites

The pricing procedure was determined from the order type for the order-related billing document, and not transferred from the sales order.

Additional key words

VF01

Solution

Corrected in 3.0B

Header Data


Release Status:	Released for Customer
Released on:	31.10.1995 23:00:00
Master Language:	German
Priority:
Category:
Primary Component:	SD-BIL-IV-BP Billing Plan

Affected Releases

Software Component	Release	From Release	To Release	And subsequent
SAP_APPL	30	300	30A

SAP Note 28463 - SE06 Setting up the Workbench Organizer

Symptom:

Operational ambiguities

Cause and prerequisites

The system is not initialized for the Workbench Organizer

Solution

Using SE06:
This transaction, for setting up the system for the Workbench Organizer has a few preconditions:

What is the system status (depends on the past) ?

Was the system freshly installed ?

Was the system created by a database copy ?
This option has more far-reaching consequences than the installation or the option: "modified with the Workbench Organizer". In addition, all repairs are completed and the tasks and requests which did not originate in the current system are also completed. The requests that can be transported are not exported.
Furthermore, the control tables for the upgrade and transport are initialized.

Has the Workbench Organizer already been used ?
By 'use', we mean objects have been changed with the Workbench Organizer. Tasks or requests have been created.

Which configuration of the systems is to be created (where are the objects created/changed and where are they to be transported to) ?

Individual system
Only 1 system is installed from which no objects should be exported. Everything required to import a new maintenance level or release is generated.

Test and production system
A system group should be created which consists of a test system (create, change and test objects) and a production system.

Any configuration
You can define another system group here. In this case, the tables for the definition of the system group must be individually maintained. A consultant should be brought in to model any non-standard system environment. A check function exists to aid the correct definition. A message log is generated and the long texts can be displayed using help.

3 system group (from Release 3.0C)
The system group consists of a development system (create, change objects), a quality assurance system (test objects) and a production system.
The requests from the development system should first be imported into the quality assurance system before they are imported into the production system.

The creation of a transport layer is refused because at least one of the specified systems is not listed in TSYST.
Enter the required systems in the maintenance of TSYST and save the newly entered systems.

When maintaining TASYS - Do you allow non-standard transports or not?
Generally, they should not be allowed.

Problems with the requests
No requests are deleted. All requests are retained. Repairs and external requests are completed when using "Database copy".
Note that problems occur with the number range of the requests if frequent database copies are made. If, for example, you imported a request from a system E11 and then rename the system E11, then the usable number range begins with the highest E11 request.

SAP Note 28451 - Reconcilliations reporting

Symptom:

There are a number of reason why the reconciliations reporting has been redelivered.
1) The columns were too small to hold large values. There can of course be some very large values in these columns.
2) To deal with late payments to leavers the adjustments were not reacting correctly.
3) Where someone is a starter then we attempt to add their P45 details to the adjustments column. If however their P45 details are not input until after their first payroll period has ended (and been reconcilled), then the input figures will not be picked up as adjustments.

Cause and prerequisites
Solution
Please import the transport files K021939.KIS and R021939.KIS from SAPSERV3. They can be found in directory /dist/permanent/note.28451

SAP Note 28450 - Change option for cost price

Symptom:

The cost price was set as changeable in Customizing. When trying to change this in change mode, you get the error message
'Requirements are not fulfilled'

Cause and prerequisites

Condition VPRS uses requirement 004.
This does not work correctly in change mode.

Solution
corrected in 2.2G/3.0B

Additional key words

VA02 VPRS

SAP Note 28449 - Rebates: Message 'Missing source for screen 1501'

Symptom:

One of the following messages appears when maintaining the rebate agreement:
A Program "SAPMV13A": Missing source for screen "1nnn".
OR
V0102: Flow control: Entry SAPMV13A, SEE2, B1, *, 1601, * is missing
OR
The incorrect screen was offered for maintainence. (The screen number
is incorrecly between 1001 and 1999 and not 6001 to 6999).

Cause and prerequisites

Program error

Solution

Change table T681S with transaction SE11. Select the field 'Table maintenance allowed'. Activate the table.

Edit table T681S with transaction SM31. Please use CAUTION when making the change. The corresponding entries can be found using the search argument 'E' '500'. Enter '6' in the first position of the field Screen for all the condition tables between '501' and '999' listed under 'E'.

Change table T681S with transaction SE11. Deselect the field 'Table maintenance allowed'. Activate the table.

Run program RV12A001 with usage 'E' and 'Reports and Screens'.

Change program LV12AU17.

Additional key words

Volume-based rebate
Transactions: VBO1, VBO2, VBO3

SAP Note 28448 - Batch split: Correction for confirming transfer orders

Symptom:

The confirmation of a WM transfer order was incorrectly updated in the delivery.

Cause and prerequisites

Program or handling error

Solution
Install the notes on batch split. Start the repair program.

As of 3.0B, repair program WSLIPS02 is available. As of 2.2G, correction program SDLIPS02 is available in 2.2 releases.

Enter the delivery number, and optionally the items to be corrected (default is 'All items'), the WM warehouse number and the WM transfer order number.

The program adjusts the picked quantity to the delivery quantity and sets the picking status to confirmed.

If there are main batch split items with incorrect data (cumulative weight/volume/quantity of all batch split items), start the correction program from note 20854.

SAP Note 28447 - Currency format in the invoice list

Symptom:

For invoice lists, various fields on the overview screen are not formatted currency-specifically.
For example, invoices in BEF are displayed with two decimal places.

Cause and prerequisites

Program error

Solution
corrected in 2.2G/3.0B

Additional key words

VF21 VF22 VF23 RV60A-MWSBP RV60A-KWERT_RL RV60A-MWSBP_RL RV60A-SUM_RL

SAP Note 28442 - Access sequences: defaulting the access fields

Symptom:

When maintaining the access sequences, the field material is not correctly defaulted for purchasing.

Cause and prerequisites

Program error.

Solution
Program change

SAP Note 28441 - Agreements: conditions are not displayed

Symptom:

When maintaining an agreement (rebate agreement or sales deal), the conditions disappear on the fast entry screen.
This only happens after an overview screen has been called and the last line of the overview screen was a header line.
The conditions then disappear on the fast entry screen.

Cause and prerequisites

Program error

Solution
Program change

Additional key words

Transactions: VB21, VB22, VB23, VBO1, VBO2, VBO3

SAP Note 28438 - Incorrect valuation at goods receipt

Symptom:

If a production order contained a planning plant different from the production plant, the valuation was carried out at goods receipt for the production plant, although posting was made to the planning plant. Consequently, posting to the plant activity account was made with the value of the material from the production plant.

Cause and prerequisites
Solution
Correction in ABAP/4 Include LCOSFU02

Additional key words

MB31

SAP Note 28437 - 06658 Not possible to determine a condition type

Symptom:

When you call the transactions 'Change/Display/Create Outline Agreement' or 'Change/Display/Create Purchasing Info Record', no pricing conditions are displayed if you branch to the 'Conditions' functionality. Error message E06658 is displayed: 'Not possible to determine a condition type'.

Cause and prerequisites

The pricing procedure for pricing is not maintained correctly.

Solution
At least one pricing condition to be used in the outline agreement or purchasing info record must be maintained in the pricing procedure (SAP standard is RM0000). The following conditions must be met in this case.
A pricing condition is selected if it is a master condition. Master conditions are conditions to which an access sequence is assigned. Furthermore, you may not define the master condition as statistical condition in the pricing procedure. The access sequence must be active. In the detail screen of the access sequence, you must specify condition tables that refer to the purchasing info record or outline agreement. The gross price in the standard SAP System, for example, is maintained as master condition. Access sequence PB01 is assigned to this condition in the pricing procedure. In the detail screen, it contains entries for condition tables 16, 17, 18, and other. These tables refer to the purchasing info record or outline agreement.

Please also see note 29661 for more information.

Additional key words

Pricing

SAP Note 28436 - Save WBS elements w/o required characteristic

Symptom:

You can save WBS elements although you have not entered values for the mandatory characteristics (required entry).
The system does display an appropriate error message, however, it still saves the data when the user cancels.

Cause and prerequisites

Program error

Solution
Correction

Additional key words

Project summarization, classification, SAP_KKR_CLASS
Transactions CJ01,CJ02,CJ11,CJ12,CJ20,CJ21,CJ23,CJ27,CJ2B,CJ2D

SAP Note 28435 - Maintaining project profile in work breakdown structure

Symptom:

CJ01, CJ02, CJ03
Edit project -> Project definition -> Profile details

The user cannot access the project profile from the work breakdown structure,
however the profile does exist.

Cause and prerequisites

Customizing view V_TCJ41 with unnecessary selection condition "task list usage".

Solution
In the standard system as of 3.0B: Selection condition "task list usage" deleted

Additional key words

TCJ41, V_TCJ41

SAP Note 28429 - TD427 Element PART_BOX window MAIN is not defined

Symptom:

Element PART_BOX window MAIN is not defined for layout set PM_ACT_TEMPLATE.

Cause and prerequisites

Delivery system failed to deliver PM_ACT_TEMPLATE 3.0A version.

Solution
The formular is expected to be in the 3.0b delivery system.
You can add the missing element to the formular as follows.
Trans: Se71
-> page windows
-> textelements

The text element you must add appears below. Please add it to the very
end of all textelements.
The solution is common for all Languages.

Additional key words

IW22,IW21,IW51,IW52 Maintenance Print IPRT

SAP Note 28427 - Cumulation of capacity in planning tables

Symptom:

The cumulation of capacity load in hierarchy work centers in the capacity leveling functions (graphical and tabular planning tables) does not give correct data in hierarchy explosion at the same time..

Cause and prerequisites

Problems occur only if a corresponding setting (profile) is carried out
in customizing. (No problems occur with standard settings).

Solution
Problem corrected in 3.0C (complete correction)

Additional key words

Capacity leveling, cumulation of capacity, planning table

SAP Note 28423 - Billing document (item) not transferred to CO-PA

Symptom:

Individual billing documents/billing items which are released from SD to FI Accounting are not passed on to CO-PA.
SD conditions are assigned to the CO-PA value fields in the Profitability Analysis configuration menu. Other billing documents/billing items are copied correctly.
The items that are not transferred have the item category 'TAB,' that is, individual purchase order.

Cause and prerequisites

Individual purchase orders have a value in the field VBRK-VBELV in the billing document. This is then interpreted in CO-PA as a billing document for a sales order and is therefore not updated, since the costs and revenues from sales orders must be passed on to CO-PA per settlement.
To check whether a sales order exists, the system needs to check the flag TKA00-RVAUF. If this flag is activated, sales orders can be CO-relevant as account asignment objects.
This additional check was not taken into account up to now, which resulted in the error described above.

Solution
The error was corrected with corrections P21K004632 and P22K005459 in Release 2.1K and 2.2E.
In Release 3.0 the error is corrected as of correction level 3.0C.

Additional key words

SD/CO-PA interface, billing document transfer

SAP Note 28422 - Dump ASSIGN LENGTH NEGATIVE for display loop screen

Symptom:

For the full screen representation of some screens in CATT, a dump is generated with ASSIGN LENGTH NEGATIVE.

Cause and prerequisites

This always occurs for screens with variable step loops and the following fields.

Solution
Change to the FORM routine FORM BLOW_LOOP in the include file MSCATF50 from line 19810. The function body must be completely replaced (up to line 20230).
Then insert the following program code:
FORM BLOW_LOOP.
DATA LOOPLINE LIKE IMPORT_F-LINE.
DATA NEWLINES TYPE I.
DATA NEWLREP TYPE I.
DATA REST TYPE I.
DATA RAHMEN_BOT TYPE I.
DATA LAST_USED_LINE TYPE I.
DATA BINPT_LINES TYPE I VALUE 22.

CHECK NOT IMPORT_H-VALP IS INITIAL.
DESCRIBE TABLE IMPORT_F LINES SY-TABIX.
* letzter Eintrag ist OKCODE mit line FF, also vorletzten Eintrag lese
SY-TABIX = SY-TABIX - 1.
READ TABLE IMPORT_F INDEX SY-TABIX.
* groesste Zeilennummer >= binpt_lines --> kein Platz
CHECK IMPORT_F-LINE < BINPT_LINES.
* Es ist vielleicht noch Platz auf dem Dynpro
IF IMPORT_F-LTYP = 'L'.
* Letzte Zeile ist ein Loop
NEWLINES = BINPT_LINES - ( IMPORT_F-LINE +
( IMPORT_F-LREP * IMPORT_F-LBLK ) - 1 )
ELSEIF IMPORT_F-FILL = 'R'
OR IMPORT_F-FILL = 'B'
OR IMPORT_F-FILL = 'T'.
* Letzte Zeile ist ein Block oder Rahmen oder TableControl
NEWLINES = BINPT_LINES - ( IMPORT_F-LINE + IMPORT_F-DIDX - 1 ).
ELSE.
NEWLINES = BINPT_LINES - IMPORT_F-LINE.
ENDIF.
* Anzahl der freien Zeilen bestimmt
CHECK NEWLINES > 0.
LAST_USED_LINE = BINPT_LINES - NEWLINES.
* Rahmenlinien am unteren Bildrand?
SORT IMPORT_F DESCENDING BY LINE COLN ASCENDING.
LOOP AT IMPORT_F
WHERE FILL = 'R'.
RAHMEN_BOT = IMPORT_F-LINE + IMPORT_F-DIDX - 1.
IF RAHMEN_BOT > LAST_USED_LINE.
NEWLINES = BINPT_LINES - RAHMEN_BOT.
LAST_USED_LINE = BINPT_LINES - NEWLINES.
ENDIF.
ENDLOOP.
SORT IMPORT_F ASCENDING BY LINE COLN.
* Loop kann vergroessert werden
* die kennung fuer den variablen Loop steht in lanf
LOOP AT IMPORT_F
WHERE LANF = IMPORT_H-VALP.
* Newlines kleiner Blockgroesse -> kein Vergroessern moeglich
IF NEWLINES < IMPORT_F-LBLK.
NEWLINES = 0.
LOOPLINE = 255.
EXIT.
ENDIF.
IF LOOPLINE = 0.
* alte Endezeile merken fuer die Verschiebung der nachfolgenden Felder
LOOPLINE = IMPORT_F-LINE + ( IMPORT_F-LREP * IMPORT_F-LBLK ).
IF IMPORT_F-LBLK > 1.
* fuer blockgreossen ungleich 1 die passende vergroesserung berechnen
REST = NEWLINES MOD IMPORT_F-LBLK.
SUBTRACT REST FROM NEWLINES.
NEWLREP = NEWLINES DIV IMPORT_F-LBLK.
ELSE.
NEWLREP = NEWLINES.
ENDIF.
ENDIF.
* loop vergroessern
ADD NEWLREP TO IMPORT_F-LREP.
MODIFY IMPORT_F.
ENDLOOP.
* alle nachfolgenden felder verschieben
LOOP AT IMPORT_F
WHERE LINE >= LOOPLINE
AND LANF <> IMPORT_H-VALP
AND LTYP <> 'O'.
ADD NEWLINES TO IMPORT_F-LINE.
MODIFY IMPORT_F.
ENDLOOP.
* Rahmen vergroessern
LOOP AT IMPORT_F
WHERE FILL = 'R'
AND LINE < LOOPLINE.
RAHMEN_BOT = IMPORT_F-LINE + IMPORT_F-DIDX - 1.
CHECK RAHMEN_BOT >= LOOPLINE.
ADD NEWLINES TO IMPORT_F-DIDX .
MODIFY IMPORT_F.
ENDLOOP.
ENDFORM. "BLOW_LOOP

SAP Note 28421 - Vendor evaluation - additional information log

Symptom:

ME61/ME63 vendor evaluation - calculation logs:
If you positioned the cursor on a line and chose 'Details' and there was no additional information for this line, either the system did not react at all, or an initialized popup was brought up.

Cause and prerequisites
Solution
A message is now issued if there is no additional information for the selected line.

SAP Note 28420 - Inspection lot creation for movement type 350

Symptom:

Goods movement is carried out with movement type 350 (TR blocked to quality). The QM inspection type assigned to inspection lot origin 08 is active for the material.
The material is posted correctly to the blocked stock, however, the inspection lot is technically managed in unallocated stock. That is, at the usage decision, you can carry out an inventory posting for lot quantity from unallocated stock.

Cause and prerequisites

Table T156S maintained incorrectly

Solution

Please make the following changes to table T156S using transaction SM31:
Assign inspection lot origin 08 (column ILO) to all lines of movement type 349 (column MvT).
Delete inspection lot origin 08 (column ILO) from all lines of movement type 350 (column MvT).

SAP Note 28419 - IS-HCO: No CO order created on admission

Symptom:

Settings have been made in IS-HCO that a CO order should be automatically created on admission. However, this does not (or not always) occur. Furthermore, no warning message appears.

Cause and prerequisites

This may be due to diverse causes. You are recommended to check the Customizing at any rate.
A special problem can be that fields required within CO order type maintenance for the field selection were not set to ready for input. This is actually not necessary for the order type used here.
A warning message does not seem useful. This warning message would appear at every admission, however the admitting department employee could not usefully processed it.

Solution
Correct any errors you find in Customizing. Set all fields of the corresponding order type to "entry". Using the function "create case-based order" you can subsequently create case-based orders for the corresponding cases.

Additional key words

Consulting

SAP Note 28418 - Problems when maintaining sales personnel

Symptom:

Problems when creating, changing or displaying sales personnel.

Cause and prerequisites

Missing entries in HR Customizung tables, particular if you are using SD without HR.

Solution

1. Complete copy of the HR tables from the standard client

Dialog control

Infotypes: T582A, T582S, T591A, T591S

Menus: T588A, T588B, T588C, T588D, T588T

Screen Header: T588I, T588J

Screen control: T588M

Infotype Events

Events: T529A, T529T, T529U

Reasons for event: T530, T530T

Infotype Personal Data

Marital status and title: T502T, T516T, T522G, T522T

Parts of name: T522N, T535N

Release 2.2 only: T502, T516, T522

Infotype Organizational allocation

Employee groups: T501T, also, from 3.0: T501

Employee subgroup: T503, T503T, also from 3.0: T503K

Personnel area and subarea: T001P, also from 3.0: T500P

Payroll area: T549A, T549T

Organization key: T527, T527A, T527O

2. Selective copy of HR tables from the standard client

The following entries must be available in the client (you may have to maintain this with transactions SM30/31 or copy from client 000):

Infotypes (Table T582A, from Release 3.0 View V_T582A):

Infotype Infotype/View

0000 Events I

0001 Org. Assignments I

0002 Personal Data I

0006 Addresses I

0105 Communication I

0900 Sales data I

Infotype menus/Info groups (table T588c, as of 3.0 View T588c):

Menu type Menu User-dep. Reaction Ref. I L1 Sales Personnel _ _ 00
M L1 Sales Personnel _ _ 00

Events

Table T529A:

Event Pl PG PS IGN FCh .. Status

L1 Create Sales Representative X X X L1 1 __ _ 3 1 _ X

Status ID

Copy table T529U

Reasons for event

T530 Copy for event L1

T530T Text for T530

Transaction properties (Table T588A):

Release 2.*:

Transaction code ITMEN MSMenu ActCat Data UIntf

PAL1 Create Sales Representative L1 P A L

PAL2 Display Sales Representative L1 A A L

PAL3 Maintain Sales Representative L1 P A L

From Release 3.0:

Transaction code MenTyp Menu ActCat Data UIntf

PAL1 Create Sales Representative M L1 P A L

PAL2 Display Sales Representative I L1 A A L

PAL3 Maintain Sales Representative I L1 P A L

Infotype menu (Table T588B, from 3.0 View V_T588B, maintan menu I/L1):

User gr. No Infotype

00 01 0000 Events

00 02 0002 Personal Data

00 03 0006 AAddresses

00 04 0001 Org. Assignments

00 05 0900 Sales Data

00 06 0105 Communication

Event menu (Table T588B, from 3.0 View V_588B_M, Menu M/L1 ):

User gr. No Event

00 01 L1 Create Sales Representative

Infogroups (Table T588D, Infogroup L1):

User grp. IGrModif No Operation Infotype Type

00 _ 01 INS 0001 Org. Assignment _

00 _ 02 INS 0002 Personal Data _

00 _ 03 INS 0006 Addresses _

00 _ 04 INS 0900 Sales data _

00 _ 05 INS 0105 Communication _

Personnel area, Personnel subarea: Table T001P, T500P

In IMG:

- Definition of personnel subarea ==> Adjust text

- Enterprise structure --> Assignment --> Personnel Administration -->

Assignment: Personnel area --> Company code

==> Enter the correct company code

Warning: The country groupings in T001P and T500P must be the same

Employee groups: Table T501, Text table T501T

Copy entry '1' (Active) (for each language)

Employee groups/subgroups:

Table T503K for Germany, copy employee subgroup DZ (Sales personnel) for USA employee subarea UZ, etc.

Table T503 Copy entry 1 DZ (1 UZ, ...) (1 --> Active (according to T501), DZ/UZ --> Sales personnel)

Warning: Country groups must match T500P

Table T503T Text for T503K

Marital status and title:

Title T522G, Text T522T

Marital status Text T502T

Religion Text T516T

Parts of name:

Academic title, additional words T535N

Country group dependent name formatting T522N

Organizational key:

T527, T527A, T527O Copy completely

Payroll areas: T549A

T549T Text for T549A

Select payroll area that is ot relevant (e.g. 99)

Screen Header:

T588I, T588I Copy completely

Screen control:

T588M, Entries: MP000200

MP000600

Infosubtypes (T591A)

Entries: 00061 (Infotype 0006)

00062

00063

01050001 (Infotype 0105)

01050002

01050003

01050004

01050005

01050006

01050011

Table T591S Text table for T591A

Actions to be carried out

Transaction PE03

Menu --> Characteristic --> Generate

- Do not enter a characteristic

- it doesn't matter what is checked

- on the subsequent screen:

- Do not enter a characteristic

- Generation type: '1'

Transaction PE03: Deactivation of position management

- Characteristic: PLOGI

- Decision tree: Change

- Set &PLOGI = ' '

- Generate

Transaction SM31 (from 2.2F)

Table T588J

Button 'View maintenance'

---> Generate all headers

Transaction SA38/SE38 (to 2.2E)

Execute report RPHGEN00

Transaction PA04 (Set up number range for object RP_PREL)

- Interval: 01

Additional key words

PAL1, PAL2, PAL3, SAles personnel, Employee, Representative, Sales Support

SAP Note 28414 - FI-SL: Allocation terminates during backgr. proc.

Symptom:

Error message: 00671 "ABAP/4 processor: CALL_FUNCTION_CONFLICT_TYPE"
The following error message is written to the job log:
"Type conflict when calling function module ENQUEUE_EGGLREFS in program SAPLKGA2;
In the interface of the function module, it was determined that only fields of a certain type may be specified under "RLDNR". However, the current field is of another field type".
Description: If you start an assessment or distribution of application FI-SL in the background, the background job terminates with the above error message or error cause. Online, the distribution or assessment can be executed without problems.
Transactions: GA15, GA35, GA2B, GA4B
Program name: SAPLKGA2; RKGAL000

Cause and prerequisites

Program error

Solution

If you cannot start the offsetting online, you must implement the correction specified below:

Additional key words

Allocation

SAP Note 28409 - Linking the purchasing display/change transaction

Symptom:

So far only the display/change transaction for the purchase order was activated.

Cause and prerequisites

Other document categories were not programmed.

Solution
See source code corrections

SAP Note 28406 - IP11,IP12: Copy maint. strategy with packages

Symptom:

When copying maintenance strategies, the maintenance packages should also be copied. In this case, the counters, number of packages, total cycle and smallest cycle are not copied onto the strategy detail screen.

Cause and prerequisites

Program error

Solution
Please correct the program code of program SAPL0IP1, in Include L0IP1O10.

Additional key words

Strategy table, T351, T351P

SAP Note 28402 - Terminat. during matchcode sel. for jurisdiction

Symptom:

During the matchcode selection for jurisdictions, a termination ASSIGN occurs with length 0 in program SAPLFHL1.

Cause and prerequisites

A jurisdiction structure with the overall length 15 was created in table TTXD.

Solution
Corrected in 3.0B. Advance correction:
Change program LFHL1TOP. Insert the following line at the end: DATA DUMMY.
Change program LFHL1U07. Insert the lines indicated with <<<<<<<<: .
.
* ------ Rest von GENFD = SPACE --------------------------------------
J1 = TTXD-LENG1 + TTXD-LENG2 + TTXD-LENG3 + TTXD-LENG4.
J2 = 15 - J1.
IF J2 > 0. " <<<<<<<<<<
ASSIGN GENFD+J1(J2) TO .
ELSE. " <<<<<<<<<<
ASSIGN DUMMY TO . " <<<<<<<<<<
ENDIF. " <<<<<<<<<<
.
.
Additional key words

Jurisdiction code, matchcode, FTXP

SAP Note 28401 - Table T459W is without contents

Symptom:

Table T459W is without contents.
This can cause a termination of transaction MD61.

Cause and prerequisites
Solution
Transfer on sapserv3:
You can import the missing data records with transport request A30K000469. Data file and cofile can be found on sapserv3 in the directory: /dist/permanent/Note.0028401.
Please proceed according to note 13719 during the import.

Additional key words

Transaction MD61

12.10.11

SAP Note 28399 - Incorrect time conversions of the standard values

Symptom:

Incorrect time conversions during cumulation of the standard values

Cause and prerequisites

The source code is not adapted when upgrading from 2.2 to 3.0.

Solution
Numerator/denominator relationship has been corrected.

Additional key words

Scheduling. cumulation standard_value

SAP Note 28398 - MI08: Incorrect posting period for several items

Symptom:

If you create a physical inventory document with 2 or more items and then post the count and the difference to this document in 1 step (MI08: Post Count and Differences), the following error message is displayed for the 2nd item 'Posting period 00 1995 differs from xx 1995' (xx is the current period).

Cause and prerequisites

Field 'LFMON' was missing in structure VM07I.

Solution
The error is corrected in Release 3.0B. You can make the following advance correction:
Tools -> ABAP/4 Workbench -> Development -> ABAP/4 Dictionary:
Object name: VM07I, Dictionary Objects: Structures -> Change -> New fields -> Field name: LFMON, Data element: LFMON -> Save -> Table -> Activate.

Additional key words

MI10 M7179

SAP Note 28397 - F12 and F3 do not function on cap.eval.comb.

Symptom:

F12 and F3 do not function on the selection combination popup in capacity evaluation.

Cause and prerequisites

Source code error and user interface

Solution
Source code corrections

Additional key words

Evaluation, F12, F15, Selection, Combination

SAP Note 28392 - Two R/3 Systems on one Windows NT Server

Symptom:

This note describes the configuration or installation of two SAP R/3 systems on one Windows NT server.

Other terms

Several instances, parallel, NT, multiple, second

Reason and Prerequisites

You want to install an additional central instance or an additional dialog instance on a Windows NT server that has an existing R/3 system. Plausible reasons for this could be:
- Easier administration of small MySAP landscapes
- Better utilization of large amounts of available resources in the Windows 2000 DataCenter (for example, main memory up to 64 GB or multi-processor up to 32 CPUs)

Solution

You must plan all resources carefully. Mutual effects with regard to performance and stability are to be expected.

It is technically possible to install and operate several SAP systems on one host without restrictions. We therefore provide support for a configuration of several SAP systems on the same host under the usual prerequisites. For this, take the following further recommendations into account:

- A combination of test, consolidation and production systems
on the same host is not recommended because of possible negative effects
on the stability of the production system.
All systems should represent components of one landscape.
- Furthermore, you should ensure in the case of several databases (RDBMS)
that all databases on a server come from the same manufacturer.

For further enquiries about this contact your database partner.
Your database partner can tell you which database systems
and versions can be installed together on one host.

If it turns out that performance problems are caused mainly by incorrect sizing during implementation (in other words, by inadequately assigning the individual server resources), support should be provided by the implementation partner.

a) Memory Management

Releases 3.x
Note the memory requirement of the second R/3 system and, in the case of two central systems, the requirements of the second DB. Size your system correspondingly using Notes 68544 and 88416. Use the output of the tool sappfpar (point 'Worst case requirements') for determining NT Paging file requirements of every R/3 instance:
sappfpar check pf=\
and adjust the instance profile and the paging file accordingly.

Releases 4.x
Note the value of the instance profile parameter PHYS_MEMSIZE which is used to calculate all memory management parameters that can be calculated dynamically. Adjust this value in accordance with the recommendations in Note 88416. Also notice the changed resource requirements for Release 4.0x in Note 98252.

b) SAP processes

Note that only one SAPOSCOL process can run at a time and that bottlenecks and blocking statuses can occur in the case of simultaneous access to system resources that only exist once (see point 'General information').

c) Other operating system resources

Every SAP R/3 instance is characterized by a unique instance number and a SID, which in no case may be assigned twice, since these characteristics are partially used for the description of system-specific R/3 resources (TCP ports).
In general, the installation tool (R3INST or R3SETUP) takes this into account, however, in case of problems, check the files .sapconf (usr\sap\trans, only for R3INST) and SERVICES (%windir%\system32\drivers\etc) as to whether the ports for SAP resources (sapdp00, sapgw00 and sapms) of the available instances are uniquely available for every R/3 system.
Instance numbers 98 and 99 are reserved (see Note 29972).

d) Database compatibility

You generally should make sure that there is no conflicts between the chosen database platforms before the installation of the second system.

e) R/3 release compatibility

No conflicts between the different R/3 update levels are known to exist. Since, however, only one SAPOSCOL can run on the server, you should make sure that it is a later R/3 release.

f) Batch operation

As of Release 3.1x, the host name was used for the definition of event triggered jobs in batch operation, which caused undeterminable behavior in two instances on an R/3 server. As of Release 4.0x, the logical instance name of the application server on which the batch job should run is specified during job planning.

SAP Note 28390 - KSPU, revaluation: Incomplete lock indicator

Symptom:

Parallel to performing the revaluation, you can manually plan the same data records or you can perform a revaluation although the data has already been manually planned.

Cause and prerequisites

Cause: The lock indicator is incomplete when you perform the revaluation.

Solution
Corrected in 3.0B.
You can make the following advance correction in all releases.

Additional key words

Transaction: KSPU
Program name: SAPMKPU2

SAP Note 28389 - FI-LC, Interactive Excel, error during logon

Symptom:

When you log on from Interactive Excel, an abend can occur in MS Excel when you select a system from the logon list box.

Cause and prerequisites

The error can occur if

MS Excel is started in a separate memory space in Windows NT.

entries are manually created in the SAP-Logon.

Solution

Additional key words

Interactive Excel, Consolidation, Reporting

SAP Note 28384 - Bar code in Asset Accounting

Symptom:

Can Asset Accounting

1. create a bar code label?

2. carry out a physical inventory with the bar code label? Cause and prerequisites
Solution

1. There is a report for creating barcodes as of program level 3.0C, RABARC01.

SAP Note 28383 - ME11 SAPMM06I: Purchasing group not checked

Symptom:

During the creation of an info record, the system did not check the purchasing group (ME11), so that a buyer was able to assign a purchasing group for which he had no authorization. In ME12, the authorization check was carried out, which meant that he was now unable to make any more changes.

Cause and prerequisites
Solution
See below.

SAP Note 28380 - Unexpected monospaced font on screen

Symptom:

Although the field attribute "monospaced" was deactivated in the Screenpainter, the field is displayed with a monospaced font.

Cause and prerequisites
The field contents cannot be displayed in whole width using a proportional font, as the width of a field is determined by the monospace font.

SAP Note 28369 - Production order with sales order

Symptom:

If you created a production order with reference to a sales order, all components were reserved for the sales order stock regardless of their dependent requirements indicator in the material master.

Cause and prerequisites
Solution
Correction

Additional key words

CO01

SAP Note 28367 - Missing F4 tool in popup 'Change Database Profile'

Symptom:

In the popup "Change Database Profile" on the selection screen of logical database PSJ, there is no possible entries pushbutton (F4) available for the project view.

Cause and prerequisites

The processing for PROCESS ON VALUE-REQUEST is not defined.

Solution
Delete the following lines in the flow logic of screen SAPLCJDB 0100 (transaction SE51): PROCESS ON VALUE-REQUEST. " <--- DELETE
FIELD TCNDB-DB_VIEW MODULE LADE_KTXT_ZU_TCNDS. " <--- DELETE

Additional key words

Project Information System

SAP Note 28365 - MB01: Material description in incorrect language

Symptom:

During the goods receipt for a purchase order, the material material is not displayed in the logon language but in the language of the purchase order.

Cause and prerequisites

Program error

Solution
See the source code corrections

SAP Note 28364 - Prel.planning reduc. during GI for rej.sales ord.

Symptom:

If an already partially delivered sales order is rejected, the preliminary planning is not reduced during the goods issue of the respective delivery.
In addition, the MRP record for the sales order is retained with the planned quantity. The other requirement quantities are correct (=0).

Cause and prerequisites

Program error. The preliminary planning must be activated.

Solution
Please make the following corrections in program FV50VF0A:

Additional key words

Planned quantity allocation, reason for rejection

SAP Note 28363 - Order status in CM01 is not determined correctly

Symptom:

The order status during the capacity evaluation is not determined correctly.

Cause and prerequisites

Source code error

Solution
Correction: P30K023679

Additional key words

Status, evaluation, order status

SAP Note 28362 - KSPU: Reverse revaluation: Update termination

Symptom:

An update termination occurs when you reverse a plan revaluation. Termination: DUPLICATE RECORD in table COEJ

Cause and prerequisites

Preconditions:
- Activity-dependent planned cost elements exist
and
- there are activity-dependent planned cost elements that are not
contained in the revaluation definition.
- The plan integration (line item update) is active in the affected
version

Cause: The selection of the activity-dependent cost elements was made
without cost element restriction so that a rate with zero
values was written for all cost elements not specified in the
revaluation definition because the calculation was made with 0 %
here.
During the reversal, no new document numbers are assigned for
these rates and the update termination occurs.

Solution
Corrected in 3.0A.
You can implement the correction as described below in all releases < 3.0A.

Additional key words

KSPU, SAPMKPU2, SAPSQL_ARRAY_INSERT_DUPREC

SAP Note 28360 - MMIM: Withdrawal for assigned stock transp. order

Symptom:

An error can occur when you try to make a withdrawal for a stock transport order with movement type 351 whose item is assigned.
If the order item is assigned, for example, to an asset, message AA821 is displayed: 'Company code & not defined in Asset Accounting'.
The reason for this error message is that the company code is not set for the account assignment check/asset check.

Cause and prerequisites

Program error.

Solution
Please change the following Includes:

Additional key words

MB1B, stock in transit

SAP Note 28358 - Alerts disabled and other inexplicable errors

Symptom:

Alerts inexplicably set to 'disabled'.
Further inexplicable errors in the areas factory calendar buffer, TemSe, semaphore monitoring, database buffers, Nametab buffer, spool.
Shared memories are observed, whose create date (ipcs -ma) is before the last restart. (this is only allowed for SCSA!)

Cause and prerequisites

Shared memories that normally exist in the pool, were removed from the pool with ipc/shm_psize_ =0.
Some shared memories are not correctly cleaned up on shutdown if they are not in the pool. In particular, this is valid for shared memory with the SAP key 13, Alert Area.
Especially after an upgrade, problems can occur if shared memories are not cleaned up during the upgrade.

Solution
Use the standard configuration !
Avoid profile entries ipc/shm_psize_13 =0 ..psize_16 =0, or ensure that all shared memories are cleaned up on shutdown, for example with cleanipc or by rebooting the host.

Additional key words

shared memory pool ipc shm_psize_10, shm_psize_13, showipc cleanipc ipcs

SAP Note 28352 - Reports Show Blank/Empty Results

Symptom:

Report execution appears to function but, it displays no results. This includes data types such as actual, plan, variance, etc.

Cause and prerequisites

The report results summate to a net value of zero, line items pertaining to the report are present in the
Reporting ==> Line Items ==> .... menu path,
and the display settings for the report are set to display zero values as blank.

Solution
After the execution of the report in question, in the
Settings ==> Layout ==> Representation ==> Zero Value menu path, activate the '0' option.

Additional key words

Transaction Codes: KSB1, KSB2, KC48, KC14, KC46, KC13, KC47, KC26, KCBO, KOB1, KOB2, KOB3, KOTC, KOTE, KOTD, KOTF, KOU0, KOTG, KE5Z, KE5Y, KE24, KE25, KE30, F.51, KPU1
----- SUPPORTGUIDE 20010330131459 -----
REPORTWRITER, SGRW_AMOUNT, SGRW_DATA, SGRW_DOCU_CONS_NOTE,
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

SAP Note 28348 - E:Flow control:Entry SAPMC65A is missing in T185V

Symptom:

After double-clicking on requirements with value zero and the output of message 'No requirements found ...', you return to the standard overview list. If you then press PF3, you remain in the list instead of branching to the selection list. The following message is displayed:
'E: Flow control: Entry SAPMC65A is missing in T185V'.

The same phenomen applies to the variable overview.

Cause and prerequisites

Error in T185.

Solution
Correction: P30K023529

Additional key words

T185V, PF3, Evaluation, Overview list

SAP Note 28347 - RM07IDRU: Error in status selection

Symptom:

In Release 2.2C, we removed the logical database from report RM07IDRU (print physical inventory document) and programmed the two popups for the status selection of the physical inventory documents and the inventory items ourselves. Afterwards, the 'Execute' pushbutton on the popup of status selection did not function (that is, the function key did not lead to printout of the physical inventory documents but instead the user returned to the selection screen and had to press 'Execute' here again. In other words, the key only had the function 'ENTER' but not 'Execute'.

Cause and prerequisites

Program error

Solution
The error is corrected in Release 2.2G and 3.0B. You can carry out an advance correction by making the following changes (in 2.2, you only have to change report RM07IDRU, in 3.0 you must make 3 changes):

SAP Note 28343 - MM-SRV Services w/o service master not printed

Symptom:

Services without service master are not printed.

Cause and prerequisites

Services without master were specified in the service overview of a document (service number 0, short text). These items were not considered when printing.

Solution
See the source code corrections.

Additional key words

MEDRUCK

11.10.11

SAP Note 28341 - SE06 - problems with previously created requests

Symptom:

Summary

Symptom

TADIR HEAD SYST entry is incorrect.

Created order numbers do not start with the SAP System name

Error message about un-installed Workbench Organizer from the programs R3up or R3trans

Cause and prerequisites

Incomplete installation; SE06 did not run
Requests or tasks have already been created.

Solution

If the outstanding requests and tasks were created as a test, you must delete all of these. If the number of requests is high, you can use the option 'database copy' in SE06. The risks are described in the online help when executing.
All repairs are set to RELEASED.
If the open orders are to remain usable, this is not possible. A function to rename the requests is also not possible. Requests from the source system of database copies can only be changed from the status "RELEASED" with the option "Copied from another system'.
A further problem is the original system of the created objects in this system. This can be converted with SE06 'Database copy' for all objects (not in Releases 3.0D and 3.0E).

Caution!
Objects can also exist, which really belong in this system with this name (possibly the source of a database copy). This distinction is not possible. If this conflict occurs, the automatic conversion must not be used. All originals of the objects must then be converted individually by the system administrator (SE09 -> Tools --> Transport properties).
On renaming systems:
The problems of the requests that are closed or not exported can be avoided by releasing and exporting all requests before renaming the systems. It is harder to handle a request that has been left open (as this is not exported) than to export a current working status. The imports of objects are carried out in exactly the same order as the exports.

Header Data


Release Status:	Released for Customer
Released on:	27.11.1996 23:00:00
Master Language:	German
Priority:	Recommendations/additional info
Category:	Consulting
Primary Component:	BC-CTS-TMS Transport Management System

Affected Releases

Software Component	Release	From Release	To Release	And subsequent
SAP_APPL	22	22A	22J	X
SAP_APPL	30	300	30F

Related Notes

28571 - Why are no requests deleted in SE06?

28463 - SE06 Setting up the Workbench Organizer

Print Selected Notes (PDF)

Attributes

Attribute	Value
old release	00121G R3STD 0028341
old release	00121H R3STD 0028341
old release	00121I R3STD 0028341
old release	00121J R3STD 0028341
old release	00121K R3STD 0028341
old release	00121L R3STD 0028341

SAP Note 28340 - Depreciation area '00' appears when scrolling

Symptom:

When you scroll in the company code-related specifications of the depreciation areas (transaction OAEC), depreciation area '00' is displayed.

Cause and prerequisites

The corresponding table T093B contained more depreciation areas than were defined in the chart of depreciation.
This is caused by an incorrect delivery class of the table in Release 2.1x.

Solution
Advance correction in program MA07CO01, syntax check in main program SAPMA07C.

Additional key words

SAPMA07C, T093B

SAP Note 28338 - Finite scheduling: Error in Insert operation

Symptom:

Planning board: Error in inserting an operation into an available commitment situation.

Cause and prerequisites

The indicator 'Insert operation' is active in the planning strategy.

Solution
Source code corrections

Additional key words

Finite scheduling
Multiple commitment
Gaps in capacity commitment

SAP Note 28336 - Cust./vend. interest scale WRITE_FROM not allowed

Symptom:

The customer and vendor interest scale (RFDZIS00 and RFKZIS00) terminate with the error message TD443 WRITE_FROM not allowed since START_FROM is missing.

Cause and prerequisites

Form not opened, close anyway and/or
write the form

Solution
See program code

SAP Note 28334 - Online dump when copying WBS structure

Symptom:

In the project planning board or the planning according to structure, you can copy existing subhierarchies into WBS structures.
You can do this via Project -> Copy WBS -> WBS element project.
In this case, an online dump can occur in SAPLCXOR or SAPLCXOT.

Cause and prerequisites

Incorrect query during date specification of the WBS elements.

Solution
Change the source code as described below.

SAP Note 28332 - ME33 Conditions are displayed

Symptom:

The prices are displayed in contracts and scheduling agreements despite lack of user authorization.

Cause and prerequisites

The interpretation of the user parameter 'Display conditions' was so far restricted to purchase orders.

Solution
Either remove the authorization for the user to display price data for the authorization object (for example, 'M_RAHM_EKO') or make the following correction.
Through the implementation of this note, the display authorization - and thus also the effectiveness of the field selection key '$$$$' is activated with respect to the creation and changing of purchasing doucments too. In the standard system, it will become effective in this way as of Release 3.0D.

Additional key words

User parameters, EFB, authorization to display price data.

SAP Note 28331 - Repetitive manufacturing: Backflush cancellation

Symptom:

If the withdrawal fails because of missing material availability when backflushing a run schedule header, the corresponding components are included in the processing list (transaction MF47).
However, these components are not deleted or reduced automatically in the processing list when you cancel the backflush (transaction MF41).

Cause and prerequisites

Missing functionality.
The functionality will be enhanced in 3.0C.

Solution
You must delete or change the components manually in the processing list.

Additional key words

Repetitive manufacturing

SAP Note 28324 - R3trans: Composite note "duplicate key" array insert

Symptom:

Caution: This is a composite note. It describes only one symptom which can have many different causes. It is therefore not advisable to give this note to a customer "just in case". More precisely, the problem must be analyzed, so it has to be clear which of the causes described below applies.

R3trans terminates during the import due to a "duplicate key" on array-insert.
This termination can be recognized as of Release 2.1G by the following messages at the end of the log:
2EETW150 sap_dext called with msgnr "900":
2EETW000 Internal error in DB interface
2EETW000 ---- db call info ----
2EETW000 function: db_xrtab (or db_rtab)
2EETW000 fcode: RT_MI_END
2EETW000 tabname:
2EETW000 keylen: ...
2EETW000 key: ...
4 ETW000
4 ETW000 ROLLBACK (...).
(The function code RT_MI_END represents the writing out of the entries gathered in the database. The key included in the log is the last one written. However, it is not necessarily the entry which caused the error.)

If the table in which the error occurs is not a transparent table (that is, with corresponding DB table), but a pool or cluster table, the duplicate key error can also occur.
Here, however, there is no termination of R3trans, but only error messages such as:
2EETW000 Duplicate Key error during insert into table ... occured
The first two of the causes listed below do not apply to non- transparent tables. The first two causes listed below deal with incorrect index definitions.

Cause and prerequisites

The error can have different causes.

1. Several UNIQUE indexes are defined on the table.

The most frequent cause of "duplicate Key" errrors during import are unique indexes which are defined in addition to the primary index (index over the key fields). You can find out with the data dictionary (SE11) wether such indexes are defined (the primary index is always defined and will not be diplayed by the data dictionary).

Dependent from the data contents, R3trans is sometimes not able to handle such indexes. R3trans tries to merge the existing table entries with the to be imported ones and to write back only the changed entries. This may fail with such indexes depending on the table contents.
Up to now, this error was observed for the following tables:
COFIO1 GLPCA GLPCC GLPCO
Solution: remove the table entries manually (with an ABAP program or native tools like sqlplus, dbaccess, ...) in the target client.
This problem is solved as of R3trans release 3.1I.

In some cases the cause of the "duplicate key" error is a unique index which is not defined correctly.
Up to now, this error was observed for the following tables:
PROJ, PRPS, see note 16095.
CABN, MAPR, see note 5625.
Solution: Create the index as non-unique index or add the field MANDT to the index.

2. Missing primary index.

The primary index is missing in the source system. It is thus possible that entries were inserted in a table with the same key.
If the primary index is created in the target system, the error occurs during the import.
The primary index of a table is generally created immediately when creating the table. If it is missing, the author either overlooked an error when creating the table, or the index was the victim of an incorrect reorganization.
Up to now, this error was observed only for the following tables (all in 3.0):
CDMMT COSRV KONV M_MBANP T622 WLK1

Solution: Clean up the table in the source system (remove duplicates), create the index and repeat the export.

3. Different structure.

The table is different in the source and target systems with respect to the key structure. At least one key field is missing in the target system. As a result, entries which are unique in the source system are duplicated in the target system.
In this case, the following warning is found in the import log:
3WETW000 different nametabs for table (field ).
4 ETW000 Field is not in NTAB.

Solution: Adjust the table and repeat the import.

4. Language-dependent tables with meaningless values in the language field.

For language-dependent tables which have the language field at the end of the key and have language entries which do not occur in the R3trans default language vector (esp. ' '), the import termination due to a duplicate key can also occur.

This problem was solved in Release 2.1G/2.2A in that R3trans selects the languages later. Thus, the error can only occur if the export was created with a R3trans <= Release 2.1F.
Up to Release 2.1F, the default language vector had the value DEFIJKNOSV.

Up to now, this error was observed only in the following tables:
CKHT KNVD MAKT SKAT STXH STXL T513U

Solution, see Note 2666.

5. Several ABAP/4 Dictionary short texts are active in the source system.

Due to a sporadically occurring error in the ABAP/4 Dictionary, the short text for tables, domains, data elements etc. can be stored more than once and the only difference for the entries is the internal version number. During import, R3trans always sets this internal version number to '0001'. This then causes duplicate entries.
You can check whether this is the cause of the problem with Transaction SE17 (General table display) in the source system.

The error can only occur in the following tables:
DD01T DD02T DD03T DD04T DD06T DD07T DD08T DD12T DD20T DD23T DD25T

Solution: Clean up the entries in the source system by reactivating the corresponding Dictionary object. Then repeat the export.

6. ORACLE database is installed incorrectly.

It is possible that the ORACLE DB system is installed incorrectly with regard to the national language support (nls). R3 databases must run with AMERICAN_AMERICA.US7ASCII. Otherwise, R3trans has difficulties if entries are required in a sorted sequence, but are not actually sorted (for example, with a binary search).
Up to now, this error was observed only in the following tables:
D021T, see Note 5625.

Solution: Set the variable NLS_LANG = AMERICAN_AMERICA.US7ASCI. See Note 8760; This error is quite rare and has other symptoms (for example, umlauts displayed incorrectly).

7. Preceding deletion did not work.

R3trans always uses array-insert if it can assume that none of the entries to be imported already exist. This is also the case, for example, if they were just deleted by R3trans. If no entries were deleted due to an internal error in the deletion, the termination can occur.

In Releases 2.1 and 2.2, the termination can be caused by an incorrect WHERE condition for DELETE. This error is corrected as of 2.1M/2.2G by converting the deletions to another database interface function.

Up to now, this error was only observed in the following tables:
FINS M_CLASE RFDT T130F T52A0 T582S T804C T811I TCM4 TTXID TTXIT TVDIR
TWFDB

Solutions and details for the problem, see Note 7100.

8. Preceding deletion was incorrect due to keys with different structures

The deletion of entries can fail because the structure of the table in the key was changed.

Cause: R3trans saves the key(s) to be deleted as a generic string, but the string is not converted if the structure is different.

Result: Deletion uses an incorrect string, which usually does not delete enough entries.

Solution: First transport the modified structure and then the corresponding entries.

9. Incorrect decision for array insert after a previous deletion of a similar table entry

In certain circumstances R3trans can incorrectly assume that a table entry about to be imported has just been deleted, and can therefore be imported with array insert. The following conditions must all be fulfilled:

Two entries from the same table must be selected directly after each other in the transport request.

The first of the two selections contains a completely specified key: that is, not a generic with *.

The first selection is shorter than the second, but is, at the same time, a partial string.

Example: two entries are selected from table T51TF with the following keys:
011E10HR_F_UNEMP
011E10HR_R_UNEMP_CA

Result: the keys are not compared long enough and it is incorrectly decided that the entries of the second selection can be imported per array insert. When they already exist, however, an error occurs.

So far the error has been observed only for table T51T7.

Solution: transport the first entry generically (*). Error corrected in Release 3.0D.

10. Incorrect merging of table entries with long keys (> 50 Bytes) when transport with R3TR VDAT

The error comes up as of Release 3.0C and was solved with Release 3.1I.

The cause and a workaround are described in Note 65887.

11. Incorrect import of language-dependent tables

In Releases 3.0FCS - 3.0C, the duplicate key error can occur when transporting entries from language-dependent tables, if the following conditions are met:

a specific language is explicitly given in the key entry
- when exporting this transport request, a language vector is used which does not contain this language (in TPPARAM),
in addition, these keys already exist in the target system.

Since in a normal customer installation there is no explicit language vector given in TPPARAM; the error practically does not occur in customer systems.

So far, this error has only been observed in table T241H.

Solution: In TPPARAM, expand the language vector to include the languages selected in the transport request and repeat the export.
In Release 3.0D the error is corrected.

12. Other problems during preceding deletion.

It is theoretically conceivable that R3trans has other deletion problems in 3.0. From the log it is possible to see how many table entries R3trans deleted previously, and with which key. With Transaction SE17 (or native tools, such as sqlplus, dbaccess ...), you can check whether this number is correct.
If it is not, ask the author of this note for further information.

13. Subsequent errors after other SQL errors for array-insert.

If other SQL errors (for example tablespace overflow) occur when using array-insert within R3trans, further insert attempts are mistakenly refused with the error "duplicate key".

Solution: Correct the original error and repeat the import.

14. Export from all clients

It is possible to enter the option "client=all" in the control file when using R3trans directly during the export. This exports from all clients for client-specific tables. If you now import into a certain client ("client=..."), or with "client cascade = yes", the termination can occur due to double entries.
It should be clear from the logs whether these options were used.
However, the option "client=all" is neither documented nor supported.

Solution: Do not use "client=all" during the export.

15. Termination on insert in table DDPRS for logical R3trans backups

The status information on every R3trans backup is internally logged by R3trans in table DDPRS. This causes a termination if several of these backups run in a system at the same time.

Solution: Use organizational means to run these backups sequentially.
The error is corrected in Release 3.0F.

16. Only with DBMS DB2/400 (operating system AS/400): tables with key fields of type 'P' (packed data).

For packed data, several different but equivalent representations of the sign are possible. With DB2/400, this packed data is converted internally to a normalized representation. In this way, R3trans causes duplicates of table entries that differ only in the representation of the sign symbol.

This problem occured only with table T5J40 so far.
It may theoretically occur with the following tables:
BSIP T440Y T5J14 T5J39 T5J40 T5J41 T5J42 T5J43 T5J44 T5J57 T5JA3 T5JC3 T5JC4 T5JSY T5JT1 T5JT2 T5JT2 T5JT3 T5JT3 T5LER T7NZTE

Solution: solved with 3.0F.

17. For operating system DEC alphaosf only: Tables with key fields Type I (INTEGER) or S (SHORT).

On DEC machines the internal representation of 2 and 4 byte integers doesn't always allow a bigger/smaller comparision with memcmp().

So far this problem occured only with table CNTLSTREAM.

Solution: solved with 3.1H.
Duplicate key error with table SREPALOG
Because of the different structures of table SREPALOG in Release 3.1 and 4.0 duplicate key errors can occur during the transport from 4.0 to 3.1.
Solution: solved with Rel. 3.1 R3trans version from 12/11/98 or more recent.
This corrected R3trans is provided on sapservX, path:
~ftp/general/R3server/patches/rel31I.

Solution
Depending on the cause, there are different solutions (see above). In all the above-mentioned cases, the import can also be carried out with the R3trans option safeandslow=yes. This is especially useful if there is no time for extensive error recovery.
This option forces R3trans not to use array-inserts, thus making the import secure, but slow. All table entries which cannot be inserted are logged in the file trans.dsc.

Additional key words

R3trans rt_mi_end array insert arrayinsert rc128 duplicate key in index

SAP Note 28322 - MM-SRV: Creating a service item in the quotation

Symptom:

When you create a quotation, you cannot add new services.

Cause and prerequisites
Solution
See the source code corrections

Additional key words

Services management
SRV

SAP Note 28314 - MMIM: Valuation type check for batch '*'

Symptom:

If you specify a batch during the goods receipt that is allocated to a valuation type which is different from the valuation type defined in the order item, the following message is displayed: "Valuation type xxx unequal to valuation type of batch xxx".
If you select the batch with "*", the message is not displayed and you can select a batch that is allocated to a different valuation type.

Cause and prerequisites

Program error.

Solution
Please change the following Includes:

SAP Note 28313 - Line items: Other items/refresh - and/or

Symptom:

1. The "Other line items with selection criteria" function in the line item display considers the selection criteria that have been entered previously, but it always links the criteria for different fields with "AND" even if they were previously linked with "OR".
As a result, the number of hits is not the same even if you do not change the account.
2. The error occurs in the same way for the "Refresh" function.

Cause and prerequisites

Error

Solution
1. Corrected in 3.0B.
2. Corrected in 3.0D.

Additional key words

RFEPOS00, FBL1, FBL3, FBL5

SAP Note 28306 - Selection of the alternative BOM in production order

Symptom:

Choosing alternative BOMs as of Release 2.2*/3.0*:

BOM selection is controlled via the BOM application and by the field 'AlternSelection' (MARC-ALTSL) in the material master (MatPlannDatScr):

Only the BOMs, in whose application (TA OS20) the characteristic 'items relevant to production' was not set to '-' at the time of the BOM creation, are copied into the production order.

The BOM application is derived from the 'order type dependent' parameters (TA OPL8).

The selection ID (TA OS31) is derived from the BOM application (TA OS30) and the status prerequisites to be checked are established (TA OS23).
Important: Only bills of material with the appropriate status (TA
OS23), that is, the status must show the same
characteristics as the BOM application used, are copied
into the production order during the BOM selection.
The BOM application finally specifies whether the alternative selection can be overridden from the material master, that is, whether the BOM selection can be selected according to the production version (for the value '2' 'selection according to production version' in the field 'AlternSelection' (MARC-ALTSL) in the planning view of the material master) or whether the alternative stored in Customizing (TA OS32, T415A) (for the value '1' 'selection according to explosion date in the field 'AlternSelection' in the planning view of the material master (MARC-ALTSL)') is selected. Corresponding settings in the field AlternSelection in the material master for the controlling category of BOM selection are only taken into account if this is allowed here.

In the Selection ID (TA OS31), it is specified which BOM usages are taken into account in which sequence during selection.

Explanation of the selection criteria depending on the field 'AlternSelection' (MARC-ALTSL) in the planning view of the 'Material master':

1. Selection via the lot size range
Preconditions:
a) Value of the field 'AlternSelection' (MARC-ALTSL) in the planning view of the material master: ' ' ('selection according to order quantity')

A BOM application is derived from the order type. Using the BOM application and the Selection ID derived from it, a bill of material is now searched for with:

- appropriate lot size
- valid at the explosion date
- Indicator 'Items relevant to production' not set to '-' in the usage (TA OS20) of the BOM
- appropriate status

2. Selection via the validity date
2.1. Take indicator for 'Alternative selection for multiple BOMs' into account
Preconditions:
a) Value of the field 'AlternSelection' (MARC-ALTSL) in the planning view of the material master: '1' ('selection according to explosion date')
b) BOM application allows selection:
Value 'X' in the field Alternative selection for multiple BOMs (X415A, TA OS30)

A BOM application is derived from the order type. If the indicator for the 'alternative selection for multiple BOM' is set in this application, alternative BOMs are searched for via the table T415A (TA OS32). Finally, it is checked afterwards whether this bill of material fulfills the following preconditions:

- available at the explosion date
- indicator 'Items relevant to production' not set to '-' in the usage (TA OS20) of the BOM
- appropriate status (see above)

If this is not the case or if no corresponding entry is found in table T415A (TA OS32), no bill of material is transferred into the production order.

2.2. Do not take indicator into account for 'Alternative selection for multiple BOM'
Preconditions:
a) Value of the field 'AlternSelection' (MARC-ALTSL) in the planning view of the material master: '1' ('selection according to explosion date')
b) BOM application allows selection:
Value ' ' in the field Alternative selection for multiple BOM (X415A, TA OS30)

By means of the BOM application and the Selection ID derived from it, a valid bill of material is searched for at the explosion date of the production order. It is checked afterwards whether this bill of material fulfills the following preconditions:

- available at the explosion date
- indicator 'Items relevant to production' not set to '-' in the usage (TA OS20) of the BOM
- appropriate status (see above)

If several valid alternative BOMs exist, the first one found is transferred into the production order.
If no valid alternative BOMs exist, a further BOM usage is determined using the Selection ID and the search is continued correspondingly.

Notes on the BOM selection via the validity date:
The lot size range of the bill of material is not checked for the 'Selection according to explosion date' against the order quantity.
The validity period of bills of material can only be maintained with the help of engineering change management.

Additional key words

Alternative, Bill of material, Production version, CO01, CO02
Production order, BOM selection, Master data, CS01, CS02, MRP, MD01,
MD02, explosion, 29603, 29602

Cause and prerequisites

What does not work:

1. A manual selection of the alternative BOM is not possible.
As of Release 3.0, a production version can be specified during order creation. If several alternative BOMs which are not differentiated by the lot size or the period of validity exist, the first valid bill of material found is transferred into the production order.

2. The routing selection and BOM selection are independent of each other, that is, the assignment of the BOM components to routing operations in routing maintenance is not taken as a basis for selecting the bill of material when creating the production order.
An assignment can only be carried out via the production version.
If the components of the bills of material found are not assigned to any operations of the routing found, they are assigned to the first operation.

Solution

Enhancement as of Release 3.0*:

Selection via the production version
Preconditions:
a) Value of the field 'AlternSelection' (MARC-ALTSL) in the planning view of the material master: '2' ('selection according to production version')
b) BOM application allows a corresponding selection:
Value 'X' in the field production versions (XFVRS, TA OS30)

Via the lot size and the explosion date, a production version from which the bill of material is then determined is calculated. If no valid production version is determined, the BOM selection is carried out as described under 'Selection via the lot size range'.

If the bill of material determined via the production version does not fit the lot size, explosion date, usage or status conditions, no bill of material is selected.

Furthermore, the possibility to import other master data into a production order already created exists as of Release 3.0*