Show TOC

Background documentationGeneric Critical Objects

 

You can specify generic critical Customizing objects for the purposes listed below.

Note Note

If you are not sure which object type and object name to enter, check the object list of your transport request, and check the Object Type and Object Name columns.

End of the note.

  • To flag a critical transport object that contains a generic table key.

    Example Example

    System Name: ABC

    System Type: ABAP

    Client: 100

    Program ID: R3TR

    Object Type: TABU

    Object Name: UST04

    Table Key: 100*

    In this case, the entries in table UST04 that have a table key beginning with 100 have to be approved before they can be transported.

    End of the example.

  • To flag a critical transport object that contains a generic table name.

    Example Example

    System Name: ABC

    System Type: ABAP

    Client: 100

    Program ID: R3TR

    Object Type: TDAT

    Object Name: UST*

    Table Key:

    In this case, Customizing content of tables with a name beginning with UST 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.

    Example Example

    System Name: ABC

    System Type: ABAP

    Client: 100

    Program ID: R3TR

    Object Type: CDAT

    Object Name: SCMGV_ATTR*

    Table Key: *

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

    End of the example.

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

Example Example

System Name: ABC

System Type: ABAP

Client: 100

Program ID: R3TR

Object Type: TABL

Object Name: ZCUST*

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

End of the example.