You can process SAP ECC and SAP S/4HANA records with Customer 360 SaaS in batches.
Run ingress batch jobs to import records from SAP ECC and SAP S/4HANA into Customer 360 SaaS in batches. Run egress batch jobs to export processed records from Customer 360 SaaS to SAP S/4HANA in batches. The job uses a taskflow to run mapping tasks. Each mapping task includes a mapping that maps the fields in SAP with the business entity fields in Customer 360 SaaS.
Ingress data
You can import SAP ECC and SAP S/4HANA records to Customer 360 SaaS and process these records in batches using predefined ingress jobs.
When you import SAP ECC customer and FI customer records and SAP S/4HANA business partner records to Customer 360 SaaS, the ingress job imports them as customer records. A customer record contains a source primary key, such as a customer number for an SAP ECC customer and FI customer record or a business partner number for an SAP S/4HANA business partner record. After the initial import, you can run incremental ingress jobs to incrementally import the records that are added or updated in SAP ECC and SAP S/4HANA to Customer 360 SaaS.
To import records from SAP, the ingress job uses SAP Table Connector and Business 360 FEP Connector. To read data from SAP, you require SAP Table Connector. To write data into Customer 360 SaaS, you require Business 360 FEP Connector. After you import SAP records, you can process the records in Customer 360 SaaS.
For more details about predefined ingress jobs, see Batch jobs.
The following image shows how to ingress SAP records in batches:
Egress data
You can export the customer records from Customer 360 SaaS to SAP S/4HANA in batches using the predefined egress jobs.
After you create, update, or process customer records in Customer 360 SaaS, you can export them to custom SAP table in SAP S/4HANA in batches. Use predefined egress jobs, Cloud Data Integration assets, and multiple Business Application Programming Interfaces (BAPIs) to export the processed customer records from Customer 360 SaaS to SAP S/4HANA in batches. After you export the records to SAP S/4HANA, the integration status of records, which is either successful or failed, is added to Customer 360 SaaS.
You can export the following records from Customer 360 SaaS to SAP S/4HANA in batches:
•Records imported from SAP ECC. After you import customer and FI customer records from SAP ECC, you can process these records in Customer 360 SaaS and export them to SAP S/4HANA as business partner records.
•Records imported from SAP S/4HANA. After you import business partner records from SAP S/4HANA, you can process these records in Customer 360 SaaS and export them to SAP S/4HANA as business partner records.
•Records created or updated in Customer 360 SaaS. After you create a customer record in Customer 360 SaaS, you can process it and then export it to SAP S/4HANA as a business partner record. SAP S/4HANA then assigns a new business partner number to the processed record and stores the number in an SAP custom table. This business partner number is retrieved and stored in the Identifier field of the Organization or Person business entity in Customer 360 SaaS. If you update a record in Customer 360 SaaS that was previously exported to SAP S/4HANA, you can export the incremental changes to SAP S/4HANA using the existing business partner number without creating duplicates.
The following images show how to export customer records to custom SAP table in SAP S/4HANA in batches:
Import reference data
To import reference data sets from SAP ECC or SAP S/4HANA into Reference 360, you can create import jobs in Reference 360.
You can import the following reference data from SAP ECC or SAP S/4HANA:
