How To Fix MCLI002 - Cross-client cust. objects must have multi-client doc. and status

SAP Error Message - Details

• Message type: E = Error

• Message class: MCLI - Multiple Client Messages

• Message number: 002

• Message text: Cross-client cust. objects must have multi-client doc. and status

What causes this issue?

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.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

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.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MCLI002 - Cross-client cust. objects must have multi-client doc. and status ?

  The SAP error message MCLI002 indicates that there is an issue with cross-client customizing objects in the SAP system. Specifically, it states that cross-client customizing objects must have a multi-client document and status. This error typically arises when there is an inconsistency in the configuration of cross-client objects, which are settings that should be available across multiple clients in the SAP system.
  Cause:
  
  Missing Multi-Client Document: The customizing object in question does not have a corresponding multi-client document, which is necessary for it to be recognized as a cross-client object.
  Incorrect Status: The object may not be in the correct status that allows it to be used as a cross-client object. For example, it might be in a development status instead of a released status.
  Transport Issues: There may be issues with the transport of the customizing objects between different clients, leading to inconsistencies.
  Client-Specific Settings: The object may have been created or modified in a client-specific manner, which is not allowed for cross-client objects.
  
  Solution:
  
  Check Object Status: Verify the status of the customizing object. Ensure that it is set to a status that allows it to be used as a cross-client object (e.g., released).
  Create Multi-Client Document: If the object does not have a multi-client document, you may need to create one. This can typically be done through the customizing transaction (e.g., SPRO) or by using the appropriate development tools.
  Transport Request: Ensure that the customizing object is included in a transport request that is properly configured for cross-client transport. You may need to re-transport the object to ensure it is correctly set up in the target client.
  Review Client Settings: Check if there are any client-specific settings that need to be adjusted. Ensure that the object is not inadvertently set to be client-specific.
  Consult Documentation: Refer to SAP documentation or notes related to the specific customizing object you are working with for any additional guidance or known issues.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), or SPRO (Customizing) to investigate and manage customizing objects.
  SAP Notes: Check SAP Notes for any known issues or patches related to the MCLI002 error. SAP frequently updates its knowledge base with solutions to common problems.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to resolve the MCLI002 error and ensure that your cross-client customizing objects are correctly configured.