Solution : https://service.sap.com/sap/support/notes/114213 (SAP Service marketplace login required)
Summary :
The SAP Note addresses the mechanism of determining document types when automatically generating purchase orders from purchase requisitions in SAP. When converting purchase requisitions to a purchase order, the system ascertains the document type based on the document type of the first requisition in the group. Key functions involve checks against Customizing settings (using tables such as T161A and transactions like OMEC) to validate if the document type is permissible. Specific conditions are outlined for instances like stock transport orders or item category splits, using designated tables (T161W) and transactions (OMGN). Additionally, recent changes in system behavior from Release 4.70 clarify the priority of document types. A modification solution using table T160 is suggested for cases where a specific default document type is needed but not permissible by standard settings, applicable primarily when neither stock transport order nor item category split scenarios apply. Planned future updates include system enhancements and the introduction of a user exit to cater to broader needs.
Key words :
terms me59 rm06bb10 rm06bb20 t160 t161a omh5 omec, supplying plant/receiving plant combination, purchase order document type exists, purchase order document type determination, purchase order document type, purchase requisition document type, customizing transaction omec, customizing transaction omh5, purchase order split, stock transport order
Related Notes :
| 491211 | FAQ: Purchase order (general) |