Archiving Steps |
Resulting Product Status |
Status of the Archiving Run in the Archive Administration (ADK) |
Physical Location of Data |
Archiving flag (either manually or via customer-specific programs) |
To archive |
Database |
|
Preprocessing (can be scheduled to be periodic). |
Archivable Locked To be deleted |
Database |
|
Writing (can be scheduled to be periodic). |
Archivable Locked To be deleted |
Incomplete |
Archive file and database |
Deletion (can be scheduled to be periodic). |
Archivable Locked To be deleted |
Complete |
Archive file and database |
Postprocessing (can be scheduled to be periodic). |
Product status no longer visible in product maintenance as it has been physically deleted from the database. |
Complete |
Archive file |
The following programs and functions are used for archiving SAP Products:
Archiving Function |
Program |
User Interface / Use |
Execution Type |
Archive administration preprocessing |
COM_PRODUCT_ SELECTIONS |
Transaction SARA |
Job |
Archive administration writing |
COM_PRODUCT_ARC_WRITE |
Transaction SARA |
Job |
Archive administration deletion |
COM_PRODUCT_ARC_CHECKBACK |
Transaction SARA |
Job |
Archive administration postprocessing |
COM_PRODUCT_ARC_DELETE |
Transaction SARA |
Job |
Select product GUIDs to be archived |
Function COM_PRD_PRESELECT_FOR_ARCDEL |
BOR Method |
Implicit Use |
Usage check |
Function COM_PRD_VERIFY_FOR_ARCDEL |
BOR Method |
Implicit Use |
Delete products |
Function COM_PRD_DELETE_FOR_ARCDEL |
BOR Method |
Implicit Use |
Display products from the archive |
Transaction COMM_PRDARC |
||
Customer-defined deletion checks |
Implementation of Business Add-In PRODUCT_ARCHIVE Method VERIFY_EXTRA_DATA |
BAdI Method |
Implicit use: Calling point in program COM_PRODUCT_ARC_CHECKBACK |
Customer-defined usage checks |
Implementation of Business Add-In PRODUCT_ARCHIVE Method CHECK_ARCHIVABLE |
BAdI Method |
Implicit use: Calling point in preprocessing program in function module COM_PRD_VERIFY_FOR_ARCDEL |
Customer-defined extension for archiving additional data |
Implementation of Business Add-In PRODUCT_ARCHIVE Method ARCHIVE_EXTRA_DATA |
BAdI Method |
Implicit use: Calling point in program COM_PRODUCT_ARC_ WRITE |
Customer-defined extension for archiving additional data in structures |
Implementation of Business Add-In PRODUCT_ARCHIVE Method EXPAND_EXTRA_STRUCTURE |
BAdI Method |
Implicit use: Calling point in program COM_PRODUCT_ARC_ WRITE |
Customer-defined extension for deleting additional data |
Implementation of the Business Add-In COM_PRODUCT_DELETE Method DELETE_EXTRA_DATA |
BAdI Method |
Implicit use: Calling point in program COM_PRODUCT_ARC_ DELETE |
The archiving of SAP Products can be extended using the following Business Add-Ins:
Business Add-In |
Method / Use |
PRODUCT_ARCHIVE |
Using the method CHECK_ARCHIVABLE, you can define your own usage checks for SAP Product. Using the method ARCHIVE_EXTRA_DATA, you can write additional data per product to the archive file. Using the method EXPAND_EXTRA_STRUCTURE, you can include additional table structures for the SAP Product in the archiving . Using the method VERIFY_EXTRA_DATA, you can define your own deletion checks for SAP Product. |
COM_PRODUCT_DELETE |
Using the method DELETE_EXTRA_DATA, you can define other data that is to be deleted when deleting a product and that does not directly belong to product master. However, you do not use this BAdI to delete the data of customer-defined set types; this is automatically integrated in archiving during generation. |
For more information on Business Add-Ins, see the Customizing of the
Cross-Application Components
under
The following structures are used to define the archiving object:
Defines the product archiving framework. |
PRODUCT_MD |
Archiving information structure Defines the amount of all those fields that can be indexed that can used in field catalogs and thus in product archives. For more information, see Archive Information System . |
SAP_PRODUCT_AIS |
Structure of an archive index that is maintained in the SAP Archiving Information System. A field catalog always belongs to an archiving information structure. An archiving information structure always belongs to an archiving object. |
SAP_PRODUCT_MD |
The data archived and deleted in the archiving object PRODUCT_MD comes from the following fixed tables. All of the table structures that are to be archived (such as customer-defined set types) are determined when the archiving write program is run:
Table |
Description |
COMM_PRODUCT |
Product header data |
COMM_PRODUCTH |
History of the product header data |
CRM_JCDO |
Change documents for the status object |
CRM_JCDS |
Change documents for the system /user status |
CRM_JEST |
Individual status per object |
STXB |
SAPscript texts: Texts not in SAPscript format |
STXH |
SAPscript texts: Header |
STXL |
SAPscript texts: Lines |
Additional data for the product (for example, set types and multi-value attributes) are archived and deleted. This data is determined dynamically in the archiving write program.