SAP SHP_DELIVERY_PARTNER_UPDATE Function Module for NOTRANSL: Änderung von Partnern einer Lieferung

Search SAP Function Modules

SHP_DELIVERY_PARTNER_UPDATE is a standard shp delivery partner update 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: Änderung von Partnern einer Lieferung 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 delivery partner update FM, simply by entering the name SHP_DELIVERY_PARTNER_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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

Function SHP_DELIVERY_PARTNER_UPDATE 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_DELIVERY_PARTNER_UPDATE'"NOTRANSL: Änderung von Partnern einer Lieferung
  EXPORTING
   IT_PARTNER_UPDATE =  "Request Partner Changes for a Delivery
*  IF_VBTYP = 'J' "SD document category
   IF_PARGR =  "Partner Determination Procedure
   IF_VKORG =  "Sales Organization
   IF_VTWEG =  "Distribution Channel
   IF_SPART =  "Division
*  IF_IGNORE_UPDATE_ERRORS = ' ' "

TABLES
   CT_XVBPA =  "
   CT_YVBPA =  "
   CT_XVBADR =  "
   CT_YVBADR =  "
   CT_XVBUV =  "Structure for Internal Table XVBUV
*  IT_BAPIADDR1 =  "BAPI Reference Structure for Addresses (Org./Company)

EXCEPTIONS
   MISSING_PARTNER_SCHEME = 1    PARTNER_CHANGE_NOT_ALLOWED = 2    ERROR_ON_PARTNER_CHANGE = 3 

.

IMPORTING Parameters details for SHP_DELIVERY_PARTNER_UPDATE

IT_PARTNER_UPDATE - Request Partner Changes for a Delivery

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

IF_VBTYP - SD document category

Data type: TVLK-VBTYP
Default: 'J'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IF_PARGR - Partner Determination Procedure

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

IF_VKORG - Sales Organization

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

IF_VTWEG - Distribution Channel

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

IF_SPART - Division

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

IF_IGNORE_UPDATE_ERRORS -

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

TABLES Parameters details for SHP_DELIVERY_PARTNER_UPDATE

CT_XVBPA -

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

CT_YVBPA -

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

CT_XVBADR -

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

CT_YVBADR -

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

CT_XVBUV - Structure for Internal Table XVBUV

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

IT_BAPIADDR1 - BAPI Reference Structure for Addresses (Org./Company)

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

EXCEPTIONS details

MISSING_PARTNER_SCHEME -

Data type:
Optional: No
Call by Reference: Yes

PARTNER_CHANGE_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

ERROR_ON_PARTNER_CHANGE - Error During Partner Change

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SHP_DELIVERY_PARTNER_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM SHP_DELIVERY_PARTNER_UPDATE

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