SAP Delete CO Transaction data

Delete CO Transaction data

Delete Test Data If you posted transaction data or created master data during customizing for testing purposes in your production system, you must delete it for the production start. The SAP System offers the option of removing the following data groups: •

Transaction data

•

Master data o o o o

Cost elements Cost centers  Activity types Orders

If you implement the module CO later than other SAP modules, you can automatically copy the cost-accounting-related postings to CO.

Delete Transaction Data In this IMG activity you can delete transaction data created through test postings. This function does not allow selective editing of data: it deletes all the transaction data in acontrolling a controlling area. area. Note The delete function is intended for test data only. For archiving productive transaction data, the SAP System offers the archiving function, found in the application menu for Cost Center Accounting under the menu option "Tools".

•

•

In the IMG "Financial Accounting", you can find a program for resetting transaction data under "Financial  Accounting Global Settings → Delete Transaction Data". This program program also deletes the transaction data for the CO module.

Warning If you start the program from the FI Implementation Guide, all plan data for Cost Center Accounting will also be deleted. The program also resets the document numbers. Recommendation If you use the reset program from FI and want to keep the CO plan data, start the program without the indicator "Delete CO data". Afterwards, selectively delete plan data and/or transaction data in the CO module.  Activities 1. Check in which controlling area you wish to delete data. 2. Enter the desired controlling area. 3. Start the program. o

If you wish to see an overview of the data records to be deleted, select "Test run" before you start the program. If "Test run" is not selected, all transaction data will be deleted.

o

Page 1 of 5

If you select "Do not delete plan data" the system only resets actual postings. Cost center planning is then retained in all versions and is available for production operations.

Delete CO Transaction data

IMG Transaction: OKC3 IMG Path: Controlling  General Controlling  Delete Transaction Data

Example CoArea not existed:

Page 2 of 5



Production Start-Up Preparation



Delete Test Data

Delete CO Transaction data Example CoArea with data:

Report: RKSCUS01 Description This report deletes all CO transaction data in a controlling area. The following options exist: 1. Do not delete plan data: If you activate this parameter, plan data is not deleted. 2. Test run: If you activate this parameter, no records on the database are deleted. The records to be deleted are displayed only on the database. The number ranges are only reset to zero if both parameters are deactivated. If number ranges are reset, you cannot update any update records using the monitor function, unless no CO documents are created by doing this. Otherwise you must rerun the report with the same options to remove the records subsequently updated and to reset the number  ranges to zero. If you do not do this, duplicate records will occur. The CO documents are deleted entirely; the other data (such as totals records) are deleted by transaction. The report is intended only for resetting test data. You should use the archiving or reorganization tools in productive systems.

Page 3 of 5

Delete CO Transaction data Technical tips 1. The plan li ne items and totals records are organized internally by business transaction. All records are deleted that do not contain one of the transactions listed below: KAZP KZPP RKP1 RKP2 RKP3 RKP4 RKP5 RKP6 RKP7 RKP8 RKP9 RKPU RKPV RKPW RKPX KEKB KEKZ KPPB KPPZ

Plan cost center imputed costs Plan surcharges (periodic) Plan costs Plan activities Plan activity input Plan statistical key figures Plan revenues Plan activity-dependent costs Plan activity-dependent activity input Plan order costs Plan activity-dependent order costs Pla assessment Pla distribution Secondary order cost planning Secondary activity-dependent order cost planning Unit costing (base) Unit costing (overhead) Create plan from reference object Create surcharge from reference object

2. If it is not possible to select using the controlling area due to the data structure, the SAP System determines all CO objects belonging to the controlling area. A selection can then be made using the CO object number. The list below shows which object types are created by the report:  AO Reconciliation object EK Product costing HP Process manufacturing hierarchy KL Cost center/activity type KS Cost center  OR Order  OV Order operation PR Work breakdown structure VB Sales document item VD Summarization object 3. The following tables are reset: a) Line items and header for CO documents: COEP COEPL COEPR COEPT COEPB COEJ COEJL COEJR COEJT COBK b) Open items: COOI c) Totals recs: COSP COSS COSR COSL COST COSPD COSSD COSPP COSSP COSB d) Plan control: COKP COKR

Page 4 of 5

Delete CO Transaction data COKS COKL e) Cost element control: COKA f) Plan long texts: STXH STXL g) Cost center/activity type: CSSL h) Detailed planning of primary costs: CKIP CKIT CKIS CKHT CKHS i) Budgeting: BPTR BPEG BPEJ BPEP BPBK BPGE BPHI BPIG BPIJ BPJA BPPE  j) Product costing: header: KEKO only field: OBJNR k) Order settlement:  AUAA  AUAB  AUAO  AUAS  AUAV  AUAK l) Object numbers (indices): ONRAO ONRKL ONR00 m) Allocations document management: T811D n) Revaluation document management : T823D o) Number range status: NRIV 4. Some of the tables can only be deleted by object (such as the totals records). All the numbers of the object (field OBJNR) must exist in the client. If this is not the case, the report will not be able to find all the records to be deleted. Possible causes for inconsistencies are: o o

deleting master data with a user report that does not check whether dependent records exist transporting data from other systems or clients (for example, master data from client AAA and CO documents from client BBB).

Requirements This report is protected against unauthorized use by means of authorization assignment.

Output  A list of the tables deleted or reset is displayed.

Page 5 of 5