Supplier Management

Get Involved. Join the Conversation.

This is a public Forum public

Posts

<< First
< Prev
11-20 of 91
Next >
Last >>

Broad-Based Black Economic Empowerment (B-BBEE)15.0
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
Child fields in request parameter for Get All Suppliers REST...Answered3
Topic posted November 8, 2019 by David Wright, tagged Business Intelligence, Fusion, How-To
Title:
Child fields in request parameter for Get All Suppliers REST API
Summary:
What's the notation for child fields for expanded items in this API
Content:
The documentation says "If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. "

So, if my parameters say 'fields' : 'Alias,AlternateName,Supplier,SupplierId,SupplierNumber,sites.PaymentTerms' then shouldn't sites.PaymentTerms be valid for Suppliers? However, when I try to use any variation of this (with . or ; or :) it fails with 'URL request parameter fields with value Alias,AlternateName,Supplier,SupplierId,SupplierNumber,sites.PaymentTerms is not valid.'

Is my notation incorrect, or can I not access child items in such a manner for Supplier?
Configurable auto creation of site assignments for spend...Answered74.7
Topic posted September 28, 2018 by Shivani Roy, 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.

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.
Configure to Route a Supplier Initiated Profile Change...5.0
Topic posted December 20, 2018 by Piyush Singh, 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.

Step 1:

Login as Procurement Application Administrator.

Step 2:

Navigate to Task Configuration in BPM Worklist.

Step 3:

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

Step 4:

Access the task and click to edit.

Step 5:

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

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.

Step 7:

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

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.
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.
Contact Duplicate Identification and Address Duplicate...35.0
Topic posted October 6, 2019 by Catherine Hull, tagged How-To, Setup, Supplier Creation, Supplier Profile Management
Title:
Contact Duplicate Identification and Address Duplicate Identification
Summary:
What is the purpose of "Contact Duplicate Identification" or "Address Duplicate Identification" ?
Content:
Under Define Supplier Matching > Manage Enterprise Data Quality Matching Configurations, what is the purpose of "Contact Duplicate Identification" or "Address Duplicate Identification" ?

This question arose, because after following the Oracle setup documentation (all steps of Implementing-Procurement.pdf > Enabling Supplier Match: Explained), I obtained results after setup of 'Account Duplicate Identification' BUT no results after setup for 'Contact Duplicate Identification' or 'Address Duplicate Identification'. The 'Account Duplicate Identification' setup provided results when testing in the system or testing Actions > Review Configuration Results.

My results are in a system with multiple suppliers, duplicate information within multiple supplier records, and duplicate information within one supplier record.

The Oracle Implementing Procurement manual does not provide any detail about the purpose of "Contact Duplicate Identification" or "Address Duplicate Identification". I have not been able to find additional insight anywhere else.

Thanks, Catherine

Version:
Oracle Cloud 19B
Document:
implementing-procurement-19c.pdf (4.4MB)
Creating an Existing Party as a Supplier15.0
Topic posted April 25, 2019 by Piyush Singh, tagged How-To, Import, Supplier Creation, Tip
Title:
Creating an Existing Party as a Supplier
Summary:
How to establish a supplier relationship for an existing party
Content:
In today’s competitive business environment, organizations must continuously strive to optimize business flow efficiency and operate more strategically. One opportunity is for smarter modeling of trading relationships with key business partners to gain better visibility and business insight into these relationships. This is achieved in Oracle Cloud by creating multiple relationships with the same company, for example, a banking provider that is also a customer or, a customer that also serves as a strategic supplier providing goods or services. These represent different business relationships with a single enterprise, which can be managed from both the supplier and customer master by leveraging a single shared party profile record.

You can establishing a supplier relationship with an existing party either using Data Quality Management or using Supplier Import process. Following is a brief on the usages of these approaches.
1. Data Quality Management (DQM): DQM is a preventive mechanism empowering users such that they do not create duplicate parties identified as parties with similar names. DQM does not rely on exact match of the name (depending upon the configuration) to list out the potential duplicates therefore is very effective in preventing duplicate parties in the application.
2. Establishing supplier relationship using supplier import: When user knows the party that he or she has to create as a supplier, then this approach will be more effective. Following this approach, user saves time required to review all the potential matches as well as avoids any mistake in form of picking up incorrect party for supplier relationship establishment.
*Details on Data Quality Management will be covered in another post.

If you know the exact party that you want to create as a supplier, use the supplier import capability to achieve the same. Following are the steps you need to follow when creating supplier from an existing party (customer in the example below).

1. Find the Registry ID of the customer from the Manage Customers task.

2. Use this Registry ID and the Organization Name to create a supplier relationship for this customer using the supplier import process. Populate the FBDI template for Supplier Import as shown in the screen shot below.

Points to consider when using Registry ID in the template:
1. Provide Registry ID only for the import action ‘Create’.
2. Organization Name must be entered exactly as the Supplier Name. If not, the record will be rejected.
3. Complete the supplier import process (generate csv > load file to interface > run supplier import job).
4. After the import process completes successfully, search for this supplier, and review the registry ID along with the Relationships of the supplier.
Additional reference:

- Create Supplier From Existing Party Using Supplier Import: TOI
Customizing an Attribute as Required in Party Sharing Data...15.0
Topic posted November 30, 2018 by Piyush Singh, tagged How-To, Tip
Title:
Customizing an Attribute as Required in Party Sharing Data Model
Summary:
Point to consider when configuring an attribute as required in the party sharing data model through Application Composer
Content:
In one of our earlier posts, we shared information about party sharing model. The note also covered points to consider in managing parties under such structure.

Refer: Party Sharing Impacts and Managing Parties

In this post, we will cover the impact of using Application Composer to customize a field as required in the central data model that caters to different parties sharing data, including suppliers.

Application Composer provides customization flexibility in CRM pages. One such customization is to make an attribute required. There are possibilities that this customization will affect supplier flows and result in errors when creating suppliers.

Therefore, when creating a supplier, if you encounter a required attribute error for attribute that is not available on the UI, you can follow these steps to resolve the issue.

Root Cause:

The error shows because of an attribute that is configured as required through Application Composer. You can identify the attribute from the error message too.

Steps to resolve this error:

Step 1: Create a new sandbox and set it as active.

Step 2: Access Application Composer (Navigator > More > Configuration > Application Composer)

Navigation to Application Composer

Step 3: Make following selections:

Application – CRM Cloud

Objects – Standard Objects > Account > Fields

Select Account Fields for Standard Objects under CRM Cloud application

Step 4: On the Fields page, click on the Standard tab and search for the attribute for which the error was shown. For example, if the error was for attribute ‘Fiscal Year End Month’, search for attribute 'Fiscal Year End Month'. The search result will show that the attribute is set as required (Required column shows the flag as enabled). This is the cause for the error when creating the supplier.

Attribute Fiscal Year End Month is configured as required

Step 5: Edit the attribute’s property to remove the required constraint and save the change.

Edit the attribute’s property to remove the required constraint

Step 6: Publish the sandbox and then try to create the supplier. You will not see the error anymore.
Difference between external Registration URL Link -...10
Topic posted August 14, 2018 by Ramesh Radhakrishnan, tagged How-To, Supplier Registration
Title:
Difference between external Registration URL Link - Prospective Vs Spend Authorized
Content:
I would like to know what is the key difference between prospective and spend authorized link URL's. I see that both are having similar feilds and there is no difference where the supplier can indicate if they are registering for spend authorized or prospective? How is this behaviour controlled when customers publish these links to the suppliers in thier external website.

Any explanation on the difference between the spend authorized and prospective registration URL links will be helpfull.
Disable All Emails notificationsAnswered3
Topic posted August 22, 2019 by Prateek Parasar, tagged Approvals/Notifications, How-To, Supplier Creation
Title:
Disable All Emails notifications
Summary:
Disable Email in Supplier Registration
Content:
Hi, I would like to know if there is a way to disable all emails from the system. I know I can run BPM in test mode to send all emails to one address but I am more interested to know other emails such as User registration, forgot password and emails from supplier portal. Anyway to disable all ? Are these kind of emails considered OIM emails ? (I believe OIM notification requires a SR) but want to confirm if thats the only thing needs to be done.
Does supplier portal support Contract authoring in R124
Topic posted August 1, 2017 by Ramesh Radhakrishnan, tagged How-To
Title:
Does supplier portal support Contract authoring in R12
Summary:
Does supplier portal support Contract authoring in R12
Content:
Hello,

I wanted to know if supplier portal supports Proc contracts red lining functionality in R12. I see that there is a ER: Bug 22391858 for this functionality? Any updates on this?

Thanks

Ramesh