Symptom
Message Table &1 is not part of the customizing object &2 is raised
NA TK428
____________________________________________________
Short Text
Table &1 is not part of the customizing object &2
Diagnosis
Entries in table cannot be edited in connection with customizing object as table does not belong to customizing object , according to the object definition.
System Response
The function terminates.
Procedure
Check whether the entered objects and keys are correct.
Then check in the Implementation Guide whether the object was created correctly.
Correct the object definition or the entry for the Transport Organizer interface.
Read more...
Environment
This KBA applies for all SAP Products based on NetWeaver and S4H.
Keywords
Properties of the object of type V compared with ABAP Dictionary
Message no. OZ118Diagnosis
The attributes of the object of type V were compared with the information from ABAP Dictionary. The function was either called explicitly or the table piece list of the object was changed.System Response
Some object attributes are not edited directly and are derived from ABAP Dictionary instead. These are the following attributes:- Category
The object category is synchronized with the table piece list. The delivery classes in the object tables must not differ from the category. The following rules apply:
-
- the category CUST is not allowed for cross-client tables
-
- the delivery classes W and S do not allow the category CUST for client-specific tables nor the category CUSY for cross-client tables
-
- the category APPL is only allowed for the delivery class A
- Transport
Tables (with text table), views, and view clusters flagged as Standard Recording Routine in view maintenance, or for which transport interface maintenance events are defined, are flagged as Automatic Transport.
- Client-specific
An object is client-specific if the piece list tables are client-specific.
- Translation-relevant
An object is translation-relevant if its piece list contains a table which is translation-relevant.
- Piece list
For tables (with text tables) and views, the table object list is generated from the definition in the ABAP Dictionary (for the generated tables, the Dictionary flag is set). Tables added manually (the Dictionary flag is not set here) are not affected. For view clusters, the piece list of the views and tables involved is derived from the view cluster definition.
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.