SAP APPLICATION_IDOC_POST_IMMEDIAT Function Module for Inbound: Send application IDoc to the application immediately
APPLICATION_IDOC_POST_IMMEDIAT is a standard application idoc post immediat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Inbound: Send application IDoc to the application immediately 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 application idoc post immediat FM, simply by entering the name APPLICATION_IDOC_POST_IMMEDIAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BD12
Program Name: SAPLBD12
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function APPLICATION_IDOC_POST_IMMEDIAT 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 'APPLICATION_IDOC_POST_IMMEDIAT'"Inbound: Send application IDoc to the application immediately.
EXPORTING
* ERROR_FLAG = C_FALSE "Flag: called from error handling
* INBOUND_PARTNER_PROFILE = "Partner profile for inbound processing
* DO_COMMIT = C_TRUE "Flag: Commit Work stopped in program
TABLES
IDOC_CONTROL = "IDoc control records
IDOC_DATA = "IDoc data segments
EXCEPTIONS
ERROR_OPENING_IDOC = 1 ERROR_WRITING_IDOC_STATUS = 2 NO_IDOCS = 3
IMPORTING Parameters details for APPLICATION_IDOC_POST_IMMEDIAT
ERROR_FLAG - Flag: called from error handling
Data type: BDAPPLIDOC-POST_IMMEDDefault: C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
INBOUND_PARTNER_PROFILE - Partner profile for inbound processing
Data type: EDP21Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_COMMIT - Flag: Commit Work stopped in program
Data type: EDIGENERAL-DO_COMMITDefault: C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for APPLICATION_IDOC_POST_IMMEDIAT
IDOC_CONTROL - IDoc control records
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
IDOC_DATA - IDoc data segments
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OPENING_IDOC - Unable to open IDoc
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_WRITING_IDOC_STATUS - Unable to write IDoc status
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_IDOCS - No IDocs with correct status in packet
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for APPLICATION_IDOC_POST_IMMEDIAT 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_error_flag | TYPE BDAPPLIDOC-POST_IMMED, " C_FALSE | |||
| lt_idoc_control | TYPE STANDARD TABLE OF EDIDC, " | |||
| lv_error_opening_idoc | TYPE EDIDC, " | |||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_inbound_partner_profile | TYPE EDP21, " | |||
| lv_error_writing_idoc_status | TYPE EDP21, " | |||
| lv_no_idocs | TYPE EDP21, " | |||
| lv_do_commit | TYPE EDIGENERAL-DO_COMMIT. " C_TRUE |
|   CALL FUNCTION 'APPLICATION_IDOC_POST_IMMEDIAT' "Inbound: Send application IDoc to the application immediately |
| EXPORTING | ||
| ERROR_FLAG | = lv_error_flag | |
| INBOUND_PARTNER_PROFILE | = lv_inbound_partner_profile | |
| DO_COMMIT | = lv_do_commit | |
| TABLES | ||
| IDOC_CONTROL | = lt_idoc_control | |
| IDOC_DATA | = lt_idoc_data | |
| EXCEPTIONS | ||
| ERROR_OPENING_IDOC = 1 | ||
| ERROR_WRITING_IDOC_STATUS = 2 | ||
| NO_IDOCS = 3 | ||
| . " APPLICATION_IDOC_POST_IMMEDIAT | ||
ABAP code using 7.40 inline data declarations to call FM APPLICATION_IDOC_POST_IMMEDIAT
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 POST_IMMED FROM BDAPPLIDOC INTO @DATA(ld_error_flag). | ||||
| DATA(ld_error_flag) | = C_FALSE. | |||
| "SELECT single DO_COMMIT FROM EDIGENERAL INTO @DATA(ld_do_commit). | ||||
| DATA(ld_do_commit) | = C_TRUE. | |||
Search for further information about these or an SAP related objects