Backlog Management: Release Plan Common Issues and Frequently Asked Question
(Doc ID 2773841.1)
Last updated on APRIL 09, 2024
Applies to:
Oracle Supply Planning Cloud Service - Version 11.13.20.04.0 and laterInformation in this document applies to any platform.
Purpose
This document provides information about Backlog Management Release Plan Common Issues and Frequently asked questions (FAQ).
Scope
The functionality described in this document is applicable to Fusion Backlog Management 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 |
Frequently Asked Question |
Why Backlog Management Planning Scheduling Sales Orders to the Plan's End Of Horizon? |
In backlog management, what are the best practices to avoid too many orders being planned to the end of horizon? |
Schedule ship date is not getting updated in OM and not able to update through Manage Conditions |
After Release the plan in Backlog Management the status in sales order are not update |
The REST API of Release process should have the capability to release only the marked for release demand to OM. |
Why backlog management is not releasing a planned date that has a horizon of 2000 days? What is the maximum horizon days? |
Common Issues and Errors |
Backlog Management: Plan Run does not populate Release Status which causes no sales order recommendation file to be generated after 20C Update. |
Planned ship date is not updating on sales order lines after releasing the line |
Release recommendations from backlog management for PTO items not working as expected. |
Error while releasing ASL items from Planning. |
Last_updated column not updated in Order Management after BM release |
Release plan is not updating sales orders in Order Management |