Inbound and Outbound idocs in the S/4

HANA Retail Template

Table of Contents
Outbound idocs ..................................................................................................3
ARTMAS (Material master data) ............................................................................................ 4
System Preparation ................................................................................................................................... 4
Idoc Generation ......................................................................................................................................... 4
WE02 : Display generated idoc (example : 5085)................................................................................................. 4
LIKOND (Listing conditions) .................................................................................................... 5
System Preparation ................................................................................................................................... 5
Idoc Generation ......................................................................................................................................... 5
WE02 : Display generated idoc (exemple : 5089) ................................................................................................ 5
INREF (Purchasing info-record)............................................................................................... 6
System Preparation ................................................................................................................................... 6
Idoc Generation ......................................................................................................................................... 6
WE02 : Display generated idoc (exemple : 5092, 5093, 5094) ............................................................................ 6
BOMMAT (Bill of material of an material) .............................................................................. 7
System Preparation ................................................................................................................................... 7
Idoc Generation ......................................................................................................................................... 7
WE02 : Display generated idoc (exemple : 5095) ................................................................................................ 7
WMATGRP (Customer Decision Tree – CDT) ........................................................................... 8
System Preparation ................................................................................................................................... 8
Idoc Generation ......................................................................................................................................... 8
WE02 : Display generated idoc (exemple : 5096) ................................................................................................ 8
COND_A (Pricing conditions) .................................................................................................. 9
System Preparation ................................................................................................................................... 9
Idoc Generation ......................................................................................................................................... 9
WE02 : Display generated idoc (exemple : 5100) ................................................................................................ 9

Inbound idocs ................................................................................................... 10

ARTMAS (Material master data) .......................................................................................... 11
System Preparation .................................................................................................................................11
Idoc Generation .......................................................................................................................................11
WE02 : Display generated idoc (example : 5097)............................................................................................... 11
LIKOND (Listing conditions) .................................................................................................. 12
System Preparation .................................................................................................................................12
Idoc Generation .......................................................................................................................................12
WE02 : Display generated idoc (example : 5099)............................................................................................... 12
COND_A (Pricing conditions) ................................................................................................ 13
System Preparation .................................................................................................................................13
Idoc Generation .......................................................................................................................................13

https://www.linkedin.com/in/mickaelquesnot/
Page | 1
 WE02 : Display generated idoc (example : 5101)............................................................................................... 13
INFREC (Purchasing info-record)........................................................................................... 14
System Preparation .................................................................................................................................14
Idoc Generation .......................................................................................................................................14
WE02 : Display generated idoc (example : 5110)............................................................................................... 14
MBGMCR (Goods movement – Receipt per initial entry of stock balances into unr.-use (561))
........................................................................................................................................... 15
System Preparation .................................................................................................................................15
Idoc Generation .......................................................................................................................................15
WE02 : Display generated idoc (example : 5111)............................................................................................... 15
MBGMCR (Goods movement – Goods receipt for purchase order into warehouse/stores
(101)) .................................................................................................................................. 16
System Preparation .................................................................................................................................16
Idoc Generation .......................................................................................................................................16
WE02 : Display generated idoc (example : 5113)............................................................................................... 16
MBGMCR (Goods movement – Goods receipt for purchase order into warehouse - reversal
(102)) .................................................................................................................................. 17
System Preparation .................................................................................................................................17
Idoc Generation .......................................................................................................................................17
WE02 : Display generated idoc (example : 5115)............................................................................................... 17
CONDCONTRACT_CREATE (Condition contract) .................................................................... 18
System Preparation .................................................................................................................................18
Idoc Generation .......................................................................................................................................18
WE02 : Display generated idoc (example : 5123, 5127)..................................................................................... 18
CONDCONTRACT_CHANGE (Condition contract) ................................................................... 19
System Preparation .................................................................................................................................19
Idoc Generation .......................................................................................................................................19
WE02 : Display generated idoc (example : 5124)............................................................................................... 19
ORDRSP - VMI (Purchase order creation from VMI) .............................................................. 20
System Preparation .................................................................................................................................20
Idoc Generation .......................................................................................................................................21
WE02 : Display generated idoc (example : 5133)............................................................................................... 21

https://www.linkedin.com/in/mickaelquesnot/
Page | 2
Outbound idocs
One way to identify field mapping for an inbound idoc is to generate its outbound equivalent.

Output an outbound idoc from an existing document or an existing master data will often
indicate where to input certain data in fields of the inbound idoc.

Here’s some outbound idocs from the S/4 HANA Retail Template and how to create them :

https://www.linkedin.com/in/mickaelquesnot/
Page | 3
ARTMAS (Material master data)
Idoc message type ARTMAS
Idoc basic type ARTMAS09
Transaction BD10

ARTMAS idoc is used to send material master data from a Retail Specific environment
(MATMAS idoc is used for a non-retail environment)

Often used with ARTMAS idocs are :

• INFREC (Purchasing info-record)
• LIKOND (Listing conditions for a material)
• COND_A (Pricing conditions of a material)
• BOMMAT (Bill of material of a material)

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o In order to create ARTMAS idoc, system must knows which distribution model to
use when creating idoc (From which system to which system)
o Create a model model view
o Choose the created model view and click Add BAPI
o Choose a sender system and a receiver system
o Enter for Object Name / Interface : RetailMaterial
o Enter for Method : Clone

Idoc Generation
• BD10 : Generate ARTMAS idoc from a material
o Enter material number, message type (standard) = MATMAS and execute
o 2 messages should appears :
▪ 1 master IDocs set up for message type ARTMAS
▪ 1 communication IDoc(s) generated for message type ARTMAS
WE02 : Display generated idoc (example : 5085)

https://www.linkedin.com/in/mickaelquesnot/
Page | 4
LIKOND (Listing conditions)
Idoc message type LIKOND
Idoc basic type LIKOND01
Transaction BD10

LIKOND idoc is used to send listing conditions for a given material (data from table WLK1)

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o Choose the created model view and click Add Message Type
o Choose a sender system and a receiver system
o Enter for message type : LIKOND

Idoc Generation
• BD10 : Generate LIKOND idoc from a material
o Enter material number, message type (standard) = MATMAS
o Select the option “Send material in full” and execute
WE02 : Display generated idoc (exemple : 5089)

https://www.linkedin.com/in/mickaelquesnot/
Page | 5
INREF (Purchasing info-record)
Idoc message type INFREC
Idoc basic type INFREC01
Transaction BD10

INFREC idoc is used to send purchasing all info-records for a given material (data from table
EINE and EINA)

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o Choose the created model view and click Add Message Type
o Choose a sender system and a receiver system
o Enter for message type : INFREC

Idoc Generation
• BD10 : Generate INFREC idoc from a material
o Enter material number, message type (standard) = MATMAS
o Select the option “Send material in full” and execute
WE02 : Display generated idoc (exemple : 5092, 5093, 5094)

https://www.linkedin.com/in/mickaelquesnot/
Page | 6
BOMMAT (Bill of material of an material)
Idoc message type BOMMAT
Idoc basic type BOMMAT05
Transaction BD30

BOMMAT idoc is used to send bill of material for a given material (data from transaction CS03,
tables STKO, STOP, STAS, etc.)

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o Choose the created model view and click Add Message Type
o Choose a sender system and a receiver system
o Enter for message type : BOMMAT

Idoc Generation
• BD30 : Generate BOMMAT idoc from a material
o Enter material number, hit enter and system will indicate how many BOM are
found
o Choose the proper message variant (Create, Change, Delete)
o Execute
o From the list, click on “Distribute”
WE02 : Display generated idoc (exemple : 5095)

https://www.linkedin.com/in/mickaelquesnot/
Page | 7
WMATGRP (Customer Decision Tree – CDT)
Idoc message type WMATGRP
Idoc basic type WMATGRP01
Transaction WRF_MATGRP_REQ_DLD

WMATGRP idoc is used to send the active and distribution chain-indenpendant CDT (Customer
Decision Tree)

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o Choose the created model view and click Add Message Type
o Choose a sender system and a receiver system
o Enter for message type : WMATGRP

Idoc Generation
• WRF_MATGRP_REQ_DLD : Generate WMATGRP idoc
o The CDT id is automatically displayed
o Execute
WE02 : Display generated idoc (exemple : 5096)

https://www.linkedin.com/in/mickaelquesnot/
Page | 8
COND_A (Pricing conditions)
Idoc message type COND_A
Idoc basic type COND_A04
Transaction VK13, MEK3

COND_A idoc is used to send pricing conditions for a given material

System Preparation
• SM59 : Ports are created
• BD64 : Maintain distribution model
o Choose the created model view and click Add Message Type
o Choose a sender system and a receiver system
o Enter for message type : COND_A

Idoc Generation
• VK13 : Display SD pricing information
o Enter condition type, lick on Condition Information
o Select the wanted data and execute
o When the list appears, select the conditions to send and click on “Send
Condition”
o Leave default Message Type “COND_A”
o Message appears : The system successfully created the IDoc for the conditions
selected
o Generated idoc(s) are displayed
WE02 : Display generated idoc (exemple : 5100)

https://www.linkedin.com/in/mickaelquesnot/
Page | 9
Inbound idocs
One way to identify field mapping for an inbound idoc is to generate its outbound equivalent.
Refer to the previous section about Outbound idocs for some outbound idocs examples.

Creation an inbound idocs is usually done manually by creating a test idoc using transaction
WE19.
In can also be done with LSMW
Also, it’s possible to create multiple idocs from a file using WE16 transaction.

Here’s some inbound idocs from the S/4 HANA Retail Template and how to map the data so it
can process a document or a master data.

Each idoc in examples are available on a Spreadsheet on the same folder as this file.

https://www.linkedin.com/in/mickaelquesnot/
Page | 10
ARTMAS (Material master data)
Idoc message type ARTMAS
Idoc basic type ARTMAS09
Transaction WE19

ARTMAS idoc is used to create of change material master data in a Retail Specific environment

Often used with ARTMAS idocs are :

• INFREC (Purchasing info-record)
• LIKOND (Listing conditions for a material)
• COND_A (Pricing conditions of a material)
• BOMMAT (Bill of material of a material)

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type ARTMAS

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5097
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5097)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

Idoc 5097 :

https://www.linkedin.com/in/mickaelquesnot/
Page | 11
LIKOND (Listing conditions)
Idoc message type LIKOND
Idoc basic type LIKOND01
Transaction WE19

LIKOND idoc is used to assign or terminate listing of a material master

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type LIKOND

Message code
Message function
Process code LIKO

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5099
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5099)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 12
COND_A (Pricing conditions)
Idoc message type COND_A
Idoc basic type COND_A04
Transaction WE19

COND_A idoc is used to create or modify a pricing condition

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type COND_A

Message code
Message function
Process code COND

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5101
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5101)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 13
INFREC (Purchasing info-record)
Idoc message type INFREC
Idoc basic type INFREC01
Transaction WE19

INFREC idoc is used to create or modify a purchasing info-record

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type INFREC

Message code
Message function
Process code INFR

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5110
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5110)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 14
MBGMCR (Goods movement – Receipt per initial entry of stock balances into unr.-use
(561))
Idoc message type MBGMCR
Idoc basic type MBGMCR03
Transaction WE19

MBGMCR idoc is used to process goods movement like in transaction MIGO

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type MBGMCR

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5111
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5111)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 15
MBGMCR (Goods movement – Goods receipt for purchase order into warehouse/stores
(101))
Idoc message type MBGMCR
Idoc basic type MBGMCR03
Transaction WE19

MBGMCR idoc is used to process goods movement like in transaction MIGO.

Note that in order to get the expiry date and the production date, you’ll need to configure in
OMJ5 for both movement code and site).

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type MBGMCR

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5113
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5113)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 16
MBGMCR (Goods movement – Goods receipt for purchase order into warehouse -
reversal (102))
Idoc message type MBGMCR
Idoc basic type MBGMCR03
Transaction WE19

MBGMCR idoc is used to process goods movement like in transaction MIGO.

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type MBGMCR

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5115
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5115)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 17
CONDCONTRACT_CREATE (Condition contract)
Idoc message type CONDCONTRACT_CREATE
Idoc basic type CONDCONTRACT_CREATE03
Transaction WE19

CONDCONTRACT_CREATE idoc is used to create a condition contract (WCOCO).

CONDCONTRACT_CHANGE idoc is used to modify an existing contract

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type CONDCONTRACT_CREATE

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5123 or 5127 (5127 is with Business Volume
Exclusion)
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5123, 5127)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 18
CONDCONTRACT_CHANGE (Condition contract)
Idoc message type CONDCONTRACT_CHANGE
Idoc basic type CONDCONTRACT_CHANGE03
Transaction WE19

CONDCONTRACT_CHANGE idoc is used to modify an existing contract

In this example, the condition amount will be changed from 18 % to 15 %

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type CONDCONTRACT_CHANGE

Message code
Message function
Process code BAPI

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5124
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5124)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 19
ORDRSP - VMI (Purchase order creation from VMI)
Idoc message type ORDRSP
Idoc basic type ORDERS05
Transaction WE19

ORDRSP, with message variant VMI is used to receive Purchase Order from Supplier (as the
customer).
Outbound idoc PROACT is previously sent to the vendor to inform its level of stock.

System Preparation
• SM59 : Ports are created
• WE20 : Maintain partner profiles
o Maintain the idoc message on the corresponding partner representing the
sender’s system
o In the inbound parameters section, add

Message type ORDRSP

Message code VMI
Message function
Process code ORDV

Process code ORDV calls the workflow : WS20000183

Configuration of the vendor must be done with transaction WVM7:

Vendor 1000000
Cust.(Sold-to Party) D001
Cust. (Ship-to Party) D001

Purch. organization 1000 Canada

Purch. Group 001 Buyer 1
Plant D001 DC1 Montreal
Purchasing Doc. Type NB Standard PO

With transaction BP, vendor must be allowed to receive purchase order by idoc

https://www.linkedin.com/in/mickaelquesnot/
Page | 20
Configuration of the MRP type :
Configure the MRP type for the relevant combination of material and plant properly. The MRP
type must have the following characteristics:
Characteristic Value Meaning
MRP procedure "W" Replenishment
Planning method "1" planned by external system

Assign this MRP type to the material (DC view)

Assign authorizations to user WF_BATCH with transaction SU01: With Role Z_SR_BUYER_5 for
example (Role must authorize the following:)
Object: M_BEST_EKO
ACTVT: 01
EKORG: 1000

Idoc Generation
• WE19 :
o Choose from Retail Template, idoc # 5133
o Change needed values
o Process the inbound idoc
WE02 : Display generated idoc (example : 5133)
To display the idoc content and to export it in Excel, display the idoc in WE02 and choose Print
Idoc from the Idoc menu.
From there, right click on the grid and choose Spreadsheet.

https://www.linkedin.com/in/mickaelquesnot/
Page | 21