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

Function FP_IS_OTF 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 'FP_IS_OTF'".
EXPORTING
I_OTF = "Smart Forms: Table OTF
IMPORTING
IS_OTF = "Boolean Value (True or False)
IS_PDF = "Boolean Value (True or False)
EXCEPTIONS
EMPTY = 1 UNKNOWN = 2
IMPORTING Parameters details for FP_IS_OTF
I_OTF - Smart Forms: Table OTF
Data type: TSFOTFOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FP_IS_OTF
IS_OTF - Boolean Value (True or False)
Data type: FPBOOLOptional: No
Call by Reference: Yes
IS_PDF - Boolean Value (True or False)
Data type: FPBOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
EMPTY - No data
Data type:Optional: No
Call by Reference: Yes
UNKNOWN - Unknown Format
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FP_IS_OTF 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_empty | TYPE STRING, " | |||
| lv_i_otf | TYPE TSFOTF, " | |||
| lv_is_otf | TYPE FPBOOL, " | |||
| lv_is_pdf | TYPE FPBOOL, " | |||
| lv_unknown | TYPE FPBOOL. " |
|   CALL FUNCTION 'FP_IS_OTF' " |
| EXPORTING | ||
| I_OTF | = lv_i_otf | |
| IMPORTING | ||
| IS_OTF | = lv_is_otf | |
| IS_PDF | = lv_is_pdf | |
| EXCEPTIONS | ||
| EMPTY = 1 | ||
| UNKNOWN = 2 | ||
| . " FP_IS_OTF | ||
ABAP code using 7.40 inline data declarations to call FM FP_IS_OTF
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