This blog will explain how to archive CO Order data via object CO_ORDER:
Read program: RKAARCS1
Relevant OSS notes:
1270936 – CO order: Deletion indicator without deletion flag
3146990 – EC_PCA_ITM: Error while determining the BOR key when archiving
plan data
3239597 – PCA Archving: MESSAGE_TYPE_X when executing delete program
SAP Note 3228893 – Usability enhancements in ILM Data Destruction
Worklists – UDO Report for SAP_BASIS 740 to 757:
Implement the following manual instructions:
1. Use transaction SE38 to execute the report NOTE_3208261.The report is
attached to this SAP Note.
2. Select TESTRUN and execute the report.
3. Check the log of the execution: There should only be information
messages (green traffic lights).
4. Go back to the execution screen (choose “Back” or press F3),select
Update & Activate, and execute the report again.
5. The system will prompt you to enter a transport request: Enter a
transport request (you may have to create a new task in the transport
request if the existing task does not match the correction).
6. Confirm the message for the restricted object editing if the system
prompts you to do so (this message is generated for each object; confirm
this message for each object).
7. Confirm the message for the object creation as a copy if the system
prompts you to do so (this message is generated for each object; confirm
this message for each object).
8. Confirm the proposed package assignment (this package assignment is
generated for each object; confirm this assignment for each object).
9. The system may issue a message for object maintenance in the original
language; confirm this message (this message is generated for each
object; confirm this message for each object).
10. As a last step, the system displays a list of all objects processed.
Activate all objects from this list.
11. Check the log of the activation; there should be only warnings and
information messages.
12. Go back to the execution of the report (choose “Back” or press F3),
select Show logs, and execute the report again.
13. Select the last execution log and check that there are only
information messages (green traffic lights).
SAP Note 3208261 has other pre-requisite notes:
2313560
2523642
2966110
3068892
3070178
3107172
SAP note 3146990 – EC_PCA_ITM: Error while determining the BOR key when
archiving plan data – manual steps:
1/ Go to transaction IRM_CUST.
2/ Go to Object Categories.
3/ Select Object Category OT_FOR_BS.
4/ Go to Object Categories > ILM Objects.
5/ Select EC_PCA_ITM.
6/ Go to Object Categories > ILM Objects > Object Category-Specific
Settings.
7/ Select ILM Object: EC_PCA_ITM.
8/ Go to ILM Object > Determination of Object Instance Key for BOR Obj.
9/ Enter to change mode.
10/ Add line as per below:
Source Table: GLPCP
Source field: GL_SIRID
Position: 2
11/ Save changes.
Archiving object RV_LIKP can be handled by SAP note 2830402
Archiving of sales orders (archiving object SD_VBAK) may result in an error
(DYNSQL_GENERATE_WHERE_CLAUSE) in S3VBAKWRS because of missing
customizing on residence periods (Tcode VORA, DB-table tvara)