SAP Note 21207 - Deleting a charctrstc/value field from an op.

Note Language: English Version: 40 Validity:
Valid Since 04.12.2001

You want to delete a field (characteristic, value field or quantity field) from an operating concern, but this operating concern already contains data.

Additional key words
CO-PA: KE02, KEA0, Maintain characteristics/value fields, Maintain operating concern IS-B: JBG0

Cause and prerequisites
You added the field when you created the operating concern, but no longer need it.

This note tells you which steps are necessary for you to delete a field from an operating concern. As of Release 4.6 there will be a standard functin for deleting a field from an operating concern. As of Release 4.6, read the documentation in the Implementation Guide (IMG) on the topic maintaining operating concern. This note is intended for experienced consultants only. In order to understand it, you need to have a knowledge of CO-PA and experience in working with the development environment. The deletion of a field cannot be transported. If you want to delete field in a test and a production system, the deletion has to be carried out in each system! The reason for this is that the automatic transport recording is not possible with many objects in CO-PA. The function for transporting an operating concern can only be used to transport existing objects. No entries for objects, which no longer exist, are placed in the transport request.

o Before you delete the fields it must be possible to generate the operating concern without any errors. After you have deleted the fields, you need to convert the operating concern tables. To do this, you need to have enough hard disk space available to store the largest table (CE1xxxx, xxxx = operating concern) twice in the database temporarily. The operating concern cannot be in use while you are carrying out the following steps. Therefore make sure that no postings are made to Profitability Analysis during this time. Do not forget the interfaces with SD, FI, and so on.



In the following, xxxx represents the name of your operating concern and
23.01.2011 Page 1 of 6

01. Process the quantity field zzzzz the same way as the 23. because changes need to be made to the ABAP Dictionary. a unit field zzzzz_ME also exists in the structures. you will usually find a variable which refers to the deleted field near the place where the program terminated. all summarization levels must be deleted. . o Value field Delete fields period longer the field zzzzz from Tables CE0xxxx and CE1xxxx.5 also from Table CE1xxxx_ACCT.concern zzzzz represents the name of the fields you want to delete. If you do not delete all the references. this can lead to terminations. As of Release 3.2E and later. CE2xxxx and CE4xxxx. You can ignore the error message telling you that the structures are still being used in programs. as of Release 4. Pay special attention to the condition tables. realignments . especially in the interfaces.Deleting a charctrstc/value field from an op. CE1xxxx. These can include reports. Edit Include MKGALT8T (using Transaction SE38) and delete the TABLES definition for Table CE7xxxx.SAP Note 21207 . Delete the structures CE5xxxx. derivation structures. 5. This table can be maintained via Transaction SM30 with the View V_TKEZU. 1. You can usually solve the problem by subsequently deleting that object. Delete the desired fields from the tables listed below in the ABAP Dictionary. In the debugger. Delete all the objects which refer to the fields you want to delete. you can delete the zzzzz as follows: o 2. summarization levels. key figure schemes. you must delete all lines in table TKEZU which contain the characteristic zzzzz. 8. CE6xxxx (if it exists). 6. Characteristic Delete the field zzzzz from Tables CE0xxxx.. In Release 2. Depending on the type of field. the period block no exists (nnn is always 001). the field assignments for the interfaces and the summarization levels. as of Release 4.0 also from Table CE4xxxx_KENC. KEY1 to KEY5) in the "derivation tables" (table TKEAN). valuation.2011 Page 2 of 6 . Irrespective of which field is to be deleted.. 7. delete the table entries which refer to the characteristic to be deleted (fields: MERKMAL. 4. field assignments for the interfaces. Delete the lock objects EKC5xxxx and EKC6xxxx (if they exist) from the ABAP/4 Dictionary (Transaction SE11). and then save the table definition. 3. CE7xxxx and CE8xxxx from the Dictionary. because the structures and programs will be regenerated later. row/column structures. derivation. Create a backup of the entire system! It is not sufficient to simply save the contents of the CE* tables. o Quantity field For quantity field zzzzz. When you delete a characteristic. and the zzzzznnn from Tables CE2xxxx and CE3xxxx (nnn = 001 to the block).0: When you delete a characteristic.

Cleaning up of leftover objects The actions described above only deleted the fields from the operating concern tables. you can only do them for fields which are not being used in another operating concern.1G: Delete the value or quantity field from structure COPAVAL. the entry xxxx zzzzz from Table TKEIG and for a value or quantity field. . 23. CE4xxxx_KENC und CE4xxxx_ACCT. A value or quantity field has been deleted and is not used in any other operating concern: a) As of Release 3. The following tells you how to delete the corresponding data elements. CE2xxxx. Up to including Release 2. Up to and including Release 2. and then generate the environment. These actions are optional. you can use the operating concern again. and so on. postings should not be made in the system. domains. Use the database utilities (Transaction SE14). However.. call up Transaction KE21.0. because the program may terminate (FI. to convert Tables CE1xxxx. Customers who work with IS-B (Profitability Analysis for Banking) have to use Transaction JBG0.0: After you have generated the environment of the operating concern. 15. 9. 2.). 11. SD. CO.2 this is done in Transaction KE02. The Tables CE4* must be converted last. CAUTION: Fields from interface structures have yet to be deleted in the following.2: Delete the following in client 000(!): for a characteristic.concern value fields and the unit field zzzzz_ME the same way as the characteristic. use Transaction KEA0 to activate the data structures. Activate the checkbox "all operating concerns". While the structures are being activated..2E: If you have deleted a characteristic. If the call terminates with a dump MESSAGE_TYPE_X K/590. the deleted field can be recreated again. As of Release 3. the generation of the client-specific part is completed when calling up the first transaction.Deleting a charctrstc/value field from an op. CE4xxxx. As of Release 3. Once the actions have been performed. 12. You can also perform them at a later point in time. After that the tables will be active again. 13. Only for Release - 10.01. execute the function module RKD_SHORT_TEXT_GENERATE in the test environment (Transaction SE37) using the parameters APPLCLASS=KE and MODE=N. CE3xxxx. Regenerate the operating concern. proceed as per Note 114407. Once you have completed the above steps. the entry xxxx zzzzz from Table TKEWP. As of Release 4. To do so.0: Execute report RKEREOFC. 14.SAP Note 21207 .2011 Page 3 of 6 .

You do not have to worry about the unit field zzzzz_ME here.0A. ACCIT_PA and K9*.SAP Note 21207 .concern b) As of Release 4.Deleting a charctrstc/value field from an op.0: Delete the value or quantity field from structure COPAFIELDS. To do this. SD.01. c) Up to and including Release 3. since no objects were generated for it in the ABAP Dictionary. Start the generation program RFBIBLG0 to adjust the program RFBIBL00 to the changed BBSEG structure. COPABBSEG. delete the field zzzzz from the structure COPACRIT in the Dictionary.2011 Page 4 of 6 . all the KOM* tables in the where-used list will also be activated.0A. b) Delete the entry "A KE 001 zzzzz" from table T681F.0E. if the characteristic to be deleted was used in a derivation structure in Release 3. If any other tables are listed. Otherwise terminations may occur (FI. and activate the table.. f) As of Release 4. This structure is used as an INCLUDE in the structures BBSEG and ACCIT_PA.1I: Delete the corresponding data element RKE2_zzzzz. Consequently. d) As of Release 3. use the where-used list for domains in tables. c) Delete the field zzzzz from table KOMPAKE in the ABAP/4 Dictionary. d) As of Release 4. If you deleted a characteristic which you defined yourself: a) Check whether or not the corresponding data element is being used in other operating concerns. then activate the structure.0D: Delete the RKE_zzzzz field from the COPABBSEG structure in the Dictionary.0A: Delete the value or quantity field via function "Edit Value Fields" (Transaktion KEA6) If you deleted a : characteristic copied from the master data table a) You do not need to do anything here. COPACRIT. if it still exists. COPAFIELDS.). No one should be working in the system when you activate them.0: Delete all tables K9xxx (xxx 23. if necessary. ACCTSD. . delete the field zzzzz from the structure COPAFIELDS. T25xx. CO. Only the following tables should appear in the list: KOM*. g) As of Release 4. This structure is used as an INCLUDE in the structure ACCTSD. BBSEG. H_T25xx. Adjust your external program for creating external data files in FI. do NOT carry out the following steps. This table is used as an INCLUDE in the other KOM* tables. and activate the structure. e) As of Release 3. CAUTION: The change to the COPABBSEG structure also implicitly changes the BBSEG structure for transferring external data into FI.. CAUTION: The KOM* tables are central interface structures in SD.

Delete the Tables T25xx mentioned in the above where-used list.0A. data element and check table using "Edit Characteristics" (Transaction KEA5). the objects have to be deleted manually: Delete the entry for the check table in the domain. Execute Program RKEAGENV. the old data structures are not deleted.2: Delete the view H_T25xx.01. Now the where-used list "Tables for domain" RKEG_zzzzz only contains two tables T25xx. Up to and including Release 3. i) Up to and including Release 2.12.SAP Note 21207 .Deleting a charctrstc/value field from an op. use the menu option "Characteristics -> Delete". delete the corresponding derivation step via characteristics derivation maintenance (Transaction KEDR).concern consisting of 3 digits) that contain the field. - Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: CO-PA Profitability Analysis Released for Customer 03. you can delete domain. if the characteristic to be deleted occurs in a new derivation table K9R*. (Explanation: The derivation has been newly implemented in Release 4. During the upgrade the derivation structures were automatically converted to the new data structures.2001 23:00:00 German Recommendations/additional info Workaround for missing functionality CO-PA-ST Structures Valid Releases Software Component SAP_APPL SAP_APPL SAP_APPL Release 22 30 40 From Release 22A 300 40A To Release 22J 31I 40B and Subsequent X X X 23. However. and then activate the domain.1I.0A.0A.) h) As of Release 4. To do this. These are the check table for characteristic zzzzz and the corresponding text table. j) As of Release 4. This will regenerate the view maintenance modules for the user-defined characteristics which still remain.2011 Page 5 of 6 . Delete the data element RKEG_zzzzz. Delete the domain RKEG_zzzzz.

1 Quantity fields AKAUFS. & value flds Attributes Attribute Transaction Transaction Transaction Transaction Transaction Transaction Transaction Transaction Transaction Transaction Transaction codes codes codes codes codes codes codes codes codes codes codes Value HIER KE21 KEA0 KEA5 KEA6 KEDR SE11 SE14 SE37 SE38 SM30 23.2011 Page 6 of 6 .Deleting a charctrstc/value field from an op.SAP Note 21207 .concern Software Component SAP_APPL Release 45 From Release 45A To Release 45B and Subsequent X Related Notes Number 353257 206827 134430 122291 114407 113860 106314 100272 87745 74486 13377 Short Text Error message K6431 w/ deleting characteristic Error message w/deletion characteristic/value field Information: Euro conversion and CO-PA Error message when generating operating concern Termination in SAPLKEDR with MESSAGE_TYPE_X K/590 S00344 Batch input data for screen RK1M. Delete operating concern in Release 3.01. AVERKS as value fields Characteristics with data type UNIT INFO: Overview of consulting notes for CO-PA INFO: Naming conflicts in charactrst.