Demand Sensing options to Customer Order transactions

The feature is included in the process using a new Tag and Application Variable:

• DPLS-Demand_Orders (Tag to include Customer Orders as Transactional Data)
• dpls_demand_sensing_customer_orders (Import Customer orders as Transactional Data). Default: 0

These interface services are added to support the loading of transactional customer orders:

• DPLS - SCV - Import Demand Customer Orders (SALES HIST TRX as TD) - included in the standard macros when the application variables (dpls_demand_sensing_customer_orders) = 1 and (dpls_sales_hist_to_use) = SC_SALES_HIST_TRX.
• DPLS - SCV - Import Demand Customer Orders (SALES OPEN TRX as TD) NOT included in macros, but a customer can use it in addition to include open orders, if required.

A new transactional data record is added to customer orders:

• DPLS_CUSTOMER_ORDERS (Customer Orders), measure: DPLS_HSALESTODATE.

A new Orders worksheet is added to the Demand Sensing workbench to display the transactional customer order information where the tag and application variable(s) are appropriately set.

The tag is not included in a standard Demand cycle definition and the application variable defaults to 0, maintaining existing behavior of using scenario values.

To enable this feature:

• The DPLS-Demand_Orders tag (Tag to include Customer Orders as Transactional Data) must be added to the corresponding Demand cycle definition (this must be a copy of a standard cycle definition to maintain the tag in future updates).
• The dpls_demand_sensing_customer_orders) = 1 and dpls_sales_hist_to_use = SC_SALES_HIST_TRX application variables must be updated as a global override value or in the corresponding demand cycle.