Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | SHENQ |
| Short Description | Only shared lock in case of contract release order |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Sh. lock |
| Medium | 15 | Shared lock |
| Long | 20 | Shared lock only |
| Heading | 1 | S |
Documentation
Definition
Sets a shared lock.
Use
If you set this indicator, when a release order is created against a contract belonging to this document type, the system will impose a shared lock on the contract instead of an exclusive lock. This enables several users to release against the contract simultaneously.
However, the contract itself cannot be changed during this time.
The exclusive contract lock serves to permit the checking of the target quantity or value of the contract to be carried out consistently. In the case of a shared lock, under unfavourable circumstances it may happen that two users release against the contract simultaneously, and whereas each individual release order may be below the target quantity, the two taken together exceed it. In such a case the system will not issue a message.
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
