ASCP Workbench - MRPRSHPO Reschedule PO Fails and Do Not Understand Why Lines are Failing - Improved Messages

(Doc ID 1081378.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.0.4 to 12.1 [Release 12 to 12.1]
Information in this document applies to any platform.
Executable:MRPRSHPO - Reschedule PO
***Checked for relevance on 15-MAY-2014***



Symptoms

R12.0.4 or 12.0.6 and 12.1

PROBLEM
-------------
PO rescheduling is not working as expected.

1. Changes to Implementation Date are not being passed.

2. When lines are changed, the expectation is that line could fail validation in PO reschedule API will not reschedule the line. When failure occurs, then we should get correct log messages, Warning from the Concurrent request.

Plan was setup to have all lines suggest reschedule message
All PO and Release have both Promise Date and Need By Date populated.
Only line 3 of the PO and line 3 of the blanket release were not changed after we collected data to run the plan.

So expectation is that only line 3 would reschedule successfully.

After PO Reschedule was run
The dates changed for line 1,2 and 4
Line 3 was the only line that was not altered after collections was run
The line 1 where we changed the NEED BY Date was updated during PO reschedule
Lines 2 and 4 were we changed the PROMISE Date - this lines did not change during PO reschedule.

When line fails, nothing is reported in the log file that helps us understand which lines failed.

This happened for both the Blanket Release and the PO

I also tested this with profile MSC: Purchase Order Dock Date Calculation Preference - Need By Date and outcome did not change (which was expected result - this profile should not influence how PO reschedule works)

SUMMARY
---------
This is primarily a PO issue.

PO needs to review the PO API functionality and explain how the validation features work and do not work.

PO team should also explain why no messaging is returned in the PO application in case of failure to update when using the PO API.

STEPS
--------
Create PO with 2 lines and populate need by and promise date
Create demand that has different date to make reschedule happen in planning
Run collections, run ASCP plan, observe reschedule message
In PO application, Change Need by Date on one line, Promise date on other line
- save and re-approve the PO
Release ASCP reschedule messages
See that PO with Need by date change is updated - Need by date is put to reschedule date
PO line with Promise Date change is NOT updated

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms