SAP Knowledge Base Article - Preview

3745924 - Missing GlobalLocationNumber (GLN) in Outbound Purchase Order

Symptom

  • When transmitting an outbound Purchase Order via EDI (SOAP message OrderRequest), the XML payload does not include the supplier's Global Location Number (GLN).

  • This occurs even though the GLN is fully maintained in the Business Partner master data under Identification Numbers (ID Type: BUP005).

  • The issue affects communication arrangements such as SAP_COM_0224 and SAP_COM_0828.

  • When inspecting the raw SOAP payload, the <Party PartyType="Supplier"> node contains only the internal SAP Business Partner number (<BuyerPartyID>) and address data, but no GLN field is present.

  • Without the GLN in the outbound message, purchase orders cannot be routed or processed effectively by receiving networks.


Read more...

Environment

SAP S/4HANA Cloud Public Edition

Product

SAP S/4HANA Cloud Public Edition all versions

Keywords

orderrequest, gln missing, supplier party, globallocationnumber, buyerpartyid, outbound xml, soap payload, edi purchase order, CO_EDI_ORDER_REQUEST_OUT, message schema, serialization, BUP005, business partner identification, SAP_COM_0224, SAP_COM_0828 , KBA , MM-PUR-GF-EDI-2CL , Electronic Data Interchange (Public Cloud) , 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.