D365 SCM: Architecting 360-Day ATP in Inventory Visibility

New features, release waves and version/service updates · 12 min read
TL;DR: The Inventory Visibility Add-in now supports an Available-to-Promise (ATP) schedule period of up to 360 days, unlocking instantaneous, full-year order promising for long-lead supply chains without placing load on core D365 SCM database tables.
Supply ChainArchitectureRelease UpdatesIntegrationD365 F&O

Supply chain leaders managing capital equipment, automotive components, and seasonal retail face an identical constraint: traditional Available-to-Promise (ATP) calculations either rely on sluggish batch Master Planning runs or hit arbitrary horizon ceilings in real-time inventory services. If your procurement lead times extend between six and twelve months, order promising beyond the previous 180-day microservice window meant falling back to manual allocations or uncommitted backlog queues. With the Inventory Visibility Add-in expanding its ATP schedule period to 360 days, solution architects can now run instantaneous, omnichannel supply commitments across an entire annual planning horizon without compromising Dynamics 365 Supply Chain Management performance.

At a glance

  • 🔹 Applies to: Dynamics 365 Supply Chain Management (10.0.x), Inventory Visibility Add-in, Microsoft Dataverse.
  • 🔹 Prerequisites: D365 SCM linked with Dataverse via Power Platform Integration; Inventory Visibility Add-in installed; Entra ID application registered for service-to-service authentication.
  • 🔹 Effort level: Low to Medium configuration; requires updates to the Inventory Visibility Power App parameters and integration mappings.
  • 🔹 Outcome: Real-time, sub-second ATP schedule queries covering up to 360 calendar days into the future, eliminating long-range order promising blind spots.

How it works

The Inventory Visibility Add-in is an independent, hyper-scalable microservice hosted within Microsoft Azure that tracks real-time inventory changes across multi-channel environments. Unlike standard ERP table locks that degrade database performance under heavy concurrency, Inventory Visibility offloads inventory updates to an optimized memory store backed by Microsoft Dataverse. When calculating order feasibility, the service evaluates daily supply and demand quantities through an On-hand change schedule, aggregating transactions into discrete daily buckets.

The core of this engine is the Available to Promise (ATP) calculation model. ATP represents uncommitted inventory that can be safely promised to customer orders on specific future dates. The service calculates ATP using predefined or custom Calculated Measures, where incoming inventory (purchase orders, production orders, inbound transfers) uses an addition modifier, and outbound commitments (sales order lines, transfer order issues, soft reservations) use a subtraction modifier. A strict architectural rule governs this model: the total number of distinct physical measures across all active ATP calculated measures must remain fewer than nine to prevent computational degradation in the microservice.

Previously capped at 180 days, the Max schedule period (days) parameter now supports values up to 360 days (default remains 30 days). The scheduling period begins on the current transaction date ($Day_0$) and extends through $Day_{N-1}$, allowing 360 discrete daily availability snapshots. When an external e-commerce engine, point-of-sale terminal, or D365 SCM sales order line triggers a schedule query, the microservice returns cumulative daily ATP values along with planned inbound and outbound deltas for each day in that 360-day window.

360-Day ATP Evaluation and Soft Reservation Flow
Figure 1: Figure 1: Architectural sequence of a 360-day real-time ATP query and soft reservation.
Capability Dimension Inventory Visibility (360-Day ATP) Inventory Visibility (Legacy 180-Day) Planning Optimization (CTP / ATP)
Query Latency Sub-second (REST API microservice) Sub-second (REST API microservice) Minutes to batch-cycle dependent
Max Schedule Horizon Up to 360 calendar days Capped at 180 calendar days Configurable via coverage time fences
Omnichannel Concurrency High (scalable microservice architecture) High (scalable microservice architecture) Low (bounded by ERP SQL throughput)
Soft Reservation Support Native real-time reservation locks Native real-time reservation locks Requires D365 SCM inventory reservation
Physical Measures Limit Fewer than 9 distinct measures Fewer than 9 distinct measures Standard D365 inventory status model
📝 NoteThe schedule period always includes the current date. Setting the parameter to 360 allows queries and schedules from today through exactly 359 days in the future. Any transaction submitted past Day 359 is rejected by the service validation rules.

Step-by-step solution

1. Verify Add-in Installation and Dataverse Linking

Ensure that your target Supply Chain Management environment is properly linked to a Dataverse instance in the Power Platform admin center. Verify that the Inventory Visibility Add-in is listed as installed under your environment add-ins. Confirm that the Microsoft Entra application registration has been granted proper service principal rights to read and write to the Inventory Visibility Dataverse entities.

2. Enable On-Hand Change Schedule in the Power App

Sign in to Power Apps and open the model-driven Inventory Visibility app in your tenant environment. On the navigation pane, select Feature management. Locate the Available to promise tile, select Manage, and toggle the Enable feature switch to True.

3. Configure the 360-Day Schedule Period

Within the Available to promise configuration form, locate the field labeled Max schedule period (days). Change the value from the default of 30 (or previous ceiling of 180) to 360. Select Save to commit the configuration change to Dataverse.

⚠️ Watch outIncreasing the horizon to 360 days increases the payload size of scheduled query responses. Ensure integration middleware (such as Azure API Management, Azure Logic Apps, or custom microservices) accounts for larger response arrays containing up to 360 daily node objects.

4. Review and Consolidate ATP Calculated Measures

Navigate to Configuration > Calculated Measures within the Inventory Visibility app. Review your primary ATP calculation (typically named atp). Ensure the total count of distinct physical measures across all active ATP calculations remains below nine. For example, use standard mappings for additions (fss.pos_onhand, fss.pos_ordered) and subtractions (fss.pos_sold, fss.pos_soft_reserved).

5. Update ATP Index Set Hierarchies

In the ATP Index Set Configuration section, verify that your dimension hierarchy aligns with your business commitment levels. Common practice sets the index hierarchy to SiteId*LocationId*InventoryStatusId. Restricting the index to necessary fulfillment dimensions optimizes indexing performance over the 360-day horizon and prevents memory bloat.

6. Configure D365 SCM Data Synchronization Batch Jobs

In D365 SCM, navigate to Inventory management > Periodic tasks > Inventory Visibility integration. Ensure the recurring batch job Inventory Visibility integration is running with appropriate recurrence intervals (typically every 1 to 5 minutes). This service job pushes confirmed purchase orders, production line receipts, and sales line updates to the microservice change schedule.

7. Update External API Query Payloads

Update external calling applications (such as custom B2B portals or order management systems) to query the 360-day availability schedule using the REST endpoint. External systems should pass the appropriate JSON filter payloads specifying the product and dimension parameters.

POST https://inventoryservice.{region}.gateway.prod.island.powerapps.com/api/environment/{environmentId}/onhand/changeschedule/query
Content-Type: application/json
Authorization: Bearer {token}

{
  "filters": {
    "organizationId": ["usmf"],
    "productId": ["GEN-TURB-01"],
    "dimensions": {
      "SiteId": ["1"],
      "LocationId": ["11"]
    }
  },
  "groupByValues": ["SiteId", "LocationId"]
  
}
💡 Pro tipAlways specify when executing the query. If omitted, the service aggregates quantities over the entire horizon into a single sum rather than providing daily buckets needed for dynamic delivery date promising.

Worked example

Contoso Industrial Solutions manufactures high-capacity industrial power turbines and gas generators. Their core generator model, GEN-TURB-01, has specialized rotor assemblies sourced from international suppliers with typical procurement lead times of 240 to 300 days. Under the previous 180-day limitation in Inventory Visibility, B2B sales engineers could not promise delivery dates for large enterprise projects closing in Q3 and Q4 of the operational year without initiating offline planning reviews.

Contoso implemented the 360-day ATP capability in Inventory Visibility. They configured an ATP calculated measure composed of physical supply measures (fss.pos_onhand, fss.pos_purchased, fss.pos_ordered) minus demand measures (fss.pos_sold, fss.pos_softreserved), maintaining five physical measures—well below the architectural limit of nine.

When an engineering client requested 25 units of GEN-TURB-01 for delivery 275 days from today, the custom quoting portal issued an automated REST query against Inventory Visibility. The service returned the daily schedule array:

{
  "products": [
    {
      "productId": "GEN-TURB-01",
      "dimensions": {
        "SiteId": "1",
        "LocationId": "11"
      },
      "dates": [
        {
          "date": "2026-03-01T00:00:00Z",
          "onHand": 4,
          "scheduleChanges": {
            "fss.pos_purchased": 0,
            "fss.pos_sold": 0
          },
          "atp": 4
        },
        {
          "date": "2026-11-15T00:00:00Z",
          "onHand": 4,
          "scheduleChanges": {
            "fss.pos_purchased": 30,
            "fss.pos_sold": 0
          },
          "atp": 34
        }
      ]
    }
  ]
}

The calculation identified that an incoming purchase order of 30 units arriving on Day 258 (November 15) raised cumulative ATP to 34 units. The portal executed an immediate soft reservation for 25 units at SiteId: 1, locking the allocation across all regional channels in real time. When the sales contract finalized, D365 SCM absorbed the soft reservation via standard data sync, eliminating inventory conflict and preventing double commitments.

Contoso Turbines: Order Promising Performance Before vs After 360-Day ATP
Figure 3: Operational impact at Contoso Industrial Solutions after deploying the 360-day Inventory Visibility ATP model.
-99%
Promising Latency
360 Days
Commitment Horizon
-82%
Long-Lead Stockouts
-81%
Order Line Rework

Automation and AI opportunities

Expanding the schedule horizon to 360 days creates significant opportunities to introduce automation and conversational AI into procurement and order commitment flows.

Microsoft Copilot Studio Agents: Customer service and enterprise sales reps can use a Copilot agent grounded on the Inventory Visibility REST API. When a customer asks, "Can we take an order for 50 commercial transformers in October?", the agent invokes an action calling the 360-day change schedule endpoint. Copilot evaluates daily cumulative ATP arrays and returns the exact confirmed ship date directly in Teams or Dynamics 365 Customer Service workspace, without requiring the user to open D365 SCM.

Automated Power Automate Long-Lead Allocations: You can build automated cloud flows triggered by Dataverse business events. When a 360-day schedule query detects that projected ATP drops below a safety buffer between Day 180 and Day 360, Power Automate can automatically create a planned purchase order requisition in D365 SCM or send an adaptive card alert to the global commodity planner.

Power BI Long-Range Availability Heatmaps: By querying the Inventory Visibility Dataverse endpoints on a scheduled basis, BI teams can construct 52-week inventory availability heatmaps. Supply chain managers gain visibility into projected stock surplus and deficits across product families across an entire fiscal year.

Common pitfalls and troubleshooting

1. Exceeding the Physical Measure Threshold

Symptom: The Inventory Visibility app returns validation errors upon saving the ATP calculation, or queries fail with internal HTTP 500 exceptions.
Cause: The configuration contains nine or more distinct physical measures across all active ATP calculated measures.
Fix: Consolidate your physical measures. Review custom data sources and combine status fields (for example, merge separate inspect and quarantine counts into a single non-available status) so the distinct count across additions and subtractions remains strictly under nine.

2. Boundary Date Truncation on Day 360

Symptom: Transactions scheduled exactly one year out fail to reflect in ATP responses or produce validation errors during change posting.
Cause: The schedule horizon includes the current date ($Day_0$). Transactions scheduled for $Day_0 + 360$ fall outside the supported 360-day window (which terminates at $Day_0 + 359$).
Fix: Ensure your integration middleware calculates date fences using AddDays(today(), 359) rather than 360 full days into the future.

3. Memory Pressure and Query Throttling

Symptom: External API clients receive HTTP 429 (Too Many Requests) when issuing batch 360-day ATP queries.
Cause: Running wide queries without dimension filters over a 360-day horizon forces the microservice to build massive daily schedule graphs across all warehouse locations.
Fix: Refine query parameters. Always supply specific productId values and dimension filters (such as SiteId). Avoid open queries across entire item groups when retrieving daily schedules.

4. Time Zone Shift Across Daylight Saving Boundaries

Symptom: Quantities scheduled around annual seasonal changes appear shifted by one day forward or backward.
Cause: Calling systems submit transaction dates in local time rather than Coordinated Universal Time (UTC), causing date-bucket misalignment across a 360-day span.
Fix: Standardize all external posting payloads and query date filters to UTC format (YYYY-MM-DDTHH:mm:ssZ) before calling Inventory Visibility endpoints.

5. D365 SCM Synchronization Latency

Symptom: A purchase order confirmed in D365 SCM with a delivery date 200 days out does not appear in the ATP schedule.
Cause: The Inventory Visibility integration batch job in SCM has either stalled, failed with token expiration, or has a recurrence interval that is too slow.
Fix: Navigate to System administration > Inquiries > Batch jobs. Verify the execution status of the Inventory Visibility sync job. Check the Microsoft Entra token validity and ensure recurrence is set between 1 and 5 minutes.

Best-practice checklist

  • ✅ Set the Max schedule period (days) strictly to what your longest lead-time item requires; do not default to 360 days if your business operates within a 60-day fulfillment window.
  • ✅ Audit ATP calculated measures to ensure distinct physical measures stay well below the maximum limit of nine.
  • ✅ Always pass in your REST API query payload when temporal ATP bucket analysis is required.
  • ✅ Use precise dimension filters (SiteId, LocationId) in change schedule queries to minimize JSON payload size and API latency.
  • ✅ Standardize all outbound change timestamps to UTC to avoid daylight saving and cross-border date bucket skewing.
  • ✅ Implement automatic soft reservations immediately following a positive ATP query to avoid race conditions across channels.
  • ✅ Monitor the Inventory Visibility integration recurring batch job in D365 SCM to maintain sub-five-minute data parity.

FAQ

Does increasing the schedule period to 360 days degrade query latency?

For single-product and specific-dimension queries, latency remains well under one second because the Azure microservice stores aggregated daily indexes in high-performance memory cache. However, if external systems execute blanket queries without dimension filters, the response payload size increases significantly, which will increase network transfer times and JSON deserialization overhead.

Can we use 360-day ATP for soft reservations?

Yes. Soft reservations can be placed against any future date within the active schedule period. When a soft reservation is submitted for a future date, Inventory Visibility applies the reservation against that specific daily bucket and reduces ATP forward from that date onward.

How does this feature interact with Planning Optimization in D365 SCM?

Inventory Visibility operates independently as an omnichannel operational availability service, whereas Planning Optimization executes deep material requirements planning (MRP) across production bills of materials and supplier lead times. While Planning Optimization determines when materials should be ordered, Inventory Visibility provides the real-time execution gate for promising orders against confirmed inbound supply lines.

360-Day ATP Architecture Mindmap
Figure 2: Figure 2: Architectural components and governance pillars for the 360-day ATP engine.

Key takeaways

  • 🎯 The Inventory Visibility ATP schedule period ceiling is officially expanded from 180 to 360 calendar days ($Day_0$ through $Day_{359}$).
  • 🎯 Architects can now support long-lead supply chains (such as capital equipment, semiconductor components, and overseas procurement) with real-time, sub-second order promising.
  • 🎯 Ensure your ATP calculated measures strictly use fewer than nine distinct physical measures across additions and subtractions to remain supported.
  • 🎯 Always specify explicit inventory dimensions and pass UTC timestamps to optimize microservice throughput and avoid cross-calendar shifts.

Further reading

Note: written with AI assistance and reviewed by Gaurav Jadaun. Always validate in a sandbox environment before applying to production.

Comments

Popular posts from this blog

Monthly Inventory Close in Microsoft Dynamics AX 2012

Product Configuration Technology Ax2012R3

How to configure Fixed Assets Module in Ax2012