SAP REFXCN_IDOC_STATEMENT Function Module for IDOC Inbound: Statement Data

Search SAP Function Modules

REFXCN_IDOC_STATEMENT is a standard refxcn idoc statement SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IDOC Inbound: Statement 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 refxcn idoc statement FM, simply by entering the name REFXCN_IDOC_STATEMENT into the relevant SAP transaction such as SE37 or SE38.

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

Function REFXCN_IDOC_STATEMENT 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 'REFXCN_IDOC_STATEMENT'"IDOC Inbound: Statement Data
  EXPORTING
   IV_INPUTMETHD =  "Inbound method for the IDoc inbound function module
   IV_MASS_PROC =  "Flag: Mass processing

 IMPORTING
   EV_RESULT =  "Final value of method
   EV_APPL_VAR =  "Variable to be used by application as required
   EV_UPDATETASK =  "Flag: Application has triggered update task
   EV_CALLTRANS =  "Flag: Application has actually performed call transaction

CHANGING
   CT_IDOC_CONTRL =  "Table Type for EDIDC (IDoc Control Record)
   CT_IDOC_DATA =  "Table Type for EDIDD (IDoc Data Records)
   CT_IDOC_STATUS =  "Table Type for BDIDOCSTAT
   CT_IDOC_RETURN =  "Table Type for BDWFRETVAR
   CT_SERIALIZATION =  "Table Type for BDI_SER

.

IMPORTING Parameters details for REFXCN_IDOC_STATEMENT

IV_INPUTMETHD - Inbound method for the IDoc inbound function module

Data type: BDWFAP_PAR-INPUTMETHD
Optional: No
Call by Reference: Yes

IV_MASS_PROC - Flag: Mass processing

Data type: BDWFAP_PAR-MASS_PROC
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for REFXCN_IDOC_STATEMENT

EV_RESULT - Final value of method

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

EV_APPL_VAR - Variable to be used by application as required

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

EV_UPDATETASK - Flag: Application has triggered update task

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

EV_CALLTRANS - Flag: Application has actually performed call transaction

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

CHANGING Parameters details for REFXCN_IDOC_STATEMENT

CT_IDOC_CONTRL - Table Type for EDIDC (IDoc Control Record)

Data type: EDIDC_TT
Optional: No
Call by Reference: Yes

CT_IDOC_DATA - Table Type for EDIDD (IDoc Data Records)

Data type: EDIDD_TT
Optional: No
Call by Reference: Yes

CT_IDOC_STATUS - Table Type for BDIDOCSTAT

Data type: BDTIDOCSTA
Optional: No
Call by Reference: Yes

CT_IDOC_RETURN - Table Type for BDWFRETVAR

Data type: BDTWFRETVA
Optional: No
Call by Reference: Yes

CT_SERIALIZATION - Table Type for BDI_SER

Data type: BDTI_SER
Optional: No
Call by Reference: Yes

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

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