Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF-DRT (Application Component) Data Retention Tool⤷
FA_ILM (Package) Information Lifecycle Management
IMG Activity
| ID | ILM_C_STRC | Define Segments |
| Transaction Code | S_E4A_94000085 | (empty) |
| Created on | 20080326 | |
| Customizing Attributes | ILM_C_STRC | Define Segments |
| Customizing Activity | ILM_C_STRC | Define Segments |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ILM_C_STRC |
Use
In this Customizing step, you enter an ABAP Dictionary structure for each different type of data. In the context of Context Data Extractor, the ABAP Dictionary structure is called a "segment" or "segment structure".
Context Data Extractor is used to archive structured data. It does not archive unstructured data, such as images in TIF or JPEG format.
Furthermore, you can classify the segment as master data or transactional data, and assign an application defined in the Define Application IMG activity.
Requirements
In general, we recommend that you use application-specific programs for archiving transactional data. You should not use Context Data Extractor for archiving transactional data; or you should use it only as an exception if the volume of transactional data is low.
For very simple master data and Customizing data, you can use the structure of the corresponding database table as a segment in Context Data Extractor. If the database table contains amounts related to a currency type or unit (PC) that is stored in a different table, then we recommended that you create a new ABAP Dictionary structure to combine the amounts and the related currency types or units in one single structure. The advantage is that this makes reporting much easier later on.
Standard settings
SAP delivers predefined segments that you should not change. Usually you only have to add your own additional customer-specific segments during an Information Lifecycle Management (ILM) project. These segments must be created in the customer namespace.
Activities
Create new entries only for data that is not covered by predefined segments.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | ILM_C_STRC | 0 | HLB0100372 | Data Retention Tool |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| TXX_C_STRC | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20080407 |
| SAP Release Created in | 604 |
