My Oracle Support Banner

Incorrect Planning Time Fence Computed In Plan Output When Profile MSC: Buy Order Processing Lead Time Calendar = Supplier Calendar (Doc ID 1061803.1)

Last updated on FEBRUARY 01, 2021

Applies to:

Oracle Advanced Supply Chain Planning - Version and later
Information in this document applies to any platform.


We are seeing one issue with below combination on Planning Time fence computed in ASCP Plan output

1). MSC: Buy Order Processing Lead Time Calendar = Supplier Calendar, in our case is 5 working days calendar
2). MSC:Ignore PTF durign CTP = Yes

In ATP scheduling ==> This is working fine as Buy order lead time was computed based on Supplier calendar which is 5 working days and Planning Time fence date was reset to current date. This is per expectation.

However, the issue is related to ASCP plan output, where Planning Time Fence in ASCP computed in following ways:

Item A
At item level:
Planning Time Fence = Total Lead time, see following setup.
Pre Processing lead time = 1 day
Processing lead time = 20days
Post processing lead time = 40days

At Approved Supplier list level
Processing lead time = 20days

ASCP computed Pre Processing lead time and Processing lead time in 24X7 Calendar but Post processing lead time was computed based on 5 working days in regardless Processing lead time set in item level or Attribute supplier list level.

However, if we update Planning Time fence = user defined value = 61days in this example, Pre Processing lead time/Processing/Post processing lead time were computed based on 5 working days which is spot on.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.