confirmation-slip-reschedule

Pegs supplier confirmation slips forward through MRP to size and price reschedule options.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill confirmation-slip-reschedule-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: confirmation-slip-reschedule
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/business-workflows/confirmation-slip-reschedule
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill confirmation-slip-reschedule-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a supplier's EDI 855 order acknowledgment confirms a PO date later than promised, the shortage stays invisible until it becomes a line-down weeks later. This Skill runs the forward peg no one runs by hand the day the slip lands, sizes the exposure by week and by customer, and prices the reschedule options so the cheap-options window is used instead of missed. ## Core Features & Use Cases - Forward pegging and validation: Validates each EDI 855 (fresh, not duplicate, a real schedule change) and pegs the slipped receipt forward through SAP MRP to affected work orders and customer commitments, classifying each demand as hard or soft. - Exposure sizing and option pricing: Computes time-phased cover, nets the slip against safety stock and soft-date slack, and prices each path (accept and re-time, partial expedite, split, pull-in escalation, or hold and absorb) with explicit penalty exposure. - Gated execution: Stages the revised PO in SAP and the build-sequence change in Kinaxis as drafts, holding every committing write and outbound supplier notification for buyer approval. - Use Case: A supplier confirms a critical component three weeks late on a 5,000-unit PO. The Skill pegs forward, finds only a 900-unit slice truly exposed against a penalty-bearing customer commit, and recommends a partial expedite at +$95K instead of a +$180K full dual-source. ## Quick Start Ask the assistant to analyze a supplier confirmation slip on a PO and price the reschedule options for the affected customer commitments.

Frequently Asked Questions about confirmation-slip-reschedule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I respond to a supplier confirmation slip on a purchase order?

Validate the EDI 855 first (fresh, not a duplicate, a real schedule change), then peg the slipped receipt forward through MRP to the work orders and customer commits it feeds. Size the shortage by week, net it against safety stock and soft-date slack, and price each reschedule option before deciding.

How to decide between expediting and accepting a late PO delivery?

Compute net exposure after subtracting safety stock and soft-date flex; if it is zero, accept the slip and re-time rather than expedite. Only a non-zero net exposure against a hard commit justifies premium spend, and only for the covering slice, not the full PO quantity.

What is the difference between a hard and soft customer commitment?

A hard commit is a penalty-bearing or contractual customer commitment, or a firm-pegged MTO order, whose date cannot move without cost. A soft commit is internal build sequence or make-to-stock replenishment that can flex within downstream slack. Classification must be verified against contract terms, not due dates.

Does this workflow release the revised PO to the supplier automatically?

No. The revised PO is staged in SAP as a draft and the build-sequence change stays a Kinaxis scenario edit; every committing write and outbound supplier notification holds for buyer approval. Nothing binds money or reaches the supplier before a human approves.

Why does expediting a full PO quantity often overspend?

Safety stock and soft-date slack frequently absorb most of a slip, so only a small covering slice is truly exposed against hard commits. Expediting the full quantity pays premium on units the buffer already covers; the method prices only the exposed slice instead.

When should a confirmation slip not trigger a reschedule?

When validation fails (stale, duplicate, or no real schedule change), when the confirmed date does not slip past the committed need date, or when the forward peg finds no dependent demand. In each case the run terminates with a log entry and no reschedule is priced.