Ansicht
Dokumentation

MULTICLIENT_XANALYSIS - Multiple Client Analysis

BAL Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.

Title Multiple Client Analysis

Purpose

The tool returns a list of objects which could be critical in multi-client scenarios. Only application tables (for master and transaction data) and customizing object definitions, are examined, all other selected objects are ignored. Application tables are identified by their delivery class attribute in the Dictionary. Customizing objects are identified from the customizing object definitions created in the transaction SOBJ.

The objects to be examined are specified by parameter. They are usually selected from one or more transport requests containing piece lists for a product to be delivered (first parameter), or you can also specify a set of packages (second/third parameters).

How is the results list structured?

The analysis answers the following three questions:

• (Q1) Are there cross-client application tables with delivery class A?

• (Q2) Are there cross-client customizing objects? Which customizing tables do they contain?

• (Q3) What other cross-client customizing tables without reference to customizing objects and IMG are there?

The results list comprises 3 corresponding sublists. Each sublist contains the tables or customizing objects found and their source information, e.g. component, package, person responsible for the object in object catalog table TADIR. The Q2 sublist also resolves the customizing objects into their component views and tables.

Column headings

All three sublists have the following columns, which are not all used for all object types.

• The first column contains the name of the object in the row. For customizing objects the views and tables it contains follow,

• 'Type': Customizing maintenance type (acc. to SOBJ definition),

• 'Del. Cl': Delivery class or customizing category,

• 'Cli': Client-specific ("X") or cross-client (space),

• 'IMG': The object has a maintenance activity in the IMG,

• 'Component': Application hierarchy component,

• 'DevClass': Package,

• 'Text': Short description of the object or subobject,

• 'Author': Person responsible for the object according to TADIR, possibly also the person responsible for the package

List header

The list header contains additional statistics about the scope of the data analyzed, including the number of cross-client application tables and customizing objects. You can estimate the amount of data to be analyzed in your product area from this data.

List analysis

If objects have been found for question Q1, the application is probably not multi-client capable for these tables , if the analysis class of the tables really is 'A' (application data). In this case, contact the developer to find out whether the application can run in a multi-client environment without data security and data protection risks. If the table is in the SAP standard delivery, you can contact me. I have a list of tables which have been incorrectly assigned to delivery class 'A', and can be ignored (being corrected in Support Packages).

Objects for the other two questions Q2 and Q3 initially only mean that there are cross-client settings in the customizing environment. Such objects need not be errors, because some settings are intended for cross-client entities (e.g. all types of technical system settings), but such objects must be clearly identified as cross-client objects and explained for an ASP with a multi-client system whether conflicting requirements from different clients are possible, and what is to be born in mind in this case. The explanation must include:

• Which functions are described by the object? Do they only affect individual clients, leaving the other clients unaffected by changes in the settings?

• If so: how can an ASP avoid conflicting client requirements in a scenario and guarentee the coexistence of the clients?

If such settings model organization elements of a company or control company-specific procedures, you must analyze whether customizing of the various clients can be performed safely (data isolation) and efficiently enough in an ASP multi-client scenario, or whether the cross-client design decision must be questioned, i.e. whether client conflicts could occur.

Prerequisites

The ASP solution to be analyzed must be present and selectable in the system. It can usually be identified in an SAP System by a piece list, in the form of one or more transport requests which contain the solution objects and customizing entries

- completely and

- exclusively, i.e. there are no objects in the piece list which are not part of the ASP solution.

So a client transport in particular is not a valid transport request, because it contains the entire SAP System and the ASP solution cannot be identified.

In many cases, an ASP solution is a set of preconfigured customizing settings for a particular application scenario. The piece list only contains entries for customizing tables and customizing objects (one or more logically-related 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 by the second tool (MC_METADATA_ANALYSIS), in addition to the previously mentioned table contents check. This tool analyzes and displays potential multi-client capability conflicts in the metadata.

Selection

Input Parameters (can also be entered generically and by listing):

• Transport Request: can be more than one

• Component/Package: application component or package

Output

The results list begins with a statistical summary of the analyzed client-specific and cross-client objects.

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7152 Date: 20240520 Time: 081814     sap01-206 ( 128 ms )