Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MGA (Package) Application development R/3 material master from 3.0
Basic Data
| Data Element | SLOCK |
| Short Description | Shared Lock in Material Master (Only Tables MBEW and MARC) |
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 | SharedLock |
| Medium | 15 | Shared lock |
| Long | 20 | Shared lock |
| Heading | 1 | S |
Documentation
Definition
Use
If this indicator is set, plant data and valuation data (tables MARC and MBEW) are no longer locked exclusively in material master maintenance, but a shared lock is set. This has the advantage that goods movements can be carried out at the same time as material master maintenance if no valuation-relevant fields or inventory-management-relevant fields (such as the base unit of measure, batch management requirement indicator, valuation category, or price unit) are changed in material master maintenance.
If a valuation-relevant field or inventory-management-relevant field is changed, the system does the following:
- Locks the plant data and valuation data in material master maintenance exclusively, to prevent goods movements from being carried out at the same time.
- Rereads the plant data and/or valuation data from the database since this data may have been changed by a goods movement carried out between starting material master maintenance and changing the relevant field.
If a goods movement is carried out at the same time or immediately beforehand, your change is rejected by the system with a corresponding error message. In this case, you must change the field later.
As a result, a shared lock has the disadvantage that it prolongs the runtime if valuation-relevant fields or inventory-management-relevant fields are changed.
Procedure
Examples
Dependencies
Shared Locks for Goods Movements
Setting this indicator is only of use if shared locks have been allowed for goods movements in Customizing for General Settings. Shared locks are allowed by setting the indicator Subsequently lock exclusively in the activity Set Material Lock.
Batches
A material master record cannot be maintained at the same time as a goods movement is carried out if all three of the following circumstances apply:
- The goods movement is entered for a batch.
- A class is assigned to the batch during the goods movement.
- This class is determined on the basis of the material's batch classification.
This is because it would otherwise be possible to change the class assignment for the material, while the batch is created with reference to the previous class assignment.
History
| Last changed by/on | SAP | 19990412 |
| SAP Release Created in |
