atp-ctp-check

Computes feasible order promise dates by netting ATP inventory and CTP build slots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales and order-management teams promise delivery dates against incomplete inventory views, producing optimistic commitments that turn into next month's expedites. This Skill provides the method to net available-to-promise inventory plus in-transit receipts against an order line, check capable-to-promise build slots in planning, and confirm only dates that are feasible and within lead-set promise limits. ## Core Features & Use Cases - ATP/CTP Netting Method: Computes date-fenced ATP (on-hand minus soft reservations, hard allocations, and safety stock) plus in-transit receipts, then routes any shortfall to a CTP inquiry against constrained build slots in Kinaxis, o9, or SAP IBP. - Priced Promise Options: Constructs and prices split-shipment, push-full-date, expedite, and infeasible-escalation options so the lead sees slip versus added freight cost for each. - Limit-Gated Confirmation: Auto-confirms promises only when slip, cost, freshness, quantity, and feasibility limits all hold; escalates everything else to the order-management lead with full reasoning. - Failure-to-Recovery Playbook: Covers stale planning data, double-counted stock across quotes, partial CTP slots, in-transit ETA slips, and partial OMS writes, with gated recovery steps. - Use Case: A 500-unit order line is requested in 14 days but only 180 units are truly available. The Skill nets the shortfall, finds a day-21 build slot, prices a split shipment, and auto-confirms it because it falls within the lead's slip and cost limits. ## Quick Start Ask the assistant to check whether a customer order line can be promised by its requested date using ATP and CTP, and to confirm or escalate the promise within the defined limits.

Frequently Asked Questions about atp-ctp-check

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

FAQPage Schema
How do I calculate available-to-promise for an order line?

ATP equals unrestricted on-hand minus soft reservations, hard allocations, and safety stock, plus inbound receipts with ETA on or before the requested date. Exclude blocked, quality-inspection, and consignment stock, and re-read the values at execute time since they drift between quote-open and confirm.

What is the difference between ATP and CTP in order promising?

ATP is the date-fenced promisable quantity from existing and inbound stock, while CTP checks planning for the next capable build slot when stock falls short. A CTP inquiry is read-only and reserves nothing until confirmed, at which point it reserves constrained capacity.

How do I handle an order line that inventory only partially covers?

Net the covered quantity from ATP, send the shortfall to a CTP inquiry for the next firm build slot, then price three options: split shipment, push the full date, or expedite. Confirm only the option that stays within the lead's slip and cost limits, and escalate the rest.

Why do promise dates become infeasible after quoting?

ATP and CTP data drift: other lines commit the same stock, inbound ETAs slip, and planning re-runs move build slots. Re-read availability at execute time and net only firm constrained supply, since planned-order slots are suggestions the engine can move.

When should a promise confirmation be escalated instead of auto-confirmed?

Escalate when the confirmed date slips past the max-slip window, added freight or expedite cost exceeds the limit, planning-to-ERP sync is stale, the line quantity exceeds the auto-confirm cap, or no feasible CTP slot exists. Correcting an already-written promise is always escalate-only.