Posts

Posts

  • Ashok
    Part 1: Inventory Organizations, Deliver-to Locations,...75.0
    Topic posted November 16, 2018 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Inventory Cloud, Requisition Processing, Setup in Procurement > Self Service Procurement public
    Title:
    Part 1: 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:

    Customers

    A lot of you have recently posted various issues/questions on topics that primarily relate to one idea:

    A better understanding of how the following entities are used in Self Service Procurement flows:

    a) Inventory Organization

    b) Deliver-to Location

    c) Subinventories

    Part 1:

    I am writing this article in the hope that it will clarify a lot of these questions on behavior, interactions and process.

    Part 2:
    I will be discussing why and how an understanding of these interactions is important in the next part. Stay tuned.

    1. Glossary:

    Before we go any further, let us get some terms understood clearly.

    A. Requisitioning BU:

    A business unit that has the business function 'Requisitioning' defined. This is the cornerstone of the Self Service Procurement application. See setup: Manage Business Unit for more details

    B. Inventory Organization:

    In the context of Self Service Procurement, the first thing to note is that the terminology you will see is 'Deliver-to Organization'. This is the inventory organization that carries master items that are then configured as part of catalogs or on master agreements to then make it available for shoppers in the shopping flows. Setup: Manage Inventory Organizations

    NOTE: For the purposes of this article, I will be using the two terms interchangeably

    C. Location:

    This typically represents a physical location where a requester's items ought to be delivered. Setup: Manage Locations

    D. Subinventory:

    A subinventory is a sub entity of an inventory organization. It typically represents a storage facility for items. Subinventories are setup in the context of an inventory organization. Setup: Manage Subinventories and Locators.

    2. Relationships:

    Here is a quick overview of how these entities are related (as far as Self Service Procurement flows go)

    1. A Requisitioning BU is associated with one or more inventory organizations using the Manage Business Unit attribute in the inventory organization setup (See Screenshot A in the attached word document)

    NOTES: One Requisitioning BU can be associated to multiple deliver-to organizations through this setup

    2. A Location is associated to an inventory organization in two ways:

    a) In the Inventory Organization setup, you select a location

    b) In the Manage Locations setup, you can associate that location to a 'default' inventory organization (See Screenshot B in the attached document)

    NOTES: 

    a) These are not reciprocal. One location can be assigned to several inventory organizations via a). But one location can only be assigned one inventory organization via b)

    b)  If no inventory organization is associated to a location in b), that is termed a 'Global Location'.

    3. A subinventory is associated with an inventory organization via Manage Subinventories and Locators setup. One inventory organization can have one or more subinventories associated with it

    4. A deliver-to organization is stamped on a requisition line primarily from the Requisition Preferences setup as follows:

    a) If the Deliver-to Location setup in Requisition Preferences is a 'Global' location, then the default deliver-to organization from the Configure Requisitioning Business Function setup is used

    b) If the Deliver-to Location setup in Requisition Preferences is associated to a deliver-to organization in the Manage Locations setup, then that is used

    NOTE: A requisition on multiple lines can be associated to different Deliver-to Organizations as you can deduce from the above.

    5. The list of subinventories available in the Requisition Preferences page is based on 2 factors:

    a) Until the Deliver-to Location is picked, the list of subinventories will be all subinventories that belong to any deliver-to organization associated with the Requisitioning BU

    b) After a Deliver-to Location is picked, the list of subinventories will be restricted to only those that belong to the deliver-to organization associated with that deliver-to location (See D above)

     

  • jon whelan
    ERP Cloud Support - What's Available & How to Succeed154.9
    Topic posted December 5, 2018 by jon whelanRed Ribbon: 250+ Points, tagged Discussion Forums, Fusion, Help Center, Search, Setup, Tip, Upgrade in Core Financials > Financials – General public
    Title:
    ERP Cloud Support - What's Available & How to Succeed
    Summary:
    Slide deck from the UK OUG session covering tools, procedures, and tips available to Cloud subscribers.
    Content:

    There's more to support than just creating and managing Service Requests.  Prevention.  Proactive.  Cloud Customer Connect and My Oracle Support combined provide customers a multitude of resources to take full advantage of the self-service Premier Support investment with Oracle. 

    Customize your Dashboard. Personalize with Powerviews. Receive email notifications.   Avoid Service Requests.  Attend our monthly training webcasts.  Uncover the Oracle Learning Library.  Discover the Oracle HelpCenter.  Contribute in Cloud Forums.  Submit your ideas. Build your network.

    This and much more to accelerate your success with Oracle Support.

  • Aditya Singh
    How to Default Custom Accrual and Charge account on...Answered44.8
    Topic posted September 22, 2018 by Aditya SinghBronze Trophy: 5,000+ Points, tagged Setup in Procurement > Purchasing public
    Title:
    How to Default Custom Accrual and Charge account on Purchasing Documents (Inventory and Expense)
    Summary:
    How to Default Custom Accrual and Charge account on Purchasing Documents (Inventory and Expense)
    Content:

    Hi All,

    Usually many of us come across the scenario where we need to defaults account on requisition or purchasing documents.

    Here in fusion there is good structured SLA setup to do the same.

    I have created a document which will walk you through the SLA of purchasing and the setups need to be done to default accrual and charge account on purchasing documents.

    Thanks

    Aditya Singh

  • Ashok
    How to configure a Punchout Catalog via OSN25.0
    Topic posted November 15, 2018 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Requisition Processing, Setup in Procurement > Self Service Procurement public
    Title:
    How to configure a Punchout Catalog via OSN
    Summary:
    How to configure a Punchout Catalog via OSN
    Content:

    Customers

    A lot of you have asked us to provide documentation on this specific process: Configuring a punchout catalog via OSN.

    Please review attached document.

    Do let us know if these need edits, additions or further details.

  • Ashok
    Profile Options used in Fusion Self Service Procurement25.0
    Topic posted November 3, 2018 by AshokBlack Diamond: 60,000+ Points, tagged FAQ, Setup in Procurement > Self Service Procurement public
    Title:
    Profile Options used in Fusion Self Service Procurement
    Summary:
    Profile Options and their purpose in Fusion Self Service Procurement
    Content:

    Customers,

    A few customers have requested a note on the profile options that are available as part of the Fusion Self Service Procurement product offering. I provide below a brief introduction to the profile options and their purpose. This will hopefully provide you with a good understanding of when to use these as part of your implementations. 

    The list can be obtained using the task Manage Administrator Profile Values from the Setup and Maintenance menu option

    The table below illustrates the relevant details:

    Profile Option Code Profile Option Display Name Description Default Value Implementation Considerations
    POR_SEARCH_RESULTS_SKIN Search Results Skin

    Possible values: Paragraph and Grid

    Purpose: Controls the default display of the Shopping Search Results on the Shopping Home page. 

    Paragraph: Renders the search results in a card layout with each item displayed with an image

    Grid: Renders the search results in a tabular format

     

    Paragraph

    1. Use Paragraph mode if you prefer viewing results with images

    2. Table is more suited for multiple selection oriented operations

    POR_DISPLAY_CATEGORY_ITEM_COUNT Display Category Item Count Enabled

    Possible values: Yes and No

    Purpose: Allows customers to decide whether or not to display counts along with the categories displayed in the Shop by Category hierarchy structure

     

    No

    1. If you have an implementation that is not optimized to structure items within browsing and purchasing categories, setting this profile option value to No will improve the shopping page load performance

    2. The above is true only in cases where there really are a huge number of items that have to be brought under a single purchasing category

    3. For most customers, setting it to Yes will not cause a performance impact based on what we have seen

    4. If you set it to Yes, then the system will only display those purchasing categories that have at least one item associated with them  where price >=0.

    POR_REQUESTED_DATE_OFFSET POR: Requested Delivery Date Offset

    Possible values: Any positive numeric value

    Purpose: The value you set here determines the number of days until the requester needs the order. This value is used to compute the Requested Delivery Date on a Requisition

     

    7

    1. This value will only be used to default the Requested Delivery Date. Remember that the user can modify it

    2. If the value is set to Null in the profile option setting, the system will not default a value in the requisition for Requested Delivery Date

    3. If the item is sourced from an agreement, the Requested Delivery Date plays a role in ensuring that the agreement is valid for the date specified

    POR_ASSIGN_REQ_SAME_BUYER Use Same Buyer for all Lines in a Requisition

    Possible values: Yes and No

    Purpose: Allows all lines on a requisition to be assigned and processed by the same buyer

     

    No

    1. If the value is set to Yes, then the buyer assigned on the first line of the requisition is automatically updated to all lines on that requisition

    2. Use this option if your organization has a requirement to process requisition lines en masse and by a single buyer

    3. Remember this will overwrite any buyer assignment rules based assignments

    POR_RETAIN_LAST_ASSIGNED_BUYER Retain Last Assigned Buyer on Requisition Line

    Possible values: Yes and No

    Purpose: When a requisition line is returned by a buyer, you can choose this option to ensure that the requisition when resubmitted is processed by that same buyer

     

    No

    1. Use this option if your organization uses dynamic buyer assignment rules that could potentially reassign lines returned by a buyer to another

     

     

    I hope this information is helpful in increasing your understanding of these profile options and the implementation considerations relevant to using them. Do provide your comments and thoughts and your own organization's experiences with using these profile options. I am sure that would benefit other customers in gaining new perspectives on implementing these for their own organizations
     

  • Ashok
    Best Practices: Superuser Catalog Access to all items35.0
    Topic posted April 3, 2019 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Setup in Procurement > Self Service Procurement public
    Title:
    Best Practices: Superuser Catalog Access to all items
    Summary:
    Best practices tip for superuser access to all items
    Content:

    Customers / Support

    I wanted to write this article as an attempt to clarify some concepts in configuring Catalogs and providing users access to Catalogs.

    Customer Issue Reported:

    This customer provided the following problem statement:

    When opening the shopping home page, an error is thrown (See image attached).

    Root cause analysis:

    Development triaged this from first principles, i.e. Review the Content Zone and Catalog setup. On further detailed review, it was revealed that this specific user was a 'superuser' to whom the buying organization wanted to grant access to all items across all catalogs.

    So how did they go about doing this: They provided access to individual catalogs that were created the sum total of which would give access to all items (this amounted to around 30 or more). This was the root cause.

    Resolution:

    The best practice guidance around this is to create one catalog that provides access to all items. This is the right way of granting access to a superuser kind of role.

    Once this was done, the user was able to access all the items he/she wanted to and the shopping home page was bereft of issues.

    So, this seems simple you say. Yes, but sometimes there are efficient and not so efficient ways of configuring the system that could lead to such performance or critical errors. It is important to review how you are configuring these applications to help serve you better.

    I am hoping this serves as a configuration guidance for any customers who have implemented Self Service Procurement to take a look at their own configurations and ensure adoption of these best practices.

     

    Image:
  • 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.

  • Sumana Sarkar
    How to Personalize the Manage Requisitions Table34.7
    Topic posted January 2, 2019 by Sumana SarkarSilver Medal: 2,000+ Points, tagged FAQ, How-To, Setup, Tip in Procurement > Self Service Procurement public
    Title:
    How to Personalize the Manage Requisitions Table
    Summary:
    This article talks about leveraging the Page Composer to personalize the Manage Requisitions table.
    Content:

    Hello Customers, Support,

    There was a recent inquiry from a customer asking for the ability to customize the display columns of the Manage Requisitions table for all users rather than individual users modifying the table.

    The steps provided in the attached document demonstrate how an administrator can use Page Composer to personalize the page e.g.  select additional columns for display, re-order the columns, that would take effect for all users.

    Note: Users need to have the Procurement Application Administrator and Application Implementation Consultant roles in order to personalize the page.

  • Ashok
    Primer on Public Shopping Lists75.0
    Topic posted December 2, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, FAQ, How-To, Setup in Procurement > Self Service Procurement public
    Title:
    Primer on Public Shopping Lists
    Summary:
    Primer on Public Shopping Lists
    Content:

    A primer on Public Shopping Lists

    What is a Public Shopping List?

    Simply put, a pubic shopping list is a collection of items – master items as well as agreement lines based items. The purpose of a public shopping list is to provide a quick one stop collection of items that are likely to be ordered together by requesters in the organization.

    How does it work?

    A public shopping list is created and configured in the context of a Procurement BU. This is of key importance. A catalog administrator role allows the creation and maintenance of a public shopping list. A catalog administrator can add items that are valid in a specific procurement BU to create a shopping list.

    Why should we use it?

    Several factors determine the efficacy of configuring a public shopping list:

    1. Are there a standard set of items or services that are available to a common number of requesters?
    2. Is there a case for repeat usage?
    3. is the number of items large enough to save time and effort in searching each time?

    If the response to most of the above is in the affirmative, a public shopping list could help streamline and ease the process for the requester.

    Imagine a new hire process. You want your requesters to be set up with a standard list of items for work. Consider creating a New Hire Kit. This could include Office Supplies, any services that are to be utilized in starting work at the work place. Another use case that we frequently see is a shopping list for Legal Services that involve a set of processes (services or description based items) that are to be requested (Think of a Visa Process or Green Card process for employees that consists of a package of services to be included).

    In all such cases and more, a public shopping list saves the requester both time and effort in looking for disparate individual services.

    Features of a Public Shopping List:

    1. Effective dated:

    A public shopping list can be effective dated. It can have an end of life based on potentially the items contained within. Keep in mind if a basket of items or services is no longer relevant or has changed in its use, end dating the shopping lists makes it inaccessible to requesters. Use dates to control when a list ought to be visible. This way, you can plan a future process well ahead of time and release it based on the date that is appropriate.

    1. Suggested Quantity

    The list allows the catalog administrator to control the quantity that is needed for the standard requester to order. This is helpful specifically in cases where the items or services are complex and spares the requesters the trouble of having to ask or guess the right request quantity

    1. Agreement indicators clearly visible to Catalog Administrator:

    If the item added is based on an agreement line, the catalog administrator can also view additional attributes including the Negotiated or Negotiation Required status, agreement number, line type, buyer and supplier item details

    1. Item sequencing for display:

    The catalog administrator can specify a sequence in which the items ought to display for ease of use of the requester when ordering the items.

    FAQs on using Public Shopping Lists:

    1. How is this different from a Smart Form?

    They have a very different purpose than a smart form. A smart form is typically used for a simple category based item or service and not so much a ‘basket’ of items or services. Note that a public shopping list also leverages blanket agreements where smart forms only use contract purchase agreements.

    2. Why can’t the requester see the Public Shopping List in the Shopping Home page?

    Check the following:

    1. Has the list been assigned to a content zone through Content Security?
    2. Is the Procurement Business Unit on the shopping list the service provider for the Requisitioning Business Unit of the requester?
    3. Is the Public Shopping List still active?

    Any of these could cause the list to not be visible.

    3. Why do I see an error ‘This item is not available’?

    This essentially means the item is not available at this time to request. Possible reasons could be:

    1. The item itself is no longer valid
    2. The agreement line backing the item is not active
    3. The item is not available in the current session language
    4. Most important of all, the item is restricted in the catalog definition that is assigned to the user’s content zone

    NOTE: d) above is often the most common reason for an item not being available from a public shopping list. Catalog administrators should not forget that there is a close relationship between the Public Shopping List and the Catalog definition that configures the inclusion or exclusion of items or agreements or item categories. So, even if an item is added on a shopping list, if that item is not available to the requester through the catalog definition and assigned to the appropriate content zone.

    4. What are some implementation considerations to keep in mind in using Public Shopping Lists?

    1. Review the basket of items or services needs in your organization. Think about a public shopping list if you have use cases for the same
    2. Always check whether the Catalog configuration is likely to conflict with the items added to a public shopping list
    3. Catalog administrators should be proactive to ongoing business changes in effectively managing shopping lists (for instance, have the backing agreement lines expired causing the list of items to be redundant, is the shopping list still active and so on). 
  • Ashok
    Granting users access to multiple requisitioning business...45.0
    Topic posted November 15, 2018 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Setup in Procurement > Self Service Procurement public
    Title:
    Granting users access to multiple requisitioning business units
    Summary:
    How to grant users access to multiple requisitioning business units
    Content:

    Customers,

    We receive several forum posts on a regular basis from customers with questions on how data roles and user access works..

    Context:

    You must all be aware that out of the box, requesters with an employee role are given access to the default business unit based on the worker's primary assignment. This article discusses the points to consider and the process in assigning requesters access to multiple business units. In particular, I would request you to pay attention to the Notes section in the document that highlight some of the key pointers you have to bear in mind when implementing this.

    As always, let us know if you find the article helpful. Also share your experiences with using this feature.