Ansicht
Dokumentation
MULTICLIENT_ANALYSIS - Multiple Client Analysis
Fill RESBD Structure from EBP Component Structure TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Title Multiple client Analysis
Purpose
The tool lists the objects which could be critical in client scenarios or must be monitored. Mainly application tables (for master and transaction data) and customizing object definitions are analyzed. Other objects in the specified selection set are ignored. Application tables are recognized by their delivery class, i.e. this table attribute in the Dictionary. Customizing objects are recognized from the customizing object definitions in the transaction SOBJ.
The object set to be analyzed is specified by parameter. It is usually selected from one or more transport requests containing object lists of a product to be delivered (first parameter). Alternatively, a set of packages can be specified (second/third parameters).
Results list structure
The analysis poses the following three questions:
- (Q1) Are there any cross-client application tables with delivery class A?
- (Q2) Are there any cross-client customizing objects? Which customizing tables do they contain?
- (Q3) Which other cross-client customizing tables without reference to customizing objects and IMG are there?
The results list has 3 corresponding sections containing the table or customizing objects found, with their source information such as component, development class (package), person responsible in the object directory table TADIR. In the Q2 section, the customizing objects are also resolved into their component views and tables.
Column headers
All three sections have the following columns, which are not all used for all object types.
- Name of the object described in the row. followed by its views and tables for customizing objects,
- 'Type': Customizing maintenance type (acc. to SOBJ definition),
- 'DelivCl': Delivery class or customizing category,
- 'Cli': Client-specific ("X") or cross-client (space),
- 'IMG': Maintenance activity for the object in IMG flag,
- 'Component': Application hierarchy component,
- 'DevClass': Development class (package),
- 'Text': Short description of the object or subobject,
- 'Author': Person responsible for the object in TADIR and possibly the person responsible for the development class as well
List Header
The list header contains statistics about the scope of the analysis set, including the number of cross-client application tables and customizing objects. This lets you estimate the total scope of the product area to be analyzed.
List analysis aims
If Q1 finds objects, the application is probably not multiple-client- capable for these tables if their analysis class is really 'A' (Application Data). In this case, contact the developer to find out whether the application can run with multiple clients without data security risks. If the table is in the standard SAP delivery, you can contact me. I have a list of tables which which have been incorrectly given delivery class 'A', which you can ignore (being corrected in Support Packages).
Objects from the other two questions, Q2 and Q3, initially only indicate that there are cross-client settings in the customizing environment. Such objects are not a priori problematic, some settings are correctly made to cross-client entities (e.g. all types of technical system settings), but such objects must be clearly identified as cross-client objects and it must be clarified for an multi-client ASP whether there can be conflicting requirements from different clients and under what circumstances. You must establish:
- Which functions the object performs. Do they only affect individual clients, leaving the other clients unaffected by changes to the settings?
- If so: How should an ASP deal with heterogeneous client requirements in a scenario to ensure the coexistence of the clients?
If such settings describe organizational elements of a company, or concern company-specific procedure control, check whether customizing can be performed safely (data isolation) and conveniently enough in an ASP multi-client scenario for the individual clients, or whether the cross-client design decision is questionable, and a multi-client problem is to be expected.
Prerequisites
The ASP solution to be evaluated must be selectable in the system. You can usually identify the ASP solution in an SAP System via an object list in the form of one or more transport requests which contain all objects and customizing entries for the solution completely and exclusively, i.e. the object list contains no objects which are not part of the ASP solution.
A client transport is not a reliable transport request because it contains the entire SAP System and the ASP solution cannot be identified.
An ASP solution is often a set of preconfigured customizing settings for a particular application scenario. The object list then only contains entries from customizing tables and customizing objects (one or more logically-connected entries from one or more customizing tables). In this case you can use the first tool program (MC_TABKEY_ANALYSIS).
In other cases, the solution also contains Repository objects (especially Dictionary objects, programs or customizing object definitions). These can be checked, in addition to the previously mentioned table checks, by the second tool (MC_METADATA_ANALYSIS). This tool analyzes and displays potential metadata multi-client-compatibility conflicts.
Selection
Input parameter(can be generic or listed):
- Transport request parameter: (can be several)
- Component/package parameter: Application component or package
Output
The results list begins with a statistical overview of the analyzed client-specific and cross-client objects.
CPI1466 during Backup CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 7046 Date: 20240520 Time: 095314 sap01-206 ( 127 ms )
