SAP SHP_BAPI_DELIVERY_CHANGE_CHECK Function Module for NOTRANSL: Aufruf BAPI für Lieferungsänderung









SHP_BAPI_DELIVERY_CHANGE_CHECK is a standard shp bapi delivery change check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufruf BAPI für Lieferungsänderung 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 shp bapi delivery change check FM, simply by entering the name SHP_BAPI_DELIVERY_CHANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: V50K
Program Name: SAPLV50K
Main Program: SAPLV50K
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SHP_BAPI_DELIVERY_CHANGE_CHECK 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 'SHP_BAPI_DELIVERY_CHANGE_CHECK'"NOTRANSL: Aufruf BAPI für Lieferungsänderung
EXPORTING
IT_LIKP_NEW = "Reference Structure for XLIKP/YLIKP
IT_LIKP = "Reference Structure for XLIKP/YLIKP

IMPORTING
EF_CHG_REQUESTED = "Checkbox

TABLES
IT_LIPS_NEW = "Reference Structure for XLIPS/YLIPS
IT_LIPS = "Reference Structure for XLIPS/YLIPS
IT_VBPA = "Reference structure for XVBPA/YVBPA
IT_VBADR = "Reference structure for XSADR/YSADR
IT_SERNO_CHANGE = "Delivery Items in Which Serial Numbers Were Changed
IT_XVBUK = "Reference structure for XVBUK/YVBUK
.




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_SAPLV50K_005 User Exit BAPI Inbound Delivery Replication (Outbound from Sending System)
EXIT_SAPLV50K_006 User Exit BAPI Inbound Deliv. Confirmation (Outbound from Sending System)
EXIT_SAPLV50K_007 User Exit BAPI Outbound Delivery Replication (Outbound from Sender System)
EXIT_SAPLV50K_008 User Exit BAPI Outbound Deliv. Confirmation (Outbound from Sending System)
EXIT_SAPLV50K_011 User Exit BAPI for Changing Inbound Deliveries (Outbound)
EXIT_SAPLV50K_012 User Exit BAPI for Changing Outbound Deliveries (Outbound)

IMPORTING Parameters details for SHP_BAPI_DELIVERY_CHANGE_CHECK

IT_LIKP_NEW - Reference Structure for XLIKP/YLIKP

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

IT_LIKP - Reference Structure for XLIKP/YLIKP

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

EXPORTING Parameters details for SHP_BAPI_DELIVERY_CHANGE_CHECK

EF_CHG_REQUESTED - Checkbox

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

TABLES Parameters details for SHP_BAPI_DELIVERY_CHANGE_CHECK

IT_LIPS_NEW - Reference Structure for XLIPS/YLIPS

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

IT_LIPS - Reference Structure for XLIPS/YLIPS

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

IT_VBPA - Reference structure for XVBPA/YVBPA

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

IT_VBADR - Reference structure for XSADR/YSADR

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

IT_SERNO_CHANGE - Delivery Items in Which Serial Numbers Were Changed

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

IT_XVBUK - Reference structure for XVBUK/YVBUK

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

Copy and paste ABAP code example for SHP_BAPI_DELIVERY_CHANGE_CHECK 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_it_likp_new  TYPE LIKPVB, "   
lt_it_lips_new  TYPE STANDARD TABLE OF LIPSVB, "   
lv_ef_chg_requested  TYPE XFELD, "   
lv_it_likp  TYPE LIKPVB, "   
lt_it_lips  TYPE STANDARD TABLE OF LIPSVB, "   
lt_it_vbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_it_vbadr  TYPE STANDARD TABLE OF SADRVB, "   
lt_it_serno_change  TYPE STANDARD TABLE OF SHP_SERNO_CHANGE, "   
lt_it_xvbuk  TYPE STANDARD TABLE OF VBUKVB. "   

  CALL FUNCTION 'SHP_BAPI_DELIVERY_CHANGE_CHECK'  "NOTRANSL: Aufruf BAPI für Lieferungsänderung
    EXPORTING
         IT_LIKP_NEW = lv_it_likp_new
         IT_LIKP = lv_it_likp
    IMPORTING
         EF_CHG_REQUESTED = lv_ef_chg_requested
    TABLES
         IT_LIPS_NEW = lt_it_lips_new
         IT_LIPS = lt_it_lips
         IT_VBPA = lt_it_vbpa
         IT_VBADR = lt_it_vbadr
         IT_SERNO_CHANGE = lt_it_serno_change
         IT_XVBUK = lt_it_xvbuk
. " SHP_BAPI_DELIVERY_CHANGE_CHECK




ABAP code using 7.40 inline data declarations to call FM SHP_BAPI_DELIVERY_CHANGE_CHECK

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.

 
 
 
 
 
 
 
 
 


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!