Archiving CO_ALLO_ST: New delete program
[(ADK)] [Archive] [archiving] [CO_ALLO_ST] [Development] [Kit] [new delete] [object] [program] [RKSARSD1] [RKSARSDL] [SARA] [Transaction] [vc new delete]
- Archiving class K_COSTS without structure information IISymptom When you create AIS information structures, terminations occur because structure information is missing in the archive. Other terms AIS, Audit Information System, ADK, Archive Development Kit, PP_ORDER, PM_ORDER PR_ORDER, PS_PROJECT, P_ORDER,...
- Reloading archived actual cost component split dataSymptom When you reload archiving sessions for material ledger actual cost component split data (archiving object CO_ML_SPL), the system does not reload all of the data from the archiving session. The wrong...
Symptom
In the deletion run during archiving with CO_ALLO_ST the system does not create any statistics of the records deleted by the database. This also affects the “Display statistics (Shift + F8)” function in transaction SARA, where the relevant columns display zero.
Other terms
Archiving, Archive Development Kit (ADK)
Archiving object CO_ALLO_ST
Program RKSARSDL, RKSARSD1
Transaction SARA
Reason and Prerequisites
Functions, which are implemented for technical reasons using the new delete program, are missing.
Solution
Use a new delete program for the archiving object CO_ALLO_ST. Import the Support Package assigned to this note.
Use transaction SCPR20 to activate the BC_SET ARCH_CO_ALLO_ST. This means the new delete program is entered in the definition of the archiving object CO_ALLO_ST and the relevant system variants SAP&PROD and SAP&TEST. You can finally check this with
SM30 / V_ARC_OBJ
(enter condition for archiving object: CO_ALLO_ST)
SM30 / V_ARC_USR
(enter condition for archiving object: CO_ALLO_ST)
If you want to implement this note in advance, carry out the following steps:
Check if the program RKSARSD1 already exists in your system.
If the program does not yet exist, implement the attached corrections. This means the program is created, but without text elements, program heading and required system variants. Create these manually:You can copy and paste the title of the program from RKSARSDL.Create the following text symbols.
SymTextmLen001Reversed document was deleted60002Reversal document was deleted60100Remark for archiving run40101Detail log40202Flow control40300Test mode40305Production mode40
Create a test mode variant and a production mode variant for the program RKSARSD1.
The test mode variant should be called SAP&TEST. In this variant, select the “Test mode” and “Detail log” parameters.
The production mode variant is called SAP&PROD. In this variant, select the “Production mode” and “Detail log” parameters.
If you cannot create variants with the above names in your system, use the names CUS&TEST and CUS&PROD.Add the new delete program RKSARSD1 to the archiving object CO_ALLO_ST. To do so, proceed as follows.Call transaction AOBJ. Double-click the archiving object CO_ALLO_ST. On the subsequent screen change the delete program to RKSARSD1. Save your entries.Call transaction SM30. Enter V_ARC_USR in the “Table/View” field and choose “Maintain”. Double-click the archiving object CO_ALLO_ST to select it. Enter the new variants for “Test Mode Variant” or “Production Mode Variant”. Save your entries.
After you make these changes, the delete program for CO_ALLO_ST will also create statistics for the deleted tables.