Solution : https://service.sap.com/sap/support/notes/524487 (SAP Service marketplace login required)
Summary :
When executing an order confirmation transaction for an uncreated order using the next sequential order number, the system locks this number and error RU002 appears. Concurrent order creation attempts to assign this locked number, subsequently triggering error CO726, leading to skipped order numbers. This arises due to improper number-locking, which also incorrectly occurs with external number assignments. The issue stems from a software bug where the lock is not cleared after the error message. To resolve, apply the provided code fixes to release the lock if the order doesn’t exist, although slight timing overlap could still cause errors. Referring to Note 456777 is recommended for issues related to gaps in order sequences.
Key words :
incomplete order number assignment, error message ru002 - order &, attached correction instructions, automatic number assignment, internal number assignment, external number assignment, newly created order, terms process order, confirmation transaction responds, assigned order number
Related Notes :
| 456777 | Order numbers for internal number assignment |