Show TOC

Function documentationOutbound of sales data to SAP DMF-based applications Locate this document in the navigation structure

 

You can use this function to send the sales and related data from POS sales transactions to SAP DMF-based receiver systems. This data is needed by SAP Demand Management Foundation (SAP DMF) to create suitable demand models. In addition, other applications besides SAP DMF that require up-to-date sales information can also make use of this data.

The following information is transferred:

  • Data for the combination of store, day, product and offer:

    • Sales in base unit of measure

    • Net sales in local currency of the store

    • Gross sales in local currency of the store

    • Transaction count

    • Squared sales in base unit of measure (squared sales is calculated per transaction and then added to existing data)

    • Cubed sales in base unit of measure (cubed sales is calculated per transaction and then added to existing data)

  • Data for the combination of store and day:

    • Store traffic

You can perform the transfer in either of two ways:

  • One-step process - In the standard customizing (profile 0001) this is provided as the task with code 0050.

  • Two-step process:

    • The aggregation of the transactions in a POS aggregate is done in the first step.

    • The outbound of the aggregated data is done in the second step.

    In the standard customizing this function is provided as follows:

    • Aggregation of transactions is done by the task with code 2050.

    • The POS aggregate has code 0050.

    • The corresponding outbound task is done by the task with code 3050.

Choose either the one-step process or the two-step process based on your processing requirements:

  • The advantage of the one-step process is that it has the minimum overall resource consumption (runtime, disk space). This advantage occurs when the block size is not restricted and all data to be sent is available. (The transfer of POS data takes place after shop closing when the complete POS upload has taken place). If either the block size is restricted or the transfer starts when not all data is available, sales records might be sent several times. This increases the network load as well as the workload on the receiver system.

  • The advantage of the two-step process approach is that each sales record is sent only once if the outbound task is executed after all transactions have been aggregated in the POS aggregate. This reduces the network load and the workload on the receiver system. In addition, if you execute the aggregation task (in a trickle feed scenario) multiple times during the day, the multiple execution as well as the restriction of the package size will have no consequences for the transfer of data itself. If you restrict the package size you have more control over the main memory consumption. Additionally, if you execute the aggregation task multiple times during the day, you reduce the workload in the critical night window. The drawback of this approach is the higher overall workload because the POS aggregates have to be updated on the database.

Prerequisites

You have made the following settings in Customizing for POS Inbound Processing (PIPE):

  • You have created a suitable customizing profile by choosing   General Settings   Define Profiles  .

  • You have assigned the transfer relevant stores to that profile by choosing   General Settings   Store Settings  .

  • You have maintained a task group for the aggregation and transfer of sales transactions by choosing   Tasks   Define Task Group  .

Transaction types:

  • You have maintained a transaction type group for the transfer relevant (sales) transactions by choosing   POS Transactions   Define Type Group for POS Transactions  .

  • You have maintained the transfer relevant transaction types and assigned them to the corresponding transaction type group and task group by choosing   POS Transactions   Define POS Transaction Type  .

Sales item types:

  • You have maintained the relevant sales item type groups by choosing   POS Transactions   Define Type Group for Sales Items  .

  • You have maintained the transfer relevant sales item types and assigned them to the corresponding item type group and task group by choosing   POS Transactions   Define Sales Item Types  .

Tax types:

  • You have maintained the relevant tax type groups by choosing   POS Transactions   Define Type Group for Taxes  .

  • You have maintained the relevant tax types and assigned them to the corresponding tax type groups and task group by choosing   POS Transactions   Define Tax Types  .

Discount types:

  • You have maintained the relevant discount type groups by choosing   POS Transactions   Define Type Group for Discounts  .

  • You have maintained the relevant discount types and assigned them to the corresponding discount type groups and task group by choosing   POS Transactions   Discount Type  .

When using the one-step process:

  • You have created the outbound task by choosing   Tasks   One-Step Processing   Define Tasks   (using task 0050 for profile 0001 as a copy template). You have set the task type to 1 (Collective processing). You have set the parameter DMF_APPS to a suitable value depending on the set of applications running on the receiver system.

  • You have maintained the RFC destination of the receiver system by choosing   Tasks   Define Additional Details for Tasks  .

  • You have assigned the task to the corresponding task group for the transfer of sales transactions by choosing   Tasks   Assign Tasks to Task Group  .

When using the two-step process:

  • You have created the task for the aggregation of data in Customizing by choosing   Tasks   Two-Step Processing   Define Aggregation Task   (using task 2050 for profile 0001 as a copy template). You have set the task type to 1 (Collective processing). You have set the parameter DMF_APPS to a suitable value depending on the set of applications running on the receiver system.

  • You have created the task for the outbound of data by choosing   Tasks   Two-Step Processing   Define Outbound Tasks   (using task 3050 for profile 0001 as a copy template).

  • You have maintained the RFC destination of the receiver system by choosing   Tasks   Additional Details for Outbound Tasks  .

  • You have assigned the aggregation task to the corresponding task group for the transfer of sales transactions by choosing   Tasks   Assign Tasks to Task Group  .

If you have set the parameter DMF_APPS: You have ensured that for the value of this parameter an active implementation for the BAdI /POSDW/DMF_RELEVANCE exists (see Customizing activity   Integration with other SAP components   DMF based applications   Control the transfer relevance of products  ).

Activities

The aggregation and outbound of sales data is executed using the existing PIPE framework. You can find further information under Task Processing.