Scribd Logo
Upload

Welcome to Scribd!

  • MSC: New Planner Backward Compatibility

    Uploaded by

    xieing.et.wltfifi
    11 views3 pages
    The document discusses two planning hooks in MRP: priority/FIFO hook and safety stock hook. The priority/FIFO hook processes demand and supply through two passes. The planning engine first uses a priority hook, then uses a FIFO hook in the second pass. The safety stock hook goes through several steps to satisfy safety stock, including smoothing safety stock levels to eliminate fluctuations. It is only executed when the configuration has MSC: Use FIFO set to no.

    Original Description:

    this guide introduct ebs order management module

    Original Title

    User OM Guide

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses two planning hooks in MRP: priority/FIFO hook and safety stock hook. The priority/FIFO hook processes demand and supply through two passes. The planning engine first uses a priority hook, then uses a FIFO hook in the second pass. The safety stock hook goes through several steps to satisfy safety stock, including smoothing safety stock levels to eliminate fluctuations. It is only executed when the configuration has MSC: Use FIFO set to no.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    11 views3 pages

    MSC: New Planner Backward Compatibility

    Uploaded by

    xieing.et.wltfifi
    The document discusses two planning hooks in MRP: priority/FIFO hook and safety stock hook. The priority/FIFO hook processes demand and supply through two passes. The planning engine first uses a priority hook, then uses a FIFO hook in the second pass. The safety stock hook goes through several steps to satisfy safety stock, including smoothing safety stock levels to eliminate fluctuations. It is only executed when the configuration has MSC: Use FIFO set to no.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 3

    优先级兼先进先出挂钩

    优先级兼先进先出挂钩流程使需求和供应经过两次通过处理

    第一关

    计划引擎使用优先级挂钩的第一次关。

    第二关

    计划引擎使用先进先出挂钩的关。

    安全库存挂钩

    计划引擎通过一系列步骤来来满足安全库存：

    平滑安全库存：消除安全库存的波动。这一步是可选的。计划引擎仅在配置文
    件 MSC:使用先进先出为否时执行安全库存挂钩。

    MSC: New Planner Backward Compatibility

    Based on latest information available in Bug 9848641


    And Per bug 12352866, this needs to be set to YES in 12.1.3 to avoid a
    performance issue in
    constrained plans.
    Yes - uses the new algorithm for planning phantom items.
    When you also set MRP_NEW_PLANNER_BACKWARD_COMPATIBILITY =
    Yes,
    then Phantoms will be planned as regular items.
    When you also set MRP_NEW_PLANNER_BACKWARD_COMPATIBILITY =
    No or NULL,
    then Phantoms will NOT be planned as regular items.

    No - Uses the old algorithm for planning phantom items.


    When you also set MRP_NEW_PLANNER_BACKWARD_COMPATIBILITY =
    Yes,
    then Phantoms will be planned as regular items.
    When you also set MRP_NEW_PLANNER_BACKWARD_COMPATIBILITY =
    No or NULL,
    then Phantoms will NOT be planned as regular items.

    Most all customers should use Yes.


    If case of certain plan errors when working with byproducts and profile = Yes,
    then you need to set
    profile = No
    The failure will occur when by-product is also a component of the BOM as
    shown below

    Ex: Assembly A
    / \
    Phantom B Phantom C -> By-product C
    |
    comp C

    This setup will result in a A->C->A loop.

    This was seen in bug where plan failed with the following message:
    ### Error: found loop between FROM operation : with sequence number 10
    supply id 1018430492 item id 1181059
    TO operation : with sequence number 1 supply id 1018430492 item id
    1181059 org Id = 86

    This could occur in two conditions :


    A. There is a loop in network routing - if so, please check the set-up and fix
    the routing
    B. There are by/co-products of assembly which are also a component of an
    item forming this assembly
    If so, try to change the profile option MSO: Peg By-product Supplies to FALSE
    - APP-MRP-22064: An internal error has
    occurred (hls_failure, 1)

    MSC:Prevent Loops when pegging Non-Standard Jobs

    Discrete job demands remain unpegged in case of job demands generated


    due to Loops in BOM. Valid values are:
    • Yes - If there exists a non standard job demand for a top level item in the
    supply chain bill and the non-standard job also exists as a valid supply in the
    plan, ASCP will make the pessimistic assumption that this could cause a fatal
    loop in the pegging and essentially ignore this demand for pegging purposes.
    This default setting is recommended strongly to prevent plan failures due to
    pegging loops.
    • No - In the above case, ASCP makes the optimistic assumption that loops
    will not exist after pegging and proceeds to peg supply of the top level item to
    the nonstandard job demand. This setting should not to be used unless the
    user is completely certain that loops will not be caused based on their

    You might also like