SAP IDOC_INPUT_EVENT Function Module for









IDOC_INPUT_EVENT is a standard idoc input event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 idoc input event FM, simply by entering the name IDOC_INPUT_EVENT into the relevant SAP transaction such as SE37 or SE38.

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



Function IDOC_INPUT_EVENT 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 'IDOC_INPUT_EVENT'"
EXPORTING
DOCNUM = "IDoc Number
MESTYP = "IDoc Output Category
APPLICATION_VARIABLE = "
* IN_UPDATE_TASK = ' ' "
* ONLY_TRIGGER_APPL_EVENT = ' ' "
* EXCEPTION = 0 "

TABLES
RETURN_VARIABLES = "
IDOC_STATE = "

EXCEPTIONS
BAD_IDOC = 1
.



IMPORTING Parameters details for IDOC_INPUT_EVENT

DOCNUM - IDoc Number

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

MESTYP - IDoc Output Category

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

APPLICATION_VARIABLE -

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

IN_UPDATE_TASK -

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

ONLY_TRIGGER_APPL_EVENT -

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

EXCEPTION -

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

TABLES Parameters details for IDOC_INPUT_EVENT

RETURN_VARIABLES -

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

IDOC_STATE -

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

EXCEPTIONS details

BAD_IDOC -

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

Copy and paste ABAP code example for IDOC_INPUT_EVENT 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_docnum  TYPE EDIDC-DOCNUM, "   
lv_bad_idoc  TYPE EDIDC, "   
lt_return_variables  TYPE STANDARD TABLE OF BDWFRETVAR, "   
lv_mestyp  TYPE EDIDC-MESTYP, "   
lt_idoc_state  TYPE STANDARD TABLE OF BDIDOCSTAT, "   
lv_application_variable  TYPE BDWF_PARAM-APPL_VAR, "   
lv_in_update_task  TYPE BDWFAP_PAR-UPDATETASK, "   ' '
lv_only_trigger_appl_event  TYPE CHAR1, "   ' '
lv_exception  TYPE BDWF_PARAM-EXCEPTION. "   0

  CALL FUNCTION 'IDOC_INPUT_EVENT'  "
    EXPORTING
         DOCNUM = lv_docnum
         MESTYP = lv_mestyp
         APPLICATION_VARIABLE = lv_application_variable
         IN_UPDATE_TASK = lv_in_update_task
         ONLY_TRIGGER_APPL_EVENT = lv_only_trigger_appl_event
         EXCEPTION = lv_exception
    TABLES
         RETURN_VARIABLES = lt_return_variables
         IDOC_STATE = lt_idoc_state
    EXCEPTIONS
        BAD_IDOC = 1
. " IDOC_INPUT_EVENT




ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_EVENT

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 DOCNUM FROM EDIDC INTO @DATA(ld_docnum).
 
 
 
"SELECT single MESTYP FROM EDIDC INTO @DATA(ld_mestyp).
 
 
"SELECT single APPL_VAR FROM BDWF_PARAM INTO @DATA(ld_application_variable).
 
"SELECT single UPDATETASK FROM BDWFAP_PAR INTO @DATA(ld_in_update_task).
DATA(ld_in_update_task) = ' '.
 
DATA(ld_only_trigger_appl_event) = ' '.
 
"SELECT single EXCEPTION FROM BDWF_PARAM INTO @DATA(ld_exception).
 


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!