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

Function FKK_ORDER_POST 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_ORDER_POST'".
EXPORTING
I_CONTROL = "Process-Control Requests
I_FKKORDER = "Requests: Header Data
* I_FKKORDER_OLD = "
* I_XREQEF = ' ' "
IMPORTING
E_ORDNR = "Request Number
E_FIKEY = "
TABLES
T_FKKORDERPOS = "Requests: Items
T_FKKORDERDUE = "Requests: Due Dates
* T_FKKORDERLOCKS = "Requests: Processing Locks
* T_FKKORDERPOS_OLD = "
* T_FKKORDERDUE_OLD = "
* T_FKKORDERLOCKS_OLD = "Requests: Processing Locks
* T_OPBEL = "Requests: Generated Documents
* RETURN = "Return Parameter(s)
IMPORTING Parameters details for FKK_ORDER_POST
I_CONTROL - Process-Control Requests
Data type: FKKORDERCONTROLOptional: No
Call by Reference: Yes
I_FKKORDER - Requests: Header Data
Data type: FKKORDEROptional: No
Call by Reference: Yes
I_FKKORDER_OLD -
Data type: FKKORDEROptional: Yes
Call by Reference: Yes
I_XREQEF -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_ORDER_POST
E_ORDNR - Request Number
Data type: FKKORDER-ORDNROptional: No
Call by Reference: Yes
E_FIKEY -
Data type: FIKEY_KKOptional: No
Call by Reference: Yes
TABLES Parameters details for FKK_ORDER_POST
T_FKKORDERPOS - Requests: Items
Data type: FKKORDERPOSOptional: No
Call by Reference: Yes
T_FKKORDERDUE - Requests: Due Dates
Data type: FKKORDERDUEOptional: No
Call by Reference: Yes
T_FKKORDERLOCKS - Requests: Processing Locks
Data type: DFKKORDERLOCKSOptional: Yes
Call by Reference: Yes
T_FKKORDERPOS_OLD -
Data type: FKKORDERPOSOptional: Yes
Call by Reference: Yes
T_FKKORDERDUE_OLD -
Data type: FKKORDERDUEOptional: Yes
Call by Reference: Yes
T_FKKORDERLOCKS_OLD - Requests: Processing Locks
Data type: DFKKORDERLOCKSOptional: Yes
Call by Reference: Yes
T_OPBEL - Requests: Generated Documents
Data type: FKKORDEROPBELOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_ORDER_POST 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_e_ordnr | TYPE FKKORDER-ORDNR, " | |||
| lv_i_control | TYPE FKKORDERCONTROL, " | |||
| lt_t_fkkorderpos | TYPE STANDARD TABLE OF FKKORDERPOS, " | |||
| lv_e_fikey | TYPE FIKEY_KK, " | |||
| lv_i_fkkorder | TYPE FKKORDER, " | |||
| lt_t_fkkorderdue | TYPE STANDARD TABLE OF FKKORDERDUE, " | |||
| lv_i_fkkorder_old | TYPE FKKORDER, " | |||
| lt_t_fkkorderlocks | TYPE STANDARD TABLE OF DFKKORDERLOCKS, " | |||
| lv_i_xreqef | TYPE XFELD, " SPACE | |||
| lt_t_fkkorderpos_old | TYPE STANDARD TABLE OF FKKORDERPOS, " | |||
| lt_t_fkkorderdue_old | TYPE STANDARD TABLE OF FKKORDERDUE, " | |||
| lt_t_fkkorderlocks_old | TYPE STANDARD TABLE OF DFKKORDERLOCKS, " | |||
| lt_t_opbel | TYPE STANDARD TABLE OF FKKORDEROPBEL, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'FKK_ORDER_POST' " |
| EXPORTING | ||
| I_CONTROL | = lv_i_control | |
| I_FKKORDER | = lv_i_fkkorder | |
| I_FKKORDER_OLD | = lv_i_fkkorder_old | |
| I_XREQEF | = lv_i_xreqef | |
| IMPORTING | ||
| E_ORDNR | = lv_e_ordnr | |
| E_FIKEY | = lv_e_fikey | |
| TABLES | ||
| T_FKKORDERPOS | = lt_t_fkkorderpos | |
| T_FKKORDERDUE | = lt_t_fkkorderdue | |
| T_FKKORDERLOCKS | = lt_t_fkkorderlocks | |
| T_FKKORDERPOS_OLD | = lt_t_fkkorderpos_old | |
| T_FKKORDERDUE_OLD | = lt_t_fkkorderdue_old | |
| T_FKKORDERLOCKS_OLD | = lt_t_fkkorderlocks_old | |
| T_OPBEL | = lt_t_opbel | |
| RETURN | = lt_return | |
| . " FKK_ORDER_POST | ||
ABAP code using 7.40 inline data declarations to call FM FKK_ORDER_POST
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 ORDNR FROM FKKORDER INTO @DATA(ld_e_ordnr). | ||||
| DATA(ld_i_xreqef) | = ' '. | |||
Search for further information about these or an SAP related objects