Solution : https://service.sap.com/sap/support/notes/722320 (SAP Service marketplace login required)
Summary :
Following a work center change in the R/3 system, an error "Order could not be scheduled" (/SAPAPO/OM 024) occurs due to the violation of unique mode assignment in the system's integration structure. This issue arises when modes with identical primary resources are used within a Production Planning and Manufacturing (PPM) environment, contradicting the requirement for unique mode-to-resource assignments. The error implicates disruptions in the scheduling between R/3 and APO systems, pinpointing a flawed mode linkage, particularly when a work center is altered. SAP Note 760511 supersedes the current guidance, recommending implementation of updated solutions through BAdI adjustments outlined therein, addressing mode selection and uniqueness validations.
Key words :
terms /sapapo/om 102 rc 59, source code corrections contained, source code corrections, sample code delivered, object directory entry, undesired side effects, primary resources violates, identical mode number, incorrect mode selection, call transaction se19
Related Notes :
| 834771 | Operation/Phase x occupies non-existent resource |
| 760511 | Order could not be scheduled, or a dump occurs |
| 733728 | R/3 -> APO: Order could not be scheduled |
| 727275 | R/3-> APO: Exception condition "LC_APPL_ERROR" raised |
| 629366 | Copying work center changes from R/3 to APO (BAdI solution) |
| 423626 | Different dates in R/3 and APO |