Posts

Posts

  • Ashok
    How to Restrict Requesters in the Requester LOV34.9
    Topic posted June 27, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, White Paper in Procurement > Self Service Procurement public
    Title:
    How to Restrict Requesters in the Requester LOV
    Summary:
    How to restrict Requesters in the Requester LOV
    Content:

    All

    We recently had a customer use case that cited the following requirement:

    The Manage Requisitions page allows users to search for requisitions belonging to other requesters using the Requester LOV. However, the LOV displays all persons that belong to any requisitioning BU in the organization. This customer wanted to restrict the search capability whereby the search results in the LOV would only return those Requesters belonging to the same business unit as the current requester.

    This is supported using some configuration via the Security Console.

    This attached document details the process and steps involved in such a configuration.

    NOTE: The idea here is exploratory that provides customers an idea of what is feasible using this infrastructure. The idea in publishing this to familiarize the customers with this feature capability and have the customers use their consulting and professional resources to use the infrastructure for their own specific business needs.

    Happy reading! As always, appreciate the feedback and ranking on whether this is helpful and ideas on what other articles would be of interest.

    Thanks

    Ashok

  • Ashok
    Part 2: Inventory Organizations, Deliver-to Locations,...25.0
    Topic posted November 17, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, Requisition Processing in Procurement > Self Service Procurement public
    Title:
    Part 2: Inventory Organizations, Deliver-to Locations, Subinventories: Interactions in Self Service Procurement Flows
    Summary:
    An overview of how inventory organizations, deliver-to locations, subinventories interact in Self Service Procurement transaction flows
    Content:

    In Part 1, we reviewed the various entities in play and how they are interlinked here:

    https://cloudcustomerconnect.oracle.com/posts/14d8d1cefd

    In this part, we will examine impact on creating and editing requisitions with these entities and associations.

    1. Shopping for an Expense Item:

    When the requesters shop for an item, the items visible are based on the deliver-to organization associated with that Requisitioning BU. This is known. But which deliver-to organization?

    That is set from the deliver-to location on your requisition preferences. Ok, let's continue.

    Now when the user shops for an item, adds to cart and navigates to the Edit Requisition page, the deliver-to location, destination type (Expense)  default from the Requisition Preferences setup

    Now, let's say the user wants to switch Deliver-to Location to a different one of his choice, but his choice is not available in the selection. Why?

    The choices available to the user are:

    a) Any 'Global' location or

    b) Any other deliver-to locations that are specifically associated with the deliver-to organization stamped on the requisition line.

    In either case the location has to be associated with the same deliver-to organization  as the one stamped on the requisition line.

    So, how is a deliver-to organization stamped on the requisition line?

    This is where the Requisition Preferences come into play. The deliver-to location that is set guides the system to identify which deliver-to organization is stamped on the line. (See Part 1 for how this works)

    NOTE: The user cannot choose a deliver-to location here that does belongs to a different deliver-to organization. This is the question many customers seem to want to get clarification on. The model works on a deliver-to organization being identified on a specific line and CANNOT be modified.

    So what do I do if I want a different deliver-to location that belongs to a different deliver-to organization?

    Well, then delete this line, go back to requisition preferences and select the deliver-to location that you want (that belongs to a different deliver-to organization) and then come back and shop

    NOTE: The item has to be available in that deliver-to organization too.

    See how this works?

    2. Shopping for an Inventory Item:

    The concept is akin to the expense item flow. We are however now introduced to a new entity - Subinventories. Thankfully, the logic of how this works is the same as the deliver-to location. Let me explain.

    In Part 1, you saw how subinventories are modeled. Now the list of subinventories available to the requester on the Edit Requisition line is based on the deliver-to organization stamped on the requisition line (as we saw earlier). Often customers ask, but I want a different subinventory and I don't find it. Why?

    The answer is simple: That subinventory is modeled under a different organization. Once the requester has selected an item, the deliver-to organization is stamped and done. It cannot be modified. The list of subinventories available at this point is all those that are modeled within that organization.

    So the process to select a different subinventory is the same as earlier. Change the Requisitioning Preferences to a different deliver-to location (that uses a different deliver-to organization where your choice of subinventory is modeled). Then engage in a new flow.

    Customer Feedback:

    Of  late, we are hearing of business requirements around this. Some customers are suggesting that they need flexibility for requesters to choose any deliver-to location or subinventory of their choice and not be constrained by the deliver-to organization being stamped on the line.

    I offer you this:

    1. While the requirement is simple, the design and implementation behind it is perhaps needlessly complex. Deliver-to organizations do more than just model deliver-to locations and subinventories. They drive and control items that a user can see. They drive the transfer price for internal items and so on.

    2. Modeling it in such an open ended fashion has to be looked into carefully taking into account, item, accounting, costing, pricing ramifications.

    3. Other flows using Requisition Preferences defaulting for these entities:

    Similar to 1. and 2. above, when users navigate to the Enter Requisition Line page (advanced requesters), the same defaulting behavior occurs on that page too. The deliver-to location, subinventory are all attributes that are controlled by the deliver-to organization derived from Requisition Preferences.

    I am hoping I have demystified and answered some of the lingering questions that we have seen on forum posts, bugs or even enhancements.

    Please convey your feedback to see how I can improve this or any other article that you review.

  • Ashok
    Self Service Procurement Privileges not assigned out of the...114.9
    Topic posted September 19, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, FAQ, Requisition Mobile, Requisition Processing, Tip in Procurement > Self Service Procurement public
    Title:
    Self Service Procurement Privileges not assigned out of the box to Roles
    Summary:
    Self Service Procurement Privileges not assigned out of the box to Roles
    Content:

    Hi all

    You asked and we heard you. There was a response to my query on this forum asking what sort of topics you would like to see articles written. One of the suggested topics was to see a list of all privileges that were defined for Fusion Self Service Procurement but not assigned to any roles out of the box and a brief description of their function.

    Here you go:

    Privilege Title

    Privilege Technical Name

    Privilege Description

    Comments

    Create Requisition via Mobile App

    POR_CREATE_REQUISITION_VIA_MOBILE_APP

    Allows a user to create a requisition using the Mobile App.

    You need this privilege to enable access for a user to create a requisition using the Fusion Self Service Procurement Mobile Application.

    Edit Requisition as Approver

    POR_CREATE_REQUISITION_-_ALLOW_APPROVER_MODIFICATION

    Allows users to modify requisitions as approvers.

    Use this privilege if you wish to allow approvers the ability to edit a requisition during the approval process. A link entitled ‘Edit Requisition’ will be enabled with this privilege on the approval notification.

    Reassign Requisition

    POR_REASSIGN_REQUISITION

    Allows users to reassign requisitions entered by others.

    Without this privilege you can only reassign requisitions that you created.

    View Requisition - All

    POR_VIEW_REQUISITION_ALL

    Allows users to view all requisitions in the authorized business units.

    Use this privilege to assign to those users who need access to view requisitions created by any requester or preparer. The feature is based on the business units to which the user currently has access.

    Edit Approval Rules in Oracle BPM Worklist

    POR_EDIT_APPROVAL_RULES_IN_BPM_WORKLIST

    Allows users to edit approval rules in Oracle Business Process Management Worklist Application after using the Oracle Procurement Manage Approvals to edit rules.

     

    Cancel Requisition Line in Spreadsheet

    POR_CANCEL_REQUISITION_LINE_IN_SPREADSHEET

    Enable self-service users to submit cancellation of requisition lines in bulk using a spreadsheet.

    With this privilege, a task entitled ‘Cancel Requisition Line in Spreadsheet’ will be available in the Shopping home page under the More Tasks menu.

    At this point, I would also like to remind you of the manual that lists all privileges and roles across Procurement. Here is a link to the latest security manual for additional reference.

    https://docs.oracle.com/en/cloud/saas/procurement/18b/oapcm/index.html#_Toc468200735_1

    Do let us know through your feedback on whether you found this useful!

  • Ashok
    Update 18C Feature: Fulfill Expense Requisitions for...Answered105.0
    Topic posted November 10, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, Internal Material Transfer, Requisition Processing in Procurement > Self Service Procurement public
    Title:
    Update 18C Feature: Fulfill Expense Requisitions for Agreement-based Catalog Items from Internal Sources
    Summary:
    BPA backed items will be sourced internally by default if eligible
    Content:

    Customers

    In Update 18C, we introduced a new feature that was driven off of requirements from the health care sector. The solution on offer should help any customer with similar requirements.

    Business Problem:

    If a requester searches for an item that happens to be both purchasable and available for internal transfer, and if that item was also backed by a BPA, then the system always sourced the item from the BPA. i.e. even if internally available, the system always processed a purchase order for it. Customers wanted a change in this behavior. 

    To quote a health care example, if a nurse at the nurse's station required an item for immediate use, if the item was available in stock, the expectation was to be able to utilize that rather than wait and place an order and expected it to be shipped and then be issued to the nurse. 

    Solution Details:

    A. Configuration:

    The following must be true to use this feature:

    a) Opt-in 'Fulfill Expense Requisitions for Agreement Based Catalog Items from Internal Sources' must be enabled. You will find this opt-in under the feature 'Internal Material Transfers'

    b) Requester must have the privilege 'Create Internal Material Requisitions'

    c) The destination type should be 'Expense'

    d) A valid BPA must exist for the item

    e) The master item must be available in the appropriate Deliver-to Organization

    B. How it works:

    When a requester searches for an item that is both internally transferable and purchasable, if that item has a valid agreement to source, the system will retrieve the search results for display. 

    NOTE: The system will display the BPA details by default (including price and other attributes). The idea is to allow users to leverage the rich functionality that an agreement offers in displaying attributes that describe the item in more detail

    When the user adds the item to cart, the system will source the item from the appropriate source organization and use the transfer price configured for that organization.

    IMPLEMENTATION CONSIDERATIONS:

    1. In order for the system to source the item internally, the internal transfer setup has to be complete. For instance, if there is no valid source organization determined, then the system will not attempt to source the item internally and instead use the agreement

    2. If you are noticing that the system is sourcing the item only from an agreement even though all the setup indicates it should be sourced internally, check the destination type on the requisition preferences. If it is not 'Expense', then what you are seeing is expected behavior

    3. If you are noticing that the system is sourcing the item only from an agreement even though all the setup indicates that it should be sourced internally, and the issue is not 2. above, then check if the master item is available in the Deliver-to Organization (This would either be the deliver-to organization of the Default Deliver-to Location on your Requisition Preferences page or if that Deliver-to Location was a global one, then the default Deliver-to Org from the Configure Requisitioning BU Preferences setup). If the item is not available in that organization, then the internal sourcing process cannot work.

    4. If you have setup the organization sourcing rules correctly but the transfer price setup is not correct or incomplete, then the system will not allow you to add the item to the cart. It will display an error suggesting transfer price related errors. You need to fix that before you can proceed

    5. The user should also have access to at least one catalog where all master items are enabled for access

    6. Master Org and Child Org Setup: If the item is set up to be Internally Transferable in the Master Org but not in the child org where the transactions are occurring, the system will not source the item to a Transfer Order. As these are item attribute setup configurations specific to an org (master or child), ensure that the attributes are correctly set in the org in which you seek to transact (if that is the child org, then the item should be internally transferable even in that org).

    Please review the attachment for some relevant screenshots.

     

     

  • Ashok
    How does the system assign a buyer on a requisition...24.8
    Topic posted November 19, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, Requisition Processing in Procurement > Self Service Procurement public
    Title:
    How does the system assign a buyer on a requisition converted to an order
    Summary:
    Buyer Assignment hierarchy on a requisition converted to an order
    Content:

    Customers

    I do hope this brief article helps clarify the logic of how the system computes a buyer for a given requisition line when converting to a purchase order

    Premise:

    A buyer is a mandatory element of a purchase order. If one does not exist, neither does a purchase order. If a requisition cannot determine a valid buyer, the requisition is placed in the Process Requisitions queue for the buyer (with the appropriate access) to review said requisitions and help create an order.

    Design:

    In Self Service Procurement, you can add a suggested buyer as a requester. I have covered this facet in a different customer connect article. (Please review that for context).

    If a suggested buyer is not entered, then the system's logic kicks in. Now you can review buyer assignment logic for two different kinds of items:

    A) A master item defined in inventory without a backing agreement:

    For such items, the system will first try to source the buyer from the item definition using the attribute 'Default Buyer'. If one is not prescribed in the item definition, additional logic kicks similar to the master item that has a backing agreement. See below.

    B) A master item or a description-based item with a backing agreement:

    Hierarchy:

    i) First resolve using buyer assignment rules

    ii) If buyer assignment rules cannot derive a valid buyer, then use the buyer if defined in the attribute 'Buyer', on the configuration page: Configure Procurement Business Function

    iii) If there is no buyer available in ii) above, then the requisition line will not be stamped with a buyer.

    NOTE: The same hierarchy defined in B) also applies to A) above.

    So the next time you find a requisition in the Process Requisitions queue because there is no buyer assigned, you know what to research.

    Thanks.

  • Ashok
    Illustration and steps for making Charge Account read only...65.0
    Topic posted May 3, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To in Procurement > Self Service Procurement public
    Title:
    Illustration and steps for making Charge Account read only on a Requisition
    Summary:
    How to make the charge account attribute on a requisition read only
  • Ashok
    Deep Link (Direct Link) to Self Service Procurement...85.0
    Topic posted November 16, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, Tip in Procurement > Self Service Procurement public
    Title:
    Deep Link (Direct Link) to Self Service Procurement Requisitions
    Summary:
    Deep Link to Self Service Procurement Requisitions
    Content:

    Customers

    This was something I thought would be interesting and helpful to share with you. We recently interacted with a customer that wanted to know if we can provide them  with a deep link (direct link) to requisitions.

    Business Requirement:

    Customer wants to have URL to access and view specific requisition data directly say, from an external system or during email communication. Currently each user has to log into application and navigate to Procurement > Purchases Requisitions > Manage Requisitions > Search, to search for a specific requisition each time.

    Resolution:

    Development provided this link that the customer then confirmed worked successfully.

    https://<host>/fscmUI/faces/FndOverview?fnd=%252FWEB-INF%252Foracle%252Fapps%252Fprc%252Fpor%252FmanageReq%252Fui%252Fflow%252FManageReqMainAreaFlow.xml%2523ManageReqMainAreaFlow%3BparamInvokedApp%253DNOTIFICATION%253BparamReqHeaderId%253D<req header id >%3B%3B%3Bfalse%3B256%3B%3B%3B&fndGlobalItemNodeId=itemNode_my_information_purchase_requisitions

    Thanks

    Ashok

  • Ashok
    Follow up and Feedback: Catalog Management Best Practices...25.0
    Topic posted October 9, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, Manage Procurement Catalog, Setup, Tip in Procurement > Self Service Procurement public
    Title:
    Follow up and Feedback: Catalog Management Best Practices Session
    Summary:
    Follow up and Feedback: Catalog Management: Best Practices session
    Content:

    Customers

    Here is a link to the post that contains the Replay of the recording and the presentation material.

    https://cloudcustomerconnect.oracle.com/posts/165ea574c1

    For those of you that could not attend the event or even those that attended that require a refresher, navigate down to the post details and you will find links to the recording and the slide deck.

  • Ashok
    Quick Tip: Buyer Assignment Rules for Non Catalog Requests144.9
    Topic posted January 13, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, FAQ, Requisition Processing, Tip in Procurement > Self Service Procurement public
    Title:
    Quick Tip: Buyer Assignment Rules for Non Catalog Requests
    Summary:
    Can I define buyer assignment rules exclusively for Non Catalog Requests
    Content:

    Customers / Support

    This tip comes to you courtesy of a customer who had asked this question last week. The customer was concerned that the buyer assignment rules were not functioning in the manner expected. Customer had created a smart form and expected the corresponding buyer assignment rules to apply. However, the rules were not applied to the requisition and the order.

    On further analysis, it was determined that the Buyer Assignment Rules were set to apply to Non Catalog Requests. 

    Tip:

    1. In the Buyer Assignment Rules setup, one of the attributes is entitled 'Non Catalog Request'. Use this attribute to determine whether or not a specific assignment rule should or should not apply to a non catalog request

    2. Non Catalog Request attribute can be Null, Yes or No. Null means the rule will apply to all requisition sources including Non Catalog Requests. Yes means that the rule will ONLY apply to requisitions created from Non Catalog Requests. No means that the rule will not apply specifically to requisitions created from Non Catalog Requests

    Please be aware of this behavior the next time you create these rules.

    Image:
  • Ashok
    Update 19B: Shopping Results: New Visual Indicator for...24.5
    Topic posted April 13, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, Internal Material Transfer in Procurement > Self Service Procurement public
    Title:
    Update 19B: Shopping Results: New Visual Indicator for Internally Orderable items
    Summary:
    New visual indicator introduced in the Shopping Search Results for an item that is Internally Orderable
    Content:

    Customers / Support

    In Update 19B, we have introduced a new feature that quickly identifies if an item is internally orderable.

    Pre-requisite:

    The Opt-in 'Internal Material Transfers' must be enabled.

    Feature:

    When the user searches for items in the Shopping home page, items that are internally orderable (the PIM attribute 'Internally Transferable' is checked for the item) are returned in the search results with a visual indicator and the text 'Internally Orderable'.

    Function:

    This helps provide a quick understanding of whether the item can be potentially sourced internally even if it is a purchasable item. The visual indicator is shown for all the following item configurations:

    a) Item is only internally transferable

    b) Item is both purchasable and internally transferable (whether the item is a master item or an agreement-backed item.

    NOTE:

    There have been other requests around whether we can indicate the item availability in stock in the search results. This is not in scope in the feature we have detailed above. I am providing this detail for context only.

    Image: