SAP ABAP Data Element WLF_SPERREN (AB: Document Lock (Mass Processing))

Hierarchy

☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-AB (Application Component) Agency Business (Global Trade)
     ⤷ WZRE (Package) Agency Business

Basic Data

Data Element	WLF_SPERREN
Short Description	AB: Document Lock (Mass Processing)

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	WLF_SPERREN
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	ENQUEUEALL
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Doc. Lock
Medium	15	Document Lock
Long	20	Document Lock
Heading	7	Lock

Documentation

Definition

Indicator used to determine how and whether agency documents should be locked during the program run:

• Single document lock: During processing, agency documents are locked individually. Documents that cannot be locked are not processed (error message). If documents cannot be locked during package processing, package processing is terminated, triggering a fatal error.
  Note: When processing large numbers of documents for each LUW (for example, posting or remuneration list creation), this option can lead to a huge number of entries and therefore to an overflow in the lock table.
• Process lock: When processing large numbers of documents in one processing step (package), for example, for posting list creation, the process lock should be used instead of the single document lock to prevent a capacity overload (or to ensure that processing does actually take place if the number of documents is greater than the capacity of the lock table). The process lock blocks agency documents at process level rather than locking them individually. Only one or two lock entries are made for each processing unit (normally package for invoicing party or payer).
  In addition to setting a process lock, for each individual agency document, the system checks whether a single document lock exists. Conversely, when an agency document is locked, the system checks whether a process lock has been set for the invoicing party or payer.
  A check is still made that no process lock for the same document category exists for any of the agency document partners. Locks may only exist for the partner for which the process lock is set, and only for the same process type.
  Lock entries are described on the following level: Partner/partner function/document category/Process/Subprocess. Example for posting list creation for payer 4711: 4711/payer/P/31. The subprocess is used to create enhanced remuneration lists for the combination of remuneration list partner and condition type group, to be able to create different remuneration lists simultaneously for one agency document.
  
  This lock can be used for the following processes:
• Creating posting lists/Customer settlements/Remuneration lists
• Mass release of all agency document categories (for list documents the process lock is set for the list documents and the list item documents).
• No lock: Agency documents are not locked. Note: You should only select this option if the agency documents were locked beforehand using an appropriate lock mechansism (For example: Posting list creation using report RWLF2010 is started simultaneously for different payers in several different processes using a dispatcher program. This locks all agency documents).
• Lock all documents: All agency documents are locked together during the program run and cannot be changed. Neither is it possible to enter any new documents.

History

Last changed by/on	SAP	20100310
SAP Release Created in	500