Do you have any question about this error?
Message type: E = Error
Message class: S_CUS_IMG_ACTIVITY - IMG Activity
Message number: 161
Message text: View/table &2 added to object &1 manually
The table/view &V2& was added to the object &V1& manually when the BC
Set or request was created. It is not in the object definition (see
transaction SOBJ).
The BC Set display/maintenance transactions display the table/view as
part of the object &V1&. The activation procedure also regards the
table/view as part of the object, and activates it, with any other
tables/views, as part of the object.
A table/view is usually only added to an existing object if it is
missing in the object definition (SOBJ) piece list. If it is part of the
object, the SAP developer responsible for the object must put it in the
object piece list in SOBJ.
If the table/view is independent of an object, this is a legitimate way
of putting an object-independent table/view in the BC Set. There is not
yet any other way of putting such a table/view in BC Sets, independently
of an object.
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_ACTIVITY161
- View/table &2 added to object &1 manually ?Get instant SAP help. Start your 7-day free trial now.
S_CUS_IMG_ACTIVITY160
View/table &1 explicitly allowed for BC Sets
What causes this issue? The table/view &V1&, whose DDIC attributes (e.g. delivery class) are not appropriate for BC Sets, has been explicitly...
S_CUS_IMG_ACTIVITY159
At least one table for object &1 explicitly forbidden for BC Sets
What causes this issue? At least one table in the logical transport object &V1& (type 'L') has been explicitly forbidden for use in...
S_CUS_IMG_ACTIVITY162
No data for object &1 in BC Set; Other tables added
What causes this issue? The BC Set contains the object &V1&, but the object tables in the piece list definition (see transaction SOBJ) are mi...
S_CUS_IMG_ACTIVITY163
View/table &2 of piece list for object &1 is not used
What causes this issue? Objekt &V1& does not contain all object tables/views in the definition of object &V1& (see transaction SOBJ)....
Click on this link to search all SAP messages.