- 1. You want to change the description of a user-defined characteristic or value field in your operating concern.
- 2. You have a user-defined characteristic in your operating concern. When you try to maintain values for this characteristic, the system does not let you maintain the corresponding check table. Instead, it takes you to a maintenance view that has nothing to do with that characteristic.
Symptom 2:
When you created the user-defined characteristic, you encountered a naming conflict for the field ID. The program for maintaining characteristic values (SAPMKEA1) is designed to check whether the screen text (on the screen SAPMKEA1 300) and the keyword text in the field catalog are the same. You therefore encounter problems when two characteristics in the same operating concern have the same keyword text. To eliminate these problems, you need to change the texts for your user-defined characteristic.
Example:
You have defined a user-defined characteristic "WWXYZ" for your operating concern and entered the name "Cost center" for this characteristic. The corresponding data element "RKEG_WWXYZ" also has "Cost center" as the medium text. When you maintain characteristic values for this characteristic, the system takes you to a maintenance view for the table CSKS.
This is because the operating concern already has a predefined field "SKOST", which references the check table CSKS. The data element that belongs to this field, "SKOST", also has the keyword "Cost center". Since the fixed field "SKOST" comes before the user-defined field "WWXYZ" in the data structures, the system takes you to the maintenance view for table CSKS when you try to maintain the values for "WWXYZ".
You can change the for your user-defined characteristic by changing the so-called "Field ID" of the corresponding data element "RKEG_XXXXX" (where XXXXX is the name of the characteristic). To change the description of a value field, change the corresponding data element "RKE2_YYYYY" (where YYYYY is the name of the value field). There are two ways to do this, depending on what release you are using:
- In releases 2.1 and 2.2, you need to use transaction SE11 to change the data element. Do not forget to reactivate the data element again after changing it.
(If your client is set up so that changes are automatically added to transport requests (table T000), you need to enter a transport request when saving. If you want to transport this transport request, read Note 78850)
Once you have done that, go to Transaction SE38 and execute program RKEAGENF to rebuild the CO-PA field catalog (independently of release).
Furthermore, change the texts of the value fields in the calculation scheme. For this, use Transaction SE16, table T237T, line number >= 9000.
Additional key words
KE01, KE02, KEA0, Maintain characteristics, KES1, KES2, field ID, field name, SV038
No comments:
Post a Comment