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 |
|
Material |
|
Cost Center |
|
GL Account |
|
Profit Center |
|
Internal Order |
|
Project |
|
Perform the following steps to resolve import errors:
- Open the required staging table.
- Review and fix the error messages captured. For example, if the
COMPANY_CODEin 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. - Once errors are resolved, rerun the data load job:
Entity Job Business Partner
MDR_JOB_Business_PartnerMaterial
MDR_JOB_MaterialCost Center
MDR_JOB_Cost_CenterGL Account
MDR_JOB_GL_AccountProfit Center
MDR_JOB_Profit_CenterInternal Order
MDR_Internal_Order_GOLD_LOADProject
MDR_JOB_Project _<DataSourceName>_GOLD_LOAD - Load data from the insert job using the BAPI method. For example, run the
RFC_MD_BP_MAINTAINmethod 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_CTRLRtable parameter to eitherMAGSH/RFC_MD_BP_MAINTAINor/MAGSH/RFC_MDR_BP_MAINTAINmethod. - For cost center and GL account entities, load data using the IDoc partner number (
$G_PARTNER_NUMBERvariable).