In this article, i will show you step by step how to make configuration.

Please take note that before ready this article, you need have some basics knowledge about retails and SAP retails
functionalities.

Per business requirements In SAP CAR now, there are many features support retails industry. One of the main function of SAP
CAR (Customer Activity Repository ) is POS DTA.

POS DTA (Point of Sales Data Transfer and Audit) is central engine of SAP CAR. POS DTA support consume sales / inventory /
financial transaction from legacy system. Multi sales channel will be send to SAP CAR and data audit will be apply and transfer
to destination ERP system consistently and correctly. More than that, POS DTA help reduce amount of unvaluable transaction
data to SAP ERP through aggregation behavior however raw data also available in SAP CAR for detail reporting purposes.

You need to understand what are :

 Integration
 Transformation data between two or many systems.
 Inbound
 Data from legacy system to main system
 Outbound
 Data from main system to legacy system
 Transaction
 Business documents (Sales Order / Purchase Order / Delivery Order …etc..)
 Item
 Article / Material in Business document
 Discount type
 Type of discount in receipt / Sales Order / Purchase Order (Manual discount, Promotion discount …etc.)
 Tender type
 Paying method of customer (Card, Cash, Voucher … etc)
 Tax type
 Tax on each item
 Store / Site / Plan
 Store number / Code
 And a little bit about SAP IDOC Structure or EDI document.
 Sales transaction IDOC inbound to SAP CAR.

Below are 23 steps for basis configuration

1.Inbound profile

2.Check Profile

3.Define Profile

4.General Setting

5.Define Standard Values

6.Store Class

7.Store Setting

8.Store Group

9.Define Task Group

10.Define Tasks

11.Assign Tasks to Group

12.Define type group for sales items

13.Sales Item Types

14.Discount Groups

15.Discount Types

16.Tax Groups

17.Tax Types

18.Tender Groups

19.Tender Types

20.Financial Transaction Groups

21.Financial Transaction Types

22.Transaction Groups

23.Transaction Types

1. Inbound profiles

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define
Inbound Profiles

Use

Inbound profile help us control inbound transaction data in queue before data. For example, in retails landscape we have two
POS (Point of Sales) system and we want process sales transaction data of each system with different period or business
models.
2.Check Profile

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define Check
Profiles

Use

In this procedure, we define check profiles that are used to check master data. SAP CAR will check master data when you
process relevant tasks.

If the filter value is defined for master data check, the relevant Business Add-In(BAdi) will be call and executed.

You can customize master data checking and determinate the check to be carried out. Since data is enriched as part of the
master data checks, processing errors may occur if you deactivate one of the checks.
Master data will be loaded from SAP ECC through SAP BW or SAP HANA through SAP SLT (System Landscape Transformation)

Store: Store information

Table : T001W from ERP
No ABAP View : HANA view directly accessed
HANA View : sap.is.retail.ecc.Plant
Or sap.is.retail.s4h.Plant
Material: Article information
Table : MARA from ERP
ABAP View : /POSDW/V_MAT
HANA View : sap.is.retail.ecc.Material
Or sap.is.retail.s4h.Material
EAN Mapping: Mapping EAN/barcode to Article and sales unit of measure
Table : MEAN from ERP
ABAP View : /POSDW/V_MEAN
HANA View : sap.is.retail.ecc.MaterialInternationalArtlNmbr
Or sap.is.retail.s4h.MaterialInternationalArtlNmbr
UOM Mapping: Mapping from sales unit of measure to base unit of measure
Table : MARM from ERP
ABAP View : /POSDW/V_MARM
HANA View : sap.is.retail.ecc.MaterialUnitofMeasure Or sap.is.retail.s4h.MaterialUnitofMeasure

3.Define Profile

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define Profiles

Use

In this procedure, you can create customizing profile for (PIPE) POS Inbound Processing Engine. For each store / site / plan
you can decide which profile to use. For each PIPE you should create different setting for each profile.
4.General Setting

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define General
Setting

Use

In this procedure, you make general settings that a valid for the whole PIPE, independently of the profile.
5.Define Standard Values

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define General
Setting

Use

In this procedure, you can define standard values for each profile. Some variants need done after relevant steps are done.

6.Store Class

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define
Standard Profile

Use

You want to aggregate the sales of all stores in two countries into cross-store aggregates. You use two store classes for
country 1 and country 2, and in the next step you assign these store classes to the stores in the respective countries. The store
classes are assigned to their respective store groups. The store groups in turn are assigned to various aggregation tasks.

7.Store Setting

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Store Setting

Use

In this procedure, you can define store and mapping with specific profile, which perform business process and master data
checking.
8.Store Group

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define Store
Group

Use

In this Customizing activity you create store groups and assign store classes to them. Store groups pool together stores, for
example for cross-store aggregation.

Each store group has a reference store. The Customizing profile of each reference store is used to determine the Customizing
profile of the store group.

9.Define Task Groups

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound Processing -> General Settings -> Define Task
Groups

Use

In this procedure, you can define group of tasks as business requirement such as:

– Group of sales movements tasks, Group of Totals Records transaction tasks..etc.

SAP CAR – POS DTA Configuration Step by Step (Part 2)

10.Define Tasks
In this guide, i used “One-Step Processing”
Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> Tasks -> One-Step Processing -> Define
Tasks

Use
In this procedure, you can define tasks which can perform process your sales / transaction data from
legacy system.
For example, data from POS (Point of Sales) send to SAP CAR at End of Day. All raw data will be stored
in inbound queues. Tasks will collect sales data perform master data checking, validation and
aggregation before send aggregated data to SAP ERP.
Such as SAP CAR standard tasks, you can copy and change parameters per requirements.

Each receipt was send to SAP CAR should perform tasks as below:
1. Supply BW with Distribution : This task will send raw data with details information to SAP BW
(Reporting and analysis).
2. Check for Duplicate Transactions : This task will perform check duplication transaction from POS.
3. Check for Balanced Transactions : This task will perform check balance amount of transaction,
checking sales items total amount and payment amount.
4.Generate IDoc WPUTAB : This task will perform aggregation and generate summary payment of
each payment method document and send to SAP ERP.
5.Generate IDoc WPUUMS : This task will perform aggregation and generate sales data per store /
business date / item / Unit of Measure and send to SAP ERP.
6.Generate IDoc WPUFIB : This task will generate financial transaction and send to SAP ERP without
any aggregation.

Notes:
By SAP CAR data aggregation standard methodology, sales and payment will be aggregated base on key
fields on receipt (Example : Store / Business Date / Item / Unit of Measure / …etc). and aggregated
data information send to SAP ERP very limited. Per business requirement we need to enhance standard
aggregation behavior to capture more detail additional data.
Parameters:

Group : Processing Type

Type of Task help you define task perform behavior, you can perform task immediately or collect
before perform.

Base on my experiences, tasks handling master data checking should perform immediately when
transaction data come to SAP CAR Workbench.
Task Priority : There may many tasks will be assigned to inbound transaction, we need define
sequence of tasks will perform processing. Example, when inbound sales transaction come to SAP CAR
Workbench we need perform tasks follow sequence : Check Duplicate Transaction -> Check Balance
Transaction -> Supply Data to SAP BW ->… and so on…

Mirror Tasks should be implemented in SAP Retail Model

1.Aggregate and generate sales transaction to SAP ERP

As i mentioned above, main functionality of SAP POS DTA is aggregation sales transaction then send to
SAP ERP. In SAP CAR, IDOC with message type : WPUUMS will be use.
As you see, type of Task will be set to “Collective Processing“, mean sales raw data will be collected
before perform aggregation.
In the “Control” group, “Parameter Group” define kind of document will be passed to SAP ERP. In here,
sales transaction data will pass to SAP ERP by IDOC with message type is WPUUMS.
Benefits of aggregation are:
– Reduce raw data to SAP ERP.
– Reduce numbers of business transaction send to SAP ERP
– Apply for all retails models (B2B, B2C, Online etc..)

2.Aggregate and generate payment transaction to SAP ERP

One if major task in retail SAP CAR is send aggregated payment by method to SAP ERP. Such as
financial perspective, financial operation care about totals amount of each payment method. SAP CAR
give to us standard IDOC message type call : WPUTAB.
Similar with sales, task for payment methods also collective before process and pass data to ERP.

As you see image below, payment methods will be grouped.

In some scenario, finance operation want more additional information for reconcile, the enhancement
need to applied in task.

11.Assign Tasks to Group

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> Tasks -> One-Step Processing -> Assign
Tasks to Task Group

Use

This procedure to assign tasks to group of business transaction. Example below, all my checking tasks
assigned to “Sales Movements” group and financial transaction assigned to “Financial Movements”
group.
SAP CAR – POS DTA Configuration Step by Step (Part 3)

12.Define type group for sales items

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Type Group for Sales Items

Use

For each material in receipt could be different meaning. SAP allow us customizing group
of items.

13.Sales Item Types

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Sales Item Types

Use
Sales item can be different by type. Define item types follow business requirements and
reporting purpose.
In SAP retail module, each item type may have different posting / pricing etc ..
behavior. Define item type specifically help business process more flexible.
Operation analysis reporting also details.

14.Define Type Group for Discounts

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Type Group for Discounts

Use
You can grouping discount methods by meaning

15.Define Discount Types

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Discount Types

Use
We can define discount type base on business analysis requirement.
Example: Manual discount / Promotion Discount / Coupon Discount etc…
The important parameters we should consider are : “Task Processing” group. Assigned
to group, aggregation behavior will be applied.

16.Define Type Group for Taxes 111

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Type Group for Taxes

Use
you determine the category group for taxes.

17.Tax Types 111

Transaction Code
/N/POSDW/IMG
IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions -> Define Tax Types

Use

You determine the type for taxes.

SAP CAR – POS DTA Configuration Step by Step (Part 4)

18.Tender Groups 111

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> General Settings -> Define Type Group for Tender

Use

Tender group help us can group mean of payments

19.Tender Types 111
Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> General Settings -> Define Tender Types

Use

This procedure help us define mean of payment in receipt. By SAP CAR Aggregation
standard, additional information of tender won’t pass to SAP IDOCs. Enhancement need
to be done to pass extra information. Example, tender type is internal voucher we need
pass Voucher’s Serial Number to SAP ERP.
SAP CAR – POS DTA CONFIGURATION STEP BY STEP (PART 5)

20.Financial Transaction Groups 111

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions-> Define Type Group for Financial Transactions

Use

You determine the type group of the goods movements.

21.Financial Transaction Types 111

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions-> Define Financial Transaction Types
Use

You determine the type of financial movements.

22.Define Type Group for POS Transactions

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions-> Define Type Group for POS Transactions
Use

You determine the type group for POS transactions by meaning. Example, here i have
three group (Sales / Financial Transaction and Totals)

23.Define POS Transaction Types

Transaction Code
/N/POSDW/IMG

IMG Menu
SAP Customer Activity Repository -> POS Data Management -> POS Inbound
Processing -> POS Transactions-> Define POS Transaction Types

Use

For each transaction that is different to other transactions in meaning and in

Customizing, you need to create a new transaction type. You can then group these
transaction types so that you can compare and analyze them better.
End.