Other Information on Data Pools
The Purchase Requisition data model makes use of all the views available in the global schema of this data pool. As defined in the Global Jobs Section, this is where information from the O2C, P2P, MM and PP data pools can be incorporated into the model. Further, it is also where the Purchase Requisition specific tables are consolidated and then filtered down based on the imported process data.
Global Job Changes on Install: Data Connection Parameters
For each of the transformations inside of global job 0.0, you will need to update the schema to which the respective tables make reference. See below for the jobs requiring updates.
 |
For example, if you wanted to bring the EBAN table from the Purchase to Pay data pool, you can make use of the template available on the global job 0.0 “[data connection 1] Import and Push Tables”. In the sample below, <%=DATASOURCE:SAP_ECC%> represents the connection on the local schema, while <%=DATASOURCE:SAP_ECC_-_PURCHASE_TO_PAY_SAP_ECC%> represents the connection imported from the P2P data model.
 |
You can add that connection to the sql by simply clicking on the bottom left, as shown in the below image.
 |
Using Imported Tables in the Purchase Requisition ‘Local’ Jobs
Although this feature is not currently used in the standard configuration of the PR connector, it is possible to import tables from other data pools and ‘push’ them to the local pool of the PR connector.
Example Use Case
If you are already extracting and using some of the PR specific tables in the other data pools that you work with, such as EBAN, you are not required to re-extract them in the local job of the PR connector. Instead you should use the following steps:
Disable the table from the local extraction.
If it’s not already available, navigate to the PR global job and create a new global job named “0.1 Import and Push tables” and then create a new transformation.
Inside of the transformation, the objective is to create a table in the local job based on the table from the source data pool. It is important that you update the data connection parameter in the FROM statement to the parameter of your system.
Incorporate the new global job into your data job scheduling, so that these import and push transformations are executed prior to the Local PR data job. This ensures that the EBAN table (from this example) is updated in the local job prior to the local transformations that depend on it are run.
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.
 |