How To Fix MCLI002 - Mandantenunabhängige Cust-Objekte müssen MCli-Doku und MCli-Status haben

SAP Error Message - Details

• Message type: E = Error

• Message class: MCLI - Multiple Client Messages

• Message number: 002

• Message text: Mandantenunabhängige Cust-Objekte müssen MCli-Doku und MCli-Status haben

Was verursacht dieses Problem?

As well as application data (master data and transaction data), which
must be client-specific, a mySAP.com system also contains a large number
of Customizing tables. Many of these tables control business processes,
which means that they contain the following:
Data that represents the organizational structures of the enterprise
Parameters that control business processes.
Most of these tables are defined as client-specific, due to their
business relevance. They can be defined individually for each customer
in a multiclient system. However, there is also a range of cross-client
Customizing tables.
Operators of multiclient systems need to know which Customizing settings
are cross-client, since they need special attention when modifications
are made. These operators also need to know what functions are in all
cross-client Customizing tables, so that they can react correctly to
competing requirements from different clients. For this reason, each of
these objects must have appropriate multiclient documentation, and have
its multiclient compliance confirmed with an explicit OK status.
Explanation of Terms: "Customizing Table" or "Customizing Object"
There are often strong mutual dependencies between Customizing tables.
For this reason, tables are not maintained individually, but as
Customizing objects. The object-specific logic integrated into a
Customizing object makes sure that it remains consistent in its table
group when you edit its entries. In the following we speak about
Customizing objects when we mean the representation of Customizing
tables on the user interface, and about Customizing tables when we mean
their technical implementation in the database.
A Customizing object can contain both client-specific tables and
cross-client tables. We speak of client-specific objects if all tables
maintained through this object are client-specific. Likewise, if at
least one cross-client table maintained through the object can be
changed, then the object itself is cross-client. Remember that an object
is client-specific if it contains one or more cross-client tables whose
values can only be displayed or read, and not changed.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

Wie behebe ich diesen Fehler?

The following must be defined for a cross-client object:
Is an object entry always valid for one individual customer only? In
this case, the object must be defined as client-specific.
Does an entry describe a business situation that might be relevant for
more than one customer? In this case, it is a good idea to define the
object as cross-client. You must usually make a pragmatic decision about
this, but you must create multiclient documentation.
Is it technically necessary that the object is cross-client? Entries
often describe program objects from the mySAP.com Repository; some
Repository objects are even generated from table entries. In these cases
there is a one-to-one relationship between table entry and Repository
object; this enforces the cross-client nature of the object.
The initial requirements (short document and OK status) are checked
automatically in the multi-client check in CheckMan. You can capture and
display cross-client objects in the <ZK>Multi-Client Manager</>
(transaction <DS:TRAN.MCLIMAN>MCliMan</>) subsequently, in response to
CheckMan messages.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE