SAP OBJECT_CHECK_MCHA Function Module for Read batches for classification

Search SAP Function Modules

OBJECT_CHECK_MCHA is a standard object check mcha SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read batches for classification 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 mcha FM, simply by entering the name OBJECT_CHECK_MCHA into the relevant SAP transaction such as SE37 or SE38.

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

Function OBJECT_CHECK_MCHA 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_MCHA'"Read batches for classification
  EXPORTING
*  CALLED_FROM = 1 "1=document 2=class
*  LANGUAGE = SY-LANGU "Language key
*  LOCK = ' ' "Indicator: X = master record locked
*  SINGLE = ' ' "Individual access via CL20/CL21
*  DATE_OF_CHANGE =  "Change date
*  I_AUTH_CHK = ' ' "

 IMPORTING
   FAULT_TEXT =  "Error text for output in classification
   MESSAGE_TYPE =  "Message type E,W,I, or S
   NO_AUTH =  "No authorization for object
   MEINS =  "Unit of measure

TABLES
   OTAB =  "Table of batches

EXCEPTIONS
   FOREIGN_LOCK = 1    OBJECT_NOT_FOUND = 2    SYSTEM_FAILURE = 3 

.

IMPORTING Parameters details for OBJECT_CHECK_MCHA

CALLED_FROM - 1=document 2=class

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

LANGUAGE - Language key

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

LOCK - Indicator: X = master record locked

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

SINGLE - Individual access via CL20/CL21

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

DATE_OF_CHANGE - Change date

Data type: RMCLF-DATUV1
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_MCHA

FAULT_TEXT - Error text for output in classification

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

MESSAGE_TYPE - Message type E,W,I, or S

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

NO_AUTH - No authorization for object

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_MCHA

OTAB - Table of batches

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

EXCEPTIONS details

FOREIGN_LOCK - Record locked by other user

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

OBJECT_NOT_FOUND - Batch not found

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

SYSTEM_FAILURE - System lock error

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

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

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