Symptom
- When the purchase requisition (PR) is created with MRP, both fields 'Created by' (EBAN-ERNAM) and 'Requisitioner' (EBAN-AFNAM) are filled with the MRP Controller.
- When the purchase requisition (PR) is created manually (with transaction ME51N) the field 'Requisitioner' (EBAN-AFNAM) is filled with the user ID.
- When the purchase requisition (PR) is created converted from a planned order (with transaction MD16) the field 'Requisitioner' (EBAN-AFNAM) is filled with the user ID.
Read more...
Environment
- Materials Management (MM)
- Production Planning (PP)
- SAP ERP Central Component
- SAP ERP
- SAP enhancement package for SAP ERP
- SAP enhancement package for SAP ERP, version for SAP HANA
- SAP S/4HANA
- SAP S/4HANA, on-premise Environment
- SAP S/4HANA Cloud Private Edition
Product
SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA Cloud Private Edition all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions
Keywords
Username, creator, created_by, EBAN, EBAN-ERNAM, T024D-DSNAM, purchase requisition, pr, mrp controller, AFNAM, EBAN-AFNAM, created by, requisitioner, user id, MD01, MD02, MD03, MD01N, MD_PURREQ_CHANGE, MD_PURREQ_POST, PPH_MRP_RUN_BADI, PURREQ_BEFORE_UPDATE_ADJUST, mrp run, MD16, ME51N, , KBA , MM-PUR-REQ , Purchase Requisitions , PP-MRP , Material Requirements Planning , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview