Skip to main content

Load Data Directly into SAP S/4HANA

This topic covers the post-load steps for all entities.

When data fails to import into SAP S/4HANA, it is logged in the following table depending on the entity:

Entity Table

Business Partner

MDR_BP_GOLD_LOG

Material

MDR_MATERIAL_MDG_LOG

Cost Center

MDR_COSTCENTER_MDG_LOG

GL Account

MDR_GLACCOUNT_GOLD_LOG

Profit Center

MDR_PROFITCENTER_MDG_LOG

Internal Order

MDR_INTERNALORDER_GOLD_LOG

Project

MDR_PROJECT_GOLD_LOG

Perform the following steps to resolve import errors:

  1. Open the required staging table.
  2. Review and fix the error messages captured. For example, if the COMPANY_CODE in the extracted record is invalid, you will see "Company Code: Invalid value (foreign key check failed)" and the record will not import into SAP S/4HANA.
  3. Once errors are resolved, rerun the data load job:

    Entity Job

    Business Partner

    MDR_JOB_Business_Partner

    Material

    MDR_JOB_Material

    Cost Center

    MDR_JOB_Cost_Center

    GL Account

    MDR_JOB_GL_Account

    Profit Center

    MDR_JOB_Profit_Center

    Internal Order

    MDR_Internal_Order_GOLD_LOAD

    Project

    MDR_JOB_Project _<DataSourceName>_GOLD_LOAD

  4. Load data from the insert job using the BAPI method. For example, run the RFC_MD_BP_MAINTAIN method for the business partner entity. This creates a unique data record in SAP S/4HANA.

    Note: To create business partner data with a data controller, add the IT_BP_DATA_CTRLR table parameter to either MAGSH/RFC_MD_BP_MAINTAIN or /MAGSH/RFC_MDR_BP_MAINTAIN method.

  5. For cost center and GL account entities, load data using the IDoc partner number ($G_PARTNER_NUMBER variable).

Was this article helpful?

We're sorry to hear that.