J_3G_PARTNER_ERMITTELN SAP Function module - Determine Sender and/or Recipient in ETM Using SD Document

J_3G_PARTNER_ERMITTELN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name J_3G_PARTNER_ERMITTELN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: J3GE
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM J_3G_PARTNER_ERMITTELN - J 3G PARTNER ERMITTELN

CALL FUNCTION 'J_3G_PARTNER_ERMITTELN' "Determine Sender and/or Recipient in ETM Using SD Document
  EXPORTING
    belnr =                     " vbap-vbeln
*   posnr =                     " vbap-posnr
    parvw =                     " vbpa-parvw
*   i_protocol =                "
  IMPORTING
    kunnr =                     " kna1-kunnr
  EXCEPTIONS
    NO_PARTNER_FOUND = 1        "
    .  "  J_3G_PARTNER_ERMITTELN

ABAP code example for Function Module J_3G_PARTNER_ERMITTELN

The ABAP code below is a full code listing to execute function module J_3G_PARTNER_ERMITTELN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_kunnr  
 
 TYPE KNA1-KUNNR
.

 

SELECT single VBELN 
  FROM VBAP 
  INTO @DATA(ld_belnr).

 

SELECT single POSNR 
  FROM VBAP 
  INTO @DATA(ld_posnr).

 

SELECT single PARVW 
  FROM VBPA 
  INTO @DATA(ld_parvw).


DATA(ld_i_protocol) = 'some text here'.
.

CALL FUNCTION 'J_3G_PARTNER_ERMITTELN'
  EXPORTING
    belnr =                      ld_belnr
*   posnr =                      ld_posnr
    parvw =                      ld_parvw
*   i_protocol =                 ld_i_protocol
  IMPORTING
    kunnr =                      ld_kunnr
  EXCEPTIONS
    NO_PARTNER_FOUND =           1
    .  "  J_3G_PARTNER_ERMITTELN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_kunnr
 
 TYPE KNA1-KUNNR ,
ld_belnr
 
 TYPE VBAP-VBELN ,
ld_posnr
 
 TYPE VBAP-POSNR ,
ld_parvw
 
 TYPE VBPA-PARVW ,
ld_i_protocol
 
 TYPE STRING .



SELECT single VBELN 
  FROM VBAP 
  INTO ld_belnr.


SELECT single POSNR 
  FROM VBAP 
  INTO ld_posnr.


SELECT single PARVW 
  FROM VBPA 
  INTO ld_parvw.

ld_i_protocol = 'some text here'.