No Tables/Views Assigned to a Customizing Object
Message type: E = Error
Message class: IMG_CONS - Messages for IMG_CONS Checkman
Message number: 033
Message text: No Tables/Views Assigned to a Customizing Object
&WHAT_FOR&
The customizing object piece list is empty.
INCLUDE BC_IMG_CONS_AT_05 OBJECT DOKU ID TX
Empty piece lists usually only occur in modified SM30/SM34 view
maintenance transactions, individual transactions (customizing object
type 'T') and logical transport objects (customizing object type 'L'),
because individual exits use other tables, or create customizing objects
in SOBJ, and the piece lists must be maintained manually. The piece
lists of tables, views and view clusters are created automatically when
the maintenance dialog is generated with the transaction SE54.
<ZU>Determine correct piece list:</>
For tables, views and view clusters, regenerate the maintenance dialog.
For other customizing object types, analyze the tables maintenaned in
the transaction interface.
Or create a customizing request for a data record of the IMG activity,
in the IMG, with the transaction SPRO, and read the tables involved from
the piece list of the order, in transaction SE09.
The analysis can be by code inspection.
Create the piece list with the transaction SOBJ, by entering all objects
which are maintained by the transaction.
<ZU>Notes:</>
If possible, convert the object to the standard table and view
maintenance SM30/34. The piece list is then created automatically from
the view definition when the maintenance dialog is generated in SE54.
If the wrong object is assigned, assign the correct one with a
maintained piece list, in the IMG maintenance (SIMGH). If the activity
does not change any tables (dummy activity), assign a dummy object (e.g.
IMGDUMMY) in the IMG maintenance. At the same time, delete the obsolete
customizing object in SOBJ, because it is still incorrect, and the next
CheckMan run will show it as an error again.
If the transaction transports all changes with the transport object R3TR
TDAT <object name>, the transport system checks the piece list, so it
should already be correctly maintained.
INCLUDE BC_IMG_CONS_AT_02 OBJECT DOKU ID TX
&HOW_DOES_IT_WORK&
This check determines whether the piece list for the customizing object
is maintained in SOBJ. It checks wheter there is an entry for the object
in the table OBJS.
The customizing object piece list is empty.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE BC_IMG_CONS_AT_01 OBJECT DOKU ID TXINCLUDE BC_IMG_CONS_AT_05 OBJECT DOKU ID TX
Empty piece lists usually only occur in modified SM30/SM34 view
maintenance transactions, individual transactions (customizing object
type 'T') and logical transport objects (customizing object type 'L'),
because individual exits use other tables, or create customizing objects
in SOBJ, and the piece lists must be maintained manually. The piece
lists of tables, views and view clusters are created automatically when
the maintenance dialog is generated with the transaction SE54.
<ZU>Determine correct piece list:</>
For tables, views and view clusters, regenerate the maintenance dialog.
For other customizing object types, analyze the tables maintenaned in
the transaction interface.
Or create a customizing request for a data record of the IMG activity,
in the IMG, with the transaction SPRO, and read the tables involved from
the piece list of the order, in transaction SE09.
The analysis can be by code inspection.
Create the piece list with the transaction SOBJ, by entering all objects
which are maintained by the transaction.
<ZU>Notes:</>
If possible, convert the object to the standard table and view
maintenance SM30/34. The piece list is then created automatically from
the view definition when the maintenance dialog is generated in SE54.
If the wrong object is assigned, assign the correct one with a
maintained piece list, in the IMG maintenance (SIMGH). If the activity
does not change any tables (dummy activity), assign a dummy object (e.g.
IMGDUMMY) in the IMG maintenance. At the same time, delete the obsolete
customizing object in SOBJ, because it is still incorrect, and the next
CheckMan run will show it as an error again.
If the transaction transports all changes with the transport object R3TR
TDAT <object name>, the transport system checks the piece list, so it
should already be correctly maintained.
INCLUDE BC_IMG_CONS_AT_02 OBJECT DOKU ID TX
&HOW_DOES_IT_WORK&
This check determines whether the piece list for the customizing object
is maintained in SOBJ. It checks wheter there is an entry for the object
in the table OBJS.
Error message extract from SAP system. Copyright SAP SE.
