Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Srikanth
    Wrong quantity for expense requisition - agreement based...
    Topic posted September 16, 2019 by SrikanthGold Medal: 3,500+ Points, tagged Create Requisition, Internal Material Transfer 
    106 Views, 15 Comments
    Title:
    Wrong quantity for expense requisition - agreement based catalog items sourced internally
    Summary:
    Wrong quantity for expense requisition - agreement based catalog items sourced internally
    Content:

    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.

    Version:
    19C

    Comment

     

    • Ashok

      Srikanth

      Did this work differently in 19B? Can you confirm? I am already aware of this issue but wanted to confirm. This has nothing to do with the other post. This relates to Unit of Issue based usage and conversions is my current thought.

      • Srikanth

        Yes Ashok, in 19B, the quantity used to carry over without any change. Below was earlier behaviour related to quantity:

        Before adding to cart: 1 [Case of 100]

        After adding to Cart: 1 [Box of 10]

        After 19C, the quantity is appearing as given in the post. (1 to 0.1)

    • Ashok

      Please raise an SR and provide this Customer Connect link to Support and have them raise a bug.

    • Srikanth

      Hi Ashok, while SR has been raised, wanted to highlight the similarity between this post and the post link below, where you first indicated Bug 29530538 - INCORRECT QUANTITY ADDED TO CART FOR INTERNALLY ORDERED ITEM DURING SHOPPING

      https://cloudcustomerconnect.oracle.com/posts/bac84dca2b

      Quantity discrepancy on adding to cart - 19B and 19C
      Version Unit of Measure Quantity
      19B Changed to unit of issue Same quantity after adding to cart (1 before adding to cart; 1 after adding to cart as well)
      19C

      Changed to unit of issue

      Quantity changed, but wrong quantity calculated

       

      Summary [Same behaviour] [Different behaviour, but still wrong result]

       

      Pls let me know if you need further information.

       

      Thanks,

      Srikanth.

    • Ashok

      Yes, the similarity is not lost on me. However Unit of Issue is a separate flow that we incorporate into the UOM related design considerations. While I will not completely rule out a causal link, I don't believe that to be the case. Irrespective of that, let us triage this through a bug further. Such analysis cannot be concluded with conversations here. There is need for more triage.

      Thanks

      Ashok

    • Srikanth

      Hi team,

      As I understand from the concerned SR, the bug # raised against this issue is 30318104 (but not visible externally).

      Since this is a basic bug, which needs a fix, kindly request to backport it to 19D.

      Thanks,

      Srikanth.

    • Ashok

      Srikanth

      This is being reviewed by the SCM team. Also this forum may not be the way to make backport requests. It is best you work through the SR with Support  through the formal process that has been provided for such requests.

    • Srikanth

      Hi Ashok/Oracle team,

      In the corresponding SR related to this issue, got an update that this will be fixed in 19D. The current bug id is 30318104.

      Just curious if above bug and bug 29530538 have the same fix?

      Thanks,

      Srikanth.

    • Ashok

      Srikanth

      Per the latest update on the bug/s, the issue for the newer bug seems to have been addressed in a bug that I logged (the older one you are referring to). Although the original bug was not specifically dealing with Unit of Issue, it appears to have been addressed as part of the test cases that were tested during the bug fix process. This has already been fixed in 19D and so when you upgrade, you should be able to confirm that it now works for your use cases.

      NOTE: I am still confirming that your issue is in fact fixed. I only communicated to you what was stated in the bug, above.

    • Srikanth
      Thank you for the clarification Ashok!
      
    • Ashok

      Hello Srikanth

      i did dig into this a bit more. Turns out the bug updates were only intended to communicate this was not a regression from the earlier bug fix. In essence, this fix is not yet done. It is in progress. So it is not available in 19D.

      Thanks

      Ashok

      • Srikanth

        Hi Ashok,

        Kindly request to fix this bug, since this is a fundamental UOM conversion error.

        For the healthcare scenario, requesting for goods from store is common (even the ones in a BPA).

        Thanks,

        Srikanth.

    • Ashok

      Srikanth

      The fix is in progress. Will revert when I have an update on when it is completed.