11/22/22, 1:05 PM Document 1324086.

1
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

Memory-Based Snapshot (MSCNSP) or Memory Based Snapshot 64-bit (MSCNSP64) Errors With
APP-FND-01564, ORA-01405, Begin msc_snapshot_pk.calculate_plan_buckets (Doc ID
1324086.1)

In this Document

Symptoms
Cause
Solution

APPLIES TO:

Oracle Advanced Supply Chain Planning - Version 11.5.10 and later

Information in this document applies to any platform.

Executable:MSCNSP - Memory-Based Snapshot

SYMPTOMS

Users are running an ASCP plan. However it fails with the following errors in MSCNSP - Memory Based Snapshot or any of the
64 bit Memory Based Snapshots for HP, HP Itanium, Sun, Linux, IBM AIX

before call to calculate plan buckets=20

APP-FND-01564: ORACLE error 1405 in
main

Cause: main failed due to ORA-01405: fetched column value is NULL

The SQL statement being executed at the time of the error was: begin =

=
msc_snapshot_pk . calculate_plan_buckets ( :plan_id , :err_mesg: and was
executed from the file .

APP-MRP-22075: An internal error has occurred (main, 1, , )

STEPS:

1. Navigate to Responsibility > Advanced Supply Chain Planner.

2. Run an ASCP Plan

3. The Memory Based Snapshot ends with multiple errors

CAUSE

There are multiple causes for this issue

1.  There's a Calendar defined with an End date near to the Planning Horizon End date.

Plan buckets are calculated based on Mfg Calendars. If the buckets , days , weeks , periods , i.e. Planning horizon is given with
a end date greater than the end date in the calendar, the plan buckets will not be calculated..

2.  ASCP Profile 'MSC: Calendar Reference for Bucketing' may have the wrong calendar selected or is NULL

3.  If the instance was recently cloned, the profile' MSC: Calendar Reference for Bucketing' shows the wrong instance code but
has the correct calendar name

SOLUTION
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w24x164x3_53&id=1324086.1 1/3
11/22/22, 1:05 PM Document 1324086.1

Review the following solutions and apply the most appropriate:

A.  One or more calendars are not built out at least 5 years in the future

1. Navigate to Responsibility Inventory > Setup > Organizations> Calendar.

2. Query up your calendar.

3. Change the end date to a later date say 2020.

4. Navigate to Tools > Rebuild.

5. A concurrent request would get launched to rebuild the calendar.

6. Once this is completed successfully, run Data Collections with Complete Refresh.. so that the Calendar changes are
collected.

7. Run the Plan once you have finished with Data Collections.

B.  Profile MSC: Calendar Reference for Bucketing is not setup correctly.

1. Set the profile option MSC: Calendar Reference for Bucketing to the calendar which you want to use for the plan. The
available calendars will be shown in the List Of Values (LOV) for the profile option.

2. Rerun the plan

If there is a same calendar name coming from two source instances, this problem could also occur. In this situation, change
the name for one of the calendars and recollect the planning data.

You can determine the duplicate calendar names by running the following SQL:

select min (CALENDAR_DATE),

max(CALENDAR_DATE),

calendar_code,

sr_instance_id

from msc_calendar_dates
group by calendar_code,
sr_instance_id

When identical calendar names are seen from different instances  rename the one that is to be used in the appropriate source
instance, recollect it, then rerun the plan. Also set the profile MSC: Calendar Reference for Bucketing to the new name before
running the plan again.

C.  Recently cloned one instance to another (eg PRD cloned to DEV)

In this case it was found that all calendars were built out at least 5 years in the future.  However profile MSC: Calendar
Reference for Bucketing = PRD:CP-Mon-70.  Notice that the example shows this instance called DEV was cloned from PRD,
yet the profile option still shows the PRD instance code in the value even though the calendar code was fine.  This creates a
problem during the Snapshot as it's looking for a calendar from PRD instead of DEV which causes the error.  Perform the
following:

1.  Run a complete refresh of data collections to make sure all data is collected for DEV instance

2.  Verify ASCP profile MSC: Calendar Reference for Bucketing has the correct instance code and calendar.  In this example it
should be DEV:CP-Mon-70

3.  A problem in the plan options was found as well.  Make sure to check the organizations tab in the plan options and make
sure all organizations included in the plan run show DEV:<Org_Code> and not PRD:<Org_Code>

4.  Also verify all demand and supply schedules attached are also shown with the correct instance code and demand schedule
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w24x164x3_53&id=1324086.1 2/3
11/22/22, 1:05 PM Document 1324086.1

name

5.  Rerun the ASCP plan

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w24x164x3_53&id=1324086.1 3/3