Mapping Onto Lock Object Types (SAP Library - Cross System Lock (BC-CST-EQ))

Mapping Onto Lock Object Types

Creating Lock Object Types (Table CSL_EOTY)

Mapping of standard lock objects onto a lock object type has to be defined in Customizing by developers during the development phase. To do this, they enter the lock object types in the Customizing table CSL_EOTY (the Z* namespace is reserved for customers). The entries are part of the delivery and serve as a selection criterion in the monitor.

Caution

The entries in table CSL_EOTY have to be defined during the development phase after a system group has been set up. This means that if tokens exist, it is problematic to change them.

Example

The following lock object types are available in the system for SAP Web AS 6.10:

Lock Object Type	Meaning
SALES_DOCUMENT	Order
PURCHASING_DOCUMENT	Purchase order
DELIVERY	Delivery

Creating Mapping Rules (Table CSL_EOME)

You enter the mapping rules in the database table CSL_EOME:

Note

Mapping rules are also known as mappings.

Fields in the Customizing table CSL_EOME

Field	Meaning	Example
EOMPKY	Name of the mapping The name must be the same as the component name that the mapping is valid for. After a transport, or after the table has been replicated in other systems, the CSL can then select the correct mapping using the components that exist in the system.	SAP_APPL
EOTYKY	Lock object type in table CSL_EOTY	SALES_DOCUMENT
EODDKY	Name of standard lock object in ABAP Dictionary	EVVBAKE

Example (Continued)

The following standard lock objects are part of the SAP Web AS 6.10 delivery:

Standard Lock Object (ABAP Dictionary)	Meaning
EVVBAKE	Sales document only (order)
EMEKKOE	Purchase document only (purchase order)
EVVBLKE	Delivery only

These standard lock objects are mapped onto the following lock object types with the table CSL_EOME:

EOMPKY (Mapping)	EOTKY (Lock Object Type)	EODDKY (Standard Lock Object)
SAP_APPL	DELIVERY	EVVBLKE
SAP_APPL	PURCHASING_DOCUMENT	EMEKKOE
SAP_APPL	SALES_DOCUMENT	EVVBAKE
SAP_DEFAULT	DELIVERY	EVVBLKE
SAP_DEFAULT	PURCHASING_DOCUMENT	EMEKKOE
SAP_DEFAULT	SALES_DOCUMENT	EVVBAKE

There are therefore two mapping rules for the lock object types: SAP_APPL and SAP_DEFAULT.

Selecting the Mapping Rule

If there is more than one mapping rule, the CSL has to select one at runtime. There are two ways of configuring Customizing to determine the selection:

To explicitly assign a mapping to a token manager, you can make an entry in the Customizing table CSL_MEOM.

It makes sense to give the mapping the same name as the name of the corresponding component. You can enter the relevant components in the table CSL_EOMP and assign them a lookup of 1-N. The CSL uses this lookup to check in the logical system whether the component exists in the CVERS database table (that is, whether the component exists in the system). The CSL selects the first mapping in the set order for this component.

Note

The component names are determined by SAP. The development groups of a cross-component scenario must be in agreement on the components and lookups so that the CSL can select the correct mapping in each system.

The CSL selects a mapping according to these table entries:

In function module calls of the CSL, the name of a standard lock object is always contained in the token key. The CSL gets all the mappings that are defined for this object from the CSL_EOME Customizing table.

Then the CSL uses the CSL_MEOM table to check whether a mapping was explicitly assigned to the token manager in the function module call. If so, then this mapping is used.

If no mapping can be determined with this method, the CSL looks at the entries in the CSL_EOMP table (components and lookup) according to the lookup 1-n. The first mapping that is also found in the table of the CVERS software components because it has the same name is selected.

If the CSL cannot determine a mapping rule with this method, the SAP_DEFAULT mapping is activated. The lookup for this mapping is 0 so that the CSL can recognize that it is not a component. The CSL therefore does not need to check whether SAP_DEFAULT is entered in the CVERS.