SAP ABI_IDOC_DISPATCH Function Module for Dispatch IDocs received from auto-ID infrastructure
ABI_IDOC_DISPATCH is a standard abi idoc dispatch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dispatch IDocs received from auto-ID infrastructure 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 abi idoc dispatch FM, simply by entering the name ABI_IDOC_DISPATCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABI_MSG_HANDLER
Program Name: SAPLABI_MSG_HANDLER
Main Program: SAPLABI_MSG_HANDLER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ABI_IDOC_DISPATCH 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 'ABI_IDOC_DISPATCH'"Dispatch IDocs received from auto-ID infrastructure.
EXPORTING
INPUT_METHOD = "Inbound method for the IDoc inbound function module
MASS_PROCESSING = "Flag: Mass processing
IMPORTING
WORKFLOW_RESULT = "Final value of method
APPLICATION_VARIABLE = "Variable to be used by application as required
IN_UPDATE_TASK = "Flag: Application has triggered update task
CALL_TRANSACTION_DONE = "Flag: Application has actually performed call transaction
TABLES
IDOC_CONTRL = "Control record (IDoc)
IDOC_DATA = "Data record (IDoc)
IDOC_STATUS = "ALE IDoc status (subset of all IDoc status fields)
RETURN_VARIABLES = "Assignment of IDoc or document no. to method parameter
SERIALIZATION_INFO = "Serialization objects for one/several IDocs
* ET_IDOCS_SENT = "Control record (IDoc)
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
IDoc processing FM
This FM is the Processing Function module for IDoc: AIDOP01AIDOP01 - Auto-ID Operational IDoc
AIDOP02 - AII Operational Idoc
AIDRQ01 - Auto-ID Request IDoc
IMPORTING Parameters details for ABI_IDOC_DISPATCH
INPUT_METHOD - Inbound method for the IDoc inbound function module
Data type: BDWFAP_PAR-INPUTMETHDOptional: No
Call by Reference: Yes
MASS_PROCESSING - Flag: Mass processing
Data type: BDWFAP_PAR-MASS_PROCOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ABI_IDOC_DISPATCH
WORKFLOW_RESULT - Final value of method
Data type: BDWFAP_PAR-RESULTOptional: No
Call by Reference: Yes
APPLICATION_VARIABLE - Variable to be used by application as required
Data type: BDWFAP_PAR-APPL_VAROptional: No
Call by Reference: Yes
IN_UPDATE_TASK - Flag: Application has triggered update task
Data type: BDWFAP_PAR-UPDATETASKOptional: No
Call by Reference: Yes
CALL_TRANSACTION_DONE - Flag: Application has actually performed call transaction
Data type: BDWFAP_PAR-CALLTRANSOptional: No
Call by Reference: Yes
TABLES Parameters details for ABI_IDOC_DISPATCH
IDOC_CONTRL - Control record (IDoc)
Data type: EDIDCOptional: No
Call by Reference: Yes
IDOC_DATA - Data record (IDoc)
Data type: EDIDDOptional: No
Call by Reference: Yes
IDOC_STATUS - ALE IDoc status (subset of all IDoc status fields)
Data type: BDIDOCSTATOptional: No
Call by Reference: Yes
RETURN_VARIABLES - Assignment of IDoc or document no. to method parameter
Data type: BDWFRETVAROptional: No
Call by Reference: Yes
SERIALIZATION_INFO - Serialization objects for one/several IDocs
Data type: BDI_SEROptional: No
Call by Reference: Yes
ET_IDOCS_SENT - Control record (IDoc)
Data type: EDIDCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_FUNCTION_CALLED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ABI_IDOC_DISPATCH 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, " | |||
lt_et_idocs_sent | TYPE STANDARD TABLE OF EDIDC. " |
  CALL FUNCTION 'ABI_IDOC_DISPATCH' "Dispatch IDocs received from auto-ID infrastructure |
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 | |
ET_IDOCS_SENT | = lt_et_idocs_sent | |
EXCEPTIONS | ||
WRONG_FUNCTION_CALLED = 1 | ||
. " ABI_IDOC_DISPATCH |
ABAP code using 7.40 inline data declarations to call FM ABI_IDOC_DISPATCH
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