Unconstrained Supply Planning: Supply Planning Snapshot and Plan Output Information and Troubleshooting Document
(Doc ID 2662425.1)
Last updated on MAY 18, 2023
Applies to:
Oracle Fusion Planning Central Cloud Service - Version 11.13.17.05.0 and laterOracle Supply Planning Cloud Service - Version 11.13.17.05.0 and later
Information in this document applies to any platform.
Purpose
This document provides information about Supply planning Snapshot and plan output related setups, Common Issues, Frequently asked questions (FAQ) and Troubleshooting tips.
Scope
The functionality described in this document is applicable to Fusion Supply Planning Cloud
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| Introduction |
| Factors Impacting Snapshot Data |
| Frequently Asked Questions (FAQ) |
| How supplier calendar is snapshotted in the plan Or how to exclude weekends while calculating supplier lead time. |
| What is maximum value for supply network model parameter “Past due supply days” |
| How to View Supplier Schedule Data in Supply Planning |
| Can Purchase Requisitions and Purchase Orders created manually in Purchasing be rescheduled from Planning? |
| Can supply plan use forecasted planning percentages? |
| Is it possible to view sales orders in a plan if Sales Orders is unchecked in the 'Demand and Supply Netting' options? |
| What is Default calendar for pivot table? |
| How to identify if plan was run with Refresh with Current Data or Do not refresh with current data? |
| Transfer order is created with both source and destination inventory as non nettable. Plan is not considering TO as supply in destination org while considering same as demand in source org. |
| Why Supply plan pulls dependent demand from measure 'Final Option Demand Forecast' even though Option Demand LOV in demand schedule has "Null" value. |
| How to use fractional lead times in supply plans. For example intransit lead time for 2.5 days defined between 2 organizations. |
| REST API - Sample Payload to Create and Update Supplies |
| Common Issues & Errors |
| Item in a certain organization is not included in the plan. |
| Scheduled Receipt and Purchase Order are in different time buckets. |
| Resource requirement and Resources do not have data under supply plan. Resource data is available in plan inputs but missing from plan output. |
| Forecast is collected but not included in the plan. |
| Incorrect Planning Time Fence (PTF) Date calculation for Buy Items. |
| Newly defined subinventories do not show in plan options as well as in plan output. |
| Transfer Order collected from external source is not considering in transit lead-time to calculate suggested due date in source org. |
| Item description is changing for same item in "Items" table in Supply Planning. |
| Plan is not honoring the FOQ or any other attribute change specified in the Simulation Set. |
| Sales Order Quantity is Zero in Supply Plan. |
| Past due closed sales order coming in Supply Plan. |
| Plan comparison is not showing other supply plan in the list of plan to compare. |
| Parent model not populated in Supplies and Demands Table. None of the configured items have the value Parent Model populated in Supplies and Demands table |
| Ineligible Status For Purchase Order Recommendations |
| Transfer Order supply not included in plan output for destination org where as transfer order demand is available for source org in plan output. |
| Getting error "requested operation can be performed only on externally managed requisitions" when trying to reschedule a PR. |
| Work definition (Routing) is available in Plan inputs but missing from Plan output routing table. |
| Why Suggested Due Date changed after plan run compared to Plan Inputs? |
| MRP Plan not getting demand from MPS supply plan. |
| User has created supply plan and selected Supply Planned Item Type=Production Plan. However, in plan output, MRP items can be seen. |
| Sales Orders with ATO items are not included in plan output, even though they show collected in Plan Inputs. |
| Plan start date comes as yesterday's date. |
| Transit Time is not considered for manually created Purchase Order. |