Scope: managed applications, mobile applications, and ordinary applications.
We do not recommend that you shift the sequence boundary when posting documents. This can lead to waiting upon lock and decrease overall system performance. We recommend that you take the operation of shifting the sequence boundary out of real-time operations into scheduled operations. For example, execute it using a scheduled data processor with given frequency.
The sequence boundary of a single set of dimension values is a single resource. This means that when the sequence boundary moves within a single set of dimension values, different users will try to capture the same resource, that is, they will lock each other.
Systems based on 1C:Manufacturing Enterprise Management, version 1.x use an accounting policy that involves calculating the cost of goods being written off in real time (directly upon writing off).
In 1C:Manufacturing Enterprise Management, batch accounting algorithms use the "Batch accounting" sequence that has one dimension: Company.
To calculate the cost of goods to be written off upon disbursement document posting, shift the sequence boundary for this company to the time of the document being posted.
If two users simultaneously post disbursement documents for one company (which is very likely), they will lock each other. This system behavior is not a feature of sequence implementation in 1C:Enterprise but is required for the algorithm. So you need to know the exact sequence of documents. That is, all documents being posted at the same time must follow each other.
Shifting the sequence boundary upon real time posting of documents can significantly reduce the overall system performance. In this case, the best solution would be to clear this check box, that is, to refuse to calculate the cost upon document posting in real time. Use the scheduled data processor instead, which is part of 1C:Manufacturing Enterprise Management. It will calculate the cost with specified frequency.