SAP CHECK_INFO_APAR_APPL Function Module for PTF-check on local application server
CHECK_INFO_APAR_APPL is a standard check info apar appl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PTF-check on local application server 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 check info apar appl FM, simply by entering the name CHECK_INFO_APAR_APPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU4
Program Name: SAPLSTU4
Main Program: SAPLSTU4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CHECK_INFO_APAR_APPL 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 'CHECK_INFO_APAR_APPL'"PTF-check on local application server.
EXPORTING
* PATHNAME = INFOAPAR_PATH "Pathname of INFO-APAR file in IFS
TABLES
AS4_PTF_STATUS = "OS/400: PTF-Status
EXCEPTIONS
WRONG_INFOAPAR = 1 API_ERROR = 2
IMPORTING Parameters details for CHECK_INFO_APAR_APPL
PATHNAME - Pathname of INFO-APAR file in IFS
Data type: APARPATHDefault: INFOAPAR_PATH
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CHECK_INFO_APAR_APPL
AS4_PTF_STATUS - OS/400: PTF-Status
Data type: AS4ALVPTFOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_INFOAPAR - INFO-APAR file is not valid for this OS-release
Data type:Optional: No
Call by Reference: Yes
API_ERROR - Internal error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CHECK_INFO_APAR_APPL 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_pathname | TYPE APARPATH, " INFOAPAR_PATH | |||
| lt_as4_ptf_status | TYPE STANDARD TABLE OF AS4ALVPTF, " | |||
| lv_wrong_infoapar | TYPE AS4ALVPTF, " | |||
| lv_api_error | TYPE AS4ALVPTF. " |
|   CALL FUNCTION 'CHECK_INFO_APAR_APPL' "PTF-check on local application server |
| EXPORTING | ||
| PATHNAME | = lv_pathname | |
| TABLES | ||
| AS4_PTF_STATUS | = lt_as4_ptf_status | |
| EXCEPTIONS | ||
| WRONG_INFOAPAR = 1 | ||
| API_ERROR = 2 | ||
| . " CHECK_INFO_APAR_APPL | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_INFO_APAR_APPL
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.| DATA(ld_pathname) | = INFOAPAR_PATH. | |||
Search for further information about these or an SAP related objects