SAP IQS0_RFC_SD_DOC_PARTNER_READ Function Module for Reading a partner of an Vertriebsbelegspositon with RFC









IQS0_RFC_SD_DOC_PARTNER_READ is a standard iqs0 rfc sd doc 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 Reading a partner of an Vertriebsbelegspositon with RFC 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 iqs0 rfc sd doc partner read FM, simply by entering the name IQS0_RFC_SD_DOC_PARTNER_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function IQS0_RFC_SD_DOC_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 'IQS0_RFC_SD_DOC_PARTNER_READ'"Reading a partner of an Vertriebsbelegspositon with RFC
EXPORTING
I_PARVW = "Partner role, e-g, WE = Ship-to party
I_POSNR = "Position Number, 0 = Kopf
I_VBELN = "Sales document number

IMPORTING
E_VBPA = "Sales Document: Partner
E_VBADR = "Adress workarea

EXCEPTIONS
NOT_FOUND = 1
.




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_SAPLIQS0_001 Customer Exit 'Check Status Change for Permission' for PM/CS Notifications
EXIT_SAPLIQS0_002 User Exit for Influencing the F4 Help for Catalogs
EXIT_SAPLIQS0_003 Function Code '+US3/4' in Menu 'Goto/Task' in Notification Processing
EXIT_SAPLIQS0_004 Function Code '+US5/6' in Menu 'Goto/Activities' in Notif. Processing
EXIT_SAPLIQS0_005 Determining Processing Deadlines According to Priority
EXIT_SAPLIQS0_006 Default Partner When Adding A Notification
EXIT_SAPLIQS0_007 Determination of BOM application for BOM Explosion
EXIT_SAPLIQS0_008 Supply Function Codes with Text/ Deactivate Codes: 'Goto/Task'
EXIT_SAPLIQS0_009 Supply Function Codes/ Deactivate Codes: 'Goto/Activity'
EXIT_SAPLIQS0_010 Function Codes in Menu 'Goto/Notification' in Notification Processing
EXIT_SAPLIQS0_011 Supply Function Codes with Text/ Deactivate Codes: 'Goto/Notification'
EXIT_SAPLIQS0_012 Function Codes in 'Goto/Cause' Menu in Notification Processing
EXIT_SAPLIQS0_013 Supply Function Codes with Text/ Deactivate Codes: 'Goto/Cause'
EXIT_SAPLIQS0_014 Function Codes in Menu 'Goto/Item' in Notification Processing
EXIT_SAPLIQS0_015 Supply Function Codes with Text/Deactivate Codes: 'Goto/Item'
EXIT_SAPLIQS0_016 Function Module for Deactivating Notification Function Codes
EXIT_SAPLIQS0_017 Default Values when Adding PM/CS Notification
EXIT_SAPLIQS0_018 Check Whether a Change of Notification Type is Allowed
EXIT_SAPLIQS0_019 Influence Data Transfer for New Notification Type
EXIT_SAPLIQS0_020 User Exit 'Check Authorization for Status Change'

IMPORTING Parameters details for IQS0_RFC_SD_DOC_PARTNER_READ

I_PARVW - Partner role, e-g, WE = Ship-to party

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

I_POSNR - Position Number, 0 = Kopf

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

I_VBELN - Sales document number

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

EXPORTING Parameters details for IQS0_RFC_SD_DOC_PARTNER_READ

E_VBPA - Sales Document: Partner

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

E_VBADR - Adress workarea

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

EXCEPTIONS details

NOT_FOUND - It was not a partner with the role found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IQS0_RFC_SD_DOC_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_e_vbpa  TYPE VBPA, "   
lv_i_parvw  TYPE VBPA-PARVW, "   
lv_not_found  TYPE VBPA, "   
lv_e_vbadr  TYPE VBADR, "   
lv_i_posnr  TYPE VBUP-POSNR, "   
lv_i_vbeln  TYPE VBUK-VBELN. "   

  CALL FUNCTION 'IQS0_RFC_SD_DOC_PARTNER_READ'  "Reading a partner of an Vertriebsbelegspositon with RFC
    EXPORTING
         I_PARVW = lv_i_parvw
         I_POSNR = lv_i_posnr
         I_VBELN = lv_i_vbeln
    IMPORTING
         E_VBPA = lv_e_vbpa
         E_VBADR = lv_e_vbadr
    EXCEPTIONS
        NOT_FOUND = 1
. " IQS0_RFC_SD_DOC_PARTNER_READ




ABAP code using 7.40 inline data declarations to call FM IQS0_RFC_SD_DOC_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 PARVW FROM VBPA INTO @DATA(ld_i_parvw).
 
 
 
"SELECT single POSNR FROM VBUP INTO @DATA(ld_i_posnr).
 
"SELECT single VBELN FROM VBUK INTO @DATA(ld_i_vbeln).
 


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!