3775787 - Purchase Requisition number missing in monitor purchase order items app or CDS view I_PURCHASEORDERITEM

• In the Monitor Purchase Order (PO) Items app, the Purchase Requisition (PR) number field is missing for many purchase orders that were created from purchase requisitions.
• PR number is shown in PO, but its not showing in CDS views I_PURCHASEORDERITEM (EKPO table).  
• The Display Purchase Order app shows the requisition reference for items where the Monitor Purchase Order Items app does not.
• The reference requisition data is not visible in the EKPO CDS view, while the requisition and purchase order linkage is visible in the EBAN CDS view.
• No error messages are shown.
  
  Image/Data is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.  

SAP S/4HANA Cloud Public Edition

1. Create Purchase requisition.
2. Open the Monitor Purchase Order Items app or "Create Purchase Order advance app". 
3. Provide reference PR number while creating PO. 
4. Then  In PO create screen go to "Delivery Schedule" and remove PR number (1 - from image) and hit enter key, that will allow to remove PR number at Item level.  Then remove PR number at item level (2 -from image).
   
   
   
   
5. Then add PR reference number again at "Delivery schedule" and press enter. Do not add at item level.  
   See at item level PR number will be blank and grade out. 
   
   
   
   
   
6. Save the PO.
   
   
7. Now check result in CDS view, I_PURCHASEORDERITEM field PURCHASEREQUISITION or in Table EKPO filed BANFN.
   

• The system does not populate EKPO-BANFN during ME21N. This is the expected behavior if, 
• The reason for this behavior is the following:
  • When creating a purchase order and in the scheduling lines, adding for example 3 different purchase requisitions, it is not clear which one should appear in the I_PURCHASEORDERITEM (EKPO).
  • This would cause inconsistencies (in EKPO there would be only one BANFN and in the EKET there would be 3 entries).
  • Therefore, table EKET should be used to check the purchase requisition number (e.g., for reporting purposes).
  • Purchase requisition number only provided in "Delivery schedule" and not at item level in PO screen, pressed entered and save PO. For example, specify the PReq at schedule line level (table EKET), the field EKPO-BANFN is not filled. 
• Note: CDS - _PURCHASEORDERITEM reads data from table EKPO.

• Fields EKPO-BANFN and EKPO-BNFPO serve as informational fields only.
• No correction report is available to update EKPO-BANFN, as these fields have no operational impact. For reporting purposes, the data should instead be retrieved from EKET-BANFN.
• When a third-party purchase order (PO) is created, the EKPO-BANFN field is not populated in the database. However, if the PR reference is manually maintained in ME22N, the EKPO-BANFN field will be updated accordingly.
• If Only single PR is used, please update PR number at item level as well as in "Delivery Schedule". 

• PR is not displayed in the Monitor Purchase Requisition Items app - SAP S/4HANA
• Purchase Requisition number is not updated in EKPO - SAP ERP & SAP S/4HANA

monitor purchase order items, requisition number missing, reference pr missing, ekpo, eban, sto, stock transport order, fiori, output settings, deleted line item field, pr to po, monitor po items, requisition reference, cds view, s/4hana cloud , KBA , MM-PUR-REQ-2CL , Purchase Requisitions (Public Cloud) , Problem