Show TOC

Background documentationGeneric Critical Objects Locate this document in the navigation structure

 

You can specify generic critical Customizing objects for the following purposes:

  • To flag a critical transport object that contains a generic table key. The Master Type, Master Name, and Table Name fields are mandatory. The View Name field is optional.

    Example Example

    Master Type: TDAT

    Master Name: USTAT

    View Name:

    Program ID: R3TR

    Object Type: TABU

    Table Name: UST04

    Table Key: 100*

    In this case, the entries in the table UST04 whose table key begins with 100 have to be approved before they can be transported. This restriction applies only to entries to be exported with the TDAT transport object USTAT.

    End of the example.
  • To flag a critical transport object that contains a generic table name. The Master Type and Master Name fields are mandatory. The View Name field is optional. The Table Key field must remain blank.

    Example Example

    Master Type: TDAT

    Master Name: USTAT

    View Name:

    Program ID: R3TR

    Object Type: TABU

    Table Name: UST*

    Table Key:

    In this case, Customizing content of tables whose name begins with UST, and subobjects of the TDAT transport object USTAT, have to be approved before they can be transported.

    End of the example.
  • To flag a critical transport object that contains a generic view name. The Master Type and Master Name fields are mandatory. The Table Name and Table Key fields must remain blank.

    Example Example

    Master Type: CDAT

    Master Name: SCMGVC_ATTRPROF

    View Name: SCMGV_ATTR*

    Program ID: R3TR

    Object Type: TABU

    Table Name:

    Table Key:

    In this case, Customizing objects of the views in the view cluster SCMGVC_ATTRPROF whose names begin with SCMGV_ATTR have to be approved before they can be transported.

    End of the example.
  • To flag a critical transport object that contains a generic master name. The Master Type field is mandatory. The View Name, Table Name, and Table Key fields must remain blank.

    Example Example

    Master Type: TABU

    Master Name: UST

    View Name:

    Program ID: R3TR

    Object Type: TABU

    Table Name:

    Table Key:

    In this case, Customizing objects of tables whose names begin with UST have to be approved before they can be transported.

    End of the example.

You can specify generic critical ABAP objects by the object name only.

Example Example

Program ID: R3TR

Object Type: TABL

Object Name: ZCUST*

In this case, all tables whose name begins with ZCUST* have to be approved before they can be transported.

End of the example.