Bluesky
- SAP Managed Tags
This dynpro corresponds to a confirmation pop-up, what is written in the messagem (execute batch-input in mode 'A')
I would suppose some 'lock' problem, so try to lock required record before execution of CALL TRANSACTION.
- SAP Managed Tags
First, read some documentation such as found in The SAP Lock Concept.
- I guess you have to run the same program simultaneously from two sessions/nodes to trigger the error (both runs attempt to update the same data and the second fails because the first locks the data).
- Provide more information (which transaction do you call, is it a standard one?)
- Execute in mode 'A' and before the final save/post execution, execute SM12 in another session/node to find which tables/records you are currently locking
- You could set a break-point at start of FM of group SPO1 (FM name start with POPUP_TO_CONFIRM)
- SAP Managed Tags
The text description of table OOKAQ 'CO Object: Control Data for Cost Elem. (Inttab for Enqueue)' is explicit.
The lock object sould be EKCOKAE (or S, look at SM12 which contains the nformation, lock object and key values) so you have to try to lock with ENQUEUE_EKCOKAE
- When sucessful, unlock with DEQUEUE_EKCOKAE followed by CALL TRANSACTION
- Try a LOOP calling ENQUEUE_EKCOKAE using wait option til successful, prevent infinite loop with a maximal number of try, then abort
NB: An OSS note advises against calling this transaction as batch-input - 314528 - CO-OM, CO-PC: batch input in Release 4.6 (but provides no BAPI, sad)
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
