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

Hi Guys,

I will show you steps how to config SAP POSDM or SAP CAR (Customer Activity Repository) simplest step by step. Hope you guys can understand and control SAP POSDM / CAR POS DTA in your organization.

In this article, i won’t tell you what is SAP POSDM / CAR POS DTA. Those conceptual already in SAP official website, you can refer at : https://www.sap.com/sea/products/pos-data-repository.html

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)