Create a Data Mapping Definition with SAP ECC as Source

Data Mapping supports SAP ECC as a source from SAP_APPL 600 (SAP ECC 6.0, ERP 2005) on.

Prerequisites

To use an SAP ECC system as a source instance, you must create a dedicated destination in the SAP BTP Cockpit, which will let the application know the location of the SAP ECC system you want to use. For more information, see Configure Destinations for SAP ECC as Source Instance.

Context

You can read the following SAP ECC tables with Data Mapping:

  • GL tables:

    • GLT0

    • GLT3

    • GLFUNCT

    • GLPCT

    • Customer special ledger Z tables (supported with customer extension scenario)

  • New GL tables:

    • FAGLFLEXT standard fields

    • Customer extended fields

The returned table structure stays the same for all scenarios.

The field content depends on the available fields of the source tables mentioned above.

Local Currency, Transaction Currency, and Group Currency are all supported.

Based on the general ledger principle, the source data table is determined by the ledger selected, a commonly used ledger is 0L (delivered standard ledger), where data is read from source data table FAGLFLEXT.

Users with access to the backend can display the relationship between ledger and source table in table T881 (field rfctarget).

The source table based on the ledger parameter is determined by function module BAPI_SL_GETTOTALRECORDS.

Users with access to the backend can use BAPI to locate and view their source data, which also helps building data mapping definitions more easily.

To access BAPI:

  1. Connect to the SAP ECC source system.

  2. Run the SE37 transaction to display the Function Builder.

  3. In the Function Builder, select function module BAPI_SL_GETTOTALRECORDS.

  4. Click Test/Execute.

  5. In function module BAPI_SL_GETTOTALRECORDS, define your import parameters.

  6. Click Execute.

  7. Under Start of the navigation pathTables Next navigation step TOTALS_SPL Next navigation step ResultEnd of the navigation path, choose Entries to display the source data selected.

You must create your mapping file in Microsoft Excel, as described in the chapter Structure of the Mapping File.

Procedure

  1. From the Data Mapping Definitions page, choose the Create button.
  2. In the General Information section, enter a name and a description.
  3. Optionally, select a parent definition. For more information, see Create Hierarchies in Data Mapping Definitions.
  4. Optionally, choose the Runnable from Packages option. For more information, see Specific Mapping File Structure for Jobs Runnable from Packages and Run a Job from Within a Package.
  5. In the Source Definition section, select the Source: SAP ECC System.
  6. In the Source Instance Used field, select an instance from the available instances retrieved from the SAP BTP Cockpit.
  7. In the Source Filters section, you can choose to filter values on SAP ECC dimensions.

    You can also use predefined keywords to define source filter values. For more information, see Use Predefined Keywords in Source Filters.

    1. In the Field column, select a dimension for which you want to restrict values. Each dimension can only be used once as a filter.

      For each filter, the Operator is forced to Include: Equal to and can't be changed. Therefore, you can only select one value for each dimension except for COMPANYCODE, if you use a BAPI that allows you to select multiple company codes. For more information, see Create Destination for SAP ECC as Source.

    2. In the Value column, specify a value.
  8. In the Mapping File section, select the mapping file you have created.

    If the mapping file contains errors, they will be displayed in the Errors section.

    You can download and correct your mapping file in Excel by choosing the Download Mapping File link. After you have corrected any errors, upload the mapping file once again.
  9. In the Import Options section, select the different import options you want to apply. For more information, see Import Options.
  10. In the Traceability section, choose if you want to force generate a traceability log file for each job run, or upon request when the job is run. For more information, see Force Generate Traceability Logs.
  11. Choose Including Mapping File Sheets if you want the different mapping file sheets of your data mapping file to be displayed in the traceability log. For more information, see Traceability Logs.
  12. In the Access Restrictions section, you can optionally choose to restrict access to your mapping definition by selecting specific dimension values. Once the restriction set, the application compares these dimension values to the global parameters of the user. If the global parameters of the user are included in the access restrictions of the definition, the definition is visible to the user. For more information, see Define Access Restrictions.
  13. Choose Create.
Related Information