SAP OBJECT_CHECK_PLKO Function Module for NOTRANSL: Planprüfung für Klassifizierung

Search SAP Function Modules

OBJECT_CHECK_PLKO is a standard object check plko 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: Planprüfung für Klassifizierung 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 object check plko FM, simply by entering the name OBJECT_CHECK_PLKO into the relevant SAP transaction such as SE37 or SE38.

Function Group: CP99
Program Name: SAPLCP99
Main Program: SAPLCP99
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OBJECT_CHECK_PLKO 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 'OBJECT_CHECK_PLKO'"NOTRANSL: Planprüfung für Klassifizierung
  EXPORTING
*  CALLED_FROM = 1 "1=of task list 2=of class
*  LANGUAGE = SY-LANGU "Read lang. for short texts (request)
*  LOCK = ' ' "Lock Object
*  SINGLE = ' ' "Individual access
*  DATE_OF_CHANGE =  "Key Date
*  I_AUTH_CHK = ' ' "

 IMPORTING
   FAULT_TEXT =  "Text for error message
   MESSAGE_TYPE =  "Type of error message
   NO_AUTH =  "no authorization
   MEINS =  "Unit of Measure

TABLES
   OTAB =  "List of the documents

EXCEPTIONS
   FOREIGN_LOCK = 1    OBJECT_NOT_FOUND = 2    SYSTEM_FAILURE = 3 

.

IMPORTING Parameters details for OBJECT_CHECK_PLKO

CALLED_FROM - 1=of task list 2=of class

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

LANGUAGE - Read lang. for short texts (request)

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCK - Lock Object

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

SINGLE - Individual access

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

DATE_OF_CHANGE - Key Date

Data type: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_AUTH_CHK -

Data type: RMCLF-KREUZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OBJECT_CHECK_PLKO

FAULT_TEXT - Text for error message

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

MESSAGE_TYPE - Type of error message

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

NO_AUTH - no authorization

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

MEINS - Unit of Measure

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

TABLES Parameters details for OBJECT_CHECK_PLKO

OTAB - List of the documents

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

EXCEPTIONS details

FOREIGN_LOCK - Lock logic exception handed through

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

OBJECT_NOT_FOUND - Object not found

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

SYSTEM_FAILURE - Lock logic exception handed through

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

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

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