Supplier Management

Get Involved. Join the Conversation.

Posts

  • Ramesh Radhakrishnan
    "Update Supplier Keyword Search Index and Source to...6
    Topic posted June 9, 2019 by Ramesh RadhakrishnanBlack Diamond: 60,000+ Points, tagged Audit, Business Intelligence, FAQ, How-To, Sourcing Programs, Supplier Creation, Tip 
    Title:
    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes and Errors
    Content:

    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes  and Errors and it is not generating any error log. Any pointers about this program how to troubleshoot this program. Also I see below note relevant to this program

    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes (Doc ID 2474423.1)
    Version:
    R13-19B
  • Hong Gao
    Access to Supplier BI Reports45.0
    Topic posted September 25, 2018 by Hong GaoGold Medal: 3,500+ Points, tagged Business Intelligence, Security, Tip 
    Title:
    Access to Supplier BI Reports
    Summary:
    Function security for accessing supplier related OTBI reports
    Content:

    As part of supplier administration and management, internal users want to leverage Oracle Transactional Business Intelligence (OTBI) to review seeded reports as well as construct ad-hoc reports to meet business requirements. Seeded job roles like Supplier Administrator or Supplier Manager has all the function security set up out of the box to satisfy the reporting needs for managing suppliers. However, from time to time, you may want to grant other functional users the ability to review and build reports related to supplier data.

    To achieve that, here are a couple of function security considerations.

    1) there are currently four BI subject areas that are dedicated to supplier and supplier profile data: Supplier - Supplier Real Time, Supplier Registration - Supplier Real Time, Supplier - Profile Change Request Real Time, and Supplier Import - Supplier Real Time.  Content in these subject areas are all secured by duty role Supplier Master Data Transaction Analysis Duty. If your reporting need requires information from these subject areas, this duty role is necessary to access the content.

    2) apart from the duty role above, to have the ability to build an ad-hoc report, the user would also need to have the BI Author role.  

    Within the four supplier content subject areas, there are a few seeded reports:

    a) Supplier Export Reports (catalog path: /Shared Folders/Procurement/Embedded Content/): this folder contains seeded reports that can be used to extract data to populate the import supplier FBDI templates for mass update:

    •  
    • Export supplier data for import template
    • Export supplier addresses data for import template
    • Export supplier business classifications data for import template
    • Export supplier contacts data for import template
    • Export supplier contact addresses data for import template
    • Export supplier products and services category data for import template
    • Export supplier site assignments data for import template
    • Export supplier sites data for import template
    • Export supplier site third-party relationships data for import template

    b) Listing of Supplier Profile Change Requests (catalog path: /Shared Folders/Procurement/Supplier Profile Change Request/Transactional Analysis Samples/): this report allows users to search and report on profile change requests across the supply base.

    User can access the seeded reports by browsing through Catalog.  However, to properly view the data in these reports, user will also need to have the Supplier Master Data Transaction Analysis Duty.

    A special note for supplier portal users:

    • While collaborating with suppliers through Supplier Portal, it's important to note that supplier portal user does not have a navigation path to Report and Analytics work area to build ad-hoc reports.  On Supplier Portal landing page, there is an infolet for Transaction Reports.  From there, user can drill down to an OTBI dashboard with seeded reports on their transactions.
  • Hong Gao
    Allow users to view supplier profile PII attributes unmasked5.0
    Topic posted May 28, 2018 by Hong GaoGold Medal: 3,500+ Points, tagged How-To, Security, Supplier Profile Management, Tip 
    Title:
    Allow users to view supplier profile PII attributes unmasked
    Summary:
    Configure view only supplier profile access to see unmasked PII attributes
    Content:

    Internal users with Supplier Profile Inquiry Duty have view only access to supplier profile.  With this duty, user typically sees supplier PII attributes as masked, such as taxpayer ID and tax registration number (for suppliers with Individual or Foreign Individual tax organization type) as well as national insurance number.  When there is a need to allow a particular group of users to see these PII attributes as unmasked, it's necessary to configure a duty role to include the data security policy that enables this.  To achieve this, the following steps can be followed by an administrator or someone who can create and modify job roles:

    • Go to Security Console.  Search and copy duty role Supplier Profile Inquiry (ORA_POZ_SUPPLIER_PROFILE_INQUIRY) with copy option "Copy top role and inherited roles".
    • Under the Data Security Policies train stop, click Create Data Security Policy button.
    • Search for Supplier Personally Identifiable Information in Database Resource LOV dialog.
    • Select All values for Data Set.
    • In Actions drop-down, check Maintain Supplier Corporate Identifiers and Maintain Supplier Individual Identifiers PII.
    • Review the changes under the Summary and Impact Report train stop.
    • Complete the role copying and modification by clicking the Submit and Close button.
    • Refer to the steps above to create a new job role. Assign the new duty role to the job role.
    • Assign the job role to an internal user.

    This internal user will continue to have view only access to supplier profile, but he/she can see the supplier profile PII attributes as unmasked.

  • Patrick Daniels
    An easier way to navigate Oracle to find ERP resources!
    Topic posted October 28, 2018 by Patrick DanielsSilver Medal: 2,000+ Points, tagged FAQ, How-To, Tip 
    Title:
    An easier way to navigate Oracle to find ERP resources!
    Summary:
    Know which Oracle ERP Cloud resources to use - and when - in a single page dashboard view!
    Content:

    Check out these product specific Quick Link charts. 

    These make navigating Oracle much easier!

    We appreciate any feedback you have,

    Oracle Customer Care

  • Piyush Singh
    Approval Configuration for Supplier Profile Change Requests15.0
    Topic posted September 26, 2018 by Piyush SinghSilver Trophy: 7,500+ Points, tagged Supplier Profile Management, Tip 
    Title:
    Approval Configuration for Supplier Profile Change Requests
    Summary:
    Understanding the impact of setup task Configure Supplier Registration and Profile Change Request on the approval routing of supplier profile change requests.
    Content:
    Supplier Profile Change Request is a document that consolidates all the changes from a supplier user, either directly through profile edit in Supplier Portal or through questionnaire or negotiation response, and route it for approval.
     
    The change request approval is determined through two setup pages. The first one determines if an approval is required or not. If from the first setup, application identifies that approval is required, then it uses the second setup to determine the approvers for the change request.
    The setup pages are:
     
    1. Configure Supplier Registration and Profile Change Request, and
    2. Manage Supplier Profile Change Approvals
     
    This post intends to provide details for the first setup task i.e. Configure Supplier Registration and Profile Change Request. We will cover details for the second setup task i.e. Manage Supplier Profile Change Approvals in another topic.
     
    Configure Supplier Registration and Profile Change Request
    This is the first setup that determines whether a supplier profile change request requires approval. Oracle Procurement Cloud gives you the flexibility to configure approval required only for supplier profile entities that you consider as important for collaborative review and approval process. For the entities that you consider as not so important for reviewing changes, you can configure them as approval not required. You also get the flexibility to configure the approval requirement for the supplier profile change requests based on supplier’s business relationship.
     
    Use cases to explain the setup behavior:
     
    Use case 1:
    For all suppliers i.e. Prospective as well as Spend Authorized, you do not want approval for changes to supplier Contacts and Addresses, but you want approval for all other supplier entities.
    In the setup page, for both the business relationships, configure Contacts and Addresses as No Approval Required. Configure all other entities as Approval Required. With this setup, application will apply directly (auto approve) a change request with changes only to supplier contacts or supplier addresses or these two combined. Change request with changes to any of the other entities will be routed for approval.
     
    Use case 2:
    For Spend Authorized suppliers, profile changes to only Bank Accounts and Products and Services require approval.  For all Prospective suppliers, profile changes to only Products and Services require approval.
    In the setup page, under Spend Authorized business relationship, configure Bank Accounts and Products and Services as Approval Required and all other entities as No Approval Required. Under Prospective business relationship, configure Products and Services as Approval Required and all other entities as No Approval Required. With this setup, whenever spend authorized supplier’s bank accounts or products and services are changed, application will route the changes for approval. If for same suppliers, changes do not include bank accounts or products and services, application will apply directly (auto approve) the change request. Similarly for prospective suppliers,  if a change request has products and services changes then application will route the request for approval otherwise it will directly apply (auto approve) the change request.
     
    When evaluating a change request, if application identifies the need for approval based on this setup, it will route the change request to approvers as configured on the approvals setup task Manage Supplier Profile Change Approvals.
     
    Best Practice:
    Evaluate your business and utilize the options available to configure whether changes to supplier profile entities require approval or not.
    This will:
    1. Improve the turnaround time,
    2. Lower the change requests count that approvers will have to review and approve, and 
    3. Reduce the overhead for Supplier Administrators or Supplier Managers following up with approvers to get the profile changes dispositioned.
  • Mohammad Alhindawi
    Approval cycle for the suppliers master data creation6
    Topic posted March 11, 2019 by Mohammad AlhindawiRed Ribbon: 250+ Points, tagged Approvals/Notifications, Audit, Business Intelligence, Create Requisition, Customization, FAQ, Financials, Fusion, How-To, Import, Orders, Payables, Public Sector, Requisition Processing, Security, Setup, Sourcing Programs, Supplier Communication, Supplier Creation, Supplier Merge, Supplier Profile Management, Supplier Registration, Supplier User Account, Tip, Web Services, White Paper 
    Title:
    Approval cycle for the suppliers master data creation
    Summary:
    Approval cycle for the suppliers master data creation
    Content:

    Is there an approval cycle for the suppliers master data creation in the app?

    Version:
    Oracle Fusion Procurement Cloud
  • Lot
    Broad-Based Black Economic Empowerment (B-BBEE)1
    Topic posted November 7, 2019 by Lot, tagged FAQ, How-To, Supplier Registration, Tip, White Paper 
    Title:
    Broad-Based Black Economic Empowerment (B-BBEE)
    Summary:
    Documentation on how to configure Broad-Based Black Economic Empowerment (B-BBEE)
    Content:

    Hi, 

    Is there a documentation available on how to configure Broad-Based Black Economic Empowerment (B-BBEE)  for South Africa and what Oracle Cloud version is this available?

    Topics Requested:
    -Documentation on how to configure B-BBEE 
    -How to enable  (PPPFA) Scores Report, BBBEE Rating etc)
    -What Oracle CLoud version is this available ?

     

     

    Version:
    Oracle Cloud R13 19C
  • Piyush Singh
    Capturing Supplier Bank Accounts at Different Supplier...35.0
    Topic posted August 29, 2018 by Piyush SinghSilver Trophy: 7,500+ Points, tagged Tip 
    Title:
    Capturing Supplier Bank Accounts at Different Supplier Levels
    Summary:
    Points to consider when capturing supplier bank accounts at different supplier levels
    Content:
    Supplier bank accounts facilitate electronic payments from the buying organizations to the suppliers against Invoices. To ensure that suppliers receive payments in right bank accounts and for better usability, Oracle Cloud allows segregating bank accounts for suppliers at different profile levels, which are:
    1. Profile
    2. Addresses
    3. Sites
    Capturing supplier bank accounts at different supplier levels affects the defaulting of bank accounts on Invoices. The defaulting mechanism is as follows:
    Application first looks for valid bank account captured for the site for which the invoice is created. If no valid bank account identified, it looks for a valid bank account captured at the address level. The address looked for is the one to which site belongs. Again, if no valid bank account identified, application looks for a valid bank account at profile level. If no valid bank account identified at any of these levels, then no bank account defaults on the invoice and user has to select the right option.
    This implies that application considers all supplier levels to pick the right bank account for defaulting, and not just a specific level. 
    Review following use cases that provide details on when to capture bank accounts at different levels: 
     
    Use cases:
    1. Suppliers who transact in single currency and always receive payments in one specific bank account, irrespective of number of addresses, will have just one bank account. In such cases, capture the bank account at profile level.
    2. Suppliers can transact in multiple currencies identified through different bank accounts, but have all supplier addresses sharing same bank accounts to receive payments from the buying organization. In such cases, capture the bank accounts at profile level.
    3. Suppliers can have multiple addresses and each address independently transacts with the buying organizations i.e. each has unique bank accounts to receive the payments. For such cases, capture the bank accounts at address level.
    4. Suppliers can have multiple addresses and some of them independently transact with the buying organizations i.e. have unique bank accounts to receive the payments. The rest of the addresses share same bank account to receive the payments from buying organization. For such cases, capture the bank accounts at address level for addresses that have unique bank accounts to receive payments. For other addresses sharing same bank account, capture the bank account at profile level.
    5. Suppliers can have very complex business structure wherein for same address they provide different bank accounts to receive payments from different business units (identified through supplier sites) of the buying organizations with which they transact. For such cases, capture the bank accounts at site level.
    6. Similar to point 4 above, capture bank accounts for site only when the site has a unique bank account to receive the payments. For sites that share same bank account, capture the bank account at the address level or profile level following the cases detailed above.
    7. In certain cases, addresses or sites share same bank accounts, but each treats different bank accounts as their primary. In such cases, first create all bank accounts at profile level. Identify the bank account that is primary to most of the supplier addresses or sites. Mark this bank account as primary at profile level. Now, select and add the bank accounts that are primary for other addresses or sites at address level or site level and make them primary at that level.
    Best practice: 
    Capture the bank accounts at profile level first and then capture them at other levels only if there is a business use case as explained earlier.
  • Shivani Roy
    Configurable auto creation of site assignments for spend...Answered74.7
    Topic posted September 28, 2018 by Shivani RoyBlue Ribbon: 750+ Points, tagged How-To, Setup, Supplier Creation, Tip 
    Title:
    Configurable auto creation of site assignments for spend authorized suppliers
    Summary:
    Configurable auto creation of site assignments for spend authorized suppliers
    Content:

    After a supplier's spend authorization request is approved, the following changes will be applied on the supplier profile:

    1. Supplier’s business relationship changed to Spend Authorized,
    2. New sites created for the supplier depending upon the addresses and business units available in the request, and
    3. Site assignments can be automatically created for the new sites.

    Sites and site assignments are necessary for any financial transactions for the supplier. Site creation is automated so that sites are available at the earliest and with minimal manual intervention.

    Site assignments are also auto created based on the Procurement BU of the site. For more flexibility, you have the option to control the auto creation of the site assignments i.e. you can configure whether auto creation should happen for site assignments or not.

    This configuration is controlled by a checkbox option ‘Auto create site assignments for spend authorized suppliers’ present on the Configure Supplier Registration and Profile Change Request setup. By default, the checkbox is enabled that means site assignments will be created automatically. Unchecking this checkbox will prevent the auto creation of site assignments post spend authorization request approval.

    If you choose to not auto create site assignments, you will have to create them manually from the Edit Supplier page before you enter transactions for such suppliers.

    screenshot.JPG?version=1&modificationDate=1538132157000&api=v2

    Best Practice:

    Based on the business unit setup, consider the number of client BUs that will need to transact with the sites. If the majority of them will need to use the sites for transactions, enable the auto create site assignments option. Otherwise, it may be better to manually create the site assignments rather than deleting the unwanted assignments created from the auto create configuration.

  • Piyush Singh
    Configure to Route a Supplier Initiated Profile Change...5.0
    Topic posted December 20, 2018 by Piyush SinghSilver Trophy: 7,500+ Points, tagged How-To, Tip 
    Title:
    Configure to Route a Supplier Initiated Profile Change Request to Users with Specific Application Role
    Summary:
    How to assign a group of users, with a specific application role, to receive approval notification for Supplier Initiated Profile Change Requests?
    Content:

    You may have use case to route a change request for supplier profile to a group of users whom you have designated to review the supplier profile changes and take appropriate actions. Using the FSM task ‘Manage Supplier Profile Change Approvals’, you can achieve this by selecting routing to:

    1. An approval group, which has all the users you want to notify for approval, or

    2. All your Supplier Administrators or Supplier Managers.

    Using an approval group allows you to route change requests to a fixed set of users, who are part of the group, irrespective of their job roles. Whereas you can use seeded Supplier Administrator and Supplier Manager job roles to route the change requests to your users with these roles. We use these seeded job roles to provide an out of the box change requests routing.

    If your use case requires more flexibility and the above options do not fit the bill, then you can configure your routing based on job roles. This option is not available through the setup page ‘Manage Supplier Profile Change Approvals’, but you can change the approval configuration through BPM following these steps.

    For example, I have created a custom role POZ_Supplier_Administrator_Abstract_CR that I want to add for the routing of change requests.

    image2018-12-20_12-48-25.png?version=1&modificationDate=1545290596000&api=v2

    Step 1:

    Login as Procurement Application Administrator.

    Step 2:

    Navigate to Task Configuration in BPM Worklist.

    image2018-12-20_12-48-43.png?version=1&modificationDate=1545290596000&api=v2

    image2018-12-20_12-49-23.png?version=1&modificationDate=1545290596000&api=v2

    Step 3:

    Search for task ‘ProfileChangeRequestApproval’ and click to edit the assignees for this task.

    image2018-12-20_12-49-43.png?version=1&modificationDate=1545290596000&api=v2

    Step 4:

    Access the task and click to edit.

    image2018-12-20_12-49-54.png?version=1&modificationDate=1545290596000&api=v2

    Step 5:

    Navigate to the Assignees tab and click Go to rule icon for the participant where your approval rule is authored.

    image2018-12-20_12-50-40.png?version=1&modificationDate=1545290596000&api=v2

    Step 6:

    Identify the rule for which you need to change the routing and expand it. For this rule, under 'Then' region, enter null for Users and Groups. Use Application Role search to select and add the role that you want to add for routing.

    image2018-12-20_12-51-8.png?version=1&modificationDate=1545290596000&api=v2

    image2018-12-20_12-51-13.png?version=1&modificationDate=1545290596000&api=v2

    image2018-12-20_12-51-20.png?version=1&modificationDate=1545290596000&api=v2

    image2018-12-20_12-51-25.png?version=1&modificationDate=1545290596000&api=v2

    Step 7:

    Once done, click to save the changes and then commit the changes.

    image2018-12-20_12-51-36.png?version=1&modificationDate=1545290596000&api=v2

    image2018-12-20_12-51-53.png?version=1&modificationDate=1545290596000&api=v2

     

    Points to consider:

    1. Identify your approval requirements and then depending upon your requirements you can use either BPM or FSM to author approval rules. If approval requirements are simple and can be accomplished using FSM, then we recommend using FSM task ‘Manage Supplier Profile Change Approvals’ to author approval rules. For complex approval requirements that are not supported through FSM task, you can use BPM task ‘ProfileChangeRequestApproval’ to author approval rules.
    2. Flipping between FSM and BPM for approval configuration is discouraged and therefore you must finalize and stick to one for your approvals configuration.
    3. With the change detailed above, the approval history region will not show the actual approvers who receive the approval notification, but it will show the application role receiving the notification. 

    image2018-12-20_12-52-5.png?version=1&modificationDate=1545290596000&api=v2

    To review the list of users who have this role, you need to navigate to Security Console. Search for the role and click to edit. Under Users train stop, you will find all the users with this role.

    image2018-12-20_12-52-27.png?version=1&modificationDate=1545290596000&api=v2