Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Atul Kumar
    To default purchasing UOM on Requisition line
    Topic posted October 16, 2018 by Atul KumarBronze Medal: 1,250+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Create Requisition, FAQ, How-To, Manage Procurement Catalog, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Requisition Web Services, Setup, Tip, Update Preparer and Requester, White Paper 
    189 Views, 14 Comments
    Title:
    To default purchasing UOM on Requisition line
    Summary:
    To default purchasing UOM on Requisition line instead of Primary UOM/Stocking UOM
    Content:

    Hi,

    Did someone come across a requirement wherein we have a place holder to default purchasing UOM instead of Item's primary UOM(stocking UOM) on Requisition line while raising a requisition. How that can be achieved, Please advise.

    Thanks,

    Atul Kumar

    Comment

     

    • Ashok

      Atul

      Thank you for the post. What would really help is some business context and details. What is the business requirement? Why do you want this behavior? It could really help readers get the right perspective to respond.

      Speaking from a development perspective, I can't say I have heard this from customers. We do have Dual UOM cases that are already handled in the system. I wonder if you have explored secondary UOM setup and whether that has / has not worked for you.

      I will let customers chime in too.

      • Atul Kumar

        Hi Ashok - The requirement is, we have Blanket purchase agreements with particular purchasing UOM and we need to default the same purchasing UOM while raising the requisition for the item same as in BPA. 

    • Sunny Todkari

      Never heard of such requirement before.

      But see if this helps you:

      Need UOM To Be Defaulted On Purchase Requisition (Doc ID 2041367.1)

      Also, in 'Line Type' setup, you can attach UOM to specific line type but never tried whether it gets defaulted on the PR or not. You can give a try.

      • Atul Kumar

        Hi Sunny - The requirement is, we have Blanket purchase agreements with particular purchasing UOM and we need to default the same purchasing UOM while raising the requisition for the item same as in BPA. Please confirm if that can be acheived.

        • Sunny Todkari

          The item has primary UOM as Each which is defaulted on BPA.

          Then changed the UOM from Each to Case on BPA.

          BPA is approved.

          Created Req and linked the Req to BPA. On Req, ‘Case’ UOM has defaulted.

          Summary: If the req is linked to BPA, Req will have same UOM as BPA.

          • Atul Kumar

            Thanks Sunny, we already tried it but the problem is, users don't want to change the agreement type to blanket and search for the BPA number for the item while raising the requisition, the process should be automatic.

            • Ashok

              Atul

              You are bringing up a different issue though. The post was about dual conversion. On the default to be set to BPA, yes, this is how the system behaves today but that seems like a very reasonable process compromise to make the overall UOM related flows work seamlessly. 

              • Ashok

                Also note that if you choose to search for the item and add it, it will source the agreement automatically. That is the option that would help in this case too.

            • Sunny Todkari

              Consider a case where you have two BPAs with different UOMs.

              How would you like the system to decide which UOM should have defaulted on the req if the BPA is not selected on req? 

    • Ashok

      Atul

      That is why I asked if you had explore primary UOM and Secondary UOM in the setup. It is possible to define these and then create an agreement in the secondary UOM and source the item using that agreement.

      • Atul Kumar

        Hi Ashok - Yes, we have explored Dual UOM functionality and explained to users however customer is not comfortable to enter the quantity multiple times while raising the requisition and while receiving the item. Also the items have multiple purchasing UOM(ex: Each, BOX, BAG) for the same item.

    • Ashok

      While receiving the item, you may not need to enter the quantity unless the receipt quantity is different. And I am not sure why the requester would enter the quantity multiple times in the requisition. Can you clarify? Has it do with the conversion between the UOM types. I thought you could provide the conversion as part of UOM configuration.  I am not certain I follow what the hardship is. Please provide a detailed use case with an example and preferably screenshots.

      I am sure other customers can weigh in but I have seen other customers use this dual UOM configuration and successfully.

    • Ashok

      Reviewed the screenshots. This looks like a setup issue at your end, unless I am mistaken. I know that the secondary UOM and quantity is automatically derived in the test cases I have see. 

      Sunny

      Can you upload the Item UOM Configuration related setup for Atul to compare and contrast? I don't believe you are encountering these issues which seems right.