Release 4.6C
Copyright
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem
Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung
durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne
vorherige Ankündigung geändert werden.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind
eingetragene Marken der Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®,
AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere®, Netfinity®, Tivoli®, Informix und Informix® Dynamic ServerTM sind Marken der
IBM Corporation in den USA und/oder anderen Ländern.
UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.
HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der
Lizenz der von Netscape entwickelten und implementierten Technolog ie.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com und weitere
im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos
sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern
weltweit.
MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP Markets und Commerce
One.
Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweili gen Firmen.
Contents
1 Introduction.......................................................................................... 4
2 Other Sources of Information ............................................................. 4
3 Overview............................................................................................... 4
3.1 The Business Process ................................ ................................ ..................... 4
3.2 The Communication Process................................ ................................ ...........5
3.2.1 Replication of Deliveries (ERP WMS)................................ .......................... 5
3.2.2 Confirmation of Deliveries (WMS ERP) ................................ ....................... 5
3.2.3 Goods Movements (WMS ERP)................................ ................................ ..6
3.3 Distribution Relevance................................ ................................ ..................... 6
4 Technical Information.......................................................................... 7
4.1 Segment Structure of the IDocs................................ ................................ .......7
4.1.1 SHP_OBDLV_SAVE_REPLICA01................................ ................................ ...7
4.1.2 SHP_IBDLV_SAVE_REPLICA01 ................................ ................................ ....8
4.1.3 SHP_OBDLV_CONFIRM_DECENTRAL02 ................................ ..................... 9
4.1.4 SHP_IBDLV_CONFIRM_DECENTRAL01................................ ..................... 10
4.1.5 MBGMCR02 ................................ ................................ ................................ ..11
4.2 Important Fields of Selected Segments ................................ ......................... 11
4.2.1 Header Segments for Outbound Delivery Confirmation ................................ .11
4.2.2 Header Segments for Inbound Delivery Confirmation ................................ ....12
4.2.3 Time Stamps ................................ ................................ ................................ .13
4.2.4 Item Segments for Outbound Delivery Confirmation ................................ ......14
4.2.5 Item Segments for Inbound Delivery Confirmation................................ .........15
4.2.6 Comment on Batch Split ................................ ................................ ................ 17
4.2.7 Handling Units (HUs)................................ ................................ ..................... 18
4.2.8 Goods Movements................................ ................................ ......................... 19
5 User Exits ........................................................................................... 20
1 Introduction
The interface for the integration of Decentralized Warehouse Management systems (LE -IDW) is
used to run a Warehouse Management system (WMS) as a decentralized stand -alone system
that operates separately to SAP R/3. The WMS can be eithe r the SAP WMS or the pro duct of
any other vendor using this interface.
A warehouse is used not only for the storage of goods but also particularly for the distr ibution of
goods, and thus represents the link between internal and external logistics. The WMS should
ensure quick response times and has to be available 24 hours a day – regardless of whether
other systems are available.
Since war ehouse processes constitute an essential integral part of the supply chain, the LE -
IDW interface integrates them with th e entire logistics process. In addition, by operating on the
basis of deliveries rather than on the basis of transfer orders, the WMS gains the necessary
flexibility to organize these processes independently of the Enterprise Resource Planning (ERP)
system and to be able to also operate during a limited downtime of the ERP system.
Documentation for the Decentralized Warehouse Management can be found in the SAP Library
under Logistics Logistics Execution (LE) Decentralized Warehouse Management (LE -
IDW).
A complete description on how to configure the ERP system to use the decentralized WMS can
be found in the Implementation Guide (IMG) under Logistics Execution (LE) Decentralized
WMS Integration.
Communication takes place using Intermediate Documents (IDocs). You can find online doc u-
mentation for IDoc communication in the SAP Library under Basis Compo nents Basis Se r-
vices/Communication Interfaces (BC-SRV) The IDoc Interface (BC-SRV-EDI).
Information on how to send and receive IDocs through TCP/IP is provided in the SAP Library
under Basis Components Basis Services/Communication Interfaces (BC -SRV) Remote
Communications (BC-SRV-RC) The RFC API
In the Interface Repository at http://ifr.sap.com, you can find a description of all business objects
and BAPIs provided by SAP.
3 Overview
The interface enables the replication and confirmation of deliveries from an SAP ERP System to
a WMS system.
The link between the two systems is provided by the business object (inbound or outbound)
delivery. For every business process that starts in the ERP and involves a physical or logical
(for example posting changes) goods movement, a delivery is created and replicated to the
WMS. The WMS carries out the actual goods movement and subsequently confirms the deli v-
ery. After the confirmation of the delivery, the actual inventory d ata is adjusted in the ERP sy s-
tem.
Goods movements that are initiated by the WMS (inventory adjustments, posting changes),
have to be communicated to the ERP system also. This is done directly by calling methods of
the business object GoodsMovement.
BAPI BAPI_INB_DELIVERY_CONFIRM_DEC
IDoc SHP_IBDLV_CONFIRM_DECENTRAL01
Message Type SHP_IBDLV_CONFIRM_DECENTRAL
ERP WMS
Status = ‚A’
Delivery
creation
IDoc for
replication
Delivery
Status = ‚B’ creation
Status = ‚B’
Delivery
Status = ‚B’ confirmation
IDoc for
confirmation
Delivery Status = ‚C’
confirmation
Status = ‚C’
4 Technical Information
Documentation of the BAPIs can be found online in the Interface Repository at
http://ifr.sap.com: Logistics Execution Shipping Outbound/Inbound Delivery
4.1.1 SHP_OBDLV_SAVE_REPLICA01
IDoc Segment BAPI Parameter Description Max. Nu m- Hier.
ber of Se g- Level
ments
E1SHP_OBDLV_SAVE_REPLICA - Header Segment 1 1
E1BPOBDLVHDR HeaderData Outbound Del. Header Fields 1 2
E1BPOBDLVHDRORG HeaderOrg Outbound Delivery Organiz a- 1 2
tional Units
E1BPDLVCONTROL TechnControl Technical Control Delivery 1 2
BAPI
E1BPDLVPARTNER HeaderPartner Delivery Partner 999999999 2
E1BPADR1 HeaderPartnerAddr BAPI Reference Structure for 999999999 2
Addresses (Org./Company)
E1BPADR11 HeaderPartnerAddr BAPI Reference Structure for 1 3
Addresses (Org./Company)
E1BPDLVDEADLN HeaderDeadlines Delivery Deadlines 999999999 2
E1BPOBDLVITEM ItemData Outbound Delivery Item 999999999 2
E1BPOBDLVITEMORG ItemOrg Outbound Delivery Item 999999999 2
Organizational Units
E1BPDLVITEMSTTR ItemStockTrans BAPI Delivery Stock Tran sfer 999999999 2
Data Item
E1BPDLVCOBLITEM ItemCodingBlock BAPI Delivery Acct Assig n- 999999999 2
ment Data Item
E1BPOBDLVITEMRFO ItemReferenceOrder Outbound Delivery Item 999999999 2
Order Reference Data
E1BPDLVITEMRPO ItemRefPurchaseOrder Delivery Item Order Refe r- 999999999 2
ence Data
E1BPDLVTXTHDR TextHeader Delivery Text Header 999999999 2
E1BPDLVTXTITEM TextLines Delivery Text Lines 999999999 2
E1BPDLVHDUNHDR HandlingUnitHeader Handling Unit Header Data 999999999 2
E1BPDLVHDUNITM HandlingUnitItem Handling Unit Item 999999999 2
E1BPEXTC Extension1 BFA: Container for Cu stomer 999999999 2
Exit Parameter
E1BPEXT Extension2 BFA: Container for Cu stomer 999999999 2
Exit Parameter.
4.1.2 SHP_IBDLV_SAVE_REPLICA01
IDoc Segment BAPI Parameter Description Max. Nu m- Hier.
ber of Se g- Level
ments
E1SHP_IBDLV_SAVE_REPLICA - Header Segment 1 1
E1BPIBDLVHDR HeaderData Inbound Del. Header Fields 1 2
E1BPIBDLVHDRORG HeaderOrg Inbound Delivery Organiz a- 1 2
tional Units
E1BPDLVCONTROL TechnControl Technical Control Delivery 1 2
BAPI
E1BPDLVPARTNER HeaderPartner Delivery Partner 999999999 2
E1BPADR1 HeaderPartnerAddr BAPI Reference Structure for 999999999 2
Addresses (Org./Company)
E1BPADR11 HeaderPartnerAddr BAPI Reference Structure for 999999999 3
Addresses (Org./Company)
E1BPDLVDEADLN HeaderDeadlines Delivery Deadlines 999999999 2
E1BPIBDLVITEM ItemData Inbound Delivery Item 999999999 2
E1BPIBDLVITEMORG ItemOrg Inbound Delivery Item Organ- 999999999 2
izational Data
E1BPDLVITEMSTTR ItemStockTrans BAPI Delivery Stock Transfer 999999999 2
Data Item
E1BPDLVCOBLITEM ItemCodingBlock BAPI Delivery Acct Assig n- 999999999 2
ment Data Item
E1BPDLVITEMRPO ItemRefPurchaseOrder Delivery Item Order Refe r- 999999999 2
ence Data
E1BPDLVTXTHDR TextHeader Delivery Text Header 999999999 2
E1BPDLVTXTITEM TextLines Delivery Text Lines 999999999 2
E1BPDLVHDUNHDR HandlingUnitHeader Handling Unit Header Data 999999999 2
E1BPDLVHDUNITM HandlingUnitItem Handling Unit Item 999999999 2
E1BPEXTC Extension1 BFA: Container for Customer 999999999 2
Exit Parameter
E1BPEXT Extension2 BFA: Container for Customer 999999999 2
Exit Parameter
4.1.3 SHP_OBDLV_CONFIRM_DECENTRAL02
IDoc Segment BAPI Parameter Description Max. Nu m- Hier.
ber of Se g- Level
ments
E1SHP_OBDLV_CONFIRM_DEC - Header Segment 1 1
ENTR
E1BPOBDLVHDRCON HeaderData Verification Outbound Del. 1 2
Picking Data Header Level
E1BPOBDLVHDRCTRLCON HeaderControl Control Data Outbound Del. 1 2
Header Level
E1BPDLVCONTROL TechControl Technical Control Delivery 1 2
BAPI
E1BPDLVDEADLN HeaderDeadlines Delivery Deadlines 999999999 2
E1BPOBDLVITEMCON ItemData Verification Outbound D e- 999999999 2
livery Pic king Data Item
Level
E1BPOBDLVITEMCTRLCON ItemControl Control Data Outbound 999999999 2
Delivery Item Level
E1BPOBDLVITEMSUPCON SupConData Outbound Delivery Vendor 999999999 2
Consignment Stock
E1BPDLVHDUNHDR HandlingUnitHeader Handling Unit Header Data 999999999 2
E1BPDLVHDUNITM HandlingUnitItem Handling Unit Item 999999999 2
E1BPEXTC Extension1 BFA: Container for Cu s- 999999999 2
tomer Exit Parameter
E1BPEXT Extension2 BFA: Containe r for Cu s- 999999999 2
tomer Exit Parameter
4.1.4 SHP_IBDLV_CONFIRM_DECENTRAL01
IDoc Segment BAPI Parameter Description Max. Nu m- Hier.
ber of Se g- Level
ments
E1SHP_IBDLV_CONFIRM_DECE - Header Segment 1 1
NTR
E1BPIBDLVHDRCON HeaderData Verification Outbound Del. 1 2
Picking Data Header Level
E1BPIBDLVHDRCTRLCON HeaderControl Control Data Outbound Del. 1 2
Header Level
E1BPDLVCONTROL TechnControl Technical Control Delivery 1 2
BAPI
E1BPDLVDEADLN HeaderDeadlines Delivery Deadlines 999999999 2
E1BPIBDLVITEMCON ItemData Verification Outbound D e- 999999999 2
livery Picking Data Item
Level
E1BPIBDLVITEMCTRLCON ItemControl Control Data Outbo und 999999999 2
Delivery Item Level
E1BPDLVHDUNHDR HandlingUnitHeader Handling Unit Header data 999999999 2
E1BPDLVHDUNITM HandlingUnitItem Handling Unit Item 999999999 2
E1BPEXTC Extension1 BFA: Container for Cu s- 999999999 2
tomer Exit Parameter.
E1BPEXT Extension2 BFA: Container for Cu s- 999999999 2
tomer Exit Parameter.
4.1.5 MBGMCR02
IDoc Segment BAPI Parameter Description Max. Nu m- Hier.
ber of Se g- Level
ments
E1MBGMCR Testrun Header Segment 1 1
E1BP2017_GM_HEAD_01 GoodsmvtHeader BAPI Communication Stru c- 1 1
ture: Material Document
Header Data
E1BP2017_GM_CODE GoodsmvtCode MMIM: New Key Assig n- 1 1
ment GM_CODE to Tran s-
action of Inv. Mgmt
E1BP2017_GM_ITEM_CREATE GoodsmvtItem (up to field BAPI Communication Stru c- 999999999 1
PAR_COMPCO) ture: Create Material Doc u-
ment Item
E1BP2017_GM_ITEM_CREATE1 GoodsmvtItem (from field BAPI Communication Stru c- 1 2
DELIV_NUMB) ture: Create Material Doc u-
ment Item
E1BP2017_GM_SERIALNUMBER GoodsmvtSerialnumber BAPI Communication Stru c- 1 1
ture: Create Mat. Doc.,
Serial No.
E1BPOBDLVHDRCON:
Field name Comment
Outbound delivery number. Leading zeros required
Gross weight of delivery. Only required if correspo nding flag of
E1BPOBDLVHDRCTRLCON is set.
Net weight of delivery. Only required if corresponding flag of
E1BPOBDLVHDRCTRLCON is set.
ISO code of the unit of measurement for the weights. Only required if
a weight is given.
Volume of delivery. Only required if corresponding flag of
E1BPOBDLVHDRCTRLCON is set.
ISO code of the unit of measurement for the volume. Only required if a
volume is given.
Warehouse door for the goods issue. Only required if corr esponding
flag of E1BPOBDLVHDRCTRLCON is set.
E1BPOBDLVHDRCTRLCON:
Field name Comment
Outbound delivery number. Leading zeros required
Set to ‘X’ if the gross weight of the delivery is to be updated. Othe r-
wise, leave blank.
Set to ‘X’ if the net weight of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the volume of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the goods issue for the delivery is to be posted automat i-
cally in the SAP system. Otherwise, leave blank. (GI date and time:
Time stamp type WSHDRWADTI in E1BPDLVDEADLN. Without a
time stamp, the date and time of the processing of the IDoc is taken.)
Set to ‘X’ if the delivery date is to be updated (Time stamp type
WSHDRLFDATI in E1BPDLVDEADLN). Otherwise, leave blank.
Set to ‘X’ if the warehouse door is to be updated. Otherwise, leave
blank.
Set to ‘X’ if the complete delivery is to be deleted. Otherwise, lea ve
blank.
E1BPIBDLVHDRCON:
Field name Comment
Inbound delivery number. Leading zeros required
Gross weight of delivery. Only required if corresponding flag of
E1BPIBDLVHDRCTRLCON is set.
Net weight of delivery. Only required if corresponding flag of
E1BPIBDLVHDRCTRLCON is set.
ISO code of the unit of m easurement for the weights. Only required if
a weight is given.
Volume of delivery. Only required if corresponding flag of
E1BPIBDLVHDRCTRLCON is set.
ISO code of the unit of measurement for the volume. Only required if a
volume is given.
Warehouse door for the goods receipt. Only required if corresponding
flag of E1BPIBDLVHDRCTRLCON is set.
E1BPIBDLVHDRCTRLCON:
Field name Comment
Inbound delivery number. Leading zeros required
Set to ‘X’ if the gros s weight of the delivery is to be updated. Othe r-
wise, leave blank.
Set to ‘X’ if the net weight of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the volume of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the goods receipt for the delivery is to be posted automat i-
cally (GR date and time: Time stamp type WSHDRWADTI in
E1BPDLVDEADLN) in the SAP system. Otherwise, leave blank.
Set to ‘X’ if the delivery date is t o be updated (Time stamp type
WSHDRLFDAT in E1BPDLVDEADLN). Otherwise, leave blank.
Set to ‘X’ if the warehouse door is to be updated. Otherwise, leave
blank.
Set to ‘X’ if the complete delivery is to be deleted. Otherwise, leave
blank.
date/time
WSHDRLDDAT Loading date/time ERP
WSHDRTDDAT Transport planning date/time ERP
WSHDRKODAT Planned Picking date/time ERP
E1BPIBDLVITEMCTRLCON:
Field name Comment
Outbound delivery number. Leading zeros required
Item number
"
Set to ‘X’ if the delivery quantity for the item is to be updated. Ot her-
wise, leave blank.
Set to ‘X’ if the item is to be deleted from the delivery document. Ot h-
erwise, leave blank.
Set to ‘X’ if the volume of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the net wei ght of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the gross weight of the delivery is to be updated. Othe r-
wise, leave blank.
E1BPIBDLVITEMCTRLCON:
Field name Comment
Inbound delivery number. Leading zeros required
Item number
"
Set to ‘X’ if the delivery quantity for the item is to be updated. Othe r-
wise, leave blank.
Set to ‘X’ if the item is to be deleted from the delivery document. Ot h-
erwise, leave blank.
Set to ‘X’ if the volume of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the net weight of the delivery is to be updated. Otherwise,
leave blank.
Set to ‘X’ if the gross weight of the delivery is to be updated. Othe r-
wise, leave blank.
There are many other fields in the header segment; Refer to the Interface Repository.
Has to be ‘3’
E1BP2017_GM_CODE:
Field name Comment
Has to be ‘06’
E1BP2017_GM_ITEM_CREATE:
Field name Comment
Material number
Plant to which the material belongs
Storage location where the material is stored
Batch number
Movement type (see below)
"
Quantity for goods movement
ISO code for unit of measurement (any allowed unit of measure)
Set to ‘X’ for a posting ch ange initiated in WM, in order to prevent
SAP from sending a posting change notice
"
To ensure that no transfer requirement is created in SAP, set to ‘X’
* 321: QI + UU
* 322: UU + QI
* 343: BS + UU
* 344: UU + BS
* 349: BS + QI
* 350: QI + BS
5 User Exits
User Exits on the sending side are present in the function modules
FM SHP_BAPI_DELIVERY_REPLICA, function group V50K:
User Exits on the receiving side are present in the following BAPI function modules
BAPI_OUTB_DELIVERY_SAVEREPLICA
• Customer function for EXIT_SAPLV50I_003
BAPI_INB_DELIVERY_SAVEREPLICA
• Customer function for EXIT_SAPLV50I_001
BAPI_OUTB_DELIVERY_CONFIRM_DEC
• Customer function for EXIT_SAPLV50I_004
BAPI_INB_DELIVERY_CONFIRM_DEC
• Customer function for EXIT_SAPLV50I_002