Object documentationArchiving of Condition Records (SD-MD-CM)

 

Condition records are archived using archiving object SD_COND.

 

To call condition archiving, go to the Sales Master Data screen and choose Start of the navigation path Conditions Next navigation step Archiving Next navigation step Create Archive. End of the navigation path

Alternatively, you can call archiving using Start of the navigation path Tools Next navigation step Administration Next navigation step Administration Next navigation step Data Archiving End of the navigation path and enter object name SD_COND. Before using the archiving object for the first time, you should check Application Customizing.

See also Application-Specific Customizing (SD-MD-CM)

Structure

Tables

With SD_COND, data from various tables is archived and deleted. To find out how to display the table names, see the application documentation for data archiving under Start of the navigation path Data Archiving in the ABAP Application System Next navigation step Data Archiving with Archive Development Kit (ADK) Next navigation step Archive Administration Next navigation step Tables and Archiving Objects End of the navigation path. In addition, table entries are archived together with the condition data by means of the following archiving classes:

  • CHANGEDOCU

  • TEXT

Customer-Specific Tables

You can extend the archiving scope of SD_COND without modification with the aid of Business Add-In (BAdI) ARC_SD_COND_WRITE, which is integrated into the write program.

Programs

The following programs are delivered with SD_COND:

Program

Function

SD_COND_ARCH_WRITE

Write

SD_COND_ARCH_DELETE

Delete

SD_COND_ARCH_RELOAD

Reload

Write Program

The write program supports the ADK interruption concept, that is, you can interrupt the write phase and continue at a later point. For more information, see the application documentation for data archiving under Start of the navigation path Data Archiving in the ABAP Application System Next navigation step Data Archiving with Archive Development Kit (ADK) Next navigation step Archive Administration Next navigation step Interrupting and Continuing Archiving Sessions End of the navigation path.

A compact log with information about the data processed is written in both the write and delete runs. Alternatively, you can enable the output of a detailed log containing additional information. For more information, see Start of the navigation path Archive Administration Next navigation step Logs End of the navigation path.

Logging Non-Archivable Data

During condition archiving, the detailed log provides a list of records that cannot be archived according to the archivability check. The reason for this is also shown.

Reasons why a condition record cannot be archived:

  • The condition is still being used.

  • The deletion flag has not been set for the condition.

  • The residence time for the condition has not yet expired.

Customer-Specific Archivability Checks

You can extend the archivability check without modification with the aid of BAdI ARC_SD_COND_CHECK, which is integrated into the write program. For more information about implementing BAdIs in archiving programs, see SAP Note 673030Information published on SAP site.

Deletion Program

The standard variants SAP&PROD (production mode) and SAP&TEST (test mode) are delivered for the delete program.

ILM-Based Information for the Archiving Object

You can use this archiving object with the SD_COND ILM object as part of SAP Information Lifecycle Management. In order to do so, you must activate the associated business function Information Lifecycle Management (ILM) (transaction SFW5). The system then also displays the ILM Actions frame. You can use these actions to archive documents with the retention periods defined in the Information Retention Manager. You can also make snapshots (copies) of data or delete data that fulfills the prerequisites.

The following fields for SD_COND are defined in the ILM policy and are visible when processing ILM policies (transaction IRMPOL):

  • Available Time Bases

    End of Validity Period (END_OF_VALIDITY)

  • Available Condition Fields

    • Application (KAPPL)

    • Condition Type (KSCHL)

    • Usage of the Condition Table (KVEWE)

  • Available Policy Categories

    RTP: Retention Rules

For more information, see SAP Information Lifecycle Management.

Authorization Objects

You need the following authority object:

Authorization object

Description

V_KONG_VWE

Condition generation: Use and application of the condition table

See also:

For more information about the archiving object, see the application documentation for data archiving under Start of the navigation path Data Archiving Next navigation step Data Archiving in the ABAP Application System Next navigation step Data Archiving with Archive Development Kit (ADK) Next navigation step Archiving Object End of the navigation path.