SAP CHECK_OPER_OK Function Module for NOTRANSL: Checken ob Vorgang ok für Subsystem

Search SAP Function Modules

CHECK_OPER_OK is a standard check oper ok SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Checken ob Vorgang ok für Subsystem 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 oper ok FM, simply by entering the name CHECK_OPER_OK into the relevant SAP transaction such as SE37 or SE38.

Function Group: PPC0
Program Name: SAPLPPC0
Main Program: SAPLPPC0
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_OPER_OK 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_OPER_OK'"NOTRANSL: Checken ob Vorgang ok für Subsystem
  EXPORTING
   AUFNR =  "Order number
   AUFTYP =  "

EXCEPTIONS
   ORDER_LOCKED = 1    ORDER_COMPLETED = 2    ORDER_NOT_FOUND = 3    WRONG_ORDERTYP = 4    ORDER_HEAD_CONFIRMED = 5    ORDER_NOT_FOR_PDC = 6 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLPPC0_101 Check Additional Conditions for PDC Download of Operation Data

IMPORTING Parameters details for CHECK_OPER_OK

AUFNR - Order number

Data type: AP_ORD_PRE-AUFNR
Optional: No
Call by Reference: No ( called with pass by value option)

AUFTYP -

Data type: AUFK-AUTYP
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ORDER_LOCKED - RS Header Blocked

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ORDER_COMPLETED - Request Completed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ORDER_NOT_FOUND - Order for operation not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

WRONG_ORDERTYP -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ORDER_HEAD_CONFIRMED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ORDER_NOT_FOR_PDC -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CHECK_OPER_OK 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.

ABAP code using 7.40 inline data declarations to call FM CHECK_OPER_OK

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