Solution : https://service.sap.com/sap/support/notes/67826 (Connexion à SAP Service Marketplace requise)
Résumé :
PM orders may become inaccessible due to missing status or operational data in JSTO and JEST tables, resulting in errors like OK600. These issues typically stem from a programming error noted in SAP Note 95973. Users should utilize the RIORDST1 report provided to correct order data, including parameters for processing specific orders, all orders, or elements such as headers, operations, and components. It's critical to execute this in update mode, preferable overnight, to avert disrupting ongoing processes since this report does not lock orders. Repeat runs may be necessary for complete status object reconciliation.
Mots Clés :
order headers oper = 'x' ==> status objects, database header = 'x' ==> status objects, processed update = 'x' ==> missing statuses, operations comp = 'x' ==> status objects, additional key words iw32, logical database psj, interest calculation leads, status object number, error message ok600, status objects
Notes associées :
| 777935 | Error in report RIORDST1 |
| 586973 | Missing status objects for materials |
| 552008 | Correction report: Temporary object no. in operation |
| 494365 | Error BS(001) when changing an order (operations faulty) |
| 492498 | Operations have temporary object number |
| 453262 | Restore status and profile for orders RIORDST1 |
| 389936 | Data inconsistencies in plant maintenance orders |
| 154272 | CJ45/CJ8G: No processing of PM/SM orders |
| 127894 | Status objects not existing, object numbers deleted |
| 95973 | Missing status object when converting planned order |