SAP CAR: Fiori Apps

SAP Smart Business Apps for SAP Customer Activity Repository

App IDApp NameLink
F0807Net Sales‘F0807’)/W21
F0808Sales Analysis – Gross Margin‘F0808’)/W21
F0809Sales Analysis – Average Transaction Value‘F0809’)/W21
F0810Number of Transactions‘F0810’)/W21
F0813Sales Analysis – Items per Transaction‘F0813’)/W21

SAP Fiori Apps for Omnichannel Article Availability (part of Inventory Visibility)

App IDApp NameLink
F2530Manage Sourcing Networks (SAP Retail)‘F2530’)/W26
F3391Manage Sourcing Networks (SAP S/4HANA)‘F2530’)/W26
F3003Manage Sources (SAP Retail)‘F3003’)/W26
F3392Manage Sources (SAP S/4HANA)‘F3392’)/W26
F2586Manage Sourcing Strategies‘F2586’)/W26
F2659Manage Sales Channels‘F2659’)/W26

SAP Fiori Apps for Demand Data Foundation (DDF)

App IDApp NameLink
F2020Configure Distribution Curves‘F2020’)/W26
F2053Manage Promotional Offers‘F2053’)/W26
F2576Manage Product Groups‘F2053’)/W26
F0829AManage Product Attributes‘F0829A’)/W26
F0550AManage Location Clusters‘F0550A’)/W26

SAP Fiori Apps for Demand Planning

App IDApp NameLink
F1773AAnalyze Forecast‘F1773A’)/W26
F3479Adjust Forecast‘F3479’)/W26
F3885Manage Demand Influencing Factors‘F3885’)/W26

SAP Assortment Planning

App IDApp NameLink
F0830AMy Option Plans‘F0830A’)/W26
F0831AMatch Placeholders‘F0831A’)/W26
F1567AMy Assortment Lists
F1682AManage Modules‘F1682A’)/W26
F3021Manage Planning Configuration Sets‘F3021’)/W26
F0830BManage Option Plans‘F0830B’)/W26

SAP Allocation Management

App IDApp NameLink
F2020Configure Distribution Curves‘F2020’)/W26
F2021Manage Market Units‘F2021’)/W26
F2022Manage Allocation Parameters‘F2022’)/W26
F2038My Allocation Plans‘F2038’)/W26
F2039My Allocation Workload‘F2039’)/W26
F2590Configure Allocation KPIs‘F2590’)/W26
F2592My Allocation Results‘F2592’)/W26
F4287Manage Store Areas and Capacities‘F4287’)/W26

SAP Promotion Management

App IDApp NameLink
F3349Offer Content Assignment‘F3349’)/W21
F3089Manage Location Subgroups‘F3089’)/W26
F2053Manage Promotional Offers‘F2053’)/W26
F4103Preview Promotional Events‘F4103’)/W26


Cuong Dang

SAP CAR – Documents (PDF)

This is list of official documents from SAP.

SAP PO->Monitoring: Outbound IDocs

Hi SAP PO Guys,

Today, i will show you step by step to monitor outbound IDocs from SAP ERP to SAP PO and receiver protocol is File system (FTP / SFTP / Shared Folders).

In the ERP system landscape, SAP ERP is core system where master data, transaction data managed. In some scenarios, we need send master data and transaction data to partners system. Master data can be material master, vendor master, customer master, sales price, promotion etc… all kind of objects SAP had standard message type following EDI standard.

When SAP ERP integrate to partners system, we need to know data flow and where would be check when data wasn’t sent to destination system.

In this topic, i will show you ways to check outbound material master from SAP S/4 Hana to POS system via SAP PO with integration scenario is: SAP S/4 -> SAP PO -> SFTP -> POS (Point Of Sales), base on this example, you can do checking to another outbound IDocs as well.

Continue reading

SAP PO: Webservice with SOAP sender and REST Receiver scenario

Hi PO guys,

In this article, i will share you how to make interface webservice with sender is SOAP adapter and Receiver with REST adapter scenario, hope can help you to implement SAP PO.

In this demonstration, i will make simple login function call from SAP ERP to third party using REST and HTTP.

Enterprise Service Builder

Design data type

Design message type

Design service interface 

Design message mapping

Design operation mapping

Integration Builder

Define SOAP sender channel

Define REST receiver channel

Define Integrated Configuration Object

Continue reading

SAP CAR-POSDM Sales Receipt Logical Structure

Hi Guys,

I will show you the basic concept of objects in sales receipt in SAP CAR – POSDM. In some articles, i was talked about retails, SAP CAR and POSDM.

Yeah, but what are base information in one sale receipt ?. Picture below will show you objects on one receipt.

Basically, one receipt will contain three main part.

First is header, header contain information of retailer, transaction information.

Second is goods information, Items you bough (item code, quantity, Unit of Measure, Unit price, total amount….)

Third is Payment information, payment group define kind of payment method, amount and additional information of payment method.

SAP CAR – POSDM provided to us a standard objects can have in receipt. Other than three group of information what i mentioned above. SAP also define objects what can capture more information for reporting / analysis purpose.

To understand logical objects, will help you easy to consult to customer and adapt requirements.


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

Hi Guys,

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

This is lasted part for SAP CAR POS DTA Configuration steps.

20.Financial Transaction Groups

Transaction Code

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


You determine the type group of the goods movements.

20.FIB Group.png

Continue reading

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

Hi Guys,

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

12.Define type group for sales items

Transaction Code

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


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

Continue reading

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

Hi Guys,

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

10.Define Tasks

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

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.

Continue reading