Before buyers can begin submitting and managing Texas Instruments (TI) orders through SourceDay, the customer must complete several setup steps with TI and ensure the appropriate configuration in their ERP. This article outlines all requirements needed prior to enabling the integration.
Overview of what’s required
To use the TI API integration, customers must:
- Be configured as a TI Backlog Channel customer
- Request and securely share a TI API key and API secret
- Ensure TI part numbers and units of measure are correct in the ERP
- Complete UAT with TI and SourceDay before going live
Each requirement is explained in detail below.
1. Set up TI backlog channel access
TI must enable the customer as a Backlog Channel customer before SourceDay can place orders on the customer's behalf.
This step is completed directly with TI.
What this does:
- Allows SourceDay to send quote requests and order submissions using the TI Backlog API
- Enables real-time communication between the ERP, SourceDay, and TI
2. Obtain TI API key and API secret
After Backlog Channel setup is complete, TI will provide the customer with:
- API key
- API secret
These credentials give SourceDay secure access to send and retrieve information from TI on your behalf.
How to share credentials with SourceDay
Customers should provide the credentials to their SourceDay implementation contact or customer success manager using a secure channel. SourceDay will add these credentials to a new API Supplier Connection record in your SourceDay production environment.
3. Ensure TI part numbers are correct in the ERP
This is one of the most critical setup steps.
TI will reject quotes or orders if part numbers do not match TI’s system exactly.
ERP requirements
- TI part numbers must be present on the purchase order table in the ERP
- Part numbers must map into SourceDay’s mfg_part_number field
- Units of measure must match TI’s expectations
Why this matters
During the quote and order phases, TI validates all of the following:
- TI part number
- Quantity
- Price
- Units of measure
If any of these are incorrect or missing, SourceDay will display a processing issue risk, and the buyer must correct the PO in the ERP before SourceDay can re-submit it.
4. Complete user acceptance testing (UAT)
Once prerequisites are complete, a joint UAT cycle will be scheduled between:
- The customer
- SourceDay
- Texas Instruments
Testing ensures:
- TI credentials function as expected
- ERP part numbers sync correctly
- Quote and order workflows behave as expected
- Buyers can review and respond to TI proposed changes
- Error handling is validated
After testing, SourceDay will coordinate the move to the production API endpoint.
What SourceDay does with your credentials
After TI provides the API key and secret:
- SourceDay creates a new API supplier connection for TI
- Credentials are stored securely
- A migration call is scheduled with the customer’s IT team to move to the production endpoint
- Integration is enabled in production
No additional configuration is required by the buyer.
What happens if prerequisites are incomplete?
If any setup step is missing or incorrect, buyers may see issues such as:
- No TI quote number returned
- TI order not created
- Processing issue risks
- Rejected quote or order requests
- Missing or invalid part number errors
The buyer must update the PO in the ERP and allow SourceDay to resync the changes.