If you’ve landed on this page, chances are you have
recently received the following error from SPS:
Error Description: Unknown Trading Partner ID. SPS Commerce systems were not able to determine the receiver of the document based on the Trading Partner ID that was sent.
In order for SPS to send documents to your trading partner, we have a unique method of identifying who the document is intended for. We use what is called a Trading Partner Identifier, or TPID, that is linked to a specific trading partner relationship. Each trading partner you connect with is assigned a unique TPID.
For example, you may be setup to send and receive the 810, 850, and 856 documents with Customer X under trading partner ID 123ALLSPSCOMMER. The first 3 characters ‘123’ is Customer X’s identification number within SPS Commerce, and the other 12 characters represent your company.
How we determine TPIDs
1. You send SPS the complete TPID in your file. In the example data below, the complete TPID ‘123ALLSPSCOMMER’ is in the first field of a common csv formatted file.
2. The other way the trading partner ID is determined is by using what we call cross references, or XREFs. You send us a unique value that corresponds to a specific trading partner, and we change that value into a valid TPID. For example, below you may send us the value ‘8428’ which could be a customer number, account number, or other identification number within your ERP system for Customer X.
Internal ID = 8428
This internal ID 8428 is for Customer X, whose ID in SPS’s system is 87P.
We take the internal ID of 8428 and turn that into the TPID 87PALLSPSCOMMER.
Common causes of this failure
1. You are sending an invalid TPID. If you are setup to send the complete TPID in your file like example 1 above as 123ALLSPSCOMMER, it is possible the TPID is missing from your file or you are sending an invalid TPID. If you don’t send a valid TPID, this will cause a failure. Be sure to check the source file and ensure you are sending a valid TPID.
2. You are sending a value we do not have cross-referenced in our database. For example, if you recently added a new customer number for Customer X in your ERP system, SPS needs to setup a cross reference in our system so we can route the data correctly. Thus, when send the new internal ID of ‘8428’ we can assign it the corresponding TPID and route the data to the intended trading partner.
How to Correct and Prevent this Error
1. Are your TPIDs cross-referenced at SPS?
If you have recently added a new store location, customer number, or trading partner value in your system, please let us know the new value so we can update our database and work with you to ensure successful dataflow.
2. Do you send a complete TPID in your file to SPS?
If you send a complete TPID in your file to SPS, please ensure that you are sending the correct TPID and resend the document(s). If you are unsure of the correct TPID to send, you can verify the TPID of a previously successful document via the Ad Hoc Reporting tool within the SPS customer portal or contact Fulfillment Support.
3. Are you currently implementing this connection?
If you are in the process of implementing a new connection with this trading partner, please work with your implementation consultant to ensure the TPID is setup correctly.
4. Would you like to have this trading partner and document type setup in SPS?
If you are not setup to send this document to the intended trading partner via Integration Fulfillment, but would like to, please work with your Account Executive here at SPS to get the new connection process started.
Have Additional Questions or Need to Contact Us?
Production Inquiry: See the top right of this page for three convenient contact channels.
Implementation Inquiry: Contact your implementation consultant and/or project manager.
New Connection Inquiry: Contact your Account Executive.