Kontakt

Ansicht
Dokumentation

IRW_EDITCONF - Legacy Extraction Workbench

IRW_EDITCONF - Legacy Extraction Workbench

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

The Legacy Extraction Workbench is used to simplify the extraction of data from legacy systems using SAP Landscape Transformation (LT) for the ILM System Decommissioning scenario. The process can be defined in three main steps:

  1. Extraction of Data from LT - When you retrieve the data from LT, tables extracted from different legacy systems should be stored in different clients. This helps you identify legacy systems during the run process. The legacy system is identified by the mass transfer ID.
  2. Configuration - The configuration defines how the creation of archiving objects and Context Data Extraction (CDE) SN objects is modelled. This is a client-independent step.
  3. LT Run - You should execute the LT run in the same client that you used in the legacy system. For example, if you have extracted data for client 011 from the legacy system, you should execute the LT run in client 011 of the LT system.

Pre-requisite:

  • ILM should be switched on.
  • Rules and policy should be maintained

This enables you to create archiving object write reports that are executed based on the defined rules.

Note: If the run is not executed in the correct client, the execution fails.

Extraction:

If you are trying to extract data from an SAP system, you must extract the table DD03L. We also recommended that you extract ARCH_OBJ, ARCH_DEF and ARCH_TXT as they contain the definition of the archiving object. You must also extract the text tables associated with the corresponding tables.

Configuration steps:

Choose Configuration to open the Display View: "Mass Transfer Information": Overviewscreen.

On this screen, you maintain data for a legacy system. The legacy system can be an SAP system or a non-SAP system. If the legacy system is an SAP system, you can create new archiving object definitions or obtain object definitions for the archiving objects belonging to the legacy system. If the legacy system is a non-SAP system, you can define only the archiving objects.

You can register tables for context data extraction and maintain cluster tables.

You also use this to verify whether the configuration is consistent.

You can perform mass maintenance of Context Data Extractor (CDE) using the Maintain Mass CDE button. For more information about mass maintenance of CDE, see link.

You can also copy the configuration from the source mass transfer ID to the target mass transfer ID. For more information about copying configurations, see link.

This Customizing activity contains six subtasks:

  • Maintaining Mass Transfer Information
  • Maintaining Additional Information
  • Maintaining Archiving Objects
  • Maintaining Structure Definition
  • Maintaining Table Relationship
  • Maintaining Tables for Context Data Extraction
  • Maintaining Cluster Tables

Maintaining Mass Transfer Information

Prerequisites

Mass Transfer ID should exist.

To maintain mass transfer information, proceed as follows:

  1. Choose Mass Transfer Information.
  2. Choose Display->Change.
  3. Choose New Entries.
  4. Enter the following:

Note: If this is an SAP system, the RFC connection must be maintained and should be a trusted RFC connection.

  1. Choose Save. The Legacy Extraction Workbench checks whether the system is an SAP system. If the system is an SAP system, it checks whether the RFC connection works, whether all mandatory tables exist, and the related tables have been transferred.

Maintaining Additional Information

Prerequisites

A mass transfer ID exists.

To maintain additional information, proceed as follows:

  1. Choose Additional Information.
  2. Choose Display->Change.
  3. Choose New Entries.
  4. Enter the following:

  • Productive Client(Maintains a unique client of Legacy Extraction Workbench for each legacy system/client)

  1. Choose Save.

Maintain Archiving Objects

The archiving is performed according to the table relationship model. In the table relationship model, every child table should have a relationship with the immediate parent table. This ensures that the data is grouped logically.

The table relationship describes the relationship between parent and child tables. There must be at least one common field in the parent and child tables so that a relationship is established.

Prerequisites

  • You have configured the mass transfer information ID.

To maintain an archiving object, proceed as follows:

  1. Select a mass transfer ID and choose Archiving Object.
  2. Choose New Entries.
  3. Enter the following:
  • Archiving Object(mandatory)

Note: If the legacy system is an SAP system and if the table ARCH_OBJ is transferred, you can select the archiving object from the list. In case of non-SAP systems, the archiving object name should start with a Y or Z.
  • Description(The description of the archiving object is retrieved from ARCH_TXT)

  • Object Configuration Status(this field is for display purposes only)

  1. Choose Save.
  2. You can select the archiving objects and choose the Get Structure Definitions button to generate the structure definitions.
Note: The Get Structure Definitionsbutton is displayed only if the legacy system is an SAP system and if the table ARCH_DEF is transferred from the legacy system.

Maintaining Structure Definition

Structure definition indicates that the parent and child table are included in the modelling of archiving objects. Every archiving object has a header table that is used as the root for modelling. The header in the structure definition isindicated by thelowestsequence number and it should have the same entries for the parent table and child table

Prerequisites

At least one archiving object entry should exist.

You can view entries in a structure definition only for legacy SAP systems and only if you have already generated them using the Get Structure Definitions button.

To maintain a structure definition, proceed as follows:

  1. Select an archiving object and choose Structure Definition.
  2. Choose New Entries.
  3. Enter the following:
  • Sequence (mandatory)

  • Parent table(mandatory)

  • Child Table(mandatory)

  1. Select the structure definitions and choose Get Table Relationshipto generate the table relationship.
  2. Choose Save. The Legacy Extraction Workbench checks whether the parent table and child table are present in both SAP and non-SAP legacy systems.
Note: The parent table and child table entries should be the same for the minimum sequence number in the structure definition.

Maintain Table Relationship

Table relationship - Indicates the relationship between the parent and child tables. There must be at least one common field in the parent and child tables so that the relationship is established.

Prerequisites

A structure definition exists.

You can view entries in the table relationship if you have already generated them using the Get Table Relationship button.

Table relationships should be maintained for all structure definitions except the header. You can use the existing table relationship or create a new one, depending on your requirements.

To maintain a table relationship, proceed as follows:

  1. Select the structure definition and choose Table Relationship.
  2. Choose New Entries.
  3. Enter the following:
  • Position (mandatory) - This indicates the position of the key field in the query used to extract data from the legacy system.

  • Parent field (mandatory) – This is the key field in the parent table.

  • Child field- (mandatory) – This is a field in the child table.

  1. Choose Save. The Legacy Extraction Workbench checks whether the parent field and child field are present.

Maintain Tables for Context Data Extraction

Context Data Extraction is an extraction of all entries of each table into an archive file without any logical grouping. The company code-dependent tables in SAP are extracted based on the company code grouping.

Prerequisites

  • CDE should be switched on to make the F4 Help available.
  • A mass transfer ID exists.
  • A table maintained in an archiving object should not be added for context data extraction

To maintain tables for context data extraction, proceed as follows:

  1. Select the mass transfer ID.
  2. Choose Tables for Context Data Extraction.
  3. Choose New Entries.
  4. Enter the following:
  • Table Name (mandatory)

  • Application (mandatory)

  1. Choose Save. The legacy Extraction Workbench checks whether the table exists and whether it is part of an archiving object.

To maintain tables for context data extraction using the Get Tablesbutton, proceed as follows:

To reuse the existing CDE configuration, you can use the Get Tables button. This will reduce the configuration time. This feature enables you to view and select the tables that can be used for configuration. The Status column indicates whether the tables can be used for CDE configuration. These statuses are possible:

  • Red - Table not extracted or table not active. This is disabled for selection.
  • Green - The table can be selected for configuration.
  • Yellow - Table already registered for CDE. This is disabled for selection and the checkbox is selected by default.
  1. Select the mass transfer ID.
  2. Choose Tables for Context Data Extraction.
  3. Choose Get Tables.
  4. Select the applications for configuration.
  5. Choose Continue. A list of tables corresponding to the selected application displays.
  6. Select the tables for configuration with status Green.
  7. Choose Continue.
  8. Choose Save. The table and application configured for CDE are displayed.

Maintain Cluster Tables

The Legacy Extraction Workbench lets you add cluster tables that are transferred from the legacy system using an RFC function module since the Landscape Transformation (LT) system cannot extract cluster tables from the legacy system. For example, the cluster table BSEG (Accounting Document Line Item).

Prerequisites

  • A mass transfer ID exists.

To maintain tables for context data extraction, proceed as follows:

  1. Select the mass transfer ID.
  2. Choose Cluster Tables.
  3. Choose New Entries.
  4. Enter the following:
  • Source Table(mandatory)

  • Generated Table(mandatory)

  • Number of Records(mandatory)

  1. Choose Save. The Legacy Extraction Workbench checks whether the table exists.
  2. Choose Exit to return to the Create Archiving File for Configured Object screen.

LT Run

This is the last step of the extraction process.

The Configured Systemssection displays the list of configured systems.

Perform the following steps:

  1. Select the system from the Links to Configured Systems section.
Note: The following details are displayed on the panel at the right: Mass Transfer ID, Legacy System ID, and Configuration Status.
  1. In the Archiving Options section, you can select either Archiving Object or CDE. Depending on your selection, the values in the Sessions and Files section will change.
  2. Select the archiving object or application from the Sessions and Files section.

Perform the following steps to create archive file for the archiving objects:

  1. Choose Create Archiving Files. The Generate Write Reportdialog box appears.
  2. Choose Generate.
  3. Select the fields from the Select Fields for Write Report Selection screen.
  4. Choose Continue. The message "Write report successfully generated; schedule file creation" appears.
  5. Choose Create Archiving Files. The Schedule: Create Archive File for Archiving Objects screen appears.
  6. Enter the variant.
  7. Maintain the Start Date.
  8. Maintain the Spool Parameters.
  9. Choose Check Variant.
Note: If the variant is consistent, the Continue button appears.
  1. Choose Continue.

The message for job scheduling is displayed. You can check the job status by choosing the Job Overviewbutton.

You can also use the Archiving Session Statistics button to view the statistics of the archiving run.

For more information, look for Variant Maintenance for Archiving Jobs in the documentation for SAP NetWeaver at http://help.sap.com.

Perform the following steps to create archive files for CDE

  1. Choose Create archiving files. The Schedule: Create Archive File for CDE Objectscreenappears.
  2. There are two options available for CDE extraction:
  • Archive all tables configured for the selected CDE object

  • Enable Include or Excludeoftheselected tables for CDE extraction

Note: If you select the Include option it will consider only the tables selected for archiving. The Exclude option will not include the tables selected for CDE extraction.
  1. Select the tables.
Note: Follow steps 2 and 3 only if you want to schedule extraction for selected tables.
  1. Maintain the Start Date.
  2. Maintain the Spool Parameters.
  3. Choose Continue.

The message for job scheduling is displayed. You can check the job status by choosing the Job Overviewbutton.

You can also use the Archiving Session Statisticsbutton to view the statistics of the archiving run.

For more information, look for Maintaining Start Date and Spool Parameters in the documentation for SAP Net Weaver at http://help.sap.com.

Perform the following steps to browse the archive file for the archiving objects:

  1. Select an archive file.
  2. Choose Browse Archive File. The Browse Archive File Window appears. The mass transfer ID and the selected archive file appears.
  3. Select the Table Name. The list displays all of the tables present in the archive file.
  4. Enter the Data Object. You can also view the total number of data objects.
  5. Choose Execute or press ENTER. The table content is displayed for the selected data object in the archive file.






Vendor Master (General Section)   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 21513 Date: 20240523 Time: 190057     sap01-206 ( 251 ms )