Archiving is a service standardized by SAP that massively removes data that were not necessary. These data are archived and accessible, if necessary, in the future.
To carry out this archiving, SAP offers "archiving objects" that are used to group and relate one or more tables of data to be archived, a writing program (creation of a file), a deletion program and a reload program (optional) .
For the solution b + SII has been created the archiving object / EDGE / SII that store the following tables:
| Table | Description |
|---|---|
| EDOCUMENT | eDocuments |
| EDOCUMENTHISTORY | History of eDocuments |
| /EDGE/SII_ID_FAC | The relationship between ID Invoice and eDoc. |
| EDOCUMENTREF | Relationship between eDocuments and batches |
| /EDGE/SII_AL_002 | Alarms for eDocument |
| /EDGE/SII_AL_008 | Relationship between alarms and notifications |
| /EDGE/SII_AL_004 | Notifications |
| /EDGE/SII_AL_011 | Sending by notification |
| /EDGE/SII_AL_013 | Relationship between alarms and notifications |
Transation
AOBJ
It is necessary to create the variants of the writing program that will be responsible for selecting the records that will be stored in the generated file. You can generate as many variants as you want. It is recommended to generate a copy of the variant with the option of "Test mode" selected to be able to verify the eDocuments that will be archived in the real execution
Transaction
/EDGE/SII_EDOC_WRI
The necessary parameters must be filled in to make the selection of eDocuments to be archived and recorded 
Fill in name, description and record
These variants are those will be used later in the archiving step.The archiving process is detailed in the following point 480707227
CUSTOMIZING DESTINATION OF FILES
The destination of the generated files can be within the SAP system itself or any type of external storage
Transation
AOBJ
The object /EDGE/ SII is selected and under the section "Customizing Setting" the "Logical file name" is established, which establishes the storage destination.
