01Freeze the controlling order and schedule baseline
Record buyer entity, supplier legal entity and site, purchase order and revision, line and schedule, item or service, quantity, unit, ship-to, Incoterms or other handoff term where applicable and current status. Capture the buyer requested date, supplier acknowledged date, current promised ship date, current promised delivery date and internal need-by date as separate fields. Identify which dates are contractual, planning estimates or internal targets under the actual agreement. Link the acknowledgment or change that established the present baseline. Do not edit the old date before review. A screenshot of the current screen alone may hide prior revisions; retain the event or document history and its effective time.
02Authenticate and scope the supplier proposal
Receive the change through a validated supplier portal, B2B message, known business contact or other approved channel. Record message ID, acknowledgment code, supplier order number, sender, time zone, receipt time, reason and attachments. Confirm affected line, schedule, quantity and destination. Oracle documents supplier acknowledgments that can accept, reject or modify orders and create a supplier-initiated change order; use the concept without assuming every portal applies the update automatically. Separate a forecast, warning, requested change and confirmed commitment. If a message appears inconsistent with supplier identity, bank, product or site records, verify independently before acting. Keep unrelated commercial data out of shared escalation copies.
03Translate the date into real milestones
Ask which event the proposed date represents: material ready, production complete, inspection available, ex-works handoff, carrier pickup, port departure, arrival, customs release, warehouse delivery or acceptance. Record the time zone, calendar, delivery window and whether the date applies to all or part of the quantity. Check weekends, holidays, booking lead time and known route constraints without inventing certainty. A promised ship date and promised delivery date are distinct fields in Oracle's documented purchase-order acknowledgment mapping. If the supplier provides only one date, document the missing milestone and the assumption that remains prohibited. Recalculate any arrival estimate from named inputs and keep it separate from the supplier's explicit commitment.
04Assess inventory, customer, cost and quality impact
Compare the change with on-hand usable stock, open inbound, customer orders, launch or promotion dates, production dependencies, safety stock policy, warehouse appointments and cash plan. Quantify the affected quantity and the date gap under the business calendar. Review whether expediting, a transport change, split shipment, alternate supplier, allocation or cancellation would create inspection, packaging, rights, compliance, cost or quality consequences. Do not approve an unvalidated substitute or skip an agreed control only to restore the date. Identify the last responsible decision time: a late response can remove options even when the new date is not yet final. Show best supported, expected and adverse cases when transit or production evidence is incomplete, clearly labeled as scenarios rather than promises.
05Accept, reject, counter or split with authority
Present the original baseline, supplier proposal, evidence, impact and options to the authorized buyer or contract owner. Decide at schedule level: accept the new date, reject it and retain the existing obligation, counter with another date, split quantities across dates, change another term, cancel under authority or open a dispute. Oracle documentation shows that suppliers may split lines and that changes outside configured tolerances can enter approval workflow; actual rights and tolerances come from the controlling agreement and system. Record decision time, approver, conditions, cost ownership and required supplier response. Silence is not acceptance unless the applicable process explicitly makes it so. Keep a rejected proposal visible and give the supplier a next response date.
06Issue the approved version and update dependencies
Create or approve the formal purchase-order change, acknowledgment or schedule revision with a unique version and reason. Confirm the supplier received or accepted it through the required channel. Update material planning, expected receipts, warehouse or dock appointment, inspection booking, freight plan, cash forecast, customer allocation and internal alerts from that approved version. Prevent interfaces from applying both the proposal and later approval as two changes. Preserve the original requested and supplier-promised dates used for performance measurement even when the current operating date moves. A revised plan should not retroactively make the original delivery on time. If systems use different date names, maintain a field map and reconciliation owner rather than copying one value into every field.
07Monitor the revised commitment and learn from changes
Set evidence milestones before the new date: material, production, inspection, booking, dispatch or another relevant event. Compare actual progress with the approved revision and trigger escalation before the next option expires. Reconcile affected quantities to shipped, received, canceled, replaced and still open. Monitor date-change frequency, days moved, changes after cutoff, repeated reason, response time, split schedules and delivery against both original and revised commitments. Separate supplier-caused, buyer-caused, transport and force-event classifications only when supported. Feed confirmed results to OTIF or supplier review with the documented denominator and exclusion policy. Close when the active PO schedule, supplier position and downstream plans agree, or when an unresolved dispute has a named owner and date.