[SAP CAR] – POS DTA Understand Extension Segment in Inbound Sales IDOC

Hi guys,

When you look at SAP CAR Sales Inbound IDOC, you will see that almost segment data also has segment called “Extension”. So what does it mean of Extension segment and how to use in inbound sales ?

Inbound sales IDOC was designed for general purpose and cover various information of retail, there are fields to capture standard information but not all. So how can SAP CAR record multi information as business requirements for analysis reporting ?

SAP CAR IDOC really smart design to serve certain requirements by extension segment in SAP CAR IDOC.

In previous article, i visualized SAP CAR Inbound sales IDOC by tables relation https://sapzero2hero.com/2018/10/01/sap-car-pos-dta-idoc-segments-key-fields/

1 – Sales Transaction Level Extension

TCode WE30

Usage

In transaction extension segment where partner system (POS, ECommerce, F&B, Inventory System, etc..) can attach more information which is not standard or didn’t existed on Transaction Segment.

If business wants more information on transaction level, we can design multi extension segment.

Example

Customer wants to know meal period of walking customer get in to restaurant , F&B POS cashier will record customer meal period on POS and send back to SAP CAR through transaction extension segment.

<_-POSDW_-E1BPTRANSACTEXTENSIO SEGMENT="1">
	<RETAILSTOREID>[SAP PLAN]</RETAILSTOREID>
	<BUSINESSDAYDATE>[BUSINESS DATE]</BUSINESSDAYDATE>
	<TRANSACTIONTYPECODE>[TRANSACTION TYPE]</TRANSACTIONTYPECODE>
	<WORKSTATIONID>[POS WORKS STATTION]</WORKSTATIONID>
	<TRANSACTIONSEQUENCENUMBER>[TRANSACTION ID]</TRANSACTIONSEQUENCENUMBER>
	<FIELDGROUP>MEAL</FIELDGROUP>
	<FIELDNAME>PERIOD</FIELDNAME>
	<FIELDVALUE>[MEAL PERIOD]</FIELDVALUE>
</_-POSDW_-E1BPTRANSACTEXTENSIO>

2 – Line Item Extension Segment

Usage

With the same concept with transaction extension segment, line item extension segment used for certain purpose whenever you want record information for Line Item Level

Strong recommend to you, don’t use standard fields on line item level segment to capture your additional information. Why ? you wont know where and when those fields will be used and may effect to standard sales data logic processing.

Example

When you sale voucher, business user want capture voucher’s serial number for reconciliation purpose. We need add extension segment for line item level to capture serial number.

<_-POSDW_-E1BPLINEITEMEXTENSIO SEGMENT="1">
	<RETAILSTOREID>[SAP PLAN]</RETAILSTOREID>
	<BUSINESSDAYDATE>[BUSINESS DATE]</BUSINESSDAYDATE>
	<TRANSACTIONTYPECODE>[TRANSACTION TYPE]</TRANSACTIONTYPECODE>
	<WORKSTATIONID>[POS WORKS STATTION]</WORKSTATIONID>
	<TRANSACTIONSEQUENCENUMBER>[TRANSACTION ID]/TRANSACTIONSEQUENCENUMBER>
<RETAILSEQUENCENUMBER>[Line item sequence number]</RETAILSEQUENCENUMBER>
	<FIELDGROUP>ITEM</FIELDGROUP>
	<FIELDNAME>SERIAL</FIELDNAME>
	<FIELDVALUE>[Serial Number]</FIELDVALUE>
</_-POSDW_-E1BPLINEITEMEXTENSIO>

3 – Line Item Discount Extension Segment

Usage

Normally, discount apply to each item in transaction. Each item discount may has different information business want to capture.

Discount Extension segment help you record reference information of discount which doesn’t have standard fields on discount segment.

Example

Discount by promotion, in standard discount segment we have DisountID and BonusbuyID to capture promotion information from POS. In certain promotion like discount 10% when tender is credit card of bank XXX. Accounting want to know exactly bank’s name so we need design discount extension segment to record bank’s name along with discount id and bonus buyID.

<_-POSDW_-E1BPLINEITEMDISCOUNT SEGMENT="1">
	<RETAILSTOREID>[SAP PLAN]</RETAILSTOREID>
	<BUSINESSDAYDATE>[BUSINESS DATE]</BUSINESSDAYDATE>
	<TRANSACTIONTYPECODE>[TRANSACTION TYPE]</TRANSACTIONTYPECODE>
	<WORKSTATIONID>[POS WORKS STATTION]</WORKSTATIONID>
	<TRANSACTIONSEQUENCENUMBER>[TRANSACTION ID]/TRANSACTIONSEQUENCENUMBER>
<RETAILSEQUENCENUMBER>[Line item sequence number]</RETAILSEQUENCENUMBER>
<DISCOUNTSEQUENCENUMBER>[Discount Sequence Number]<DISCOUNTSEQUENCENUMBER>
	<FIELDGROUP>DISCOUNT</FIELDGROUP>
	<FIELDNAME>BANK</FIELDNAME>
	<FIELDVALUE>[Bank Name]</FIELDVALUE>
</_-POSDW_-E1BPLINEITEMDISCOUNT>

4 – Tender Extension Segment

One more important extension segment in SAP CAR Inbound IDOC is Tender Extension Segment. This extension help you record more information for tender.

Usage

Tender set up on SAP CAR to record payment method and amount from customer, based on tender types accounting will do posting to accounts.

In some tender types, accountant want to do settlement automatically and need information to audit and checking payments.

In SAP CAR, we can define tender extension segment to adapt requirements accordingly.

Example

In the shopping mall, there are common counter where counter’s cashier can enter data and print receipts to customer. End of day, shopping mall will pay back to shops. Accountant want to know how much payment from.

In SAP CAR, we will build tender extension segment for POS can enter payment from which shops.

<_-POSDW_-E1BPTENDEREXTENSIONS SEGMENT="1">
	<RETAILSTOREID>[SAP PLAN]</RETAILSTOREID>
	<BUSINESSDAYDATE>[BUSINESS DATE]</BUSINESSDAYDATE>
	<TRANSACTIONTYPECODE>[TRANSACTION TYPE]</TRANSACTIONTYPECODE>
	<WORKSTATIONID>[POS WORKS STATTION]</WORKSTATIONID>
	<TRANSACTIONSEQUENCENUMBER>[TRANSACTION ID]</TRANSACTIONSEQUENCENUMBER>
	<TENDERSEQUENCENUMBER>[tender sequence number]</TENDERSEQUENCENUMBER>
	<FIELDGROUP>SHOP</FIELDGROUP>	
	<FIELDNAME>SHOPCODE</FIELDNAME>				
	<FIELDVALUE>[Shop Code]</FIELDVALUE>				
</_-POSDW_-E1BPTENDEREXTENSIONS>

Conclusion

Each IDOC segment has extension segment, depend on your experience and how to use, how to send to BW, SAP S4 then you can make decision.

There are no advantage or disadvantage to use extension segment, technically data storage on SAP CAR a bit more with extension segment data.

Hope after this topic help you more about general design of SAP CAR Inbound IDOC and how flexibility to use.

Thank you

Cuong Dang