Hierarchy
⤷ FI (Application Component) Financial Accounting
⤷ FERC (Package) IS-U/FERC: Regulatory Reporting
Basic Data
Data Element | FE_WAIT |
Short Description | Number of blocking attempts |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT1 | |
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | 0 | |
Medium | 0 | |
Long | 30 | Number of blocking attempts |
Heading | 4 | NoBl |
Documentation
Definition
This parameter is only valid for background processing where you might add several regulatory procedures into one job.
If you run a regulatory procedure in production mode, it blocks access to the processed period for all other tasks. If this procedure is posting documents, the update is done asynchronously by the update task that inherits the lock. In this case the next regulatory procedure in the job could start before the update task is finished; it will abend because the period is still locked.
To avoid this problem the regulatory programs take advantage of a wait mechanism repeating the lock attempt in intervals of one second. The number of times it is repeated is given in the profile parameter enque/delay_max. The default for this parameter is set to 5 (secs). If a longer wait time is required, enque/delay_max can be set to a larger value. You are strongly advised not to use higher values which would affect all other SAP programs as well.
If you need higher wait times because your background job is still abending, then you can set the number of times you want to repeat the lock attempt. So a value of 3 lets the procedure wait for 3 times the number of seconds defined in enque/delay_max, typically 3 * 5 = 15 seconds.
The default value for this parameter is 1. If necessary increase it by 1 until the problem is gone.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |