Kontakt

Ansicht
Dokumentation

TR_CHECK_TYPE - Determine whether key can be locked, generate TADIR and TLOCK

TR_CHECK_TYPE - Determine whether key can be locked, generate TADIR and TLOCK

General Material Data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Functions

The function module TR_CHECK_TYPE can also be called outside of the Change and Transport System since the database is not updated.

The function analyses the class type of an E071 entry
(PGMID, OBJECT, OBJ_NAME) for:

  • syntactic correctness
  • transportability
  • existence of a corresponding TADIR entry
    (with corresponding key entry)
  • lockability ('request lock')
    (with corresponding lock key entry)

The analysis covers all object types defined in the Change and Transport System. The parameter PE_RESULT then assigns one of the following class types:
PE_RESULT syntax transport TADIR TLOCK
SPACE - - - -
S X - - -
R X X - -
T X X X -
L X X X X
P system object or illegal name selection

The following is displayed independently of the type class:

  • Client-dependency in parameter WE_CLI_DEP ("X"/" ")
  • Object category in parameter WE_CATEGORY
  • "SYST" = Repository object

  • "CUST" = client-dependent Customizing object

  • "CUSY" = client-independent Customizing Object

  • "APPL" = application object

  • Language-dependency of the object in parameter EV_LANGTYP
  • "I" = object with no significance for language

  • "F" = object without language-dependent components

  • "M" = object partly language-dependent

  • "L" = object consists only of language-dependent components

  • Degree of object language dependency in the parameter EV_LANGTYPA
  • "M" = purely language-dependent object in master language

  • "E" = purely language-dependent object in first level language

  • "L" = purely language-dependent object in second level language

  • A flag indicating whether only entire object can be transported is displayed in the parameter WE_COMPLETE_ONLY ("X"/" ")
  • A flag indicating whether the object (in the productive client) belongs to current settings is displayed in the EV_CURR_SETTING ("X"/" ") parameter

The following is displayed dependent on the type class:

  • Key of the object directory entry in parameter WE_TADIR
  • Structure of the request lock in parameter WE_LOCK_KEY

Special cases of syntax errors in the object name:

  • The parameter PE_NAME_TOO_LONG means: the object type is known, but the object name exceeds the maximum length permissible.
  • EV_NAME_TOO_LONG_FOR_OLD corresponds to PE_NAME_TOO_LONG, however the pre-4.0 rules (length of object names) are used for the check.
  • The parameter EV_NO_OBJECT_NAME indicates that the field WI_E071-obj_name is empty or only consists of a comment.
  • The parameter EV_R3TRTEXT_SYNTAXERROR indicates that an R3TR TEXT object has violated the rules for the formal structure of R3TR TEXT objects.

The following is displayed for table objects (table contents or view contents):

  • Table type
  • "POOL" = pooled table

  • "CLUSTER" = cluster table

  • "TRANSP" = transparent table

  • "VIEW" = database view

  • "INTTAB" = internal table

  • Delivery class of the table in parameter WE_TABLE_CONTFLAG




Parameters

EV_CASE_SENSITIVE
EV_CURR_SETTING
EV_INVALID_LANGUAGE_FIELD
EV_INVALID_PREFIX_SYNTAX
EV_LANGTYP
EV_LANGTYPA
EV_LOGO_OBJ
EV_NAMESPACE
EV_NAME_TOO_LONG_FOR_OLD
EV_NAME_WITH_NONSTANDARD_CHARS
EV_NO_OBJECT_NAME
EV_OBJLEN
EV_PREFIX_NOT_ALLOWED
EV_R3TRTEXT_SYNTAXERROR
IV_TRANSLATE_OBJNAME
PE_NAME_TOO_LONG
PE_RESULT
WE_CATEGORY
WE_CLI_DEP
WE_COMPLETE_ONLY
WE_E071
WE_LOCK_KEY
WE_TABLE_CONTFLAG
WE_TABLE_TYP
WE_TADIR
WI_E071

Exceptions

Function Group

STRD

TXBHW - Original Tax Base Amount in Local Currency   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5506 Date: 20240604 Time: 073737     sap01-206 ( 50 ms )