ATP Does Not Honor Shipping Calendar - Schedule Ship Date Does Not Save On Work Day

Saturday [ID 456786.1]

Modified 07-MAR-2011 Type PROBLEM Status PUBLISHED

In this Document
Symptoms
Cause
Solution

Applies to:

Oracle Order Management - Version: 11.5.10.2 to 12.1.3 - Release: 11.5 to 12.1

Information in this document applies to any platform.

Symptoms

A calendar was created, built, and assigned to an organization with the usage of Shipping. The
calendar is set up for 6 days on, 1 day off; workdays are Monday through Saturday, inclusive.
When entering a sales order in this organization and attempting to enter a scheduled ship date of
a Saturday (e.g., 9/1/07) and saving, the scheduled ship date automatically reverts to the
previous Friday (e.g., 8/31/07).

The problem seems to be that the scheduled ship dates are not referencing the shipping calendar
but rather the production calendar, which is 5 days on, 2 days off.

### Steps to Reproduce ###

Created same calendar in a test instance and tried with several organizations -- same result.

Order Management Manager -> Shipping -> Setup -> Calendars -> Enter / Assign

EXPECTED BEHAVIOR
Expected ATP to use the Shipping calender and schedule the line on Saturday (a valid workday
on the Shipping calendar)

Cause

The issue is caused by the following setup:

Profile MSC: Use Shipping/Receiving Calendar was set to 'No' at the site level. The setup causes
the issue because the Shipping calendar was not being used for ATP.

This issue is described in OM Forum:

http://myforums.oracle.com/jive3/thread.jspa?messageID=3294211?
This forum entry outlines the issue that you encounter: ATP is not using the Shipping Calendar.
The note also explains that the issue is caused by a setup similar to what you have. Incorrect
schedule ship date is the result.

Solution

-- To implement the solution, please execute the following steps::

1. Go into the responsibility: System Administrator
2. Navigate to Profiles > System.
3. Query for 'MSC: Use Shipping/Receiving Calendar' and set to 'Yes' at the site level.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.