SAP Knowledge Base Article - Public

3132000 - Customer number not copied to PR and PO in 3rd party scenario

Symptom

When creating a Purchase order from a 3rd party purchase requisition the customer number is sometimes not filled. 

Environment

SAP S/4HANA Cloud - All Versions 

Reproducing the Issue

1) create a 3rd party sales order 
2) after save check the PR created in the background 
3) check the address details of the purchase order created from the Purchase Requisition  

Cause

if the address is manually changed in the sales order the PR takes the manual address and does not fill the customer number. 
The purchase order copies the manual address from the Purchase Requisition. 

Resolution

Standard system behaviour. The system will always copy the ship-to partner from the sales order into the Purchase requisition customer number (EBAN-KUNNR) unless the ship to address is manually changed otherwise the EBAN-ADRN2 is updated. These field values are mapped then to PO fields EKPO-KUNNR, EKPO-ADRN2.

See Also

KBA 3277628   Ship-to Address from third-party SO not copied into subsequent PR and PO

Keywords

CMMDA-KUNNR, delivery address, eban-ADRN2, ME_REQUISITION_EXT, FV45EFMA_BESCHAFFUNG_ANLEGEN, FV45EFMA_ANLIEFERANSCHRIFT_FUE, ANLIEFERANSCHRIFT_FUELLEN, xvbpa-adrda, parm-kunnr, parm-adrn2 , KBA , MM-PUR-PO-2CL , Purchase Orders (Public Cloud) , SD-SLS-SO , Sales Orders , MM-PUR-REQ , Purchase Requisitions , SD-SLS-SO-TP , Third-party order processing , MM-PUR-GF-TP , Third Party Order Processing , MM-PUR-GF-ADR , Addresses , Problem

Product

SAP S/4HANA Cloud Public Edition all versions