SAP SD_PARTNER_ADDRESSES_TO_DB Function Module for NOTRANSL: Ziehen von Adressnummern und anstoßen der ZAV Verbuchung in UPD-

Search SAP Function Modules

SD_PARTNER_ADDRESSES_TO_DB is a standard sd partner addresses to db 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: Ziehen von Adressnummern und anstoßen der ZAV Verbuchung in UPD- 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 sd partner addresses to db FM, simply by entering the name SD_PARTNER_ADDRESSES_TO_DB into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_PARTNER_ADDRESSES_TO_DB 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 'SD_PARTNER_ADDRESSES_TO_DB'"NOTRANSL: Ziehen von Adressnummern und anstoßen der ZAV Verbuchung in UPD-
  EXPORTING
*  FIF_VBELN =  "
*  FIF_IN_UPDATE_TASK = 'X' "
*  OBJECT = 'VBPA' "
*  FIF_SAVE_ALL = ' ' "Checkbox
*  FIF_TRTYP =  "Transaction Type

TABLES
   FET_XVBPA =  "
   FET_XVBADR =  "

EXCEPTIONS
   NUMBER_COULD_NOT_BE_DETERMINED = 1    CAM_SAVING_ERROR = 2    DOCUMENT_NUMBER_MISSING = 3 

.

IMPORTING Parameters details for SD_PARTNER_ADDRESSES_TO_DB

FIF_VBELN -

Data type: VBAK-VBELN
Optional: Yes
Call by Reference: Yes

FIF_IN_UPDATE_TASK -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

OBJECT -

Data type:
Default: 'VBPA'
Optional: Yes
Call by Reference: Yes

FIF_SAVE_ALL - Checkbox

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

FIF_TRTYP - Transaction Type

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

TABLES Parameters details for SD_PARTNER_ADDRESSES_TO_DB

FET_XVBPA -

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

FET_XVBADR -

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

EXCEPTIONS details

NUMBER_COULD_NOT_BE_DETERMINED -

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

CAM_SAVING_ERROR -

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

DOCUMENT_NUMBER_MISSING -

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

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

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