Show TOC

Procedure documentationTriggering Generic CDE from the Legacy System

Prerequisites

Ensure that you have:

  • created an appropriate RFC destination to the RW system.

  • identified the tables and packages to be excluded from the generated archiving objects.

  • created transport requests, one each in the legacy system and the RW system.

  • identified an existing package or created a new package in the legacy system for the generated reports.

  • created a role and assigned the authorization object S_ILMGCDE to the users to trigger Generic CDE using the transaction ILMGENCDE.

Procedure

  1. Call transaction ILMGENCDE.

  2. Enter the following data:

    • RFC destination to the RW system

    • Package in the legacy system for the generated reports

    • Prefix for the generated reports

      Note Note

      Reports can also be generated with customer namespaces as the prefix.

      For example, if prefix is RWRI, the name of the generated report looks like RWRI_FI_AA.

      End of the note.

    • Language key

      Note Note

      • Select one or more languages to fetch the text values of the structures TXI_METADATA_TEXT and TXI_DD07T in the selected languages only.

      • Selecting more than two languages will increase the size of the newly created archiving object SN_META_G.

      End of the note.

    • Transport requests in the legacy and RW systems

    • Application component name

      Note Note

      • You can select one or more application component names

      • Only the tables only corresponding to the selected application components are considered for grouping to create an archiving object.

        Example Example

        • If you select FI* as the application component, all tables corresponding to FI and the FI sub-components (such as FI-AA, FI-AA-CP) are considered for grouping.

        • If you select FI-AA as the application component, all tables corresponding only to the sub-component FI-AA are considered for grouping.

        End of the example.
      End of the note.

  3. You can select one of the following logging options:

    • Error Messages Only

    • Detailed Log

  4. To start data extraction, choose Start Extraction.

  5. To view the log history, choose Show Log History.

Result

In the legacy system, AOBJ is updated with the newly created archiving object along with the snapshot-enabled Write report and a dummy Delete report. The Write reports are executed as background jobs to create Archive Files automatically. The archiving object SN_META_G is generated. This is similar to the archiving object SN_META generated using CDE.

In the RW system, while the archiving objects are generated, an AOBJ is updated with the same object name but with the dummy Write and Delete reports. The Structure Definition is not maintained for the archiving object generated in the RW system. In addition, IRM_CUST is updated and mapped to the ILM object.

In Customizing for the AOBJ, the description of an archiving object contains the name and description of the application component.