Material 360 > Material 360 and SAP integration > Processing data in batches
  

Processing data in batches

Use Material 360 to process SAP ECC and SAP S/4HANA records in batches.
Run a batch job to ingress SAP ECC and SAP S/4HANA records to MDM SaaS. The job uses a taskflow to run mapping tasks. Each mapping task includes a mapping that maps the SAP fields with the Material business entity fields.

Ingress data

When you ingress SAP material records to MDM SaaS from SAP ECC or SAP S/4HANA, the ingress job creates master records for the SAP records in MDM SaaS.
To read data from SAP, you require the SAP Table Connector, and to write data to MDM SaaS, you require the Business 360 FEP Connector. After you ingress SAP records, you can process the records in MDM SaaS.
The following image shows how to ingress SAP records in batches:
The image shows the process to ingress SAP ECC and SAP S/4HANA records to MDM SaaS. The ingress job uses SAP Table Connector to read data from SAP and Business 360 Connector to awrite data to MDM SaaS.

Egress data

After you process records in MDM SaaS, you can export the records to SAP S/4HANA in batches. Use Cloud Data Integration assets and multiple Business Application Programming Interfaces (BAPIs) to export the processed material records.
You can export the following records to SAP S/4HANA in batches:
The following image shows how to egress material records to SAP S/4HANA in batches:
The image shows the process to egress material records to SAP S/4HANA in batches.
Note: After you delete a record that you already exported to SAP S/4HANA from MDM SaaS, you can't synchronize the deleted record in SAP S/4HANA.