Solution : https://service.sap.com/sap/support/notes/751129 (SAP Service marketplace login required)
Summary :
In the SAP environment, there exists a discrepancy in how authorizations function between traditional and Enjoy purchasing transactions. The Enjoy transactions (e.g., ME21N, ME22N, ME23N) are designed for simultaneous multiple document handling, reducing the dependency on individual transaction authorizations. These transactions scrutinize different authorization objects like M_BEST_BSA for document types, and M_BEST_EKG for purchasing groups, controlled by activity codes rather than transaction codes. Users should generally be granted access to all Enjoy transactions to ensure comprehensive functionality. Furthermore, deletion capabilities are inherently included in transaction changes, barring specific customizations via BAdi's like ME_PROCESS_REQ_CUST, which require advanced programming skills.
Key words :
generate 02 change 03 display 08 display change documents 09 display prices, check additional authorization objects, me23n actualy refer, object class mm_e, directly viatransaction se16, error message created, object oriented programming, create purchase orders, enjoy purchaseorder transactions, purchasing enjoy-transactions
Related Notes :
| 1276099 | AFS PO:No authorization check for pricing for schedule lines |
| 1050832 | ME23N in Compliance Calibrator (RAR) Default rules |
| 668212 | ME21N: Document type authorization when holding a PO |
| 491789 | FAQ: Purchase order (ME21N, ME22N, ME23N) |
| 387978 | ME22N/ME23N: Display < > change activity category |
| 336010 | ME21: No authorization in contract reference |
| 321929 | ME23N: Authorization price display status (header) |
| 304827 | ME22N/ME23N: missing value for authorization check |
| 212447 | ME22N: Activity category |