SAP FKK_OITR_ENQUEUE_SET Function Module for
FKK_OITR_ENQUEUE_SET is a standard fkk oitr enqueue set 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 fkk oitr enqueue set FM, simply by entering the name FKK_OITR_ENQUEUE_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_OUTBOUND_INTERFACE
Program Name: SAPLFKK_OUTBOUND_INTERFACE
Main Program: SAPLFKK_OUTBOUND_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_OITR_ENQUEUE_SET 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 'FKK_OITR_ENQUEUE_SET'".
EXPORTING
* I_BASICS = "
TABLES
T_RECEIVER = "
* T_BUKRS = "
EXCEPTIONS
FOREIGN_LOCK = 1
IMPORTING Parameters details for FKK_OITR_ENQUEUE_SET
I_BASICS -
Data type: FKK_MAD_BASICSOptional: Yes
Call by Reference: Yes
TABLES Parameters details for FKK_OITR_ENQUEUE_SET
T_RECEIVER -
Data type: FKK_MAD_OITROptional: No
Call by Reference: Yes
T_BUKRS -
Data type: IBUKRSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_OITR_ENQUEUE_SET 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_i_basics | TYPE FKK_MAD_BASICS, " | |||
| lt_t_receiver | TYPE STANDARD TABLE OF FKK_MAD_OITR, " | |||
| lv_foreign_lock | TYPE FKK_MAD_OITR, " | |||
| lt_t_bukrs | TYPE STANDARD TABLE OF IBUKRS. " |
|   CALL FUNCTION 'FKK_OITR_ENQUEUE_SET' " |
| EXPORTING | ||
| I_BASICS | = lv_i_basics | |
| TABLES | ||
| T_RECEIVER | = lt_t_receiver | |
| T_BUKRS | = lt_t_bukrs | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| . " FKK_OITR_ENQUEUE_SET | ||
ABAP code using 7.40 inline data declarations to call FM FKK_OITR_ENQUEUE_SET
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