SAP OBJECT_CHECK_TMSTRIAL Function Module for NOTRANSL: TMS-API: Prüf-/Lesenbaustein für DVS

Search SAP Function Modules

OBJECT_CHECK_TMSTRIAL is a standard object check tmstrial 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: TMS-API: Prüf-/Lesenbaustein für DVS 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 tmstrial FM, simply by entering the name OBJECT_CHECK_TMSTRIAL into the relevant SAP transaction such as SE37 or SE38.

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

Function OBJECT_CHECK_TMSTRIAL 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_TMSTRIAL'"NOTRANSL: TMS-API: Prüf-/Lesenbaustein für DVS
  EXPORTING
*  CALLED_FROM = 1 "
*  LANGUAGE = SY-LANGU "SAP System, Current Language
*  LOCK = ' ' "
*  SINGLE = ' ' "
*  DATE_OF_CHANGE = SY-DATUM "Date and Time, Current (Application Server) Date
*  I_AUTH_CHK =  "Checkbox

 IMPORTING
   FAULT_TEXT =  "Error text for output in classification
   MEINS =  "Unit of Measure
   MESSAGE_TYPE =  "Message type E,W,I or S
   NO_AUTH =  "No authorization for object
   DISTRIBUTION_LOCK =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

TABLES
   OTAB =  "Classification

EXCEPTIONS
   FOREIGN_LOCK = 1    OBJECT_NOT_FOUND = 2    SYSTEM_FAILURE = 3 

.

IMPORTING Parameters details for OBJECT_CHECK_TMSTRIAL

CALLED_FROM -

Data type:
Default: 1
Optional: No
Call by Reference: Yes

LANGUAGE - SAP System, Current Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: No
Call by Reference: Yes

LOCK -

Data type:
Default: ' '
Optional: No
Call by Reference: Yes

SINGLE -

Data type:
Default: ' '
Optional: No
Call by Reference: Yes

DATE_OF_CHANGE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Default: SY-DATUM
Optional: No
Call by Reference: Yes

I_AUTH_CHK - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OBJECT_CHECK_TMSTRIAL

FAULT_TEXT - Error text for output in classification

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)

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)

DISTRIBUTION_LOCK - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

TABLES Parameters details for OBJECT_CHECK_TMSTRIAL

OTAB - Classification

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

EXCEPTIONS details

FOREIGN_LOCK -

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

OBJECT_NOT_FOUND -

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

SYSTEM_FAILURE -

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

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

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