Do you have any question about this error?
Message type: E = Error
Message class: S_CUS_IMG_ACTIVITY - IMG Activity
Message number: 197
Message text: SOBJ piece list for table/view &1 in object &2 is not consistent
The object piece list (SOBJ) of table/view &V1& in object &V2& does not
match the piece list of the table/view in the Data Dictionary.
You can put object &V2& and subobject &V1& (table/view) in BC Sets. The
subobject definition piece list (SOBJ) is relevant for the BC Set
transactions.
As only the tables/views of subobject &V1& which are in your object
definition (SOBJ for table/view &V1&) can be put in BC Sets, probably
not all required tables for the object (see Data Dictionary) will be put
in BC Sets.
The SAP developer responsible for the object must compare the object
piece list for the table/view &V1& in the transaction SOBJ, with the
piece list in the Data Dictionary (SE11), and resolve differences in the
subobject piece lists. You can use the 'Adjust to Dictionary' pushbutton
in the transaction SOBJ. It is only active in change mode.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
S_CUS_IMG_ACTIVITY197
- SOBJ piece list for table/view &1 in object &2 is not consistent ?Get instant SAP help. Start your 7-day free trial now.
S_CUS_IMG_ACTIVITY196
View/table &1 in object &2 is too wide to put in BC Sets
What causes this issue? The table/view &V1& in object &V2& is too wide to be put in BC Sets. You can only put tables/views which are ...
S_CUS_IMG_ACTIVITY195
Address data table/view &1: Cannot be used in object &2
What causes this issue? Address management tables and views (tables with fields in the domains 'ADRNR', 'CADRNR' and 'AD_ADD...
S_CUS_IMG_ACTIVITY198
System object &1: Cannot be used in object &2
What causes this issue? The table &V1& is a system object. System objects are tables that either belong directly to the ABAP Dictionary, or t...
S_CUS_IMG_ACTIVITY199
Multiple objects: Tables/views with address fields in data part
What causes this issue? The analysis determined that address fields (fields with domain 'ADRNR', 'CADRNR', and 'AD_ADDRNUM...
Click on this link to search all SAP messages.