My Oracle Support Banner

Item Lead Time Is Not Considered When Internal Requisition is Created Via Min Max program (Doc ID 2909958.1)

Last updated on DECEMBER 22, 2022

Applies to:

Oracle Inventory Management - Version 12.2.10 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.10 version, Replenish

ACTUAL BEHAVIOR
---------------
Item Lead Time Is Not Considered When Internal Requisition is Created Via Min Max program
This is causing incorrect Need by date.

Example calculations:
For Item A > Internal Requisition(IR) created in Org a and Shipping Org B.
In-transit Lead Time(LT) = 49 days
Processing LT @ 599 = 10 days
Need by Date in IR : 14-Nov-2022
Min Max Program Run date = 23-Aug-2022
Requested Date by Min Max : 14-Nov-2022
Schedule Ship Date (SSD) by Min Max: 26-Sep-2022
Schedule Arrival Date (SAD): by Min Max 14-Nov-2022
In transit time = 14-Nov-2022 (SAD) - 26-Sep-2022 (SSD) = 49 Days ( logically In transit Lead time considered correctly ) based on 24x7 Calendar Days. But Schedule ship Date was not Correct

EXPECTED BEHAVIOR
-----------------------
Expected Value =
SSD --> Current Date (23-Aug-2022) + 10 Days Processing lead time (24x5 Calendar)
SSD --> 07-Sep-2022 + 49 days = > 26-OCT-2022

Need by Date in IR , Schedule Arrival Date and Requested Date should be 26-OCT-2022

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup processing lead time, Min-Max quantity on item.
2. Setup Intransit lead time on shipping network
3. Run Min-Max >>  See that processing lead time is not considered.


Cause

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
Symptoms
Cause
Solution
References


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