SAP Knowledge Base Article - Preview

2370646 - Cannot identify BUPA by Standard ID in XML

Symptom

  • TM cannot identify a BUPA (Business Partner) by it's Standard ID.
  • The value of the <StandardID> element in an inbound B2B XML message is not recognized even though it is maintained.
  • You receive the following error: Partner &1 not found or conversion failed


Read more...

Environment

SAP TM - Transportation Management 9.0+

Product

SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023 ; SAP Transportation Management 9.0 ; SAP Transportation Management 9.1 ; SAP Transportation Management 9.2 ; SAP Transportation Management 9.3 ; SAP Transportation Management 9.4 ; SAP Transportation Management 9.5 ; SAP Transportation Management 9.6

Keywords

soa, standardid, xml, b2b, agency, code, bp, loc, business partner, carrier, scac, iata, duns, gln, schemeAgencyID, alternative id, service, /SCMTMS/TOR 483, TransportationOrderBookingWaybill_In,  "/SCMTMS/TRQ    258    Business partner standard ID &1 does not exist" , KBA , TM-FRM-INT , Integration of Documents with External Systems , TM-FWM-FWO , Forwarding Order , TM-BF-INT , Integration , 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.