Process Overview
Table 3-7 Extracts for Planning
POM Job Name | Usage Details |
---|---|
W_PDS_PRODUCT_D_JOB |
Exports a full snapshot of Product master data and associated hierarchy levels, including flex fields for alternates. |
W_PDS_ORGANIZATION_D_JOB |
Exports a full snapshot of Location master data (for stores and virtual warehouses only) and associated hierarchy levels, including flex fields for alternates. |
W_PDS_CALENDAR_D_JOB |
Exports a full snapshot of Calendar data at the day level and associated hierarchy levels, for both Fiscal and Gregorian calendars. Note: While the AIF DATA job exports the entire calendar, PDS will only import 5 years around theRPAS_TODAY date (current year +/- 2 years).
|
W_PDS_EXCH_RATE_G_JOB |
Exports a full snapshot of exchange rates. |
W_PDS_PRODUCT_ATTR_D_JOB |
Exports a full snapshot of item-attribute relationships. This is inclusive of both diffs and UDAs. |
W_PDS_DIFF_D_JOB |
Exports a full snapshot of Differentiators such as Color and Size. |
W_PDS_DIFF_GRP_D_JOB |
Exports a full snapshot of differentiator groups (most commonly size groups used by SPO and AP). |
W_PDS_UDA_D_JOB |
Exports a full snapshot of User-Defined Attributes. |
W_PDS_BRAND_D_JOB |
Exports a full snapshot of Brand data (regardless of whether they are currently linked to any items). |
W_PDS_SUPPLIER_D_JOB |
Exports a full snapshot of Supplier data (regardless of whether they are currently linked to any items). |
W_PDS_CUSTSEG_D_JOB |
Exports a full snapshot of Customer Segments data (regardless of whether they are currently linked to any customers). |
W_PDS_REPL_ATTR_IT_LC_D_JOB |
Exports a full snapshot of Replenishment Item/Location Attribute
data (equivalent to |
W_PDS_DEALINC_IT_LC_WK_A_JOB |
Incremental extract of deal income data (transaction codes 6 and 7 from RMFCS) posted in the current business week. |
W_PDS_PO_ONORD_IT_LC_WK_A_JOB |
Incremental extract of future on-order amounts for the current business week, based on the expected OTB date. |
W_PDS_INV_IT_LC_WK_A_JOB |
Incremental extract of inventory positions for the current business week. Inventory is always posted to the current week, there are no back-posted records. |
W_PDS_SLS_IT_LC_WK_A_JOB |
Incremental extract of sales transactions posted in the current business week (includes back-posted transactions to prior transaction dates). |
W_PDS_INVTSF_IT_LC_WK_A_JOB |
Incremental extract of inventory transfers posted in the current business week (transaction codes 30, 31, 32, 33, 37, 38 from RMFCS). |
W_PDS_INVRC_IT_LC_WK_A_JOB |
Incremental extract of inventory receipts posted in the current business week. Only includes purchase order receipts (transaction code 20 from RMFCS). |
W_PDS_INVRTV_IT_LC_WK_A_JOB |
Incremental extract of returns to vendor posted in the current business week (transaction code 24 from RMFCS). |
W_PDS_INVADJ_IT_LC_WK_A_JOB |
Incremental extract of inventory adjustments posted in the current business week (transaction codes 22 and 23 from RMFCS). |
W_PDS_SLSWF_IT_LC_WK_A_JOB |
Incremental extract of wholesale and franchise transactions posted in the current business week (transaction codes 82, 83, 84, 85, 86, 88 from RMFCS). |
W_PDS_MKDN_IT_LC_WK_A_JOB |
Incremental extract of markdowns posted in the current business week (transaction codes 11, 12, 13, 14, 15, 16, 17, 18 from RMFCS). |
W_PDS_INV_IT_LC_WK_A_INITIAL_JOB |
Initial history extract for inventory position data based on the timeframe established in C_SOURCE_CDC. |
W_PDS_FLEXFACT1_F_JOB |
Exports flexible fact data from the data warehouse that can be at any configurable level of hierarchies. Can be used to extend PDS with additional measures. Flex Fact 1 is also used by LPO to display custom measures. |
W_PDS_FLEXFACT2_F_JOB |
Exports flexible fact data from the data warehouse that can be at any configurable level of hierarchies. Can be used to extend PDS with additional measures. |
W_PDS_FLEXFACT3_F_JOB |
Exports flexible fact data from the data warehouse that can be at any configurable level of hierarchies. Can be used to extend PDS with additional measures. |
W_PDS_FLEXFACT4_F_JOB |
Exports flexible fact data from the data warehouse that can be at any configurable level of hierarchies. Can be used to extend PDS with additional measures. |
W_PDS_ORG_ATTR_STR_D_JOB |
Exports a full snapshot of custom flex location attributes and other location attribute types to PDS, for string-type attributes only. |
W_PDS_ORG_ATTR_NBR_D_JOB |
Exports a full snapshot of custom flex location attributes to PDS, for number-type attributes only. |
W_PDS_ORG_ATTR_DT_D_JOB |
Exports a full snapshot of custom flex location attributes to PDS, for date-type attributes only. |
W_PDS_PRODUCT_ATTR_STR_D_JOB |
Exports a full snapshot of custom flex product attributes to PDS, for string-type attributes only. |
W_PDS_PRODUCT_ATTR_NBR_D_JOB |
Exports a full snapshot of custom flex product attributes to PDS, for number-type attributes only. |
W_PDS_PRODUCT_ATTR_DT_D_JOB |
Exports a full snapshot of custom flex product attributes to PDS, for date-type attributes only. |
W_PDS_PROD_ORG_ATTR_STR_D_JOB |
Exports a full snapshot of custom flex product/location attributes to PDS, for string-type attributes only. |
W_PDS_PROD_ORG_ATTR_NBR_D_JOB |
Exports a full snapshot of custom flex product/location attributes to PDS, for number-type attributes only. |
W_PDS_PROD_ORG_ATTR_DT_D_JOB |
Exports a full snapshot of custom flex product/location attributes to PDS, for date-type attributes only. |
The PDS jobs are linked with several ad hoc processes in POM, providing you with the ability to extract specific datasets on-demand as you progress with history and initial data loads. The table below summarizes the ad hoc processes, which can be called using the standard methods such as cURL or Postman.
Table 3-8 AIF DATA Ad Hoc Processes for Planning
POM Process Name | Usage Details |
---|---|
LOAD_PDS_DIMENSION_PROCESS_ADHOC |
Groups all of the dimension (D/G table) extracts for PDS into one process for ad hoc execution. Disable individual jobs in POM to run only some of them. |
LOAD_PDS_FACT_PROCESS_ADHOC |
Groups all of the fact (F/A table) extracts for PDS into one process for ad hoc execution. Disable individual jobs in POM to run only some of them. |
LOAD_PDS_FACT_INITIAL_PROCESS_ADHOC |
History extract process for inventory positions, run only to pull a full snapshot of
inventory from the data warehouse for one or multiple weeks of data. You must set the start and end dates for extraction
in the |
C_LOAD_DATES_CLEANUP_ADHOC |
Purge the successful job records from |
Most of the PDS fact jobs leverage the configuration table C_SOURCE_CDC
to track the data that has been
extracted in each run. On the first run of an incremental job in LOAD_PDS_FACT_PROCESS_ADHOC
, the job extracts
all available data in a single run. From that point forwards, the extract incrementally loads only the data that has been
added or modified since the last extract, based on W_UPDATE_DT
columns in the source tables. There are two
exceptions to this incremental process: Inventory and On Order interfaces. The normal incremental jobs for these two interfaces
will always extract the latest day’s data only, because they are positional facts that send the full snapshot of current positions
to PDS each time they run.
To move inventory history prior to the current day, you must use the initial inventory extract to PDS (LOAD_PDS_FACT_INITIAL_PROCESS_ADHOC
). It requires manually entering the start/end dates to extract, so you must update C_SOURCE_CDC
from the
Control & Tactical Center for the inventory table record. LAST_MIN_DATE
is the start of the history you
wish to send, and LAST_MAX_DATE
is the final date of history. For example, if you loaded one year of inventory,
you might set LAST_MIN_DATE
to 04-JUN-22
and LAST_MAX_DATE
to 10-JUN-23
. Make sure that the timestamps on the values entered are 00:00:00
when saved to the database, otherwise
the comparison between these values and your input data may not align.
For all other jobs, the extract dates are written automatically to C_SOURCE_CDC
alongside the extract
table name after each execution and can be overwritten as needed when doing multiple loads or re-running for the same time
period. If you run the same process more than once, use C_LOAD_DATES_CLEANUP_ADHOC
to reset the run statuses
before the next run, then edit C_SOURCE_CDC
to change the minimum and maximum dates that you are pulling
data for. Review the table below for a summary of the configuration tables involved in PDS extracts.
Table 3-9 Planning Integration Configuration Tables
Table | Usage |
---|---|
C_SOURCE_CDC |
Configuration and tracking table that shows the interfaces supported for data warehouse to Planning integration and the currently processed date ranges. |
C_LOAD_DATES |
Tracks the execution of jobs and the most recent run status of each job. Prevents running the same job repeatedly if it was already successful, unless you first erase the records from this table. |
RAP_INTF_CONFIG |
Configuration and tracking table for integration ETL programs between all RAP modules. Contains their most recent status, run ID, and data retention policy. |
RAP_INTF_RUN_STATUS |
RAP integration run history and statuses. |
RAP_LOG_MSG |
RAP integration logging table, specific contents will vary depending on the program and logging level. |
After the planning data has been extracted from the data warehouse to PDS staging tables (W_PDS_*
), the
Planning applications use the same programs to extract both full and incremental data for each interface. You can run the
dimension and fact loads for planning from the Online Administration (OAT) tasks, or use the RPASCE schedule in POM. Refer
to the relevant implementation guides for MFP, AP, or IPO for details on these processes.