Texas Instruments (TI) uses two different date fields when processing orders: the Customer Request Date (CRD) and the Estimated Delivery Date (EDD). SourceDay manages both values automatically and keeps them updated throughout the quote and order process.
This article explains how due dates are sent to TI, how TI responds, and how SourceDay updates the dates that buyers see.
How due dates work during the quote phase
When a purchase order (PO) syncs into SourceDay:
- SourceDay sends the ERP due date to TI as the Customer Request Date (CRD)
- During the quote phase, TI does not evaluate or consider the due date
- TI only validates part number, price, quantity, and units of measure at this stage
If TI accepts the quote, the order proceeds to the order phase.
How due dates work during the order phase
After TI accepts the quote and SourceDay submits the order:
- TI evaluates the CRD
- If TI can meet the CRD, they return the official TI order number
- If TI cannot meet the date or wants to provide a different target, they may include an Estimated Delivery Date (EDD)
EDD is only returned during or after the order phase.
EDD vs. CRD explained
Customer Request Date (CRD)
- Comes from the customer’s ERP
- Sent to TI by SourceDay
- Can be updated by the customer before the order ships
- Updates resync to TI through SourceDay
Estimated Delivery Date (EDD)
- Comes from TI
- May appear after the order is placed
- Updated during TI’s daily status checks
- Overrides CRD in SourceDay if TI provides an EDD
How SourceDay updates due dates after order placement
Once the order is placed, SourceDay performs a daily TI status check at noon CST.
During the daily check, SourceDay looks for:
- EDD changes
- New CRD acknowledgments
- TI date updates or constraints
If TI provides an EDD:
- SourceDay displays the EDD in the TI column
- Buyers see updated dates in PO Collaboration
- Changes may trigger a proposed change risk if TI suggests a date outside the original CRD
What happens if the buyer updates the due date in the ERP
If the ERP due date changes before the order ships:
- The new due date syncs into SourceDay
- SourceDay sends the updated CRD to TI
- TI may respond with:
- Acceptance
- A new EDD
- A proposed change
If TI sends a change, SourceDay generates a proposed change risk for the buyer.
What happens after shipment
Once TI indicates the order has shipped:
- TI stops updating delivery dates
- SourceDay no longer sends CRD updates
- The final EDD remains as the order’s delivery reference
At this stage, buyers rely on shipment confirmations provided outside of TI’s backlog API.
When buyers need to take action
Buyers need to respond when:
- TI proposes a different delivery date
- There is a discrepancy between CRD and EDD
- A proposed change risk appears
- A processing issue risk indicates an invalid date format
All actions are taken via the Accept/Propose Change action in SourceDay.