MRCSAL1 - Load/Copy/Merge MDS Quantity Does Not Match Source Forecast Current Quantity (Doc ID 2293997.1)

Last updated on AUGUST 04, 2017

Applies to:

Oracle Materials Requirement Planning - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Master Demand Schedule in Test:

Users are running Load/Copy/Merge MDS (MRCSAL1) and they are loading ONLY the Current Quantity (ie consumed forecast) from a given forecast. However after the concurrent request completes successfully, there are many discrepancies between the qty loaded in the MDS and the Current qty in the Forecast. Example data:

Parameters for Load/Copy/Merge MDS
===========================
Destination Schedule = MDS-FS
Source Type = Specific Forecast
Source Organization = SY1
Source Name = FORECAST
Include Sales Orders = No sales orders
Sales Orders Demand Class is NULL
Demand Time Fence = Ignore demand time fence
Overwrite = All entries
Start Date = 01-AUG-2017
Cutoff Date = 01-FEB-2019
Explode = No
Quantity Type = Current
Consume = No
Everything else = 0

Debug Log file appears to show forecast consumption still occurring during Load/Copy/Merge MDS even though Consume parameter above = No
=======================
Compute sales order changes has started
The value of profile option 'MRP_COMPUTE_SO_CHANGES' is Y
Compute sales order changes completed 0:00
Before Starting Planning MGR Proc (FC)...

forecast consumption has started
The value of profile option 'MRP_FORECAST_CONSUMPTION' is Y

Org Mfg Calendar is 4/4/5 which is supported quarterly calendar type

Example data:
========
Item= JMFcst
Org = SY1

Date MDS Qty Fcst Qty
====== ========= =========
21-AUG-2017 2 0
28-AUG-2017 7 0
and problem continues for other buckets. There are times when it would be expected that Forecast Current Qty does not match with what's loaded in the MDS since the Planning Manager performs consumption on a 24x7 basis while the Load/Copy/Merge MDS may only be run once per day. The discrepancies found in this issue were glaring and not attributable to when it was run and compared with the forecast

EXPECTED BEHAVIOR
-----------------------
Expect the Qty in the MDS to match the Current Quantity in the Forecast from which it was loaded

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup forecast and create sales orders which are consumed in the Forecast
2. Load the forecast into the MDS and set parameter Quantity Type = Current and Consume = No
3. Run Load/Copy/Merge MDS
4. Review of MDS and Forecast data shows the Qty in the MDS and Current Qty in the forecast are way off for many buckets

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