New Profile MSC: Number Of Historical Calendar Years Cached For Handling Pegging Dates More Than One Year Behind The ASCP Plan Anchor Date (Doc ID 1613515.1)

Last updated on JUNE 27, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.3.8 to 12.1.3.8 [Release 12.1]
Information in this document applies to any platform.

Goal

 

This document describes the details of new profile option for caching calendars more than 1 year. (From <Bug 17025720>)

Patch Description: In Memory Based Planner, all the past due orders are rescheduled out to the current date, thereby losing track of how far in the past the supply needs to be planned to meet demands. With this enhancement, MBP will calculate a past due date for each supply based on the lead times of all the downstream supplies it pegs to. This date will be stored in the Unconstrained Latest Possible Completion Date column. This date is also propagated down to dependent demands and will be used for pegging past due supplies to past due demands. A new internal profile 'MSC: Number Of Historical Calendar Years Cached' is introduced and this needs to be set to number of years in the past for which these past due dates are to be calculated.

 

User Profile Name

 MSC: Number Of Historical Calendar Years Cached

 

 

Name

 MSC_CAL_HIST_TO_CACHE

Default Value

1

The value defaults to 1- if the profile is not created or is set a non-numerical value.

Valid Values

 Any numerical value. Internally, the minimum value is always 1 year

 

Need for this new profile

The calendars in ASCP are cached 1 year in the past. Calendar functions used to get working dates based on offsets, working days between two days, previous and next working days etc - all access this cache.  

With the enhancement to handle pegging in the past, the original dates in the past are retained for pegging.  The orders could be beyond one year in the past. To compute pegging dates, the calendar functions are used. These functions must return the correct dates for dates that are more than one year in the past.

For this purpose, calendar cache should have entries more than one year into the past. To reduce the overhead in storing additional entries for calendars, a new profile option is introduced. This defaults to 1 year and the current behavior is not affected. For customers, with orders more than 1 year in the past and who need to handle pegging in the past, this value can be set appropriately. This is an internal profile.  Please note that setting this to high value can increase the memory requirement to cache the calendars. So, please limit it to a number less than 5 (maximum). This impacts the caching of ALL calendars used by the plan. This includes organization’s manufacturing/shipping/ receiving calendars, supplier’s delivery calendar, etc.

Solution

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