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_C_CON | Define Customer-Specific Extraction Flow |
| Transaction Code | S_E4A_94000184 | (empty) |
| Created on | 20080604 | |
| Customizing Attributes | ILM_C_C_CON | Define Customer-Specific Extraction Flow |
| Customizing Activity | ILM_C_C_CON | Define Customer-Specific Extraction Flow |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ILM_C_C_CON |
Use
In this Customizing step, you assign a function module to each customer-specific segment. You also define the sequence of the segments during the archive run.
Context Data Extractor provides a generic function module for selecting data from a database table. The generic function module can be used if all entries of the database table have to be archived and the table contains no fields (amounts) related to a currency type or unit. In any other cases, you have to implement specific function modules and assign them to the related segments.
During an archive run, Context Data Extractor archives the data in the sequence defined in this step and calls the corresponding function modules. The function modules contain the implementation of the database retrieve.
Requirements
Standard settings
The table contains customer-specific configuration only. You can view the process flow provided by SAP under Define Extraction Flow.
Activities
Add your customer-specific segments and define the sequence by entering a sequence number. By default, the system processes the segments delivered by SAP first and the customer-specific segments afterwards. But you can insert your own customer-specific segment in the sequence of the SAP process flow. To do so, enter the sequence number of the SAP flow definition in the Insert Number field.
If possible, use the generic function module of Context Data Extractor to retrieve data from the database. Otherwise, you have to implement customer-specific function modules. This should be necessary only in exceptional cases.
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_C_CON | 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_CON | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20080627 |
| SAP Release Created in | 604 |
