SAP FTR_API_OKCODE Function Module for OK Code Processing - General
FTR_API_OKCODE is a standard ftr api okcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OK Code Processing - General 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 ftr api okcode FM, simply by entering the name FTR_API_OKCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_API
Program Name: SAPLFTR_API
Main Program: SAPLFTR_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FTR_API_OKCODE 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 'FTR_API_OKCODE'"OK Code Processing - General.
EXPORTING
OKCODE = "Function Code That Triggered PAI
TABLES
* RETURN = "Return Parameter(s)
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FTR_API_OKCODE
OKCODE - Function Code That Triggered PAI
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FTR_API_OKCODE
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_API_OKCODE 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 | TYPE STRING, " | |||
| lv_okcode | TYPE SY-UCOMM, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'FTR_API_OKCODE' "OK Code Processing - General |
| EXPORTING | ||
| OKCODE | = lv_okcode | |
| TABLES | ||
| RETURN | = lt_return | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FTR_API_OKCODE | ||
ABAP code using 7.40 inline data declarations to call FM FTR_API_OKCODE
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 UCOMM FROM SY INTO @DATA(ld_okcode). | ||||
Search for further information about these or an SAP related objects