SAP BAPI_INB_DELIVERY_CHANGE Function Module for Change Inbound Delivery









BAPI_INB_DELIVERY_CHANGE is a standard bapi inb delivery change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Inbound Delivery processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bapi inb delivery change FM, simply by entering the name BAPI_INB_DELIVERY_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: V50I
Program Name: SAPLV50I
Main Program: SAPLV50I
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_INB_DELIVERY_CHANGE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'"Change Inbound Delivery
  EXPORTING
   HEADER_DATA =  "Change Header Data of Inbound Delivery
   HEADER_CONTROL =  "Control Data Inbound Del. Header Level
   DELIVERY =  "Delivery
*  TECHN_CONTROL =  "Technical Control Delivery BAPI

TABLES
*  HEADER_PARTNER =  "Delivery: Partner Change
*  TOKENREFERENCE =  "Reference of CSL Token
*  HANDLING_UNIT_HEADER =  "Handling unit header data
*  HANDLING_UNIT_ITEM =  "Handling Unit Item
*  PARTIAL_GR_OBJECTS =  "Objects for Partial GR Posting
*  HEADER_PARTNER_ADDR =  "Change Partner Address in Inbound Delivery
*  HEADER_DEADLINES =  "Change Dates in Inbound Delivery Header
*  ITEM_DATA =  "Change Item Data in Inbound Delivery
*  ITEM_CONTROL =  "Control Data Inbound Delivery Item Level
*  ITEM_SERIAL_NO =  "BAPI Delivery Serial Numbers Item
*  EXTENSION1 =  "Container for 'Customer Exit' Parameter
*  EXTENSION2 =  "Container for 'Customer Exit' Parameter
   RETURN =  "Return Parameter
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV50I_001 User Exit BAPI Inbound Delivery Replication
EXIT_SAPLV50I_002 User Exit BAPI Inbound Delivery Confirmation
EXIT_SAPLV50I_003 User Exit BAPI Outbound Delivery Replication
EXIT_SAPLV50I_004 User Exit BAPI Outbound Delivery Confirmation
EXIT_SAPLV50I_009 User Exit BAPI for Changing Inbound Deliveries
EXIT_SAPLV50I_010 User Exit BAPI for Changing Outbound Deliveries

IMPORTING Parameters details for BAPI_INB_DELIVERY_CHANGE

HEADER_DATA - Change Header Data of Inbound Delivery

Data type: BAPIIBDLVHDRCHG
Optional: No
Call by Reference: No ( called with pass by value option)

HEADER_CONTROL - Control Data Inbound Del. Header Level

Data type: BAPIIBDLVHDRCTRLCHG
Optional: No
Call by Reference: No ( called with pass by value option)

DELIVERY - Delivery

Data type: BAPIIBDLVHDRCHG-DELIV_NUMB
Optional: No
Call by Reference: No ( called with pass by value option)

TECHN_CONTROL - Technical Control Delivery BAPI

Data type: BAPIDLVCONTROL
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_INB_DELIVERY_CHANGE

HEADER_PARTNER - Delivery: Partner Change

Data type: BAPIDLVPARTNERCHG
Optional: Yes
Call by Reference: Yes

TOKENREFERENCE - Reference of CSL Token

Data type: BAPITOKENREFERENCE
Optional: Yes
Call by Reference: Yes

HANDLING_UNIT_HEADER - Handling unit header data

Data type: BAPIDLVHDUNHDR
Optional: Yes
Call by Reference: Yes

HANDLING_UNIT_ITEM - Handling Unit Item

Data type: BAPIDLVHDUNITM
Optional: Yes
Call by Reference: Yes

PARTIAL_GR_OBJECTS - Objects for Partial GR Posting

Data type: BAPIPGROBJECTS
Optional: Yes
Call by Reference: Yes

HEADER_PARTNER_ADDR - Change Partner Address in Inbound Delivery

Data type: BAPIDLVPARTNADDRCHG
Optional: Yes
Call by Reference: Yes

HEADER_DEADLINES - Change Dates in Inbound Delivery Header

Data type: BAPIDLVDEADLN
Optional: Yes
Call by Reference: Yes

ITEM_DATA - Change Item Data in Inbound Delivery

Data type: BAPIIBDLVITEMCHG
Optional: Yes
Call by Reference: Yes

ITEM_CONTROL - Control Data Inbound Delivery Item Level

Data type: BAPIIBDLVITEMCTRLCHG
Optional: Yes
Call by Reference: Yes

ITEM_SERIAL_NO - BAPI Delivery Serial Numbers Item

Data type: BAPIDLVITMSERNO
Optional: Yes
Call by Reference: Yes

EXTENSION1 - Container for 'Customer Exit' Parameter

Data type: BAPIEXTC
Optional: Yes
Call by Reference: Yes

EXTENSION2 - Container for 'Customer Exit' Parameter

Data type: BAPIEXT
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_INB_DELIVERY_CHANGE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_header_data  TYPE BAPIIBDLVHDRCHG, "   
lt_header_partner  TYPE STANDARD TABLE OF BAPIDLVPARTNERCHG, "   
lt_tokenreference  TYPE STANDARD TABLE OF BAPITOKENREFERENCE, "   
lt_handling_unit_header  TYPE STANDARD TABLE OF BAPIDLVHDUNHDR, "   
lt_handling_unit_item  TYPE STANDARD TABLE OF BAPIDLVHDUNITM, "   
lt_partial_gr_objects  TYPE STANDARD TABLE OF BAPIPGROBJECTS, "   
lv_header_control  TYPE BAPIIBDLVHDRCTRLCHG, "   
lt_header_partner_addr  TYPE STANDARD TABLE OF BAPIDLVPARTNADDRCHG, "   
lv_delivery  TYPE BAPIIBDLVHDRCHG-DELIV_NUMB, "   
lt_header_deadlines  TYPE STANDARD TABLE OF BAPIDLVDEADLN, "   
lt_item_data  TYPE STANDARD TABLE OF BAPIIBDLVITEMCHG, "   
lv_techn_control  TYPE BAPIDLVCONTROL, "   
lt_item_control  TYPE STANDARD TABLE OF BAPIIBDLVITEMCTRLCHG, "   
lt_item_serial_no  TYPE STANDARD TABLE OF BAPIDLVITMSERNO, "   
lt_extension1  TYPE STANDARD TABLE OF BAPIEXTC, "   
lt_extension2  TYPE STANDARD TABLE OF BAPIEXT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'  "Change Inbound Delivery
    EXPORTING
         HEADER_DATA = lv_header_data
         HEADER_CONTROL = lv_header_control
         DELIVERY = lv_delivery
         TECHN_CONTROL = lv_techn_control
    TABLES
         HEADER_PARTNER = lt_header_partner
         TOKENREFERENCE = lt_tokenreference
         HANDLING_UNIT_HEADER = lt_handling_unit_header
         HANDLING_UNIT_ITEM = lt_handling_unit_item
         PARTIAL_GR_OBJECTS = lt_partial_gr_objects
         HEADER_PARTNER_ADDR = lt_header_partner_addr
         HEADER_DEADLINES = lt_header_deadlines
         ITEM_DATA = lt_item_data
         ITEM_CONTROL = lt_item_control
         ITEM_SERIAL_NO = lt_item_serial_no
         EXTENSION1 = lt_extension1
         EXTENSION2 = lt_extension2
         RETURN = lt_return
. " BAPI_INB_DELIVERY_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_INB_DELIVERY_CHANGE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
"SELECT single DELIV_NUMB FROM BAPIIBDLVHDRCHG INTO @DATA(ld_delivery).
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!