SAP SD_PARTNER_READ Function Module for Read partner data









SD_PARTNER_READ is a standard sd partner read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read partner data 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 read FM, simply by entering the name SD_PARTNER_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_PARTNER_READ 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_READ'"Read partner data
  EXPORTING
*  F_VBELN = ' ' "
*  OBJECT = 'VBPA' "
*  NO_MASTER_ADRESS = ' ' "
*  IV_NO_INIT = ' ' "
*  IV_PARVW =  "Partner Role
*  IV_POSNR =  "Item Number of the SD Document

TABLES
   I_XVBADR =  "
   I_XVBPA =  "
*  I_YVBADR =  "
*  I_YVBPA =  "
*  I_XVBPA2 =  "
*  I_YVBPA2 =  "
.




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_SAPLV05I_001 User Exit for Order-Related Billing Index
EXIT_SAPLV05I_002 User Exit for Billing Index for Delivery Reference
EXIT_SAPLV05I_003 User Exit for Billing Index with Reference to IV
EXIT_SAPLV05I_004 User Exit for Billing Index for Invoice List Reference

IMPORTING Parameters details for SD_PARTNER_READ

F_VBELN -

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

OBJECT -

Data type: C
Default: 'VBPA'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_MASTER_ADRESS -

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

IV_NO_INIT -

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_PARVW - Partner Role

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

IV_POSNR - Item Number of the SD Document

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

TABLES Parameters details for SD_PARTNER_READ

I_XVBADR -

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

I_XVBPA -

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

I_YVBADR -

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

I_YVBPA -

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

I_XVBPA2 -

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

I_YVBPA2 -

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

Copy and paste ABAP code example for SD_PARTNER_READ 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_f_vbeln  TYPE VBAK-VBELN, "   SPACE
lt_i_xvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lv_object  TYPE C, "   'VBPA'
lt_i_xvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_i_yvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lv_no_master_adress  TYPE XFLAG, "   SPACE
lt_i_yvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lv_iv_no_init  TYPE XFLAG, "   SPACE
lv_iv_parvw  TYPE PARVW, "   
lt_i_xvbpa2  TYPE STANDARD TABLE OF VBPA2VB, "   
lv_iv_posnr  TYPE POSNR, "   
lt_i_yvbpa2  TYPE STANDARD TABLE OF VBPA2VB. "   

  CALL FUNCTION 'SD_PARTNER_READ'  "Read partner data
    EXPORTING
         F_VBELN = lv_f_vbeln
         OBJECT = lv_object
         NO_MASTER_ADRESS = lv_no_master_adress
         IV_NO_INIT = lv_iv_no_init
         IV_PARVW = lv_iv_parvw
         IV_POSNR = lv_iv_posnr
    TABLES
         I_XVBADR = lt_i_xvbadr
         I_XVBPA = lt_i_xvbpa
         I_YVBADR = lt_i_yvbadr
         I_YVBPA = lt_i_yvbpa
         I_XVBPA2 = lt_i_xvbpa2
         I_YVBPA2 = lt_i_yvbpa2
. " SD_PARTNER_READ




ABAP code using 7.40 inline data declarations to call FM SD_PARTNER_READ

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 VBELN FROM VBAK INTO @DATA(ld_f_vbeln).
DATA(ld_f_vbeln) = ' '.
 
 
DATA(ld_object) = 'VBPA'.
 
 
 
DATA(ld_no_master_adress) = ' '.
 
 
DATA(ld_iv_no_init) = ' '.
 
 
 
 
 


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!