SAP GET_PARTNER_INFO_OUTBOUND Function Module for Gets the partner information - OutBound









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

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



Function GET_PARTNER_INFO_OUTBOUND 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 'GET_PARTNER_INFO_OUTBOUND'"Gets the partner information - OutBound
  EXPORTING
*  RCVPOR =  "Receiver port (SAP System, EDI subsystem)
*  RCVPRT =  "Partner type of receiver
*  RCVPFC =  "Partner function of receiver
*  RCVPRN =  "Partner number of receiver
*  SNDPOR =  "Sender port (SAP System, EDI subsystem)
*  SNDPRT =  "Partner type of sender
*  SNDPFC =  "Partner Function of Sender
*  SNDPRN =  "Partner number of sender

 IMPORTING
   RECIEVER =  "Receiver Name for Spec2000 message header
   SENDER =  "Sender Name for Spec2000 message header

EXCEPTIONS
   NO_LINES_READ = 1
.



IMPORTING Parameters details for GET_PARTNER_INFO_OUTBOUND

RCVPOR - Receiver port (SAP System, EDI subsystem)

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

RCVPRT - Partner type of receiver

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

RCVPFC - Partner function of receiver

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

RCVPRN - Partner number of receiver

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

SNDPOR - Sender port (SAP System, EDI subsystem)

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

SNDPRT - Partner type of sender

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

SNDPFC - Partner Function of Sender

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

SNDPRN - Partner number of sender

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

EXPORTING Parameters details for GET_PARTNER_INFO_OUTBOUND

RECIEVER - Receiver Name for Spec2000 message header

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

SENDER - Sender Name for Spec2000 message header

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

EXCEPTIONS details

NO_LINES_READ - No matching records found in table SPCPRTNRINF

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

Copy and paste ABAP code example for GET_PARTNER_INFO_OUTBOUND 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_rcvpor  TYPE EDIDC-RCVPOR, "   
lv_reciever  TYPE SPCPRTNRINF-RECIEVER, "   
lv_no_lines_read  TYPE SPCPRTNRINF, "   
lv_rcvprt  TYPE EDIDC-RCVPRT, "   
lv_sender  TYPE SPCPRTNRINF-SENDER, "   
lv_rcvpfc  TYPE EDIDC-RCVPFC, "   
lv_rcvprn  TYPE EDIDC-RCVPRN, "   
lv_sndpor  TYPE EDIDC-SNDPOR, "   
lv_sndprt  TYPE EDIDC-SNDPRT, "   
lv_sndpfc  TYPE EDIDC-SNDPFC, "   
lv_sndprn  TYPE EDIDC-SNDPRN. "   

  CALL FUNCTION 'GET_PARTNER_INFO_OUTBOUND'  "Gets the partner information - OutBound
    EXPORTING
         RCVPOR = lv_rcvpor
         RCVPRT = lv_rcvprt
         RCVPFC = lv_rcvpfc
         RCVPRN = lv_rcvprn
         SNDPOR = lv_sndpor
         SNDPRT = lv_sndprt
         SNDPFC = lv_sndpfc
         SNDPRN = lv_sndprn
    IMPORTING
         RECIEVER = lv_reciever
         SENDER = lv_sender
    EXCEPTIONS
        NO_LINES_READ = 1
. " GET_PARTNER_INFO_OUTBOUND




ABAP code using 7.40 inline data declarations to call FM GET_PARTNER_INFO_OUTBOUND

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 RCVPOR FROM EDIDC INTO @DATA(ld_rcvpor).
 
"SELECT single RECIEVER FROM SPCPRTNRINF INTO @DATA(ld_reciever).
 
 
"SELECT single RCVPRT FROM EDIDC INTO @DATA(ld_rcvprt).
 
"SELECT single SENDER FROM SPCPRTNRINF INTO @DATA(ld_sender).
 
"SELECT single RCVPFC FROM EDIDC INTO @DATA(ld_rcvpfc).
 
"SELECT single RCVPRN FROM EDIDC INTO @DATA(ld_rcvprn).
 
"SELECT single SNDPOR FROM EDIDC INTO @DATA(ld_sndpor).
 
"SELECT single SNDPRT FROM EDIDC INTO @DATA(ld_sndprt).
 
"SELECT single SNDPFC FROM EDIDC INTO @DATA(ld_sndpfc).
 
"SELECT single SNDPRN FROM EDIDC INTO @DATA(ld_sndprn).
 


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!