SAP Note 23909 - KEA0: Error AD855, abends in CO-PA transactions

Symptom:

1. The data structures of an operating concern were not activated. The activation log contains error messages about the dependencies of the value fields, such as:
AD855 -
CEyxxxx-fffff: Combination reference table/field CE4xxxx-ggggg does not exist

2. When generating the environment for an operating concern the system abends with error message

KE549 Program state is invalid -> see long text

3. Transactions in Profitability Analysis abend due to program errors. Examples:

a) An ABAP runtime error "Programm_Error" occurs in program SAPLKEPA in Transaction KE11.

b) When you create line items using Transaction KE21, you get error message RK1Mxxxx (xxxx = operating concern): "Screen source '0150' is missing".

4. In the SD interface, when you choose the function "Assign quantity fields", you get error message KE314: "Quantity field & is not contained in operating concern &"

5. During the changeover to euro, error message KE 543 'Field VRRME not contained in nametab for table CE0xxxx' is displayed for program EWUCOPLS / EWUCOPLS_40 in phase 'ANALYZE'.

Cause and prerequisites

Release 2.2 contained inconsistencies in the dependencies of the value fields of an operating concern. During the upgrade to Release 3.0, these inconsistencies were not corrected by XPRA RKEREOFC.

Solution

As of Release 3.0C the cause of the problem no longer exists. However, it is possible that inconsistencies in the dependencies are inherited to subsequent Releases.

1. If one of the symptoms described in point 2) appears in your system, check whether the field VRKME is contained in structures/tables CE0xxxx, CE1xxxx, CE2xxxx or CE4xxxx. If it is, proceed as explained in the following. If the field VRKME is not contained in these structures/tables, this note does not address your problem.

2. If you are still using Release 3.00, obtain the current version of program RKEREOFC from the sapserv3 server in Walldorf. You can find it in the directory
dist/permanent/Note.0023909 (2 files)
Follow the instructions in Note 13719. The transport request is P30K011385.
For Release 3.0A and higher, do not get the program from the sapserv3 server. The system already contains the current version.

3. Execute the report using the following parameters: Operating concern
X All operating concerns

Processing ---------------------------------
Display reorganization only
X Execute reorganization

Release upgrade 2.x -> 3.0

4. Use Transaction KEA0 to activate the data structures of the operating concerns. Tables CE1xxxx and CE2xxxx (xxxx = operating concern) will not be activated, since the database first needs to be adjusted. This will be indicated in the error log.

5. Adjust the database for tables CE1xxxx and CE2xxxx using transaction SE14. In the case of large data volumes, execute this in the background. The tables will be activated in the ABAP/4 Dictionary at the same time.
Carry out the following steps only if all the tables/structures CE0xxxx through CE8xxxx are active and saved in the ABAP/4 Dictionary:

6. Delete field VRKME from table CE4xxxx using transaction SE11. This also requires that the database be adapted. You can do this using transaction SE11. Then the table needs to be active in the ABAP/4 Dictionary.

7. Regenerate the environment for the operating concern using transaction KEA0.

Additional key words

Planning, KE11, KE21, KE23, KE24, KE4I, SD interface, ABSMG, VRKME, KE01, KE02, CE0xxxx, missing reference fields, KE 649, KE 543, fill_special_fields, SAPLKEFT, changeover to euro