Inventory

Get Involved. Join the Conversation.

Topic

    Ramesh Choudhary
    'Calculate Min-Max Planning Policy Parameters' not...
    Topic posted October 23, 2019 by Ramesh ChoudharyBlue Ribbon: 750+ Points, tagged FAQ, How-To, Inventory Cloud, SCM, Setup, Tip 
    26 Views, 2 Comments
    Title:
    'Calculate Min-Max Planning Policy Parameters' not calculating the Min and Max Quantities of the Item
    Summary:
    'Calculate Min-Max Planning Policy Parameters' not calculating the Min and Max Quantities of the Item
    Content:

    Hi Team,

    We have setup the Min-Max Planning Classification Groups,Min-Max Planning Policy profiles and Min-Max Planning Policy Profile Assignments in our POD.

    We have also uploaded 6 months of historical transactions for the item (Transaction type: In transit shipment).

    After that we are submitting 'Calculate Min-Max Planning Policy Parameters' process.

    The Process completes successfully without triggerring the 'Import Item' process and MIN MAX Quantities are not getting computed for the item.

    Can you please help us with identifying the issue. Why MIN MAX Quantities are not getting computed?

    Below is part of Log File i have pasted:

    ------------------------------------------------------------------------

    compute_policy_param function, v_org_id is 300000039088147

    compute_policy_param function, v_subinv_id is -1

    Entering the Main procedure compute_policy_params_for_org function

    Exception occured in compute_policy_params_for_org ORA-06503: PL/SQL: Function returned without value

    Calling  compute_policy_params_for_org function since SubInventory is not selected

    compute_policy_param function, v_org_id is 300000039088159

    compute_policy_param function, v_subinv_id is -1

    Entering the Main procedure compute_policy_params_for_org function

    -----------------------------------------------------------------------------

    Thanks,

    Ramesh

    Comment

     

    • Jayesh Agarwal

      Can you please open a support ticket and ask Oracle Support to log a bug for this one so that development team can take a look at this issue.

    • Jayesh Agarwal

      In the meantime please check your 'History Data Days' value. Looks like you don't have history within 'Current Date minus History Data Days'.

      You can either increase the 'History Data Days' to make sure the history transactions falls within this window.

      Or you can bring in more history within 'Current Date minus History Data Days' window.

      If history is not available then try populating 'Default Daily Demand' and check if the Min-Max values are getting calculated.

      Thanks.

      • Ramesh Choudhary

        Hi Jayesh,

        Thanks for your suggestion.

        i have changed the 'History Data Days' from previously 180 to 90 Days in our policy.
        After making the 'History Data Days' as 90 Days, the min and max quantities were computed.


        Clarification required:
        Why it worked when i changed 'History Data Days' to 90 days?
        Why it did not work with 180 Days?

        Note: We had upload the Historical data(intransit shipments) from April 2019 till September 2019 which covers 180 days. Then why it does not work with 180 days as parameter?

        What are checkpoints we should perform to find what might be causing the issue with 180 days.

        Can you please suggest.

        Thanks,

        Ramesh