Multiple SAP Source Systems
Frequently more than one SAP system is required to get a complete end-to-end view of the supply chain. This can be split by regions, business units, company codes, etc. The Purchase Requisition data is flexible enough to support this with a few minor steps required.
Step 1: Create a duplicate of the local data jobs by clicking on the three dots of the local job and then selecting duplicate. The duplication is important, because it allows for the same template transformations to be shared across the different data jobs. Do not simply copy and paste the data transformations.
 |
Step 2: Change the Data Connection of the newly duplicated data job to your other source system.
 |
Step 3: Select your data connection (or connections) from the dropdown.
 |
Step 4 (Optional): Change the name of the data job by removing the (1) that was added during the duplicating process. You can skip this step if you do not mind the (1).
Step 5: Run both (or as many as required) data jobs as usual, and remember to incorporate the new job into the Schedule.
Step 6: In the global PR jobs (Job 1.0), update the different transformations to reference both local jobs and union them together. It is also recommended that you add the source system ID as another field in the table and remove any n:m data model join issues that might occur (if the same material number is used in both source systems, this issue will occur). See below for an example of the _CEL_PR_ACTIVITIES table. Do not forget to update the schema of the second source system.
 |