cancel
Showing results for 
Search instead for 
Did you mean: 

SAP S4 HANA TM Business partner internal ID does not exist.

Prakashd
Explorer
0 Kudos
1,535

S4 HANA 2020 TM DTR Issue with Business partner internal ID does not exist.

We copied Production Client to training client. We changed the Business System names and logical system names using BDLS. Verified the master data Business partner and locaitons exist.

In the inbound processing of the service IntracompanyTransportationRequestRequest_In in SAP Transportation Management (S4 HANA TM), the system issues error message /SCMTMS/TRQ 259: " Business partner internal ID does not exist.", although the relevant master data was transferred from SAP ECC to SAP TM. Did anyone face the same issue.

Business partner internal ID does not exist.

Location sp_x (type: 1003) does not exist .

Accepted Solutions (1)

Accepted Solutions (1)

former_member809312
Contributor
0 Kudos

Hi Prakash,

The logical business system id should be updated via the BDLS transaction after you copy/clone an existing system.

Oss note:2677204 - Business partner internal ID *** does not exist (/SCMTMS/TRQ 259) in Transportation Manage...

Regards

Rogerio

Prakashd
Explorer
0 Kudos

Yes we completed the BDLS task after copying.

Prakashd
Explorer
0 Kudos

We also changed the Business System names but Business Partner and Location are having issues.

IntracompanyTransportationRequestRequest_In in SAP Transportation Management (SAP TM), the system issues, for example, error message /SCMTMS/TRQ 259:

" Business partner internal ID does not exist.",

Location 1201 (type: 1003) does not exist .

former_member809312
Contributor
0 Kudos

check if the Shipping point/ Customer you have on the XML exist as location in TM.

Prakashd
Explorer
0 Kudos

Yes the Business partners and location data exists in TM on S4 HANA.

former_member809312
Contributor
0 Kudos

The Location on XML must be the same on TM side also with the Location type.
Check if all the dates adress, number etc ,are in TM side is the same from the Source system you're replicate.

Prakashd
Explorer
0 Kudos

We fixed the issue by resetting key mapping of master data for Business Partners and location using the tcode MDG_ADJUST_IDM. The copying of client data in TM we need to do this as post copy step.

https://blogs.sap.com/2018/07/17/key-mapping-in-master-data-management/

Answers (1)

Answers (1)

0 Kudos

Hi Prakash,

have you checked, if the customer / vendor has assigned the same number in SAP TM as in ECC after replication?

Prakashd
Explorer
0 Kudos

Since we copied all master data, the numbers for Customer and Vendor are same.