Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Srikanth
    UOM mismatch and quantity discrepancy between initial search...Answered
    Topic posted July 24, 2019 by SrikanthGold Medal: 3,500+ Points, last edited July 25, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, Internal Material Transfer, Public Sector 
    94 Views, 10 Comments
    Title:
    UOM mismatch and quantity discrepancy between initial search and review cart screens - in scenario Fulfill Expense Requisitions for Agreement Based Catalog Items From Internal Sources
    Summary:
    UOM mismatch and quantity discrepancy between initial search and review cart screens - in scenario Fulfill Expense Requisitions for Agreement Based Catalog Items From Internal
    Content:

     

    1. Consider below scenario for Fulfill Expense Requisitions for Agreement Based Catalog Items From Internal Sources:

    Quantity = 1

    Item purchasing UOM: Bag of 1000 (with 1000 Each as UOM conversion)

    Item issue UOM: Each

    2. Search for item in self service procurement

    3. Purchasing UOM appears for item with quantity = 1 (i.e. Bag of 1000)

    4. Add item to cart

    5.  Review cart. UOM changes to issuing UOM (but quantity remains one). Summary: Quantity value remains same but UOM changes at this step

    6. Initial quantity = 1000 Each (considering UOM conversion)

    7. Quantity during cart review = 1 Each 

    8. Summary: UOM mismatch and quantity discrepancy between initial search and review cart screens

     

    9. Why bug? When user search, the quantity that appears is different from the quantity that appears when the user reviews the cart. This leads to operational impact (sufficient quantity not available) or excess inventory holding cost (excess inventory) if the users consider initial quantity as source of truth

    10. Suggested solution: For this scenario of internal intra-organization transfer for destination type expense, upon search with the given item, the initial search screen should return the issuing uom directly (instead of the purchasing uom). 

    If item is not internal transfer enabled in the given deliver-to location, then the purchasing UOM needs to come in the initial search screen.

    11. Conclusion: Kindly request to resolve this bug in 19D

    With 15000 users having self service procurement, such kind of discrepancies lead a lot of operational and financial issues.  The impact is also documented above

    Best Comment

    Ashok

    This is a known occurrence and has already been addressed.

    Bug 29530538 - INCORRECT QUANTITY ADDED TO CART FOR INTERNALLY ORDERED ITEM DURING SHOPPING 
     

    Comment

     

    • Ashok

      This is a known occurrence and has already been addressed.

      Bug 29530538 - INCORRECT QUANTITY ADDED TO CART FOR INTERNALLY ORDERED ITEM DURING SHOPPING 
       
    • Srikanth

      Thank you Ashok, please include this in 19D functionality list.

      This will be very helpful, if implemented for the client's business operations.

      Thanks,

      Srikanth.

    • Srikanth

      Hi team,

      I understand the status of below bug will not be visible externally, till Oracle progresses it to a particular point.

      Pls let us know the status. Kindly resolve the below bug in 19D.

      Bug 29530538 - INCORRECT QUANTITY ADDED TO CART FOR INTERNALLY ORDERED ITEM DURING SHOPPING 

      Thanks,

      Srikanth.

    • Ashok

      It should be available in 19D.

    • Srikanth

      Hi team,

      While you may have been working on this Bug 29530538 - INCORRECT QUANTITY ADDED TO CART FOR INTERNALLY ORDERED ITEM DURING SHOPPING, wanted to let you know that in 19C, we are seeing a quantity discrepancy as per the below table.

      Also this quantity discrepancy is different from the one we had earlier.

      The full test steps are elaborated in the attached document. Pls let me know if you need any further information.

      UOM in

      UOM name

      Conversion to primary UOM (Each)

      Initial requisition

      Quantity [UOM]

      On addition to cart

      Quantity [UOM]

      Remarks

      Quantity [UOM]

      BPA

      Case of 100

      100

      1 [case of 100]

       

       

      Unit of issue

      Box of 10

      10

       

      0.1 [Box of 10] 

      Should have been 10 [Box of 10]

      Thanks,

      Srikanth.

    • Ashok

      Srikanth

      Please discuss this in a new post. Using this same one will make the discussions unwieldy.

      Thanks

    • Srikanth

      Hi Ashok,

      Looking back on this idea and now that our client instance is on 19D, we are still seeing a discrepancy between the initial search and the review cart screens.

      Business need: When end user requests for products from store, the initial UOM display says CASE OF 12. But after adding to cart and in the review screen, the UOM changes to issuing UOM (e.g. Each).

      So the user ends up creating requisitions with wrong quantities/wrong UOMs, than what they planned earlier.

      [Extracted from original content of the idea]

      8. Summary: UOM mismatch and quantity discrepancy between initial search and review cart screens

      9. Why bug? When user searches, the quantity that appears is different from the quantity that appears when the user reviews the cart. This leads to operational impact (sufficient quantity not available) or excess inventory holding cost (excess inventory) if the users consider initial quantity as source of truth

      10. Suggested solution: For this scenario of internal intra-organization transfer for destination type expense, upon search with the given item, the initial search screen should return the issuing uom directly (instead of the purchasing uom). 

      Attached screenshots after 19D has been applied in the instance.

      Thanks,

      Srikanth

    • Ashok

      Hi Srikanth

      That was not evaluated during the specific issue raised on incorrect conversions. What you are requesting is better tracked as an idea.