INTEGRATION APPROACHES AND ADVISING IN SAP RETAIL (PART 2)

Hi Fellows,

Continue “INTEGRATION APPROACHES AND ADVISING IN SAP RETAIL (PART 1)“, i gave to you my understanding of “Synchronous and Asynchronous” messages in data Exchange and a bit of personal idea about master data integration in SAP Retail Landscape.

In this part, i will talk about transactional data.

[3] – Advising for SAP Retail Integration

[3.2] – Transaction Data

Integration objects

There are many documents will be exchanged from System to system, between SAP and None-SAP systems.

We can divide by three groups:

Font-end Operation Transactions

  • Customer play sales order on font-end system (POS, Mobile APP, E-Commerce website, or another touch points…)
  • Customer do Payment.
  • Customer confirm Received Goods.
  • Customer query Loyalty Information.
  • Customer query Promotion Program.
  • Customer Pick Goods at Store.
  • Delivery Processing.
  • Services Orders Documents.
  • Deposit Documents.
  • Credit Notes Documents.
  • Installment Documents.
  • Reservation Documents
  • E-Invoice Documents
  • Stock Availability Check.

Backend Operation Transactions

  • Goods movement between store and store Documents.
  • Goods movement between Store and Distribution Center (DC) Documents.
  • Goods movement between Distribution Center (DC) and Distribution Center (DC) Documents.
  • Contract Management Documents.
  • Purchase Order (PO) Documents.
  • Goods Receive Documents.
  • Delivery Orders Documents.
  • Financial Documents.
  • Production Order Documents for Manufacturing process.
  • Work In Process Documents for Manufacturing process.
  • E-Invoice Documents

Analysis Transactions

  • Retail Sales Transactions.
  • Whole Sales Transactions.
  • Profitability Analysis.
  • Retail KPI Data (Sales per employee, Conversion rate, Gross and net profit, Average transaction value, Online sales relative to brick-and-mortar locations, Year over year growth, Stock turn, Gross Margin Return on Investment, Sell-through, Shrinkage, Customer retention…)

When you look at the list of documents above in Font-end, back-end and Analysis groups, documents handled by SAP or third parties system we will realize that not all documents need to transfer immediately like “Delivery Orders(DO)“.

So what documents need transfer immediately (Synchronous Messages) ?

Cash and Carry: Customers choose items and do payments at the store, receipts are confirmed after customers do payment at the cashier. For grocery or FMCG, many customers come to the supper market and do the payment at the same time, especially is a weekend. If we designed that Synchronous message will be used then if any issues with network connection, HQ/SAP severs performance issues that will hugely impact with business and sales opportunities. The sales data no need transfer to the backend system immediately. The highest priority is to make POS process input Sales as fast as possible.

Click and Collect – Home delivery: Opposite with Cash and Carry, customers select items on Online touchpoints (Mobile App, E-Commerce website) and they don’t know the actual physical inventory of items. The Font-end system needs to check inventory immediately from the back-end system. The after confirmed order in the system, the delivery process will be performing as schedules. We don’t need to make delivery orders immediately but we need to reserve goods immediately to reduce out-of-stoc

 sales scenarios above “Cash and Carry” and “Home Delivery” we note that those transactions interact directly by the customer we can use Synchronous message transfer.

Reservation: Reserve goods to make sure that Stock Available to deliver to Customer. Reservation action need execute immediately when customer confirmed Orders.

Stock Availability Check: Consumers want to know Stock Availability on Online touch points. The synchronous message needs to be applied to get current system stock indicators.

Payment and Financials Transaction: Accounting want to control revenue as soon as possible.

What documents no need transfer immediately (Asynchronous Messages) ?

Font-end Operation Transactions

  • Sales per receipt in Cash and Carry Model. There are many receipts placed in the system at the same time, the cashier needs to scan items as fast as possible. POS need perform query and response result as soon as possible…

Back-end Operation Transactions

  • Transaction related to Inventory movements in retail also huge and does not impact the business directly. Store / DC operator can capture movement transaction and system will exchange together schedules.

Analysis Transaction

  • Analysis transactions will send to the analysis system when the source system finishes a business processing. To make sure that data enough information and data to calculate, the Analysis system needs to collect as much as possible so data transfer from ERP to the Analysis system can very huge. The synchronous in this kind of transaction not necessary.

Conclusion

Many transactions exchange between SAP and the None-SAP system. Synchronous or Asynchronous data exchange decision base on affection with Customer directly and Business Operation.

End of part 2

Cuong Dang

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.