on 2015 Dec 17 7:07 AM
We have lot of dummy values in WBS element for planning purpose from WBS01000 TO WBS10000.
Everytime a record is planned it will automatically identify the existing value and post the current input to next WBS.
For example is the data is already planned for WBS01000, the next planned input should go to WBS01001.
This we are achieving by knowing from the EVGET last WBS used and incrementing next input by 1 value to next WBS.
The issue comes when multiple users open input template and try to send value to WBS at the same time. Howcan each one post to different WBS element, rather than overwriting to the last WBS element.
We are in BPC 7.0 NW
Your input will be appreciated.
Request clarification before answering.
Usually SAP uses ENQ/DEQ methods to lock and unlock objects. So, when you found 1st unused WBS you check if it's locked or not. If it' not locked you lock it and unlock at the end of the process. If it's locked you try finding that WBS again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 7 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.