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.