Ansicht
Dokumentation
RSEXARCB - IDoc Archiving Program for Periodic Implementation in Background
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up General Data in Customer MasterThis documentation is copyright by SAP AG.
Description
The archive program has the task of reading IDocs for archiving and writing them to an archive. The actual deletion of these archived Idocs from the SAP database is carried out with the deletion program. The archiving program offers a number of selection parameters with which you can deliberately control which IDocs are to be archived. The selection parameters are:
- Time unit
- Start of archiving before runtime (in the chosen time units)
- Time that the archive should require (in the chosen time units)
- Logical message
- Message type
- Message variant
- Message function
- Direction
The archiving program puts together the list of IDoc numbers that were defined by the selection criteria and transfers these to the module 'EDI_ARCHIVE_IDOCS'. This then carries out the archiving of the IDocs.
After archiving, a log is output which lists the IDocs that have actually been archived. This list may also contain IDocs whose status does not allow archiving. Which status values can be archived and which ones cannot is currently determined explicitly by the form routine 'INITIALIZE_STATUS_QUALITY' in the function group 'EDIA', in the implementation of the archiving class and in the archiving program functionalities. This ensures that IDocs with status values intended for further processing are not archived.
This is the second archiving program with which IDocs can be archived as independent archive authorization objects (there is also the report RSEXARCA). However, this program differs from the other archiving program in its objective. This program is intended for periodic use and correspondingly provides the option of working with relative values according to the date when selecting IDocs instead of working with absolute values. As a result, the periodic use of this program in the background will be especially user-friendly, as there is only one variant that is constantly used and that needs to be maintained. The period of archiving as well as the starting time is determined in the variant used. The administrator can adjust this according to requirements. There is an option to choose the time unit, thus you can choose whether the archiving period is in days, weeks or in other predefined time units. You should make sure here that the parameters chosen in the program variant are appropriate for the chosen background parameters. Otherwise the periodic execution of the archiving program will not be carried out in the correct sequence with the selection of the IDocs to be archived This can lead to overlaps or gaps in the archiving of IDocs.
Caution :
Only use this archiving program for IDocs if the IDocs are not archived by the application. You must insure that IDocs are not archived if they could possibly still be needed by the application.
Output
A log is generated in which the most important fields of the Idoc control records are output. In addition, the total number of archived IDocs is output.
Example
Time unit : Day
Start archiving before runtime: 10 Days
Period of archiving : 5 Days
Message type :
Message variant :
Message function :
Direction (1=Outbound, 2=Inbound) :
At runtime, two dates are determined which define the range of archiving. Thus, archiving should start 10 days before runtime and include a period of 5 days. If the program runs in the background on January 10th, all IDocs that were processed from December 31st to January 4th are archived,in the next run on January 15th all IDocs from January 5th to January 9th are archived and so on.
By specifying further selection options, you can deliberately archive certain IDocs together.
Example
Time unit : Day
Start archiving before runtime : 10 Days
Period of archiving : 5 Days
Message type : ORDERS
Message variant :
Message function :
Direction (1=Outbound, 2=Inbound) : 1
As a result, only those outbound IDocs that are allocated to the message type ORDERS would be archived with this program at the times described above.
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 4687 Date: 20240601 Time: 061929 sap01-206 ( 106 ms )
