MESSAGE_TYPE_X dump with error message BA008 occurs while data archiving

[JGery]

When executing multiple data archiving programs in one job, following dump occurs:

Dump:

Runtime Errors               MESSAGE_TYPE_X

ABAP Program               SAPLARCJ

Application Component     BC-CCM-ADK
...

Message class....... "BA"

Number.............. 008

Variable 1.......... "job_init"

Variable 2.......... "WRONG ADMI_JOBS ENTRY FOR DEL"
...

Termination occurred in the ABAP program "SAPLARCJ" - in "JOB_INIT".
The main program was "PRARCHD1 ".
...
264 * no archiv_key in case of xml archiving object
265         IF gv_admi_jobs-document IS INITIAL
266         OR ( gv_xml IS INITIAL AND gv_admi_jobs-archiv_key IS INITIAL ).
>>>>>           MESSAGE x008 WITH

268           'job_init' 'WRONG ADMI_JOBS ENTRY FOR DEL'

The cause for this is that in appropriate job multiple steps with archiving programs (like write program and delete program) are executed.
For example program RSARCHD is executed as a second step after write program.

This is not suggested and also does not correspond to standard data archiving process.

So do not executed differnet archiving steps in one job.

(Data archiving should always be carried out via transaction SARA)

If you wish to execute delete step automatically following solutions can be used:

1. In customizing set delete job to be executed automatically as follows:
   1. Call transaction SARA
   2. Enter name of archiving object
   3. Click on button "Customizing"
   4. Under "Archiving Object-Specific Customizing" choose "Technical settings"
   5. Under "Delete Jobs" set "Start automatically"
      
      
2. Usage of event SAP_ARCHIVING_WRITE_FINISHED
   
   Information from online help regarding this event:
   
   Write Run Followed by Event After the creation of all archive files for an archiving session has been completed, the Archive Development Kit (ADK) triggers the system event SAP_ARCHIVING_WRITE_FINISHED. As a result of the reaction to the system event, you have the option of scheduling subsequent archiving jobs automatically. These include refilling indexes or value help as well as saving archive files prior to deletion. The event parameter is always the number of the archiving session.