Customer 360 Extension for SAP > Integrating Customer 360 Extension for SAP > Processing data in batches
  

Processing data in batches

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

Ingress and egress initial data

When you ingress initial SAP business partner records to Customer 360 from SAP ECC or SAP S/4HANA, the ingress job creates master records for all the SAP records in Customer 360. The ingress job assigns a Customer360 ID to each master record in Customer 360.
To ingress records from SAP, the ingress job uses a SAP table connector and Business 360 connector. After you process the records in Customer 360, you can export the complete record or export only specific fields of the record. When you export only the specific fields, you perform limited export of processed data. Use Cloud Data Integration assets and multiple Business Application Programming Interface (BAPIs) to export the complete Customer 360 records.
After you ingress records from SAP ECC and SAP S/4HANA, you can export the processed records to SAP S/4HANA in batches. When you export complete data from Customer 360, the data moves from custom SAP table to SAP table.
The following image displays the process to ingress SAP records in batches:
The ingress job uses SAP table connector and Business 360 connector to import data from SAP ECC or SAP S/4HANA to Customer 360.
The following image displays the process to egress initial data from Customer 360 to SAP in batches:
Use the BAPIs to export complete data to SAP S/4HANA.

Ingress and egress incremental data

After the first run, you can incrementally ingress the records that are added or updated in SAP ECC and SAP S/4HANA to Customer 360. Use the SAP table connector and Business 360 connector to ingress incremental data. When you ingress incremental records, the ingress job uses the Customer360 Id to determine whether to update or insert a record to Customer 360.
When the Customer360 Id is present in SAP ECC or SAP S/4HANA for a record, it indicates that the record exists in Customer 360, and the job updates the record in Customer 360. When the Customer360 Id is not present in SAP ECC or SAP S/4HANA, it indicates that the record is new, and the job inserts the record to Customer 360. The Customer360 Id and Customer360 Sync Date fields for the master records are updated accordingly in SAP ECC and SAP S/4HANA.
For more information about importing the incremental data using SAP Table Connector, see Configuring Data Integration assets for incremental data.
After you onboard the incremental records from SAP ECC or SAP S/4HANA, you can process the records and export the incremental data to custom SAP tables. Use the Business 360 connector and Business Application Programming Interface (BAPI) to export the incremental Customer 360 records to custom SAP tables. Use the SAP table connector and Business 360 connector to perform limited export of incremental Customer 360 data to custom SAP tables. Based on your business requirement you can write data from the custom SAP tables to the SAP tables. Every reference data set is mapped to a corresponding custom SAP table for base objects other than hierarchy objects. The values of each duplicate record in SAP ECC and SAP S/4HANA are updated with the master record values.
The following image displays the process to ingress SAP records in batches:
The ingress job uses SAP table connector and Business 360 connector to import data from SAP ECC or SAP S/4HANA to Customer 360.
The following image displays the process to egress SAP records in batches:
Use Business 360 connector and SAP table connector for limited export of incremental data from Customer 360 to SAP S/4HANA. Use BAPI and Business 360 connector for complete export of incremental data from Customer 360 to SAP S/4HANA.