SAP Data Archiving job definition

Control-M for SAP can automate the following Data Archiving sessions:

• Write: The job runs spawns Delete jobs in the SAP system. These Delete jobs then spawn Store jobs. For more information, see: Creating Data Archiving Write jobs.
• Delete: The Delete jobs that were created by the Write job in SAP are ordered automatically into Control-M by the Extractor process using this template. For more information, see: Creating a Job Definition template for Delete jobs.
• Store: The Store jobs that were created by the Delete jobs in SAP are ordered automatically into Control-M by the Extractor process using this template. For more information, see: Creating a Job Definition template for Store jobs.

  If you use a store-before-delete, instead of a delete-before-store, configuration (defined using the SARA transaction in SAP), you must switch between the Store and Delete templates in Control-M.

A sample Data Archiving session, containing all the components described above, is provided in a Control-M Workload Automation draft file, named Data_Archiving_example_XBP(10/20/30)_800.xml located in the <DVD_ROM>\Tools\Data_Archive_Drafts directory. Choose XBP1 draft, XBP2 xml or XBP3 xml files according to your Control-M/EM version.

The templates for Delete and Store jobs should only be created as templates. Do not order or submit them.