SAP IDOC_INPUT_IORUPD Function Module for IDOC IORUPD01 inbound function module: Order Status Update









IDOC_INPUT_IORUPD is a standard idoc input iorupd 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 IORUPD01 inbound function module: Order Status Update 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 idoc input iorupd FM, simply by entering the name IDOC_INPUT_IORUPD into the relevant SAP transaction such as SE37 or SE38.

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



Function IDOC_INPUT_IORUPD 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_IORUPD'"IDOC IORUPD01 inbound function module: Order Status Update
EXPORTING
INPUT_METHOD = "Method: background/foreground processing
MASS_PROCESSING = "Flag: multiple receipt (otherwise single receipt

IMPORTING
WORKFLOW_RESULT = "Result of method for workflow (return code)
APPLICATION_VARIABLE = "Application variable
IN_UPDATE_TASK = "Flag: processing of IDOC via update task
CALL_TRANSACTION_DONE = "Flag: processing via Call transaction

TABLES
IDOC_CONTRL = "IDOC management records
IDOC_DATA = "IDOC data records
IDOC_STATUS = "IDOC status records
RETURN_VARIABLES = "Result variables with values for workflow
SERIALIZATION_INFO = "

EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
.


IDoc processing FM

This FM is the Processing Function module for IDoc: IORUPD01
IORUPD01 - Order status update IDoc

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_SAPLISMPM_UPD_IDOCS_001 Validate if an order can be completed
EXIT_SAPLISMPM_UPD_IDOCS_002 Validate if a notification or notification task can be completed
EXIT_SAPLISMPM_UPD_IDOCS_003 Validate if order or operation can be updated

IMPORTING Parameters details for IDOC_INPUT_IORUPD

INPUT_METHOD - Method: background/foreground processing

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

MASS_PROCESSING - Flag: multiple receipt (otherwise single receipt

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

EXPORTING Parameters details for IDOC_INPUT_IORUPD

WORKFLOW_RESULT - Result of method for workflow (return code)

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

APPLICATION_VARIABLE - Application variable

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

IN_UPDATE_TASK - Flag: processing of IDOC via update task

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

CALL_TRANSACTION_DONE - Flag: processing via Call transaction

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

TABLES Parameters details for IDOC_INPUT_IORUPD

IDOC_CONTRL - IDOC management records

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

IDOC_DATA - IDOC data records

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

IDOC_STATUS - IDOC status records

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

RETURN_VARIABLES - Result variables with values for workflow

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

SERIALIZATION_INFO -

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

EXCEPTIONS details

WRONG_FUNCTION_CALLED - IDOCs cannot be processed

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

Copy and paste ABAP code example for IDOC_INPUT_IORUPD 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:
lt_idoc_contrl  TYPE STANDARD TABLE OF EDIDC, "   
lv_input_method  TYPE BDWFAP_PAR-INPUTMETHD, "   
lv_workflow_result  TYPE BDWFAP_PAR-RESULT, "   
lv_wrong_function_called  TYPE BDWFAP_PAR, "   
lt_idoc_data  TYPE STANDARD TABLE OF EDIDD, "   
lv_mass_processing  TYPE BDWFAP_PAR-MASS_PROC, "   
lv_application_variable  TYPE BDWFAP_PAR-APPL_VAR, "   
lt_idoc_status  TYPE STANDARD TABLE OF BDIDOCSTAT, "   
lv_in_update_task  TYPE BDWFAP_PAR-UPDATETASK, "   
lt_return_variables  TYPE STANDARD TABLE OF BDWFRETVAR, "   
lv_call_transaction_done  TYPE BDWFAP_PAR-CALLTRANS, "   
lt_serialization_info  TYPE STANDARD TABLE OF BDI_SER. "   

  CALL FUNCTION 'IDOC_INPUT_IORUPD'  "IDOC IORUPD01 inbound function module: Order Status Update
    EXPORTING
         INPUT_METHOD = lv_input_method
         MASS_PROCESSING = lv_mass_processing
    IMPORTING
         WORKFLOW_RESULT = lv_workflow_result
         APPLICATION_VARIABLE = lv_application_variable
         IN_UPDATE_TASK = lv_in_update_task
         CALL_TRANSACTION_DONE = lv_call_transaction_done
    TABLES
         IDOC_CONTRL = lt_idoc_contrl
         IDOC_DATA = lt_idoc_data
         IDOC_STATUS = lt_idoc_status
         RETURN_VARIABLES = lt_return_variables
         SERIALIZATION_INFO = lt_serialization_info
    EXCEPTIONS
        WRONG_FUNCTION_CALLED = 1
. " IDOC_INPUT_IORUPD




ABAP code using 7.40 inline data declarations to call FM IDOC_INPUT_IORUPD

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 INPUTMETHD FROM BDWFAP_PAR INTO @DATA(ld_input_method).
 
"SELECT single RESULT FROM BDWFAP_PAR INTO @DATA(ld_workflow_result).
 
 
 
"SELECT single MASS_PROC FROM BDWFAP_PAR INTO @DATA(ld_mass_processing).
 
"SELECT single APPL_VAR FROM BDWFAP_PAR INTO @DATA(ld_application_variable).
 
 
"SELECT single UPDATETASK FROM BDWFAP_PAR INTO @DATA(ld_in_update_task).
 
 
"SELECT single CALLTRANS FROM BDWFAP_PAR INTO @DATA(ld_call_transaction_done).
 
 

See full list of SAP IDocs

See full list of SAP Function Modules



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!