Show TOC

Procedure documentationRegistering Database Tables with Context Data in CDE

 

The purpose of CDE is to extract context database tables that contain Customizing settings, master data, or metadata from the legacy system. When you extract data from a legacy system, CDE writes the registered database table to the file system. The files created by CDE belong to the generated archiving objects whose names start with the prefix SN_ (such as SN_FI).

Prerequisites

To evaluate the data in an archiving object, you may need some additional information not contained in the archive files, such as the content of check tables, texts for check table content, and master data.

Check the application database tables and decide whether the check tables used there are needed for your evaluations.

Note Note

To ensure that the assignment of check tables in DDIC (transaction SE11) is correct, consult those who are responsible for the archiving objects as well as the relevant application expert when you run the check.

End of the note.

Procedure

1. Call the CDE Configuration Menu.

Call transaction ILM in the SAP system. The transaction creates the Configuration menu structure in the SAP menu.

2. Create CDE Applications

If the existing CDE applications are insufficient for grouping database tables according to business aspects, create CDE applications as follows:

  1. In the configuration menu, choose Start of the navigation path Define Application End of the navigation path (transaction ILM_C_APPL).

  2. Enter the CDE application (with a description and display sequence).

    Recommendation Recommendation

    We recommend creating separate CDE applications for company code-dependent CDE content. Use the following syntax for naming these CDE applications: <Application Name>-C.

    End of the recommendation.
3. Assign an Archiving Object Generated by a CDE Application

  1. In the configuration menu, choose Start of the navigation path Define Archiving Object End of the navigation path (transaction ILM_C_OBJECTS.

  2. Choose the application package Information Lifecycle Management and the application.

  3. Enter the CDE archiving object (SN_*) you want to generate.

    Naming convention: If the application name has the syntax <Application Name>-C, specify the name SN_<Application Name>C for the archiving object.

4. Map the Database Table as a DDIC Structure

In client 100 of the development system, create a DDIC structure corresponding to each database table. The DDIC structure is required if you want to generate data for the archiving object. Proceed as follows:

  1. Call transaction SE11 in the SAP system.

  2. Choose Data Type and enter the structure name in the form TXI_<Table Name>.

  3. Choose Create, and then choose Structure.

  4. Enter the table as the component. Changes to the table now have no effect on the DDIC structure.

  5. If you have saved information about units of currency and measurement in a separate reference table, make an according entry in the DDIC structure. Use the following syntax:

    Units of currency: <Field Name>_CY

    Units of Measurement: <Field Name>_QY

  6. Save the structure under a transport request.

  7. When you have added the entries for units of currency and measurement, proceed as follows:

    • Define a (generic) function module for exchanging the content of the reference fields in the table with that of the referenced DDIC structure. Enter the function module in transaction ILM_C_CON (segment control).

    • Enter the unit of currency or measurement in the Customizing table TXX_C_REF (reference for currency and quantity fields).

5. Map DDIC Structure as CDE Segment and Assigning CDE Application

  1. In the configuration menu, choose Start of the navigation path Define Segments End of the navigation path (or start transaction ILM_C_STRC).

  2. Add a new entry with the following data:

    • Segment Name: Enter the name of the corresponding DDIC structure TXI_<Table Name>.

    • Description: Enter the description of the corresponding DDIC structure.

    • Master Data Segment: If you want to regard BW content as BW master data (for the generation of InfoObjects), you need to select this checkbox.

    • Customer-Specific: If this segment has been defined for your company, then select this checkbox.

    • Type: Choose Data Records (Transaction and Master Data.

    • Application: Select the CDE application to which you want to assign the segment.

6. Assign CDE Segment to Database Tables

  1. In the configuration menu, choose Start of the navigation path Assigning Tables to Segment End of the navigation path (transaction ILM_C_SOEX).

  2. Create new entries with the following data:

    • Segment name

    • Name of the database table

7. Enter Tax Information of the CDE Segments

  1. Ensure that function modules are available for the following purposes:

    • Function module for the extraction of the table content of registered CDE database tables

      You can use the function module TXILM_EXTRACT_TABLE delivered by SAP directly or as a template. This function module extracts database content according to the Tax audit area supplied by SAP.

      Note Note

      The function module for the extraction of table content needs to be able to process mass data and it must not be interrupted by termination messages. The function module DB_COMMIT has to trigger the Commit Work.

      End of the note.

    • Optional segment function module for processing or formatting selected content, for example, for completing information for currency keys or units of measurement.

  2. In the configuration menu, choose Start of the navigation path Segment Control End of the navigation path (transaction ILM_C_C_CON).

  3. To define how the system is to extract segment content from database tables, create an entry with the following data for each segment:

    • Application Package: Choose Information Lifecycle Management

    • RF: Select the next free number in the number range. The number you specify must match the number range in the audit area:

      • 1 – 4999: Reserved for FI (Tax audit area)

      • 5000 – 9999: Reserved for objects from ERP processes (Product Liability audit area)

      • 10000 – 14999: Reserved for IS Utilities

      • 15000 – 19999: Reserved for IS Oil

    • Segment Name: Choose the segment (TXI_*).

    • Function Module: Select the appropriate function module for the extraction of content from database tables.

    • Segment Function Module: Optional: Choose the segment function module for enriching the selected content.

    • Active: Select the checkbox.

8. Define the Relationship Between Segments

You need to edit the relationship between segments in the following cases:

  • The content of text tables is required for evaluations, however, the content of these tables is not stored together with the archived information.

  • Foreign Key relationships between tables are not defined in DDIC or contain errors.

  1. In the configuration menu, choose Start of the navigation path Define Relationship Between Segments End of the navigation path (transaction ILM_C_RELA.

  2. Create an entry with the following data for each relationship between segment:

    • Relationship Name: Enter the relationship name subject to the following naming convention: 0<Segment Name>-<Field Name> (The 0 indicated the SAP namespace)

      Note Note

      If multiple relationships are required for a field, differentiate between them by adding the appropriate suffix to the relationship name (such as consecutive numbers).

      End of the note.

      • No.: If you define segment relationships for multiple fields, use the number to specify the sequence of these fields.

      • Segment Name and Field Name. Segment and field of the table that are to form a relationship with another table.

      • Segment Name and Field Name. Segment and field of the table for which the relationship is to be defined.

      • Constant: If a constant field value is required, enter it here.

More Information

In the configuration menu, choose Start of the navigation path Segment Catalog End of the navigation path (transaction S_E4A_94000025) or Start of the navigation path Field Catalog End of the navigation path (transaction S_E4A_94000026) to list segments or segment fields and their respective settings.