How to Locking of Transaction Data
When implementing a planning scenario it has to be ensured, that users work on a separate noninterfering set of transaction data. If this is not the case, they will be faced with messages saying that someone else is already procession the data. Hence he cant continue with the planning process. These kinds of issues might become critical close to go live if not carefully planned before. This How to outlines the rules of the locking mechanism and gives examples of typical problems and how to solve them. Please be aware of the fact that other ways of locking transaction data like Status and Tracking System (STS) or data slices will not be covered in this how to paper.