Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Srikanth
    Visual indicator 'Internally Transferable' needs to...
    Topic posted June 10, 2019 by SrikanthSilver Medal: 2,000+ Points, last edited August 19, 2019, tagged Internal Material Transfer 
    117 Views, 13 Comments
    Title:
    Visual indicator 'Internally Transferable' needs to look at the Deliver-to org level
    Summary:
    Visual indicator 'Internally Transferable' needs to look at the Deliver-to org level
    Content:

    With reference to the below idea, Visual indicator 'Internally Transferable' looking only at the master org level is a bug [19B feature]

    https://cloudcustomerconnect.oracle.com/posts/cd2eca2704?commentId=258954#258954

    Currently the internally orderable tag is being shown based on the master org value. But since this attribute can be controlled at the master org or the child org level, there is a definite possibility of this attribute being controlled at child org level, for a client. 

    The current solution does not cater to the scenario when the 'internal orderable' attribute is controlled at child org level, and may have different values in different child orgs. For e.g. in child org A the attribute value may be Y, but in child org B, it will be 'N'. In such cases, it is wrong to display as 'Internally orderable' in child org B, where it is not so. 

    If a deliver-to org in the requisition is linked to child org B, then in such cases, the 'Internal orderable' tag should not be displayed. 

    This is a clear and definite bug, which needs to be resolved. 

    This would mislead the end-user on the lead time of getting the product he/she ordered for. In healthcare scenarios, product availability is of utmost importance. For e.g in the Operating room, when a requester orders a product and sees that as 'internally orderable', he/she will think that the product will be delivered within 1-2 days. 

    But if the product is vendor sourced (internal orderable=N), then it may take a longer time. Becoz of product not being available, this will lead to postponement of surgeries and ends up with healthcare not being given in emergency situations. 

    Thanks, 
    Srikanth.

    Version:
    19B

    Comment

     

    • Ashok

      Hi Srikanth

      Thank you for the details. Such feedback is always helpful and encouraged. I will review this internally and revert.

    • Ashok

      Srikanth

      I had a couple of questions on the last 2 observations in your note:

      This would mislead the end-user on the lead time of getting the product he/she ordered for. In healthcare scenarios, product availability is of utmost importance. For e.g in the Operating room, when a requester orders a product and sees that as 'internally orderable', he/she will think that the product will be delivered within 1-2 days. 

      But if the product is vendor sourced (internal orderable=N), then it may take a longer time. Becoz of product not being available, this will lead to postponement of surgeries and ends up with healthcare not being given in emergency situations. 

      If an item is not internally transferable in the deliver-to org belonging to that deliver-to location, that item will not be processed as an internal material transfer. Correct? So the user will know right away when they add the item to the cart that the item is going to be sourced as a supplier sourced item. The risk of postponement of surgeries and similar occurrences should not be feasible.

      Let me know if I have misunderstood something from your observations above.

      Now, this has nothing to do with your original observations on the indicator needing to look at the deliver-to org. That specific aspect, I am reviewing internally. This was more about confirming that there really is unlikely to be unsavory occurrences because of the indicator because the system will not process it incorrectly. Do let me know what you think.

    • Srikanth
      Thanks Ashok for checking on this.
      
      
      
      Once the end user adds the item to the cart, he does not need to review the source (vendor or internal). Also the source details are mentioned at the bottom of the page.
      
      
      
      Since sourcing is decided based on setups (BPAs or sourcing rules), the end user need not check on the source and they don't need to bother about it. Once he/she adds item to cart and submits, he/she is expected to receive the item within a given time.
      
      
      
      Kindly consider the user base of more than 15,000 users working in a healthcare system in the public sector. Please review my inputs in this context.
      
      
      
      Thanks,
      
      Srikanth.
      
      
      
      
    • Ashok

      Understood. Once he / she adds items to cart, the lead times will be governed by whether the item is sourced internally or through the supplier. But you are saying in many cases, the users may not go in and check the details. They may come away with the impression that the item is ordered internally.  I was simply ascertaining that the flow itself will not be incorrect. It is the user's understanding that may be incorrect based on the first visual indicator. I will revert on the original issue.

      Thanks

      Ashok

    • Ashok

      Hi Srikanth

      Like I stated before, I was reviewing your observations on current behavior internally. I am unable to corroborate your assertions on current behavior of the visual indicator. 

      In summary:

      I have two inventory organizations: V1 and M1. M1 is a child of V1. I set Internally Transferable to No on V1 (Master) and Yes on M1 (Child). I am able to see the visual indicator only when I search for items in M1 and not when I search for items on V1. And vice versa.

      So I would like to understand how you were able to establish this. We can talk offline if needed. I am not seeing the bug. I need your help to see if I am missing something or something is askew with your setup.

      Thanks

      Ashok

    • Ashok

      Hi Srikanth

      The information you provided earlier is a bit insufficient. Let me confirm a few things.

      When you observed the behavior (about master org having to have the internally Transferable flag to be set to Yes) in order to see the Internally Orderable visual indicator, did that item per chance have a BPA assigned to it? What is your observation on behavior for a non BPA backed item?

      If the occurrence you are observing is always tied to the item having a BPA associated, then I think this is what is happening:

      A BPA is created in a Procurement BU. This Procurement BU has an Inventory Organization default defined in the Configure Procurement Business Function. When we source an item from a BPA, that is the Deliver-to Org we use (from the Procurement BU configuration). That is my analysis of why you are seeing what you are seeing. In your case, I think the BPA belongs to an org that has the internally transferable flag enabled. This is what drives display of the visual indicator. As we discussed, the actual sourcing happens accurately but the display is based on the deliver-to org which can be the Deliver-to org based on the Deliver-to Location in the Edit Requisition Preferences (for a non BPA item) and the Deliver-to Org on the Procurement Configuration page (for a BPA item).

      Let us talk offline (you can send me an email to discuss this further) if you wish.

      Thanks

      Ashok

    • Ashok

      In other words, the symptoms while seem to point to a master org / child org related issue, it to me does not seem to have any bearing on what you observe. My tests were based on a non BPA item which is why I am asking to confirm additional details.

      • Srikanth

        Hi Ashok,

        When I did a test yesterday, it seems to be controlled from master org level only. I will reach out to you offline.

        Not able to paste the screenshots for client confidentiality reasons.

         

        Thanks,

        Srikanth.

    • Ashok

      So, to conclude on this discussion for everyone, I discussed this offline with Srikanth and explained how this is working per current design. We are however reviewing it internally to evaluate any alternatives to meet the original ask on this post, i.e. make the visual indicator always depend on the deliver-to org during shopping.

    • Ashok

      All

      To catch everyone up, we are working on a fix for this issue. We discussed this internally and this is our root cause analysis:

      a) For BPA backed items, the system looks at the Inventory Org of the Procurement BU (this is how it was designed)

      b) We are now looking to fix this to always look at the Inventory Org (Deliver-to Org) of the Deliver-to Location on the specific requisition line

       

    • Srikanth

      Thanks a lot Oracle team for fixing this bug in 19C. Able to see the visual indicator checking the deliver to location and not the inventory org mentioned in requisition business function.

      Thanks,

      Srikanth.

       

    • Ashok

      Good to hear.