Integration With Decentarlised Wharehouse

SAP ®
Release 4.6C
© 2002 SAP AG Title: LE-IDW 4.6 Page 1 of 20

Neurottstr. 16 Version: 2.3
D-69190 Walldorf Date: 23-07-2002
SAP®
Copyright
© Copyright 2002 SAP AG. Alle Rechte vorbehalten.
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.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können

Softwarekomponenten auch anderer Softwarehersteller enthalten.
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.
ORACLE® ist eine eingetragene Marke der ORACLE Corporation.
UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.
Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix -Produkten sind Marken
von Citrix Systems, Inc.
HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.
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.

D-69190 Walldorf Date: 23-07-2002
SAP®
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

D-69190 Walldorf Date: 23-07-2002
SAP®
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.
2 Other Sources of Information

For additional information refer to the SAP online documentation at http://help.sap.com/.
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.
3.1 The Business Process

If you manage your warehouse decentrally, all your business transactions, including inventory
management of quantities, are executed in the ERP system, while all processes required for
physical goods movements run in the decentralized WMS.

D-69190 Walldorf Date: 23-07-2002
SAP®
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.
3.2 The Communication Process

The ERP system replicates an inbound or outbound delivery by calling a BAPI internally. This
BAPI call is automatically converted into an IDoc, which is sent out to the WMS. The WMS
sends an IDoc to the ERP system as confirmation. This IDoc is internally converted into the call
of a BAPI, which then performs the actual confirmation.
Goods movements initiated by the WMS are also sent to the ERP system via an IDoc, which is
then converted into a BAPI.
The IDoc communication ensures the tra nsactional integrity of the calls, that is, that the tran s-
ferred documents will be posted exactly once in the destination system. Furthermore, being
asynchronous, it a llows decoupling of the two systems: One system can proceed, even if the
other system is unavailable for a certain time.
3.2.1 Replication of Deliveries (ERP WMS)

The following BAPIs, IDocs and message types are used for replication (ERP WMS):
Outbound Deliveries:
BAPI BAPI_OUTB_DELIVERY_SAVEREPLICA
IDoc SHP_OBDLV_SAVE_REPLICA01
Message Type SHP_OBDLV_SAVE_REPLICA
Inbound Deliveries:
BAPI BAPI_INB_DELIVERY_SAVEREPLICA
IDoc SHP_IBDLV_SAVE_REPLICA01
Message Type SHP_IBDLV_SAVE_REPLICA
3.2.2 Confirmation of Deliveries (WMS ERP)

The following BAPIs, IDocs and message types are used for confirmation (WMS ERP):
Outbound Deliveries:
BAPI BAPI_OUTB_DELIVERY_CONFIRM_DEC
IDoc SHP_OBDLV_CONFIRM_DECENTRAL02 (R/3 Release ≥ 4.6B)
SHP_OBDLV_CONFIRM_DECENTRAL01 (R/3 Release 4.6A)
Message Type SHP_OBDLV_CONFIRM_DECENTRAL
Inbound Deliveries:

D-69190 Walldorf Date: 23-07-2002
SAP®
BAPI BAPI_INB_DELIVERY_CONFIRM_DEC
IDoc SHP_IBDLV_CONFIRM_DECENTRAL01
Message Type SHP_IBDLV_CONFIRM_DECENTRAL
3.2.3 Goods Movements (WMS ERP)

The following BAPI, IDoc and message type are used for goods movements initiated by the
WMS (WMS ERP):
BAPI BAPI_GOODSMVT_CREATE
IDoc MBGMCR02 (R/3 Release ≥ 4.6B)
MBGMCR01 (R/3 Release 4.5A – 4.6A)
Message Type MBGMCR
3.3 Distribution Relevance

The ERP system determines if a delivery is relevant for distribution using the following cond i-
tions:
1. The delivery type must allow a ‚Delivery split on warehouse number‘.
2. All items of the delivery must be relevant for the same warehouse number.
3. This warehouse number must be defined as a decentralized warehouse.
In the delivery header, the Distribution status controls the entire replication and confirmation
process. The possible values are:
‘‘ Not relevant
‘A’ Relevant for distribution
‘B’ Distributed
‘C’ Confirmed
This status sequence ensures that the communication process can only be run once per deli v-
ery. The delivery can be distributed and confirmed only once.
Distribution is performed immediately when the delivery is created. It can be d etained through
the delivery incompleteness log (set status incomplete for distribution).
Delivery confirmation takes place when goods movement occurs a nd adjusts the inventory on
the ERP side.

D-69190 Walldorf Date: 23-07-2002
SAP®
Communication Process Overview
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 Segment Structure of the IDocs

Here, you can find the segment structure of the involved IDocs and see which BAPI param eters
they correspond to. You can find all segment fields of the IDocs in the Interface Repos itory by
looking up the corresponding BAPI parameters. An explan ation of the important fields of the
IDocs that the WMS has to send to the ERP system is given in paragraph 4.2.
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

D-69190 Walldorf Date: 23-07-2002
SAP®
BAPI
E1BPDLVPARTNER HeaderPartner Delivery Partner 999999999 2
E1BPADR1 HeaderPartnerAddr BAPI Reference Structure for 999999999 2
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
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
BAPI
E1BPDLVPARTNER HeaderPartner Delivery Partner 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

D-69190 Walldorf Date: 23-07-2002
SAP®
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
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
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
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
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
The IDoc has to include the following segments:

• E1SHP_OBDLV_CONFIRM_DECENTR
• E1BPOBDLVHDRCON
• E1BPOBDLVHDRCTRLCON

D-69190 Walldorf Date: 23-07-2002
SAP®
• E1BPDLVDEADLN: A segment for each of the two time stamps: Delivery

Date/Time (WSHDRLFDAT), Actual Goo ds I ssue Date/Time
(WSHDRWADTI)
• E1BPOBDLVITEMCON: For all items that are to be updated
• E1BPOBDLVITEMCTRLCON: For all items that are to be updated
If Handling Units (HUs) are involved, the two segments E1BPDLVHDUNHDR and
E1BPDLVHDUNITM also have to be used.
4.1.4 SHP_IBDLV_CONFIRM_DECENTRAL01
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
BAPI
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
E1BPEXTC Extension1 BFA: Container for Cu s- 999999999 2
tomer Exit Parameter.
E1BPEXT Extension2 BFA: Container for Cu s- 999999999 2
tomer Exit Parameter.
The IDoc has to include the following segments:

• E1SHP_IBDLV_CONFIRM_DECENTR
• E1BPIBDLVHDRCON
• E1BPIBDLVHDRCTRLCON
• E1BPDLVDEADLN: A segment for each of the two time stamps: Delivery
Date/Time (WSHDRLFDAT), Actual Goods Receipt Date/Time
(WSHDRWADTI)
• E1BPIBDLVITEMCON: For all items that are to be updated
• E1BPIBDLVITEMCTRLCON: For all items that are to be updated
If Handling Units are involved, the two segments E1BPDLVHDUNHDR and
E1BPDLVHDUNITM also have to be used.

D-69190 Walldorf Date: 23-07-2002
SAP®
4.1.5 MBGMCR02
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.
The IDoc has to contain the following segments:

• E1BP2017_GM_HEAD_01: Contains header data for the goods movement
• E1BP2017_GM_CODE: Shows that the document is from a warehouse
• E1BP2017_GM_ITEM_CREATE: Item data for the goods movement
4.2 Important Fields of Selected Segments
4.2.1 Header Segments for Outbound Delivery Confirmation

E1SHP_OBDLV_CONFIRM_DECENTR:
Field name Comment

Outbound delivery number. Leading zeros required
E1BPOBDLVHDRCON:
Field name Comment


Gross weight of delivery. Only required if correspo nding flag of
E1BPOBDLVHDRCTRLCON is set.

Net weight of delivery. Only required if corresponding flag of

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

D-69190 Walldorf Date: 23-07-2002
SAP®

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


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.
4.2.2 Header Segments for Inbound Delivery Confirmation

E1SHP_IBDLV_CONFIRM_DECENTR:
Field name Comment

Inbound delivery number. Leading zeros required
E1BPIBDLVHDRCON:
Field name Comment


Gross weight of delivery. Only required if corresponding flag of
E1BPIBDLVHDRCTRLCON is set.

Net weight of delivery. Only required if corresponding flag of

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

D-69190 Walldorf Date: 23-07-2002
SAP®

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


Set to ‘X’ if the gros s weight of the delivery is to be updated. Othe r-
wise, leave blank.

leave blank.

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.
4.2.3 Time Stamps

E1BPDLVDEADLN:
Field name Comment


Time stamp type

Date and time relative to Universal Coordinated Time (UCT), corr e-
sponds to Greenwich Mean Time (GMT). Of the form YY Y-
YMMDDhhmmss

!
Time zone in which the event takes place.
Supported time stamp types:
Time Stamp Description Defined by ERP/WMS
WSHDRLFDAT Delivery date/time WMS
WSHDRWADAT Planned goods receipt (issue) ERP
date/time
WSHDRWADTI Actual go ods receipt (issue) WMS

D-69190 Walldorf Date: 23-07-2002
SAP®
date/time
WSHDRLDDAT Loading date/time ERP
WSHDRTDDAT Transport planning date/time ERP
WSHDRKODAT Planned Picking date/time ERP
4.2.4 Item Segments for Outbound Delivery Confirmation

E1BPOBDLVITEMCON:
Field name Comment


Item number

Material number

Batch number of the material (if in batches). Check chapter ‘Batch
Split’ to find out how to perform a batch split.

Superior item in an item hierarchy. Only necessary if such a hiera r-
chy exists.

Type of item usage if in a hierarchy, Otherwise, leave blank. Permi t-
ted values: Batch sub -item (1), BOM sub -item (2), Product selection
(3), Sub-item (Automotive) (4), Free-goods (on-top bonus) (5).
"
Actual received quantity for the item in sales units. Only this or the
next field is required. Only required if corresponding flag of
E1BPOBDLVITEMCTRLCON is set. We suggest you use this unit of
measurement, since it is the one used for Handling Units.
"

Actual received quantity for the item in base unit (stock -keeping unit).
Only this or the preceding field is required. Only required if corr e-
sponding flag of E1BPOBDLVITEMCTRLCON is set.

Conversion between Sal es Unit and Base Unit (sales unit part). See
below. Necessary even if the two units coincide.

Conversion between Sales Unit and Base Unit (base unit part). See

Gross weight of the item. Only required if corresponding flag of
E1BPOBDLVITEMCTRLCON is set.

Net weight of the item. Only required if corresponding flag of

ISO code of the unit of measurement for the weights. Only requ ired if
a weight is given.

ISO code of the unit of measurement for the volume. Only required if
a volume is given.

Sales unit for the quantity.

Base unit for the quantity in which stocks of the material are ma n-
aged.

Stock type from which the item is posted. If blank, this is unrestricted

D-69190 Walldorf Date: 23-07-2002
SAP®
use. Other possible values: X (quality inspection), S (blocked)

Volume of the item. Only required if corresponding flag of
Comment on conversions:
The sales unit and the stock keeping unit (base unit) do not have to coincide. For example, you
might store a liquid in casks (ca), but sell it in bottles (bt):
100 bt ≡ 1 ca
The conversion factor describes this relationship. In the exa mple,

# $% %
# $
,
E1BPIBDLVITEMCTRLCON:
Field name Comment


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.

leave blank.

Set to ‘X’ if the net wei ght of the delivery is to be updated. Otherwise,
leave blank.

wise, leave blank.
4.2.5 Item Segments for Inbound Delivery Confirmation

E1BPIBDLVITEMCON:
Field name Comment


Item number

Material number

Batch number of the material (if in batches). Check chapter ‘Batch
Split’ to find out how to perform a batch split.

Superior Item in an item hierarchy (for example batch split). Only
necessary if such a hierarchy exists.

Type of item usage if in a hierarchy, Otherwise, leave blank. Permi t-
ted values: Batch sub -item (1), BOM sub -item (2), Product selection
(3), Sub-item (Automotive) (4), Free-goods (on-top bonus) (5).
"
Actual received quantity for the item in order units. Only this or the
next field is required. Only required if corresponding flag of
D-69190 Walldorf Date: 23-07-2002
SAP®
E1BPIBDLVITEMCTRLCON is set. We suggest you use this unit of

measurement, since it is the one used for Handling Units.
"

Actual received quantity for the item in base units (stock keeping
units). Only this or the preceding field is required. Only required if
corresponding flag of E1BPIBDLVITEMCTRLCON is set.

Conversion between Sales Unit and Base Unit (sales unit part). See

Conversion between Sales Unit and Base Unit (base unit part). See

Gross weight of the item. Only required if corresponding flag of
E1BPIBDLVITEMCTRLCON is set.

Net weight of the item. Only required if corresponding flag of

ISO code of the unit of me asurement for the weights. Only required if
a weight is given.

Volume of the item. Only required if corresponding flag of

ISO code of the unit of measurement for the volume. Only required if
a volume is given.

Sales unit for the quantity.

Base unit for the quantity in which stocks of the material are ma n-
aged.

Stock type to which the item is posted. If blank, this is unrestricted
use. Other possible values: X (quality inspection), S (blocked)
Comment on conversions:
The order unit and the stock keeping unit do not have to coincide. For example, you might store
a liquid in casks (ca), but purchase it in bottles (bt):
100 bt ≡ 1 ca
The conversion factor describes this relationship. In the example,

# $% %
# $
,
E1BPIBDLVITEMCTRLCON:
Field name Comment


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.

leave blank.

D-69190 Walldorf Date: 23-07-2002
SAP®

leave blank.

wise, leave blank.
4.2.6 Comment on Batch Split

For example, item 0010, material 4711, requested quantity 100 PCE.
You pick 40 PCE of Batch ‘A911’, 60 PCE of Batch ‘B912’.
In the IDoc, you have to return the item and two sub -items of type batch sub -item
(USERHIERITM=1). The main item has delivery quantity 0 and no batch number. The item
number for the batch items must not coincide with any of the other items in the delivery. Trad i-
tionally, numbers higher than 900000 are used.
Relevant fields for the batch split:
Main item: E1BPOBDLVITEMCON (or E1BPIBDLVITEMCON):
Field name Value

0010

4711
" &
"

(' or 0
Batch 1: E1BPOBDLVITEMCON (or E1BPIBDLVITEMCON):

Field name Value

900001

4711

A911

0010

1
" &
"

(' or 40
Batch 2 : E1BPOBDLVITEMCON (or E1BPIBDLVITEMCON):

Field name Value

900002

4711

B912

0010

1
"
60
D-69190 Walldorf Date: 23-07-2002
SAP®
4.2.7 Handling Units (HUs)

For every packaging material, that is, for every receiving HU, there has to be one header se g-
ment E1BPDLVHDU NHDR. For every packing relation (A is in B), there has to be one item
segment E1BPDLVHDUNITM.
E1BPDLVHDUNHDR
Field name Comment


)

Unique identifier for the HU. Either a Serial Shippi ng Co ntainer
Code (SSCC) or a number in the external number range for the
packaging material type of the SAP system.

)

Identifier is for the number range type
a) E or F: Number range object HU_VEKP. For a newly created
HU, the system will always check against the external interval.
b) C or D: SSCC18

Material number for the packaging material

This field is a GUID in a string representation of 22 characters
length.
If created by ERP, repeat the number sent by ERP. Otherwise, the
WMS should create a GUID itself . This number has to be repeated
if the same HU is used again later.

The logical system that created the HU (and GUID)
There are many other fields in the header segment; Refer to the Interface Repository.
E1BPDLVHDUNITM (for a packed material)

Field name Comment

)

Unique identifier for the HU, into which the material is packed.


Item number that will be packed
"
Quantity of the material that will be packed into the HU

ISO code of the sales unit

Material number of the packed material

Batch number of the packed material (if in batches)

Has to be ‘1’
E1BPDLVHDUNITM (for a packed Handling Unit)

Field name Comment

)

Unique identifier for the receiving HU

)

Unique identifier for the HU that is to be packed

D-69190 Walldorf Date: 23-07-2002
SAP®

Has to be ‘3’
4.2.8 Goods Movements

E1BP2017_GM_HEAD_01:
Field name Comment

Posting date (YYYYMMDD)

Document date (YYYYMMDD)
)
‘2’: Post the goods movement in SAP; ‘1’ Create a delivery instead
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’
Movement types (UU=unrestricted use, QI=quality inspection, BS=blocked stock):

• Inventory differences
* 711: Goods issue UU
* 712: Goods receipt UU
* 713: Goods issue QI
* 714: Goods receipt QI
* 717: Goods issue BS
* 718: Goods receipt BS
• Posting Changes

D-69190 Walldorf Date: 23-07-2002
SAP®
* 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:
• Customer function EXIT_SAPLV50K_005 for inbound deliveries

• Customer function EXIT_SAPLV50K_007 for outbound deliveries
FM SHP_BAPI_DELIVERY_CONFIRM_DEC, function group V50K:
• Customer function EXIT_SAPLV50K_006 for inbound deliveries

• Customer function EXIT_SAPLV50K_008 for outbound deliveries
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
BAPI_OUTB_DELIVERY_CONFIRM_DEC
BAPI_INB_DELIVERY_CONFIRM_DEC

D-69190 Walldorf Date: 23-07-2002

Integration With Decentarlised Wharehouse

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integration With Decentarlised Wharehouse

Uploaded by

Copyright:

Available Formats

SAP ®

© 2002 SAP AG Title: LE-IDW 4.6 Page 1 of 20

© Copyright 2002 SAP AG. Alle Rechte vorbehalten.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können

ORACLE® ist eine eingetragene Marke der ORACLE Corporation.

Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.

© 2002 SAP AG Title: LE-IDW 4.6 Page 2 of 20

© 2002 SAP AG Title: LE-IDW 4.6 Page 3 of 20

2 Other Sources of Information

3.1 The Business Process

© 2002 SAP AG Title: LE-IDW 4.6 Page 4 of 20

3.2 The Communication Process

3.2.1 Replication of Deliveries (ERP WMS)

3.2.2 Confirmation of Deliveries (WMS ERP)

© 2002 SAP AG Title: LE-IDW 4.6 Page 5 of 20

3.2.3 Goods Movements (WMS ERP)

3.3 Distribution Relevance

© 2002 SAP AG Title: LE-IDW 4.6 Page 6 of 20

Communication Process Overview

4.1 Segment Structure of the IDocs

© 2002 SAP AG Title: LE-IDW 4.6 Page 7 of 20

© 2002 SAP AG Title: LE-IDW 4.6 Page 8 of 20

The IDoc has to include the following segments:

© 2002 SAP AG Title: LE-IDW 4.6 Page 9 of 20

• E1BPDLVDEADLN: A segment for each of the two time stamps: Delivery

The IDoc has to include the following segments:

© 2002 SAP AG Title: LE-IDW 4.6 Page 10 of 20

The IDoc has to contain the following segments:

4.2 Important Fields of Selected Segments

4.2.1 Header Segments for Outbound Delivery Confirmation

© 2002 SAP AG Title: LE-IDW 4.6 Page 11 of 20

4.2.2 Header Segments for Inbound Delivery Confirmation

© 2002 SAP AG Title: LE-IDW 4.6 Page 12 of 20

4.2.3 Time Stamps

© 2002 SAP AG Title: LE-IDW 4.6 Page 13 of 20

4.2.4 Item Segments for Outbound Delivery Confirmation

© 2002 SAP AG Title: LE-IDW 4.6 Page 14 of 20

use. Other possible values: X (quality inspection), S (blocked)

4.2.5 Item Segments for Inbound Delivery Confirmation

E1BPIBDLVITEMCTRLCON is set. We suggest you use this unit of

© 2002 SAP AG Title: LE-IDW 4.6 Page 16 of 20

4.2.6 Comment on Batch Split

Batch 1: E1BPOBDLVITEMCON (or E1BPIBDLVITEMCON):

Batch 2 : E1BPOBDLVITEMCON (or E1BPIBDLVITEMCON):

4.2.7 Handling Units (HUs)

E1BPDLVHDUNITM (for a packed material)

E1BPDLVHDUNITM (for a packed Handling Unit)

© 2002 SAP AG Title: LE-IDW 4.6 Page 18 of 20

4.2.8 Goods Movements

Movement types (UU=unrestricted use, QI=quality inspection, BS=blocked stock):

© 2002 SAP AG Title: LE-IDW 4.6 Page 19 of 20

• Customer function EXIT_SAPLV50K_005 for inbound deliveries

• Customer function EXIT_SAPLV50K_006 for inbound deliveries

© 2002 SAP AG Title: LE-IDW 4.6 Page 20 of 20

You might also like