Kontakt

Ansicht
Dokumentation

MCLITOBJ_PP_PI_PMA_CMX_XS - MCLITOBJ PP PI PMA CMX XS

MCLITOBJ_PP_PI_PMA_CMX_XS - MCLITOBJ PP PI PMA CMX XS

ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Short Description of Function

Using the current view or view cluster, maintain filter values for BAdI implementations. BAdI filter values control the selection of implementations when calling a BAdI, as long as the BAdIs concerned are filter dependent. In this case, BAdIs from packages CMX_XS and CMX_XSE are affected.

Because BAdI implementations with ABAP coding (see transaction SE19) are always client independent, it is advisable to ensure that new BAdI filter values that you create (which are used to call the implementations) are also client independent.

In this case it is nevertheless possible to have a strict division between data and implementations in different clients.

Recommendations for Multi-Client Operations

All values that are maintained using the current view or view cluster are assigned to an XStep namespace at the top level (first field in key of the particular database table). At the moment "SAP" is used as the (standard) XStep namespace. SAP delivers filter values in this namespace for the following standard implementations: XStep generations, XStep valuation symbols, XStep destination types and standard XStep repositories.

In the customer system you can also define the additional client-independent, customer-specific, namespaces "Y*" and "Z*". You can subsequently create client-independent filter values for customer specific BAdI implementations.

The definition of the XStep namespaces is client-independent. Once they have been defined, newly created namespaces must be released as being client-independent using transaction CMX04. The filter values are then visible in transaction SE19 (BAdI maintenance).

If several customers use a single system and it is therefore necessary to enforce a strict division between clients, enhancements must be made by creating different XStep namespaces for the individual customers, which must then be released in selected clients.

Example:

  • Customer A uses, for example, XStep namespace Y01 in client 400
  • Customer B uses, for example, XStep namespace Y02 in client 500

After defining the XStep filter values in client-independent Customizing they are not yet visible in the application; they cannot yet be used.

You can only use the corresponding BAdI implementations once the XStep namespaces have been released in the current client (using transaction CMX04).






General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 2925 Date: 20240523 Time: 200404     sap01-206 ( 54 ms )