Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Christine Schwartz
    19D: Requisitions for internally orderable items now created...
    Topic posted November 16, 2019 by Christine SchwartzGreen Ribbon: 100+ Points, tagged Create Requisition, Internal Material Transfer, Inventory Cloud 
    28 Views, 6 Comments
    Title:
    19D: Requisitions for internally orderable items now created at purchase UOM rate
    Summary:
    19D: Requisitions for internally orderable items now created at purchase UOM rate
    Content:

    In most cases, our internally orderable units of measure are lower than the purchase unit of measure (e.g. EA vs BX).

    Prior to 19D, if an internally orderable item was added to cart, it kept the quantity that the user entered but changed the UOM from the PUOM to the IUOM (e.g. 1 BX when added to cart became 1 EA). Now with 19D, when an item is added to cart, the quantity is multiplied by the intraclass conversion rate (e.g. 1 BX when added to cart is now 48 EA). 

    Is there a way to override this new system behavior? It is causing us many errors and inventory stock-outs due to requesters now ordering larger quantities than intended or expected. 

    Comment

     

    • Ashok

      Hi Christine

      Allowing the Quantity to remain the same while changing the UOM was seen as a product deficiency. If the user wanted to order 1 Box and it internally created an order for 1 Each (the previous behavior), several customers complained that this is incorrect design or behavior as the quantity and the UOM should be synchronized. This was dealt with as a bug fix primarily based on several health care customer complaints.

      The new system behavior is a fix of what was deficient behavior. There is no way to override this behavior.

      In your example, 1 Bx based on the standard conversion does equal 48 Each. That is the right conversion, is it not. The suggestion is then for the user to reduce the quantity to what they desire in the shopping cart or on the Edit Requisition page. 

      Here are a few links that might help provide the background on this:

      https://cloudcustomerconnect.oracle.com/posts/bac84dca2b (bug fixed which is the behavior you are observing)

      https://cloudcustomerconnect.oracle.com/posts/281e932cd6 (related issue and the bug fix is in progress)

      https://cloudcustomerconnect.oracle.com/posts/b34fb08f94 (Idea not a bug)

      • Christine Schwartz

        Thank you Ashok for the explanation and the background information. We are only recently live with Cloud, and did not realize this bug fix was coming in 19D. I did not see any indication of this feature in the release notes. Unfortunately, our requesters are accustomed to the previous behavior of allowing the quantity to remain the same while changing the UOM, and we are dealing with many cancelled IMTs and returns to inventory as a result. Our inventory staff will have many weeks of additional labor and rework until all requesters understand the new behavior. 

    • Ashok

      Hi Christine

      Bug fixes are usually provided in a document entitled: Bug Readme document. Do watch this space going forward. I tend to highlight important functional fixes handled through bugs in this Forums lab a bit ahead to let customers be aware. But the Readme document is something you should look out for going forward. I do understand the difficulty you are describing. But, the feature makes the behavior bug free and so better in the long run. Good luck!

      • Christine Schwartz

        Thanks again Ashok. Where can I find these Bug Readme documents? I have been unable to locate them. Are they organized by release, so that I will be able to easily locate upcoming fixes prior to 20A? I appreciate your assistance. 

    • Ashok

      Hi Christine

      Here is a link to the Procurement Readme Documents:  https://support.oracle.com/epmos/faces/DocumentDisplay?id=1554124.1

      Thanks

      Ashok