Order Management

Get Involved. Join the Conversation.


    Deepankar Patnaik
    Do we need to run or schedule Net Change Data collection and...
    Topic posted March 7, 2019 by Deepankar PatnaikRed Ribbon: 250+ Points, tagged Global Order Promising, Order Management, Order Management Analytics, Public Sector, SCM, Supply Chain Financial Orchestration, Supply Chain Orchestration, Tip, White Paper 
    117 Views, 2 Comments
    Do we need to run or schedule Net Change Data collection and schedule Refresh Promising Server too evey 2 mins or so to get accurate GOP result?

    We just completed our CRP2, The qty on hand on SO line does not show correct picture of on hand and availaibility until we run Data collection and Refresh Promising server ,so in a highly transaction driven business environment ,how to get accurate On hand result ,do we need to run Data Collection for On hand ,PO ,SO,reservation etc only with net change method every 2 mins and then schedule the Refresh Promising server,is this the best practice or there is something else.

    Even simple subinventory transfer from one location to another location,stock does not reflect correctly until we run Data collection and Refresh Promising Server,so how in a very transaction driven environment we can make order management work seamlessly taking on hand stock available into picture.




    • Matt Johnson

      You should not have to refresh/restart GOP Cloud every two minutes, even in a high volume environment. However, you may need to adjust the data you collect as well as some of your inventory management procedures to ensure better alignment of GOP’s supply picture with transactional systems.

      GOP’s job is to assign feasible shipment and delivery dates. It does not schedule at below a daily level of detail, so it assigns demand to a day’s worth of supply. That supply almost always starts with on-hand, but it can include receipt and in-transit quantities, purchase requisitions, PO’s, transfer orders, manufacturing work orders, supplier capacity and even planned orders from a supply plan that are expected for a given day. By including whichever of these supply types are relevant for your business in GOP’s in-memory model, you will avoid “surprising” GOP with new on-hand supply that seems to arrive out of nowhere.

      The same thing applies on the demand side. GOP needs to have visibility to all the demands in order not to have supply suddenly disappear. That means scheduling not only all sales orders, but also internal material transfers through GOP. GOP can schedule expense-based transfers, so you can account for non-sales-oriented consumption of supply.

      That still doesn’t cover 100% of inventory management transactions, of course. There will always be times when balances need to change due to cycle counts or miscellaneous issues. GOP Cloud does offer a “real time update” feature that allows you to update selected supply information without restarting the server. By running that process a few times a day, you can deal with those inevitable adjustments. Any remaining deviations should be small.

    • Shyam Singh Patel

      Collecting On Hand Inventory Levels for Scheduling purposes (Doc ID 2207161.1)

      Net Change

      When you use the Net Change collection type, you collect data incrementally. The Net Change collection type collects only changed or new data. Collecting data using the Net Change collection type is typically faster than using the Targeted collection type. You typically use the net Change Collection type when you have previously performed a targeted collection, and now you want to keep your planning data current with your execution system data.


      You use the Targeted collection type when you want to completely refresh data in the data repository. In this mode, the existing data for the selected entities is deleted from the data repository. Next, if subsequently collected from the source, the data for the selected entities replaces the deleted data.