Oracle Supplier Lifecycle Management (SLM) provides an extensive set of features to support the qualification, profile management and performance assessment of suppliers as well as tools to track ongoing supplier compliance with corporate and legal requirements. Utilizing these capabilities, organizations can exercise proper control over suppliers throughout the lifecycle of their relationship with the organization; from initial discovery, through qualification and on-boarding, to ongoing maintenance and possible obsolescence.
A key factor in improving the quality of an organization’s supplier master file is to establish proper processes to formally qualify different types of prospective suppliers. Supplier Lifecycle Management enables any and all of the peculiar information required to assess a prospect to be gathered and then routed through the organization to ensure efficient review of the supplier’s credentials.
Once a supplier has been approved, SLM also enables organizations to gather feedback from key stakeholders as part of an overall supplier performance tracking process. In addition, Supplier Lifecycle Management also allows key stakeholders to identify and track critical compliance documents and attributes that need to be gathered from suppliers on a periodic basis in order for the two parties to maintain an active business relationship.
One of the challenges with managing supplier information is that the pieces of information gathered about a supplier can be stored in a variety of applications and systems. This data disbursement can hamper organizations as they look to review supplier performance or to comply with audit requirements.
Supplier Lifecycle Management provides a repository for storing information from disparate sources and then enabling a 360 degree view of the data to be provided to the key business users within the organization. As well as access to basic supplier information - such as address, contact, contact points, business/diversity classification, general classification, product and services category, banking details, supplier tasks, notes, and supplier party relationships - users will be able to review qualification and on-going evaluation details for the supplier, view key documents that have been included in the supplier’s profile and check the status of deliverables that the supplier is required to provide to maintain their status within the system.
To better understand the capabilities of suppliers in key product categories, Supplier Lifecycle Management utilizes User Defined Attribute technology to allow administrators to add an unlimited range of attributes to the supplier definition and to group these into logical Profile sections. Typically, this is the sort of information stored in paper-based systems that are maintained by different departments throughout an organization. In addition to the attribute name, administrators are able to add descriptive text to help explain the purpose of the attribute.
Fine-grained access control tools allow administrators to manage which users can have access to the individual attributes in the extended set of profile details. This is particularly important when sensitive information is stored in the profile and access needs to be restricted to appropriate users either internally or at the supplier.
To assist administrators charged with managing the vendor master for their organizations, Advanced Search capabilities enable them to efficiently find and retrieve supplier records.
The Advanced Search allows any of the standard and extended profile attributes to be used as search criteria and for the results to be viewed using multiple display formats. The profile information retrieved from the search can be exported in spreadsheet format. The Advanced Search criteria and display formats can be personalized both at the administrator and business user level.
Most organizations maintain a team of administrators to deal with the flow of administrative updates from trading partners containing changes to their company profile details. To make this process more efficient, Supplier Lifecycle Management extends existing iSupplier Portal functionality to allow supplier users to be given online access to maintain a wider range of their own profile details.
The supplier user can maintain standard company profile details such as address, contacts, business/diversity classifications, products and services category, and banking details. Internal administrators can review the changes that suppliers provide before approving the changes.
Suppliers are also able to access qualification and on-going compliance information that they are required to provide to the buying organization to maintain their status in the system.
To help manage the stream of inquiries that come from supplier prospects interested in doing business with the buying organization, many companies now use their corporate websites to have potential suppliers register their interest in establishing a business relationship. This allows the organization to get key information from the supplier that can be used to qualify whether they are a suitable trading partner. Supplier Lifecycle Management provides a supplier registration feature that can be configured by business unit to gather the data elements required to assess each prospective supplier request. The registration form can be configured to include Address, Contacts, Business Classification, Product and Services category, Banking detail and any of the Extended Supplier Profile attributes. The prospective supplier can also upload attachments as part of their registration packet.
To support sophisticated and conditional qualification procedures, administrators can also establish RFI documents that allow various profile and compliance information from the prospect to be captured using a questionnaire format.
In addition to the walk-up process, buyers can pre-register and send invitations to prospective suppliers, requesting them to provide additional details for pre-qualification and approval using the self-service capability.
To support complex or lengthy supplier registration, prospective suppliers can save their draft registration request at any time, and return to it at a later date. Once a prospective supplier has registered, their request is routed through an approval hierarchy for review.
For many organizations, the processes for assessing new supplier relationships are cumbersome and inefficient. In an effort to ensure that “business gets done”, companies often support multiple channels for receiving new supplier requests and then follow a very limited or haphazard procedure to review supplier credentials. Oftentimes, this is a poorly coordinated manual process that requires tasks to be sequenced and tracked across multiple departments as credit checks are carried out, customer references called, quality standards reviewed and production facilities inspected.
Supplier Lifecycle Management leverages the Approval Management Engine to allow companies to generate customized approval flows for processing supplier requests and registrations. The details for each new supplier can be passed to multiple stakeholders across many departments within the buying organization.
Approvers are notified when they are required to review a request and can check graphically the overall approval status for a given request. As part of the approval routing, SLM includes the qualification information collected from the supplier as well as incremental feedback provided by business users assessing the request. This allows basic supplier profile and qualification details to be gathered, deliverables like Insurance certificates and Code of Conduct documents to be stored and Products and Services information to be recorded within the Qualification packet. The buying organization can apply business rules that will use the details in the request to customize the approval flow so that the appropriate approvers can look at the details.
Once a registration request has been approved or rejected, the supplier is automatically notified by email. Following approval, the qualification details provided by a supplier become part of their profile that can be updated at a later date.
Whilst there are regulatory requirements for some types of organization to keep key supplier profile elements up to date, this is also an important process for a lot of non-regulated organizations that are looking to meet Corporate Social Responsibility standards that they have set for themselves.
Supplier Lifecycle Management enables administrators to utilize the RFI tools to gather and manage supplier compliance and profile information that are required on an anniversary basis. They can define key compliance information that is required from suppliers and then store the feedback provided by the supplier into the supplier master profile record.
Companies recognize that employees who interact with suppliers can provide insightful feedback on “soft” performance metrics for the supplier. Being able to canvas opinion from these key stakeholders and then use the information to help drive an overall assessment of a supplier’s performance is a key part of any collaborative program intended to help improve supplier relationships.
Supplier Lifecycle Management enables administrators to generate internal RFI documents that can be sent to key personnel within the organization to evaluate and score specific aspects of a supplier’s overall performance. This enables stakeholders in a diverse range of departments, such as Procurement, Finance, Supply Chain, Manufacturing, Quality, Design, and Legal to combine their opinions into a rating of how well the supplier is doing. The feedback gathered about the supplier is stored in the supplier profile allowing performance trends to be tracked and risk to be effectively managed.
To assist with supplier communication, Supplier Lifecycle Management provides tools to allow notifications to be selectively communicated to a company’s supply base. Administrators enter notification information and then use search tools to generate the list of suppliers that are to receive the message.
Oracle Supplier Hub is a new application that provides a portfolio of Master Data Management tools to enable organizations to better manage their supplier master records. Built on the foundational technology used to support mastering of customer information, Supplier Hub will be used by both organizations that need to aggregate supplier data from a range of application systems and also by those running a single E-Business Suite instance.
It provides comprehensive functionality to manage supplier data: consolidating supplier information from disparate systems and business lines into one repository, cleaning and enriching data centrally, and providing the resulting "single point of truth" data as a service to consuming applications, enterprise business processes and decision support systems.
Deployment of Supplier Hub will enable organizations to have a consistent understanding of the trading partners that they use to procure the various goods and services required to support their business. This clarity is essential in order to be able to carry out effective analysis of spending patterns so that appropriate tactical and strategic decisions can be made about company procurement policies.
To enable customers to manage supplier records across their organization, Supplier Hub supports the following deployment modes:
This is the traditional Master Data Management deployment mode – the Supplier Hub is set up in a separate instance and vendor data from an organization’s source systems is loaded into the Hub in order to be mastered.
This configuration allows a customer to run the Supplier Hub functionality as part of their existing E-Business Suite R12.x transactional instance.
Note: The product is referred to as Supplier Hub Add-on for Oracle E-Business Suite when it is licensed as an option as part of an existing E-Business Suite install.
This hybrid setup is essentially an extension of the Integrated Mode in that it allows customers to run the Hub as part of their existing E-Business Suite instance and at the same time, feed it with additional supplier records from other legacy systems for the purposes of mastering the details across all of those systems.
Main features of Supplier Hub include:
Supplier Hub allows an organization to gather all of the key details they store about their vendors from across all of their heterogeneous environments and store them in a central repository. Given the wide range of information that Purchasing and Payables departments need and wish to maintain, the Hub enables buyer organizations to store data across the following range of categories:
This refers to the attributes that uniquely identify an individual supplier - primarily the supplier name and tax reference ID and number(s).
These are the attributes that are typically required to be able to do business with the supplier and so provide the more granular details about a supplier’s identity, such as location, contact and bank account information.
These are the pieces of information that identify the characteristics of the supplier, and can range from things like the corporate structure of the supplier, names of C-level officers through to the goods and services they can provide, classifications that apply to them and 3rd party credit risk information.
These are the flags and settings that are used to manage the business relationship for order collaboration, receiving, invoicing and payment between the buying organization and the supplier.
All data categories can be managed using the Integrated deployment mode. The Standalone and Mixed deployment modes support the Identity, Business and Profile category details.
To better understand the capabilities of suppliers in key product categories, and to track subjective information about how that supplier is performing, buying organizations need to be able to store a wide range of additional details in their supplier master. Typically, this is the sort of information that is gathered by different departments and stored using paper-based systems, preventing the an organization from using the details to gain a better insight into a supplier’s performance.
Supplier Hub utilizes User Defined Attribute technology that allows administrators to add an unlimited range of attributes to the supplier definition and to group these into logical Profile sections. In addition to the attribute name, administrators are able to add descriptive text to help explain the purpose of the attribute. The extended profile attributes allow disparate details to be imported from a variety of source systems or for the Hub to be used to capture and store this information centrally.
Fine-grained access control tools allow administrators to manage which users can have access to the individual attributes in the extended set of profile details. This is a key feature when sensitive information is stored in the profile and access need to be restricted to appropriate users either internally or at the supplier.
It is becoming increasingly important to a large number of organizations to be able to track classification and diversity information across their supply base in order to ensure that spending patterns can be matched to Corporate Social Responsibility goals. To allow organizations to track a wide variety of classification and diversity information about their suppliers, the Hub enables administrators to define multiple classification schemas. This information can then be used when building reports to track spending patterns.
A crucial part of supply base analysis is to understand the relationships that exist between the different suppliers that are doing business with different parts of the buying organization. This allows an organization to leverage aggregated spend information within the negotiation process with the supplier.
Supplier hierarchy management functionality within the Hub provides the ability to identify Parent and Child supplier company relationships across all of the supplier records that have been consolidated from the different systems within a company.
In addition to the basic parent and child relationship, the Hub allows business users to define an unlimited number of custom supplier relationship types and then use these to track relations between different suppliers. The custom hierarchy information can be viewed in a tree structure and can be utilized for various reporting and supplier management purposes.
Supplier Hub provides an Import Workbench to allow administrators to setup and control the process of consolidating supplier records from any spoke applications or systems running within the organization. The Import tools enable supplier Identity, Business, and Profile Details from multiple spoke/source systems to be cross-referenced. Batch Management capabilities then allow the administrator to control the loading of the imported supplier data into the Hub repository. The initial release of the Hub will support backend concurrent program import for identity, address, contacts, and general classifications.
A critical element of an administrator’s role in managing supplier data is in dealing with duplicate supplier records and establishing processes to prevent duplication in the first place.
The Data Quality Management (DQM) functionality incorporated into Supplier Hub provides features that allow an administrator to carry out systematic de-duplication and cleansing of supplier Identity, Business and Profile Details. The DQM tools have also been incorporated into the supplier creation flows that are supported by the Hub to prevent the setup of multiple records for the same supplier.
DQM provides tools to setup match rules and other data quality setups required for performing de-duplication tasks. It also provides tools for blending of the supplier records to harmonize the information about a single supplier that exists in multiple source systems. It provides tools for automatic identification of potential duplicate supplier records in the system in order that administrators and business users can take further data quality actions as required.
The Supplier Data Enrichment functionality provides features that allow organizations to enrich the profile information they are maintaining for a supplier by pulling detailed information from D&B. Information packets for a supplier(s) can be gathered during the supplier registration process and also as part of general supplier profile management. Administrators or business users are able to interactively search the D&B repository and order/purchase various D&B products to enrich the Supplier information.
One of the primary reasons for deploying Supplier Hub is to establish a single definition for each supplier and then to make sure that this representation is used across all of the systems operated across the organization.
The Supplier Data Publications feature set provides the capabilities to integrate Supplier Hub with other spoke systems. It provides the infrastructure to raise the necessary business events to trigger publication of updated supplier information and APIs that can be used by spoke systems to query and consume the updated supplier information. It also provides APIs for querying potential duplicate supplier records in the Hub and for processing the source system supplier information into the Hub.
- Extended supplier profile attribute.
- Setup, view, and edit extended supplier profile.
- Advanced search based on extended supplier profile.
- Export supplier profile into spreadsheet.
If both products are installed in the same application instance, these features are integrated seamlessly.
The Supplier Directory Services features enable buyers and administrators to query suppliers in their system, view a 360 degree view of their profiles, export search results to a spreadsheet, and notify suppliers.
Supplier Profile is composed of key supplier information required to maintain business relationship between buying organizations and their suppliers. Supplier profile includes details such as supplier identity information, addresses, contacts, contact points, business classifications, banking details, products and services category, supplier tasks, notes, and supplier party relationships. Administrators can define custom attributes to extend the profile and customize it based on their business domain. Suppliers can be given access to their profile online so the onus of maintaining the profile lies with the Supplier. Any changes by the supplier are subject to approval by the buying organization. This chapter discusses the supplier profile in detail. Oracle Supplier Lifecycle Management provides a number of customizable business processes such as Supplier Registration and Qualification Management, Supplier Compliance and Profile Audit, Item Supplier Qualification, and Supplier Performance Evaluation that use supplier profile and its extensions. These processes are discussed in further details in subsequent chapters.
If you are an existing customer of Oracle Payables, Oracle Purchasing, or Oracle iSupplier Portal, then you are familiar with the basic supplier profile that comes with any of these products. Supplier Management extends this profile and gives the Supplier Management Administrator role based access control to a supplier’s profile so they can restrict sensitive information from suppliers as well as internal users. For example, if you have created some custom attributes to gather supplier’s performance metrics, the administrator can hide these metrics from your suppliers.
Customers who are new to aforementioned Oracle Applications must follow references to those product manuals mentioned in this chapter along with the information provided to learn about supplier profile.
These pages contain information about the supplier, their identity, and their type of business. A significant portion of this information needs to be elicited directly from your contacts at the supplier. You can give suppliers access to most of the profile details so that they can maintain the information for you. The application handles any updates that the supplier provides as change requests that require approval by an internal administrator.
Log in with Supplier Management User or Supplier Management Administrator responsibility and click on Supplier Home menu. This brings up the Supplier Home page, where you can search for suppliers. Click on the supplier name link to open the supplier’s profile details page. Follow the same navigation from Supplier Data Librarian and Supplier Data Librarian Super User responsibilities to access supplier profile.
The following pages are visible to suppliers as well as internal users:
<![if !supportLists]>· <![endif]>Organization
See: Suppliers Pages Reference in the Oracle Payables User’s Guide and Supplier Profile Management in Oracle iSupplier Portal User’s Guide for descriptions of these pages.
Additionally, the following pages are visible to suppliers and internal users:
<![if !supportLists]>· <![endif]>Tasks:This page enables you to view, create, update, and delete tasks. See: Creating, Updating, and Finding Tasks in Oracle Common Application Calendar User Guide
Contact Points page is for internal users. Use this page to indicate the specific ways of contacting the organization, person, or contact. You can create and update these types of contact points: phone numbers, e-mail addresses, and URLs.
Party Relationships page is for internal users. This page enables you to specify the relationship between two parties such as a contact or employee.
General Classifications page is internal. Use the General Classification page to assign a classification to a supplier. See: Assigning Classifications.
Terms and Controls: These pages provide access to all of the attributes that are used to control the business relationship you have with the supplier. This includes account code references, internal tax setups, purchasing, receiving, invoicing, and payment options. In addition, there is a Quick Update page that can be personalized to provide access to the most commonly used setup attributes for individual users or groups of users. The following pages are visible only to internal users:
<![if !supportLists]>· <![endif]>Terms and Control:
<![if !supportLists]>o <![endif]>Quick Update – enables you to record key purchasing and payment setup information for your supplier sites. See: Key Setup Information in the Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Accounting – enables you to specify accounting default values. See: Accounting Information in the Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Tax and Reporting – use this page to record supplier tax information to enable three defaults during invoice entry, and to provide tax reporting information. See: Tax Reporting Information in the Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Purchasing – enables you to enter purchasing defaults for your suppliers.
<![if !supportLists]>o <![endif]>Receiving – enables you to enter receiving defaults for your suppliers. See: Receiving Information in the Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Payment Details – See Payment method, Payment Attributes, Specifying Separate Remittance Advice in Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Payment Relationship – See Supporting Third Party Payment in Oracle Payables User’s Guide.
<![if !supportLists]>o <![endif]>Invoice Management – See: Control Information, Payment Information in the Oracle Payables User’s Guide.
Others: The following pages are internal and significant in managing supplier profile using Oracle Supplier Management:
<![if !supportLists]>o <![endif]>Qualification and Evaluation – enables you to search, view, and act on existing qualification and evaluation RFIs.
<![if !supportLists]>o <![endif]>Surveys – Usage of user defined supplier profile attributes and RFI Questionnaires are recommended over iSurvey for extensible supplier profile management implementations. Surveys link is provided in the Supplier Management navigation menu for customers who have been using the iSurvey functionality through other products like iSupplier portal.
<![if !supportLists]>· <![endif]>Relationship Contracts: RFI Contract Clauses and Deliverables feature is part of Supplier Lifecycle Management license. However, for using contracts for any document other than RFI type, you should purchase an appropriate Oracle Contracts product license. Any contracts and deliverables pertaining to a supplier are visible from that supplier’s profile.
You can access Contract Terms Library, which is the central library of pre-approved clauses and contract templates in Oracle Contracts product that can be used to create contracts across the enterprise. See: Oracle Procurement Contracts Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Qualification Deliverables: Deliverables are contractual commitments and obligations that buyers and suppliers can associate to a contract template. Buyers and suppliers can manage deliverables that represent obligations arising from the negotiation process. They indicate the success or failure of the fulfillment of the deliverable by changing the status of the deliverable for the negotiation.
You can access Contract Terms Library, which is the central library of pre-approved clauses and contract templates in Oracle Contracts product that can be used to create contracts across the enterprise. You can create templates that include both clauses and deliverables. See: Oracle Procurement Contracts Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Profile Access Control – enables you to view and update the roles attached to suppliers that provide them access to the user-defined attributes. See: Setting up Profile Access in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Notes – enables you to view and create notes of several types. See: Setting up Tasks and Notes in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Source Systems – enables you to maintain details of the source systems related to the supplier. See: Creating and Updating Source Systems in Oracle Trading Community Architecture Administration Guide.
<![if !supportLists]>· <![endif]>Transactions - You can extend your view of transactions in Oracle Supplier Management to include transaction data from applications that are not part of E-Business Suite applications to provide a complete view into all supplier business transactions in your organization. This is available only from the Supplier Data Librarian responsibility. See: Setting up Transaction Views in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Publish Event History – enables you to track the publication history of supplier information.
User Defined Attributes: Oracle Supplier Management enables you to maintain additional supplier information using user defined attributes. User defined attributes are aggregated in user defined attribute groups. These groups appear on the supplier profile pages where you as well as suppliers can maintain extended profile information based on your business requirements. For example, you could set up attribute groups to gather compliance and certification details, insurance information, business details, quality control qualifications, and any other information that meets your business requirements.
An attribute group can be multi-row or single-row. Multi-row attribute groups enable association of multiple sets of attribute values with the same attribute group. For example, for a supplier, you can set up a multi-row attribute group called ‘services’, with ‘service name’, ‘service type’, and ‘service frequency’ as the attributes. You can associate multiple rows of services with the supplier.
You can maintain additional supplier information at one or more business entity levels such as supplier party, party site, and supplier site. At each level you can associate the attribute group with a certain type or classification of that entity. For example, an attribute group called ‘Supplier Monitor Product Attributes’ created for a business entity ‘Supplier Party’ must apply only to those suppliers that supply monitors.
A supplier party user defined attribute can be associated with a certain type of supplier party based on the following:
<![if !supportLists]>· <![endif]>Product and Service categories such as monitors, building materials, and electronic tubes.
<![if !supportLists]>· <![endif]>Supplier type such as component manufacturer, distributor, and contract manufacturer.
<![if !supportLists]>· <![endif]>Business classification such as women owned, small business, and minority owned.
<![if !supportLists]>· <![endif]>Common: This association makes the user defined attribute applicable to all supplier parties.
An attribute group for capturing party site details can be associated with certain type of party sites based on:
<![if !supportLists]>· <![endif]>Country such as US, China, and India.
<![if !supportLists]>· <![endif]>Common: This association makes the user defined attribute applicable to all party sites.
An attribute group created for capturing supplier site details can be associated with certain type of supplier sites based on:
<![if !supportLists]>· <![endif]>Country such as US, China, and India.
<![if !supportLists]>· <![endif]>Common: This association makes the user defined attribute applicable to all supplier sites.
For setting up the user defined attributes, see Setting up User Defined Attributes in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Simple search that is available from the Suppliers Home page for Supplier Management responsibilities.
<![if !supportLists]>· <![endif]>Advanced search that is available by clicking the Advanced Search button on the Suppliers Home page.
<![if !supportLists]>· <![endif]>Smart search that is available from the Suppliers Home page for Supplier Data Librarian responsibilities.
In the Search region, you can enter a wide variety of search criteria, including supplier name, supplier number, tax registration, or DUNS number. If you want to search for employee-suppliers, then select Employee as the supplier type.
Use the Supplier Management Administrator and Supplier Management User responsibilities.
To find a supplier using the Search region:
<![if !supportLists]>1. <![endif]>On the Suppliers home page, enter your search values into the appropriate search fields. You can enter complex criteria by entering information in several fields. Click the Show More Options link to access additional search fields if necessary.
<![if !supportLists]>2. <![endif]>Click Go. The search results appear in the table below the search fields. Use the Update button to access the details for the supplier.
Advanced search is provided to run complex search queries containing multiple search criteria. Search criteria are not just limited to the supplier’s name and identification information, but can include any attribute in the Supplier’s profile, including user-defined attributes. This helps buyers find appropriate suppliers to invite to a negotiation event based on the requirements of that negotiation. For example if you wish to find suppliers based in the United States who supply monitors and are ISO 9001 certified but in the process of becoming environmentally compliant with general liability insurance of at least USD $3 million, you can do that using Advanced Search.
Use the Advanced Search button available on the Suppliers page to go to the Advanced Search page. Follow these steps to search:
<![if !supportLists]>1. <![endif]>Setting the Search Context: There are three components on this page that contribute to the search. First is the Search Context. Here, select one of the classifications from Address Purpose, Business Classification, Country, General Classification, Products and Services Category, and Supplier Type. Then select a value for that classification and click Go. This sets the context for the remaining two regions, Search Criteria and Display formats.
Search criteria offer a convenient way to save frequently used search criteria and values. Display Formats enable you to predefine how search results are displayed. Results can be set up to show different sets of attributes of the suppliers that are returned by the search.
<![if !supportLists]>2. <![endif]>Creating Search Criteria and Display Formats: When you set the Search context and click Go, if there are Search criteria and Display formats for the selected search context, then the application displays them in the respective drop lists. However, in case there isn’t any search criteria or display format configured, click on Personalize to create one from this page.
Personal search criteria and display formats criteria created in this manner are only available to the user who created them. Administrators can create frequently used search criteria and display formats from the Administration tab, which become available to all users. When a user and administrator define a default search criteria template for a particular search context, the user-defined search criteria template takes precedence. See: Setting up Advanced Search Criteria and Display Format in Oracle Supplier Management Implementation and Administration Guide.
When you create search criteria and display formats, the attribute groups available to add criteria are dependent on the search context set on the Advanced Search page. For example; consider the attribute group EPA Guidelines. EPA Guidelines is associated with Country USA so it only applies to suppliers in the US. First you must set the Search context to Country and value to US. Only then EPA Guidelines will show up in the Search Criteria creation page.
<![if !supportLists]>3. <![endif]>Setting Mandatory Indexed Criteria to Search: Some of the attributes are indexed and this is indicated by a ‘^’ sign next to the attribute. The administrator can index a custom attribute at the time of creation. At least one indexed attribute must be used in the search criteria. Also a valid operator should be used to make the 'index' usable. Valid operators for an indexed attribute are - is, starts with, greater than, less than, after, and before. If you choose a 'contains' or 'ends with' operator, then the application ignores the indexing on that attribute.
A lock icon appears in the search results if the user searching for suppliers does not have the privilege required to view a particular attribute group. To assign privileges to users, see Setting up Profile Access in Oracle Supplier Management Implementation and Administration Guide.
Smart Search is a powerful search engine that finds suppliers that not only exactly match but are similar to your criteria. You can choose any search criteria from Supplier Party level attributes for the smart search (a strong advantage of smart search over simple search).
Ensure that you select the applicable attributes in the Data Quality Management (DQM) match rule as the available search criteria depends on the DQM match rule, HZ: Match Rule for Identifying Duplicates with Smart Search. Run the search with at least one criterion
Use the Supplier Data Librarian and Supplier Data Librarian Super User responsibilities to access Smart Search.
To find a supplier using the Smart Search region:
<![if !supportLists]>1. <![endif]>On the Suppliers home page, enter your search values into the appropriate search fields.
<![if !supportLists]>2. <![endif]>Click Go. The search results appear in the table below the search fields. Use the Update button to access the details for the supplier.
You can merge suppliers using the search results. Additionally, you can publish the supplier profile using the Publish button and generate the supplier profile report using the Generate Report button. See: Publishing Supplier Profile and Generating Supplier Profile Report.
Supplier Management allows export of supplier profile information into spreadsheet from the Advanced Search results page. Search for the supplier or suppliers who you wish to export. Then click on ‘Export All’ to export the entire result set to a spreadsheet. Set the display format to export the most relevant information.
Note: Before performing this step, ensure to check the Trust access to Visual Basic Project and close the MS Excel application. Refer to the applicable topic in MS Excel Help to check the Trust access.
Many times buyers may wish to notify suppliers of required actions, change in policy, or upcoming events. Use Supplier Management User responsibility and Profile Extension subtab on the Supplier tab to notify suppliers.
To notify suppliers:
<![if !supportLists]>1. <![endif]>Click on Notify All Suppliers button to send a notification to all suppliers in the Supplier Master.
<![if !supportLists]>2. <![endif]>If you wish to notify a subset of suppliers, search for those suppliers using the Search region of the Suppliers page. Select the applicable suppliers and click Notify to open the Notifications page.
<![if !supportLists]>3. <![endif]>Enter subject and message to notify the selected supplier’s contacts.
<![if !supportLists]>4. <![endif]>Select the applicable option in the Send To field. If you select All Contacts, then the application notifies all the contacts of the selected suppliers. If you select Contact Users Only, then the application sends the email and workflow notification to those contacts of suppliers that have system user accounts.
<![if !supportLists]>5. <![endif]>Optionally, select the Include OSN Registration Instruction, if you are notifying suppliers who have not yet registered on Oracle Supplier Network. See On-Boarding Suppliers on Oracle Supplier Network.
Qualification Management is the process of assessing a new supplier’s qualifications before approving their registration request. You must have a valid Supplier Lifecycle Management license for managing new supplier qualification. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
With Supplier Lifecycle Management you can gather any amount of information from prospective suppliers, before approving the registration request. This provides a powerful way of screening prospective suppliers at the beginning of the relationship even before they are created in the system. This allows only qualified suppliers who meet corporate compliance and quality standards into the Supplier Master and weeds out any ill-qualified, fake or unwarranted entries from being created.
Open the registration request from the Prospective Supplier Registrations link or the New Supplier Requests link from the Suppliers Home page. Note that the request status is Pending Approval at this stage. Follow these steps for reviewing suppliers:
- If the supplier already exists in the Supplier Master or exists only as a TCA party, then the application displays the supplier organization in the Possible Matching Organizations region.
If the matching organization is a supplier that already exists in the Supplier Master, reject the new supplier request. But if the matching organization is a TCA party (and not a supplier), select the applicable TCA party and click Use Existing Organization.
Note: When you select Use Existing Organization action on an existing TCA party, then the application enables the TCA party as a supplier in the Supplier Master. All other information such as address and contacts provided by the supplier during registration is also saved to the supplier’s profile.
If no matching organizations exist, click Create New Organization to create a new organization for the supplier. This action does not approve the supplier but only tells the system that a new organization should be created for the supplier on approval.
Click on Save. This commits the Use Existing Organization or Create New Organization action.
- Review and update the Address Book, Contact Directory, Business Classifications, Products and Services, custom Attribute Pages and Attachments provided by the supplier.
Some of the actions you can perform from the registration request page while reviewing are explained below:
- Notify – Enter a message in the Note to Supplier field. Click on the Notify button to send the note to the prospect supplier’s email address used for registration.
- Apply Template – Send a pre-configured questionnaire to the supplier. The questionnaire is actually a request for information (RFI) document.
You can add requirements to the RFI based on your business requirements for qualifying suppliers. You can also control the type of response the supplier provides. You may either predefine responses to each requirement or allow free text response, based on your choice. In case of predefined responses, you can attach an automatic score to each response. This way when the supplier selects one of the predefined values, a score is automatically assigned to that response. You must link the RFI template from the Registration Onboarding Configuration page and then publish it during the Supplier Registration process by clicking on ‘Apply Template’ from the registration request page. The apply template button takes the user to the publish RFI page.
Publishing the RFI sends an email notification to the supplier with a link to the registration form. The RFI is shown on the registration form under Pre-Qualification and Evaluation RFI.
See Setting up RFI Template for Qualification Management in Oracle Supplier Management Implementation and Administration Guide.
- Enrich –Purchase D&B reports on business verification, business information credit risk, and financial analysis of the supplier before approval. This mitigates the risk of approving suppliers going out of business, suppliers on any type of debarment list or involved in fraudulent, bribery, or money laundering activities.
- You must have a valid Supplier Hub license for using third party integration. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide and Setting Up Third Party Data Integration in Oracle Trading Community Architecture Administration Guide.
- Click Apply Template to create a request for information. Provide the Close Date as future. Click Publish to publish the RFI. A notification with a link to the RFI is sent to supplier prospect to provide more detail. The prospect/new supplier request status is set to ‘Supplier to Provide Details’. Supplier uses the link to create a response to the RFI.
When the buyer publishes the RFI, Supplier Management sends a notification with a link to the RFI to the supplier prospect to provide more detail. The supplier uses the link to create a response to the RFI. See: Managing New Supplier Qualification
The purpose of an RFI is to gather information on goods and services a supplier company provides. RFIs may or may not be concerned with line price or costs. Buyers use responses to an RFI to qualify suppliers early in the procurement process.
To respond to an RFI:
- Use the Sourcing Supplier responsibility and navigate to the Sourcing Home page.
- Select the open invitation in the Your Company's Open Invitation area.
- From the Actions field, select Create Response.
- On the Create Response page, enter response values for the requirements and lines. Since the purpose of an RFI is to obtain product and service related information for a negotiation line, most negotiation lines in an RFI have attributes defined. These line attributes identify the questions the buyer has about a particular line.
- Click Continue.
- From the Review and Submit page, click View Supplier Profile Attributes.
- Return to the Review and Submit page and submit the response.
Once the RFI response is received, you can open the RFI and review responses. The RFI may be set up with internal as well as external requirements. Internal requirements are created to involve internal users from various departments to review the supplier request. See Set up RFI Template for Qualification Management in Oracle Supplier Management Implementation and Administration Guide.
- Since suppliers do not have user accounts yet, they can only respond by opening the RFI from the registration form URL from the Pre-Qualification and Evaluation RFI section. They must open the RFI and create a response. After receiving the supplier’s response, open the RFI from the Pre-Qualification and Evaluation RFI section in the registration request.
- If you have set up internal users, then notify all internal users. To notify RFI collaborators:
Evaluators enter evaluations, by opening the RFI from Negotiations page and selecting Enter Evaluations from the Action dropdown.
- Select Analyze by Response from the Action list and click Go to open the Analyze by Response page. Click on the supplier response number link to review supplier responses. If internal evaluators are involved, select all internal evaluator responses and click on Compare requirements to view a side-by-side display of all internal evaluator responses.
- Close the RFI. Select Close RFI from the Action drop down on the RFI details page and click Go. Select a close date and click Apply. The application displays the RFI details page.
- Select Analyze by Response from the Action list and click Go to open the Analyze by Response page. The score you see is applied based on automatic scoring and weights set up for requirements. See Oracle Supplier Management Implementation and Administration Guide for setting up RFI for registration. Optionally, provide score for any requirements setup with manual scoring.
- Select Manage Scoring Teams in the Action dropdown. Click Lock Scoring to close further analysis and evaluation. The application brings you back to the RFI page.
Note: Lock scoring action calculates the overall score for supplier(s) in the RFI. This includes automatic scores based on supplier’s responses, evaluation responses and any manual scoring of the supplier or evaluator responses. The lock scoring action shortlists suppliers in the RFI. All suppliers who participated in your negotiation are initially included in the shortlist. You must remove the supplier from the list by changing its status.
- If any requirements were created with knockout scores, select Apply Knockout Results from the Action list to apply knockout scores assigned during evaluation. Once you apply the knockout values, the response is removed from the shortlist. To view the short-listed suppliers based on evaluation scores, select Analyze by Response from the action dropdown.
- Select Complete as the Action and click Submit. Complete action is significant in the qualification management process if the RFI requirements have been mapped with supplier profile attributes. You create mappings to save supplier and internal user responses into the supplier’s profile. See ‘Mapping RFI Requirements and Category Line Attributes’ with Supplier Profile and ‘Mapping RFI Item Lines with Item Supplier Profile attributes’ in Oracle Supplier Management Implementation and Administration Guide.
RFI completion triggers the synchronization of RFI responses with supplier profile for all types of RFI documents, except registration and pre-qualification RFIs. In case of a registration and pre-qualification RFI, complete action of the RFI is not enough to trigger synchronization. Supplier must first be approved along with completing the RFIs, in any order, to trigger this process.
After evaluating the supplier, next step is to approve or reject the supplier. By default all Supplier Management users in the buying organization have the authority to Approve or Reject Suppliers. To implement an Approval Hierarchy, see Setting up Supplier Approval in Oracle Supplier Management Implementation and Administration Guide.
You must have a valid Supplier Lifecycle Management license for approving supplier users. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
Navigate to new supplier registration request, and approve or reject the prospective supplier registration. On approval, the application sends an invitation to Oracle Supplier Network to the supplier. See On-Boarding Suppliers on Oracle Supplier Network.
Once approved, the Supplier is created in the Supplier Master. Open the supplier profile from the main Supplier page. The profile captures all the data gathered during registration process. If you used a Registration and Pre-Qualification RFI template during registration, then notice how RFI responses from suppliers and internal users have been recorded in the custom Attribute pages as per the mappings set up in the RFI template. This profile is now available to you as well as to the supplier for self-service profile maintenance. If you wish to register more supplier users, see Registering Supplier Users. You can create more custom Attribute pages and gather additional information from suppliers by conducting a Supplier Profile Audit. See the Managing Supplier Profiles chapter for profile maintenance features of Oracle Supplier Lifecycle Management.
Once the supplier is registered, you may wish to invite more supplier users to register or if you have the required user information, register them yourself. You must have a valid Supplier Lifecycle Management license for registering supplier users. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
To manage supplier users, use the Supplier Management User or Supplier Management Administrator responsibility and the Supplier User Management sub tab on the Supplier tab. This feature is not available to Supplier Data Librarian and Supplier Data Librarian Super User responsibility users.
You can invite a supplier user to register as a point of contact for a supplier. Complete the following steps:
- Click Invite Supplier User link to open the Invite a Supplier User page.
- Use this page to select the user’s supplier company, provide supplier user contact details, and specify the user access to applicable Oracle applications.
- Click Invite to send the user an email invitation to register. After the supplier user responds to your invitation to register, the application sends the user a notification containing system access information.
A supplier user who receives the invitation to access Oracle Supplier Management can register by providing name, job title, contact details etc. or forward the invitation to another user in the supplier company. For example, you may send an invitation to the Vice President of Sales within the supplier organization; the vice president can forward it to the appropriate person in the company. The user who responds can change any of the details except the name of the supplier company for whom they are registering. If you have multiple site definitions for the supplier company, or if the supplier company has multiple subsidiaries, you can give the supplier user access to view information for multiple site definitions.
You can directly register a supplier user if you have enough information about the user. In this case, the user receives an email notification with the URL, username, and system-generated password. Complete the following steps:
- Click Register Supplier User link to open the Register a Supplier User page.
- Provide applicable information and click Register. The user receives an email notification with the URL, user name, and system-generated password.
- If you have multiple site definitions for your company, or if the supplier has multiple subsidiaries, then you can give the supplier user access to view the multiple site definitions.
- Select Certification Reminders check box in the User Notification region to designate the user to receive business classification reminder notifications.
Use the Approve and Manage Supplier User Profile link to approve prospective supplier users. After approving the users, you can manage the user profile. Complete the following steps:
- Search for the user using the Supplier User Profile Management page.
- Select the View icon for the applicable supplier user in the search results region to open the Manage User Profile page.
- Update the user account as required and click Apply.
A supplier user with Supplier Profile and User Administrator responsibility can register more supplier users. This administrator can create new user accounts. Once the account is created, the user receives a notification containing system access information.
You can create a supplier without going through the process of registration and approval, if your business requirements need you to create a supplier quickly. The application adds the supplier to the TCA registry directly and you can initiate business with the supplier immediately.
To create a supplier, go to the Suppliers Home page and follow these steps:
- Click Create Suppliers on the Suppliers page to open the Create Suppliers page.
- Select the type of supplier.
- Optionally enter Alias, Name Pronunciation, and D-U-N-S number.
- Optionally, specify the country of origin for tax purposes.
- Optionally enter the supplier's tax identification number in the Taxpayer ID field; for example, an individual's social security number, or a corporation or partnership's federal identification number/federal tax ID.
- Optionally enter the value-added tax (VAT) registration number in the Tax.
- Registration Number field if you are entering a VAT supplier.
- Click Apply.
The application checks for duplicate records to prevent duplicate supplier creation in the system. The administrator must set up duplicate identification before matching organizations are found during supplier creation. See Setting up Duplicate Prevention in Oracle Supplier Management Implementation and Administration Guide.
After verifying that the new supplier does not exist in the system, the application creates the supplier record, assigns a supplier number, a registry ID number, and opens the Suppliers: Quick Update page.
Oracle Supplier Network (OSN) enables electronic document transformation and routing between companies through a single connection point that Oracle hosts and manages. OSN also allows buying organizations to allow direct connectivity to their Oracle iSupplier Portal sites for supplier users to access. Oracle Outsourcing hosts OSN to provide a high availability connection for trading partner collaboration, which greatly simplifies the administrative burden of creating and managing a complex multi-point integration. On new supplier registration approval in Oracle Supplier Lifecycle Management, an automated invitation to OSN is sent to the supplier.
On accepting the buyer’s invitation, a supplier automatically becomes a trading partner of the buyer. The two trading partners can now begin exchanging electronic documents. See Oracle Supplier Network User Guide.
Once supplier user accounts are created, supplier users have access to their profile online. They are responsible for adding new information and ensuring that existing information is up to date. Through profile management, suppliers can provide the buying organization with key details about their company, such as location and contact information, major business classifications, banking details, and category information about the goods and services that they provide. Additionally, suppliers can update tasks using the Supplier Profile, User and Task Manager responsibility. Allowing suppliers to enter and update this information eases the administrative burden for both buyers and suppliers.
<![if !supportLists]>· <![endif]>Organization
<![if !supportLists]>· <![endif]>Tax Details
<![if !supportLists]>· <![endif]>Address Book
<![if !supportLists]>· <![endif]>Contact Directory
<![if !supportLists]>· <![endif]>Business Classification
<![if !supportLists]>· <![endif]>Product and Services Category
<![if !supportLists]>· <![endif]>Banking Detail
<![if !supportLists]>· <![endif]>Tasks
<![if !supportLists]>· <![endif]>Any custom Attribute Pages made visible by the Buyer
Suppliers can enter new information or change existing information using the Supplier Profile Manager responsibility as seen in the following page. Changes to Addresses, Contacts, Business Classifications, Products and Services and Bank Accounts go through an approval mechanism. Any new or updated entries are logged in the buyer system as change requests. A buyer administrator must approve these change requests before the change is shown on the profile.
<![if !supportLists]>1. <![endif]>Navigate to the Supplier Home page. Click on any one of the change requests in the To-do list.
<![if !supportLists]>2. <![endif]>Select the appropriate change request and click on Approve or Reject. You may also update the change request. This allows you to modify the changes made by the supplier before approving them.
After you approve the changes, the application displays these changes in the supplier’s profile.
With Supplier Lifecycle Management, a buying organization can perform periodic compliance and profile audits to gather additional information from suppliers on a periodic basis. They can gather certifications, quality controls, cost effectiveness measures, customer support services or any other information relevant to their business processes.
Once suppliers provide the requested information, the buying organization can set up an internal evaluation team to verify that the certifications are valid and in compliance with their corporate compliance policy. The evaluation team may include members from various departments such as operations, finance, legal etc. Evaluation team members can be requested to answer questions such as - Please comment on the supplier’s response or – Have you verified that the supplier is ISO 9001 certified? Or they may be asked to evaluate the supplier’s responses by scoring each response.
<![if !supportLists]>1. <![endif]>Create a Request for Information (RFI) document either by using the RFI template or Reusable Requirements list set up by the administrator. See: Implementing Supplier Compliance and Profile Audit in Oracle Supplier Management Implementation and Administration Guide. Creating the RFI is similar to creating a RFI template. See Setting up RFI Template for Qualification Management in the Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>2. <![endif]>Set the RFI Open and Close Dates. Once you have created the RFI, click on Review, and then Publish the RFI.
<![if !supportLists]>3. <![endif]>Await supplier’s response to your audit questionnaire. A supplier accesses the RFI and responds to the audit questionnaire.
<![if !supportLists]>4. <![endif]>Review supplier response and score. See Evaluating Supplier in Managing New Supplier Qualification.
<![if !supportLists]>5. <![endif]>Review RFI synchronization with supplier profile.
Consider an organization that wants to verify supplier’s corporate compliance on an ongoing basis. For this they have created the following single-row user defined attribute in the Supplier Profile:
Attribute Group
|
Attributes (Data Type)
|
Data Level
|
Association Level
|
Quality Policy
|
<![if !supportLists]>· <![endif]>Quality Policy and Compliance (Char)
<![if !supportLists]>· <![endif]>Periodic Quality Process Auditing (Char)
<![if !supportLists]>· <![endif]>4M Management (Char)
|
Supplier Party
|
Common
|
Notice that this user defined attribute is defined at the Supplier Party data level, which means that it applies to the Supplier’s organization as a whole, instead of Party Sites or Supplier Sites. Also this user-defined attribute is associated as ‘Common’, which means it applies to all Suppliers in the Supplier Master and not to any particular classification of suppliers.
During Supplier Profile Compliance and Profile Audit, the buyer creates a RFI. The RFI contains the following requirements for the supplier:
Requirement Section
|
Requirement Type
|
Requirements (Response Type)
|
Quality Policy and Systems
|
Required
|
<![if !supportLists]>· <![endif]>Does your organization have well defined Quality Policy that is followed through quality procedures as per standards?
<![if !supportLists]>· <![endif]>Is there a Quality process audit system is in place like internal and external audits etc. on periodic basis.
<![if !supportLists]>· <![endif]>Is there a 4M (Man, Method, Machine, and Material) management system well in place that informs customers about any 4M changes along with proper inspection?
|
The requirements are mapped to user-defined attributes in the RFI. Note that mapping can be created from RFI Template or Reusable Requirements List as well.
RFx Section
|
RFx Requirement
|
RFx Response
|
Supplier Profile Data Level
|
Supplier Profile Association level
|
Supplier Profile Attribute Group
|
Supplier Profile Attribute
|
Quality Policy and systems
|
Does your organization have well defined Quality Policy that is followed through quality procedures as per standards?
|
Value
|
Supplier Party
|
Common
|
Quality Policy
|
Quality Policy and Compliance
|
Quality Policy and systems
|
Is there a Quality process audit system in place like internal and external audits on periodic basis?
|
Value
|
Supplier Party
|
Common
|
Quality Policy
|
Periodic Quality Process Auditing
|
Quality Policy and systems
|
Is there a 4M (Man, Method, Machine, and Material) management system well in place that informs customers about any 4M changes along with proper inspection?
|
Value
|
Supplier Party
|
Common
|
Quality Policy
|
4M Management
|
Once the supplier responds and RFI is completed, the supplier’s response is synchronized with Quality Policy user defined attribute.
Supplier Profile showing Quality Policy user defined attribute
This example presents a simple case of gathering quality policy and control information from a supplier. You can customize the RFI in any manner to align compliance and profile audit with your business processes. For example, you may choose to do one of the following:
<![if !supportLists]>· <![endif]>Create collaboration team and internal requirements: Create a collaboration team to involve internal users from different departments in your organization. Add requirements that are ‘Internal’ in the compliance and profile audit RFI. Internal requirements are only visible to internal users who are part of the collaboration team.
<![if !supportLists]>· <![endif]>Save responses from internal team: Responses from internal users can also be mapped to supplier profile user defined attributes. For example, The RFI may contain an internal requirement: Have you verified that the supplier follows quality controls. Response by the internal user must be mapped to the user-defined attributes. On completing the RFI, the internal user’s response will be saved to the user-defined attribute and shown in the Supplier’s profile.
See Example – Mapping a Multi-row user defined attribute with RFI Requirements in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Add contracts and deliverables: You have access to Contract Terms Library, which is the central library of pre-approved clauses and contract templates that can be used to create contracts across the enterprise. You can create templates that include both clauses and deliverables.
You can create templates from Contracts Terms Library Administrator responsibility to create contract terms template. See: Enabling Oracle Procurement Contract Deliverables in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>· <![endif]>Create item line requirements: Similar to adding requirements to RFI, you may add item lines to the RFI. Item lines are requirements with respect to a product or services category or an item. Supplier responds to these item line requirements in the same way as other requirements. Supplier responses can be mapped to product category or Item attributes in Oracle Product Information Management (PIM) product if you have PIM installed in the same instance as Supplier Lifecycle Management. See: Managing Supplier Material Qualification.
For approved suppliers, you can buy D&B information either from the Search D&B page as shown above or directly from the Supplier’s profile details page. From the supplier’s profile page, click on Enrich button to open the Review: D&B Purchase Data page. This page shows a side-by-side view of user-entered, D&B and Single Source of Truth data. See: Single Source of Truth Overview in Oracle Trading Community Architecture User Guide.
You must have a valid Supplier Hub license for using third party integration. See: Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide and Setting Up Third Party Data Integration in Oracle Trading Community Architecture Administration Guide.
If you have Oracle Supplier Lifecycle Management, the only business document types having deliverables management capability are RFIs. With Oracle Contracts you can manage deliverables of all other business documents. See: Enabling Oracle Procurement Contract Deliverables in Oracle Supplier Management Implementation and Administration Guide.
Set up deliverables on supplier approval for validity tracking:
For approved suppliers, you can use deliverables to track validity of various documents and profile attributes. See: Add contracts and deliverables in Periodic Supplier Profile Audit.
You can search for deliverables that exist in many business documents, using a variety of search parameters. You can access the Manage Deliverables page that enables you to view or update deliverables across business documents, using one of the following methods:
<![if !supportLists]>· <![endif]>Click the Deliverables link in the Negotiations Home Page.
<![if !supportLists]>· <![endif]>Open a supplier’s profile and click on Deliverables in the side navigation.
The search results show summary information for each retrieved deliverable, such as the status, responsible party, contact, and the due date. In addition, an alert marker indicates if the deliverable is overdue, or if the responsible party failed to perform the deliverable.
Note: The term ‘overdue’ applies to deliverables where the due date has passed, and the deliverable status is either Open or Rejected. For an Internal User logging on, the only deliverables that are visible and manageable are those where the user is either the Internal Contact or the Requestor. For an External User logging on, the only deliverables that are visible and manageable are those where the user is the External Contact.
After viewing the results, you can perform one or more of the following, for each deliverable:
<![if !supportLists]>· <![endif]>View details of the deliverable.
<![if !supportLists]>· <![endif]>Update the status of the deliverable.
<![if !supportLists]>· <![endif]>Add attachments to the deliverable.
You can also delete attachments to deliverables in a business document.
Note: This does not delete attachments to deliverables as defined in the business document, and visible in the Deliverables tab of the Contract Terms page.
Steps:
<![if !supportLists]>1. <![endif]>In the Manage Deliverables page, you can search for deliverables using a combination of all or part of the following search parameters (the parameters marked * are not available for deliverables managed through Oracle iSupplier Portal):
<![if !supportLists]>o <![endif]>Deliverable Name
<![if !supportLists]>o <![endif]>Status
<![if !supportLists]>o <![endif]>Due Date From
<![if !supportLists]>o <![endif]>Due Date To
<![if !supportLists]>o <![endif]>Responsible Party*
<![if !supportLists]>o <![endif]>Deliverable Type*
<![if !supportLists]>o <![endif]>Document Type
<![if !supportLists]>o <![endif]>Document Number
<![if !supportLists]>2. <![endif]>Click Go to perform the search. The results show the following for each deliverable:
<![if !supportLists]>o <![endif]>Deliverable Name
<![if !supportLists]>o <![endif]>Deliverable Type
<![if !supportLists]>o <![endif]>Document Type
<![if !supportLists]>o <![endif]>Document Number
<![if !supportLists]>o <![endif]>Responsible Party
<![if !supportLists]>o <![endif]>Contact
<![if !supportLists]>o <![endif]>Due Date
<![if !supportLists]>o <![endif]>Status
If the deliverable is overdue, or if the responsible party failed to perform the deliverable, an icon appears in the Alert column of the results. Each row also has an Update icon, to allow you to update the deliverable.
<![if !supportLists]>3. <![endif]>You may perform any of the following operations:
<![if !supportLists]>o <![endif]>Click the links on Deliverable Name or Document Number to see further details of the deliverable or document. When you choose to view deliverable details, you will be able to switch to update mode, in order to update the status of the deliverable.
<![if !supportLists]>o <![endif]>Click the Update icon to update the status of the deliverable.
Supplier Material Qualification is the process of gathering products and services category and item related information from Suppliers through a request for information. Buyers generally use this process before a sourcing award event to shortlist qualified suppliers.
With Oracle Supplier Lifecycle Management, it is possible to carry out a request for information with the following additional features:
<![if !supportLists]>· <![endif]>Map category level requirements with user defined attributes in the Supplier profile.
<![if !supportLists]>· <![endif]>Approve Category Lines from RFI to automatically create them in Approved Suppliers List.
<![if !supportLists]>· <![endif]>Map item level requirements with Oracle Product Information Management Item attributes, which are also user defined.
See: Mapping RFI requirements and Category Line Attributes with Supplier Profile and Mapping RFI Item Lines with Item Supplier Profile Attributes in Oracle Supplier Management Implementation and Administration Guide.
Manage tasks, defined as the lowest units of work, that are related to the organization or person, using the Oracle Applications Framework tasks features from Oracle Common Application Calendar. Supplier Management enables you to view, create, update, and delete tasks from the supplier details page. Additionally, Supplier Management enables you to manage notes. See: Supplier Profile.
Use the Supplier Management Administrator or Supplier Management User responsibilities and the Tasks subtab on the Supplier tab to search for tasks. Export the task information using the Export button on the Tasks page.
Organizations are constantly seeking high performance from their suppliers so they can source a bigger fraction of their requirements from cost effective, responsive, well performing suppliers while reducing business with under-performers or retiring them completely. Supplier Lifecycle management provides a mechanism to evaluate supplier performance and gather key performance metrics such as supplier responsiveness, technical performance, quality control performance, and cost performance.
Supplier performance evaluation is an internal process, where experts within various departments are invited to provide evaluation of suppliers that they deal with. With Supplier Lifecycle management, you can ask a team of internal evaluators to submit supplier performance metrics that your organization uses to track supplier performance. You have the flexibility of customizing requirements from internal evaluators. In some cases these metrics may be subjective, while in other cases, it may be absolute values. For example, you may ask internal evaluators to key in the on-time delivery information of a supplier or ask them about the overall responsiveness of the supplier.
All the information gathered from internal evaluators is saved and can be made readily available in the supplier’s profile. You can also hide supplier performance evaluations from suppliers and internal users by controlling profile access. Once you set up a template with evaluation metrics, you can use the same template on a periodic basis to evaluate one or more suppliers.
<![if !supportLists]>1. <![endif]>Create a RFI using the Performance Evaluation RFI Template or Reusable requirements set up by the Supplier Management Administrator. See Implementing Supplier Performance Evaluation in Oracle Supplier Management Implementation and Administration Guide
The RFI created for supplier performance evaluation should be created with predefined negotiation style ‘Supplier Performance Evaluation’. Only internal requirements should be added to gather supplier performance evaluations from internal users. Optionally, you can associate scores with internal requirement responses.
If you wish to save the resulting metrics in the supplier’s profile, then you must set up mappings between RFI responses and supplier profile user defined attributes. To map the exact evaluator responses, map the response value. If you have defined automatic scores for responses or if the RFI owner assigns scores to evaluations, you can map individual requirement scores, section scores as well as the total score to user defined attributes in the supplier’s profile.
See Example– Mapping multi-row user defined attributes with RFI Requirements section values and total score in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>2. <![endif]>Add existing suppliers to RFI. This does not notify the supplier as in case of a profile audit RFI, but creates an evaluation for each included supplier. Create an evaluation team with members from various departments to assign the task of evaluation. Publish the RFI. Select Open Date and Close Date
<![if !supportLists]>3. <![endif]>Evaluators receive a notification about the RFI. See Evaluating Suppliers in Managing New Supplier Qualification.
The difference between registration flow and performance evaluation flow is that suppliers do not respond to the RFI, therefore only internal evaluators can create responses to the RFI. On completing the RFI, the application synchronizes all RFI responses with the supplier profile on the basis of the mappings. The approval step is not required for synchronization.
<![if !supportLists]>4. <![endif]>Classify suppliers based on performance evaluation score. See Assigning Classifications.
One of the key elements of Oracle Supplier Management is enhanced communication between suppliers and buyers. Oracle Supplier Management generates a large number of notifications that appear throughout the supplier lifecycle. However, many of these notifications vary in relevance depending on the business process followed by the buying organization. Oracle Supplier Management has a notification framework that allows administrators to easily enable or disable notifications system-wide.
The Supplier Management administrator can set up notification subscriptions. The first set of notifications is related to request for information (RFI) documents that are used often in Supplier Lifecycle Management during supplier registration, or supplier compliance and profile audit, or during supplier performance evaluation.
For descriptions of these notifications and the detailed messages, please see Appendix C in Oracle Sourcing Implementation and Administration Guide. The administrative task of setting up these notifications is covered in Setting up Notification Subscriptions chapter in Oracle Supplier Management Implementation and Administration Guide.
The other set of notifications are specific to supplier profile and registration. Supplier Management Administrator can subscribe users to any notifications from this page.
The administrative task of setting up these notifications for various users is covered in Setting up Notification Subscriptions in Oracle Supplier Management Implementation and Administration Guide.
Another set of notification subscriptions is event-based notifications. See Setting up Business Events in Oracle Supplier Management Implementation and Administration Guide for business events supported by Supplier Management. Subscribe to any of these business events for notifications. For more information on creating notifications, see the Oracle Workflow User’s Guide.
You can notify all or a subset of your registered suppliers using Oracle Supplier Management. Navigate to the Supplier Home page. To notify suppliers:
<![if !supportLists]>1. <![endif]>Click on Notify All Suppliers button on top to notify all suppliers. To notify a subset of suppliers, search for suppliers using the Search region of the Suppliers page. Select the suppliers you wish to notify and click Notify button above the search results table to open the Notifications page. Or open a supplier’s profile details page and click on Notify button.
<![if !supportLists]>2. <![endif]>Enter subject and message to send email and workflow notification for the selected supplier’s contacts.
<![if !supportLists]>3. <![endif]>Select the applicable option in the Send To field. If you select All Contacts, then the application notifies all the contacts of the selected suppliers. If you select Contact Users Only, then the application only notifies those contacts of selected suppliers that have system user accounts.
<![if !supportLists]>4. <![endif]>Optionally, select the Include OSN Registration Instruction, if you are notifying suppliers who have not yet registered on Oracle Supplier Network.
You can also send notifications to prospect suppliers from the registration request page. Open the registration request and enter a message in the Note to Supplier field. Click on the Notify button to send the note to the prospect supplier’s email address used for registration.
Administrators have the option of notifying a group of internal users. To notify a group of internal users, navigate to the Administration tab from the Supplier Management Administrator responsibility and Supplier Home menu. Click on the Security sub tab and find the group you wish to notify. Click on Send Email to Members. This opens up your default mail client with member email addresses copied in the To field.
Buyer Administrators or owners of a sourcing document can notify document collaborators of pending tasks. To notify RFI collaborators, open the sourcing document:
<![if !supportLists]>1. <![endif]>Select Manage Collaboration team from the Action drop down and click Go.
<![if !supportLists]>2. <![endif]>Select All or some collaborators and click Notify.
<![if !supportLists]>3. <![endif]>Optionally create a Task with Target Date for each evaluator. The task shows up in the Incomplete Tasks region on the evaluator’s Negotiations home page.
Any notifications that are generated by default by the system fall into this category. Following are the list of system notifications in Oracle Supplier Management:
<![if !supportLists]>· <![endif]>When a Supplier Management User or Sourcing Buyer invites a supplier user to register, an e-mail notification is sent to supplier user containing the URL for the registration page.
<![if !supportLists]>· <![endif]>When a Supplier Management User or Sourcing Buyer approves or rejects the registration request, a notification email is sent to supplier user indicating registration status. A user ID and system generated password is also sent in the notification.
<![if !supportLists]>· <![endif]>When a Buyer publishes a RFI, all participating suppliers are notified via a workflow notification.
This chapter covers the following topics:
Classify organizations using classification schemes, which include a class category and a class code. The class category is a broad subject that you can classify entities in, and the code, or classification, is a specific value of the category. You can use standard industrial classifications, including SIC, NACE, and NAICS codes.
Use Supplier Data Librarian Super User responsibility, Supplier Home menu, Administration tab and Classifications sub tab to access Classifications page. You must have a valid Supplier Hub license for classifying suppliers. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
See Classifications Overview in Oracle Trading Community Architecture Administration Guide.
<![if !supportLists]>· <![endif]>Assign: Assign classifications of the selected category. See Assigning Classifications.
<![if !supportLists]>· <![endif]>Update: You can update only the classification's end date.
<![if !supportLists]>· <![endif]>Remove: Assign the classification an end date of today. The removed classification is immediately inactive.
<![if !supportLists]>· <![endif]>View History: View and optionally restore previously removed classifications so that they are again active classifications for the organization or person
Classifications enable better categorization of suppliers in the Supplier Master based on your business needs and corporate policies. For example, after evaluating the supplier’s performance, you can classify them as premium, preferred, or not suitable suppliers. You must have a valid Supplier Hub license for classifying suppliers. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
To manage supplier classifications:
<![if !supportLists]>1. <![endif]>Search for a supplier in the Search region on the Suppliers page.
<![if !supportLists]>2. <![endif]>Select the applicable supplier in the Search Results region and click the Update icon to open the Update page for the specific supplier.
<![if !supportLists]>3. <![endif]>Click General Classification link to open the Classifications page. Use this page to specify general and industrial classifications for the suppliers.
Oracle Supplier Management User's Guide
Release 12.1 Part Number E16534-01 |
This chapter covers the following topics:
A hierarchy is a collection of parties associated with a particular hierarchical relationship type at a given point in time. The hierarchy shows relationships between organizations in a tree structure. For example, you can get a visual representation of a corporate structure. See Relationships Overview in Oracle Trading Community Architecture User Guide.
Oracle Supplier Management allows consolidating supplier hierarchy details from source systems. If source systems do not have any supplier hierarchy details, then you can create hierarchies in Supplier Management.
Use the Supplier Data Librarian responsibility and the Hierarchies sub tab on the Suppliers Home menu to view and create supplier hierarchies. This page is also accessible from Supplier Management User and Supplier Management Administrator responsibilities, but you must have a valid Supplier Hub license to set up supplier hierarchies. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
See Hierarchies Overview, Creating Hierarchies, Viewing and Updating Hierarchies in Oracle Customers Online User Guide. Supplier Data Librarian Super User can create relationship types from the Relationships sub tab in the Administration tab.
Bulk import is the process of loading supplier data in bulk from legacy, third party, or other external sources into the Supplier Master, which includes TCA Registry. In Oracle Supplier Data Librarian responsibility, you can use Batch Import to transfer batches of data from the interface tables into the Supplier Master. A batch is a set of data to be loaded into the Supplier Master at one time. The data in one batch must be from the same data source. With Batch Import, you can review and control the import process. Supplier import process provides validations and optional de-duplication to ensure the quality of information being imported.
<![if !supportLists]>· <![endif]>Organization Party
<![if !supportLists]>· <![endif]>Address
<![if !supportLists]>· <![endif]>Contact
<![if !supportLists]>· <![endif]>Classification
<![if !supportLists]>· <![endif]>Relationships
<![if !supportLists]>· <![endif]>User Defined Attributes
Additionally, you can import child entities including supplier product and services category associations, business (diversity) classifications, bank detail, and additional tax details.
The import process creates a party in the TCA registry and enables the created TCA Parties in the Supplier Master as suppliers. You can also use the supplier import process to enable existing TCA Organization parties as suppliers in the Supplier Master using the batch import functionality described above.
<![if !supportLists]>1. <![endif]>Define Pre-requisites
<![if !supportLists]>2. <![endif]>Generate Batches
<![if !supportLists]>3. <![endif]>Load data into interface tables
<![if !supportLists]>4. <![endif]>Define Import
<![if !supportLists]>5. <![endif]>View and Update the Batch (Update works only if Pre-import only was run)
<![if !supportLists]>6. <![endif]>Purge Data from interface tables
Define Source Systems. This is required before creating batches since a batch is created for importing from a specific source system. See Source System Management in Oracle Trading Architecture Administration Guide.
Log in with Supplier Data Librarian or Supplier Data Librarian Super User responsibility and click on Supplier Home menu. Navigate to the Import tab to create batches for import. Import tab is also visible from the Supplier Management User and Supplier Management Administrator responsibilities.
Generate batches after setting up the source systems. Create import batches before loading data into the import interface tables. After a batch is generated, you can use any available loading tools to populate TCA interface tables. A generated batch initially has no batch status.
Click Generate Batch on the Import Batches page to open the Generate Batch page. See Generating Batches in Oracle Customer Data Librarian User Guide.
Use the batch ID of the import batch to load supplier data into interface tables. See Loading Data into the Interface Tables in Oracle Trading Architecture User Guide. Please note that File Load feature of TCA is not available in Supplier Hub.
Integrated supplier import program imports the data from several TCA and AP interface tables; therefore upload data into these interface tables. See: Defining Imports.
Supplier Hub enables you to import supplier details such as organization (HZ party), person, address, contact, supplier, supplier site, supplier contact, user defined attributes using a spreadsheet. Spreadsheet import uses display formats that enable you to load different set of data for a given batch into the interface tables.
While searching for supplier information, data librarians can select the search criteria and display format. The application retrieves the data in the selected format and data librarians can import data into the interface tables using these formats used for the spreadsheet. See Setting up Search Criteria and Display Formats in the Oracle Supplier Management Implementation and Administration Guide.
Use the Data Librarian Super User responsibility and the Import tab to process the batch.
To import supplier data using a spreadsheet, complete the following:
<![if !supportLists]>1. <![endif]>Click Generate Batch and enter a batch name and source system.
<![if !supportLists]>2. <![endif]>Click Apply and ensure to note the batch ID.
<![if !supportLists]>3. <![endif]>Click Advance Search available on the Supplier Home page.
<![if !supportLists]>4. <![endif]>Select Search Criteria, Display Format, and click Search.
<![if !supportLists]>5. <![endif]>Click on Export All button.
Note: Before you perform this step, ensure to check the Trust access to Visual Basic Project if you are using MS Office XP, 2003, 2007. See: Setting up Spreadsheet Import in Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>6. <![endif]>Select Excel version.
<![if !supportLists]>7. <![endif]>Save the exported excel file on your PC.
<![if !supportLists]>8. <![endif]>Open the saved excel file and click on Enable Macro.
<![if !supportLists]>9. <![endif]>Modify the record as required and save.
<![if !supportLists]>10. <![endif]>Click Add-Ins tab > Oracle > Upload or Oracle tab > Upload based on your MS Excel version to upload the modified excel file.
<![if !supportLists]>11. <![endif]>Click in the Result Format Usage ID field in the Upload Parameters window. The application displays the import batch ID in this field.
<![if !supportLists]>12. <![endif]>Click Upload. The application confirms the successful completion of the concurrent program. Note the number.
<![if !supportLists]>13. <![endif]>Navigate to Administration > Concurrent request > View request and search for the concurrent request ID. Click Refresh button till concurrent program gets completed with normal status.
<![if !supportLists]>14. <![endif]>Click Import and select the Batch number that you received after generating the batch.
<![if !supportLists]>15. <![endif]>Click Activate Batch.
<![if !supportLists]>16. <![endif]>Select the batch and click Define import. Verify the batch gets submitted for the import and complete with normal status. Search for the supplier and notice the modifications that you had made and imported using the spreadsheet import format.
After data is loaded into the interface tables for this batch, activate the batch on the Import Batches page, and then proceed to define the import. This step is optional, but active a batch to see the total number of records in the interface tables for that batch.
Select a batch in the Import Batches page and click Define Import to open the Define Import: Batch De-Duplication page.
Note: To perform address validation during import (one of the pre-processing steps), you must insert data into HZ addresses interface table (HZ_IMP_ADDRESSES_INT) and not in the AP addresses interface table (AP_SUPPLIER_SITES_INT).
See Defining Imports in Oracle Customer Data Librarian User Guide.
Import Program: Defining the batch automatically triggers batch import. In case of Supplier Hub, the concurrent program run is ‘Integrated Supplier Import program’ instead of Import Batch to TCA Registry program.
The ‘Integrated Supplier Import’ concurrent program first runs ‘Import Batch to TCA Registry’ program, which imports all the party information like party, address, contact, classification and relationships into the TCA registry. See Import Batch to TCA Registry, Oracle Trading Architecture User Guide for details on ‘Import Batch to TCA Registry’ program provided by TCA. When Party Import status is ‘Completed’, Integrated Supplier Import program automatically enables the imported party as a supplier in the Supplier Master.
The integrated import program processes the data from the TCA interface tables and creates the entities in the HZ tables. It also creates the corresponding supplier related entities in the AP tables and synchronizes them with the HZ data.
If the data is inserted into the HZ_PARTIES_INT table in the insert mode and the import program is executed, then a new party is created and it is enabled as a supplier. If the processing mode is update, then the corresponding party data is updated. If the party is already enabled as a supplier, then the supplier information would be synchronized with the updated information from the party tables. If the party being updated is not already enabled as a supplier, then a new supplier would be created with the updated information.
If the data is inserted into the HZ_IMP_CONTACTS_INT table, then the person would be associated as a contact to the party and it would also be enabled as a supplier contact. In the update mode the contact details would be updated. If the contact were not already enabled as a supplier contact then it would be enabled.
If the data is inserted into AP interface tables and not the HZ interface tables, then Integrated Supplier Import program will insert data from AP interface tables to HZ interface tables as a part of preprocessing (AP_SUPPLIERS_INT to HZ_IMP_PARTIES_INT, AP_SUPPLIER_SITES_INT to HZ_IMP_ADDRESSES_INT, AP_SUP_SITE_CONTACT_INT to HZ_IMP_CONTACTS_INT). The 'Integrated Supplier Import' concurrent program first runs 'Import Batch to TCA Registry' program, which imports all the party information like party, address, contact, classification, and relationships into the TCA registry. After the party import program is completed, it creates supplier and supplier related entities in AP tables.
When you run the Integrated Supplier Import program using Define Import > Submit, then this integrated program calls the AP interface import programs. The import process picks up the data in AP interface tables for processing based on the SDH_BATCH_ID column for which the import process is running. For further information on AP supplier interface tables, see Understanding the Supplier Open Interface Tables in Oracle Payable's Reference Guide.
The AP supplier interface tables have additional columns to support the Integrated Supplier Import program.
AP_SUPPLIERS_INT - the following columns are available in this table for storing batch id, party id, and original system references:
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ID
AP_SUPPLIER_SITES_INT - the following columns are available in this table for storing batch id, party id, and original system references:
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS_REFERENCE
<![if !supportLists]>· <![endif]>SUPPLIER_SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>SUP_SITE_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ID
<![if !supportLists]>· <![endif]>LOCATION_ID
AP_SUP_SITE_CONTACT_INT - the following columns are available in this table for storing batch id, party ids, and original system references:
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS_REFERENCE
<![if !supportLists]>· <![endif]>SUPPLIER_SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>SUP_SITE_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>CONTACT_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>CONTACT_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ID
<![if !supportLists]>· <![endif]>PER_PARTY_ID
<![if !supportLists]>· <![endif]>REL_PARTY_ID
<![if !supportLists]>· <![endif]>RELATIONSHIP_ID
<![if !supportLists]>· <![endif]>ORG_CONTACT_ID
Mandatory columns for HZ_IMP_PARTIES_INT
<![if !supportLists]>· <![endif]>BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PARTY_TYPE
<![if !supportLists]>· <![endif]>ORGANIZATION_NAME
<![if !supportLists]>· <![endif]>PERSON_FIRST_NAME
<![if !supportLists]>· <![endif]>PERSON_LAST_NAME
<![if !supportLists]>· <![endif]>CREATION_DATE (Needed in case of de duplication; this date can be sysdate)
Mandatory columns for AP_SUPPLIERS_INT
<![if !supportLists]>· <![endif]>VENDOR_INTERFACE_ID
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>VENDOR_NAME
<![if !supportLists]>· <![endif]>SEGMENT1 (Same as PARTY_ORIG_SYSTEM_REFERENCE)
Mandatory columns for AP_SUPPLIER_SITES_INT
<![if !supportLists]>· <![endif]>VENDOR_SITE_INTERFACE_ID
<![if !supportLists]>· <![endif]>VENDOR_SITE_CODE
<![if !supportLists]>· <![endif]>ADDRESS_LINE1
<![if !supportLists]>· <![endif]>COUNTRY
<![if !supportLists]>· <![endif]>ORG_ID and/or OPERATING_UNIT_NAME
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS_REFERENCE
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
Mandatory columns for HZ_IMP_ADDRESSES_INT
<![if !supportLists]>· <![endif]>BATCH_ID
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>SITE_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>SITE_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>ADDRESS1
<![if !supportLists]>· <![endif]>CITY
<![if !supportLists]>· <![endif]>COUNTRY
<![if !supportLists]>· <![endif]>PARTY_SITE_NAME (this is same as VENDOR_SITE_CODE)
Mandatory columns for AP_SUP_SITE_CONTACT_INT
<![if !supportLists]>· <![endif]>VENDOR_SITE_CODE (if it is site contact)
<![if !supportLists]>· <![endif]>ORG_ID and/or OPERATING_UNIT_NAME
<![if !supportLists]>· <![endif]>FIRST_NAME
<![if !supportLists]>· <![endif]>LAST_NAME
<![if !supportLists]>· <![endif]>AREA_CODE (if present)
<![if !supportLists]>· <![endif]>PHONE (if present)
<![if !supportLists]>· <![endif]>EMAIL_ADDRESS (if present)
<![if !supportLists]>· <![endif]>FAX_AREA_CODE (if present)
<![if !supportLists]>· <![endif]>FAX (if present)
<![if !supportLists]>· <![endif]>VENDOR_CONTACT_INTERFACE_ID
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>PARTY_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYSTEM (if it is site contact)
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS_REFERENCE (if it is site contact)
<![if !supportLists]>· <![endif]>CONTACT_ORIG_SYSTEM
<![if !supportLists]>· <![endif]>CONTACT_ORIG_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
Mandatory columns for POS_PRODUCT_SERVICE_INT
<![if !supportLists]>· <![endif]>SDH_BATCH_ID
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>PS_INTERFACE_ID (unique for table)
<![if !supportLists]>· <![endif]>REQUEST_STATUS
<![if !supportLists]>· <![endif]>SEGMENT1, SEGMENT2, SEGMENT3, SEGMENT4, SEGMENT5, SEGMENT6, SEGMENT7, SEGMENT8, SEGMENT9, SEGMENT10, SEGMENT11, SEGMENT12, SEGMENT13, SEGMENT14, SEGMENT15, SEGMENT16, SEGMENT17, SEGMENT18, SEGMENT19, SEGMENT20 (Depending upon segment definition)
<![if !supportLists]>· <![endif]>SEGMENT_DEFINITION
Mandatory columns for POS_BANK_ACCOUNT_DET_INT - at Supplier Level
<![if !supportLists]>· <![endif]>BANK_ACCOUNT_INTERFACE_ID
<![if !supportLists]>· <![endif]>COUNTRY_CODE
<![if !supportLists]>· <![endif]>ALLOW_INTERNATIONAL_PAYMENTS
<![if !supportLists]>· <![endif]>BATCH_ID
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>BANK_NAME
<![if !supportLists]>· <![endif]>BRANCH_NAME
<![if !supportLists]>· <![endif]>BANK_ACCOUNT_NUMBER
<![if !supportLists]>· <![endif]>ACCOUNT_NAME
Mandatory columns for POS_BANK_ACCOUNT_DET_INT - at Party Site Level
<![if !supportLists]>· <![endif]>BANK_ACCOUNT_INTERFACE_ID
<![if !supportLists]>· <![endif]>COUNTRY_CODE
<![if !supportLists]>· <![endif]>ALLOW_INTERNATIONAL_PAYMENTS
<![if !supportLists]>· <![endif]>BATCH_ID
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>BANK_NAME
<![if !supportLists]>· <![endif]>BRANCH_NAME
<![if !supportLists]>· <![endif]>BANK_ACCOUNT_NUMBER
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS
<![if !supportLists]>· <![endif]>PARTY_SITE_ORIG_SYS_REF
<![if !supportLists]>· <![endif]>ACCOUNT_NAME
Mandatory columns for POS_BANK_ACCNT_OWNERS_INT
<![if !supportLists]>· <![endif]>BANK_NAME
<![if !supportLists]>· <![endif]>BANK_COUNTRY_CODE
<![if !supportLists]>· <![endif]>BRANCH_NAME
<![if !supportLists]>· <![endif]>ACCOUNT_NUMBER
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM
<![if !supportLists]>· <![endif]>SOURCE_SYSTEM_REFERENCE
<![if !supportLists]>· <![endif]>ACCOUNT_OWNER_NAME
<![if !supportLists]>· <![endif]>BATCH_ID
<![if !supportLists]>· <![endif]>PRIMARY_FLAG
<![if !supportLists]>· <![endif]>BANK_ACCOUNT_INTERFACE_ID
<![if !supportLists]>· <![endif]>BANK_ACCT_OWNER_INTERFACE_ID
<![if !supportLists]>1. <![endif]>Search for the batch on the Batch Import page.
<![if !supportLists]>2. <![endif]>Select the batch in the search results region to review import results after the import process completes.
<![if !supportLists]>3. <![endif]>To view import errors, click the View Party Errors and View Supplier Errors buttons on the batch detail page.
A concurrent request is submitted for generating the error report for the batch. Click the Refresh button, until the concurrent request gets completed and then click the Output icon to view the error report.
<![if !supportLists]>4. <![endif]>To update a batch, select the batch in the search results region, and click the Update icon. You can only update a batch if the batch has a status of Action Required.
See Viewing or Updating Import Batches in Oracle Customer Data Librarian User Guide. Additionally see Resolving Import Errors in Oracle Customer Data Librarian User Guide.
Purge import batches to permanently remove all records in the batch from the import interface tables, as well as internal tables such as staging and error tables. You can purge any batch, imported or not, except those that have pre-import processes or the import process running.
You usually purge batches:
<![if !supportLists]>· <![endif]>After a satisfactory number of records are successfully imported into the TCA Registry from that batch.
<![if !supportLists]>· <![endif]>If the batch is rejected and you do not plan to import that set of data using another import batch.
Purging the interface tables improves import performance. To archive imported data, you should copy the data to a set of custom tables. See TCA Import Batch Purge in Oracle Trading Architecture User Guide.
Use the batch load process to update D&B information for a large number of parties on a regular schedule or whenever you need. You can update all parties, gather data only for new parties, or update parties that have not been updated since a specified date. Batch retrieval and loading of D&B information is usually a regularly scheduled, automated process that you set up and run. See Batch Loading in Oracle Trading Community Architecture User Guide. Instead of running "Import Batch to TCA Registry", run the Integrated Supplier Import from Supplier Data Librarian responsibility to transfer data from interface tables into the Supplier Master.
Additionally, see the following:
<![if !supportLists]>· <![endif]>Searching for Import Batches in Oracle Customer Data Librarian User Guide
<![if !supportLists]>· <![endif]>Managing Import Batches in Oracle Customer Data Librarian User Guide
<![if !supportLists]>· <![endif]>Viewing Batch Import History in Oracle Customer Data Librarian User Guide
Oracle Supplier Management User's Guide
Release 12.1 Part Number E16534-01 |
This chapter covers the following topics:
- Overview of Managing Supplier Data Quality
- Identifying Duplicates in New Supplier Request
- Identifying Duplicates During Supplier Creation
- Identifying System Duplicates
- Using Automerge
- Creating Merge Request
- Enabling Existing Party as Supplier
- Purging Suppliers
- Maintaining Parties
Supplier Management is built on the foundation of Oracle Trading Community Architecture (TCA). Therefore, a supplier entity is also a party entity in TCA. TCA provides an advanced framework for matching parties to discover possible duplicates and merge duplicates. All these features can be leveraged to find and merge duplicate suppliers, but you must keep in mind that a TCA party merge only merges data related to a party. A supplier entity is associated with more information than a TCA party entity. For example, supplier entity can have associated transactions such as purchase orders and invoices (in case of Integrated Supplier Hub mode). When merging suppliers, first merge these transactions and then merge the parties.
Data Quality Management is a data librarian function. Login with Super Data Librarian responsibility and navigate to the Data Quality tab to perform the following tasks. You must have a valid Supplier Hub license to manage data quality. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
Oracle Supplier Management enables you to prevent duplicate supplier creation in the system during new supplier registration. See Managing New Supplier Qualification.
The administrator must set up duplicate identification before matching organizations are found during registration. See Setting up Duplicate Prevention in Oracle Supplier Management Implementation and Administration Guide.
Oracle Supplier Management enables you to perform an online duplicate check during supplier creation. See Creating Supplier in Managing New Supplier Qualification.
System Duplicate Identification (SDI) feature lets you create SDI batches that contain potential sets of duplicates. De-duplication runs a program to identify duplicates based on criteria that you specify. You can use any duplicate set in a batch as the basis for a new merge request. See System Duplicate Identification in Oracle Payable’s User Guide.
To identify duplicate records, click the System Duplication Identification sub tab to open the System Duplicate Identification Batches page.
You can run Automerge as part of creating SDI batches to automatically merge definite duplicates. This process bypasses manually creating, mapping, and submitting merge requests for obvious duplicates. Parties in the SDI batch that are not merged are included in a new batch, for manual review at a later time.
<![if !supportLists]>· <![endif]>Registry ID: By selecting specific parties. From a Registry ID list of values, you select at least one party to include in your new merge request.
<![if !supportLists]>· <![endif]>Smart Search: Using Smart Search to find potential duplicates. Smart Search provides a list of parties based on your criteria. You select at least one party to include in a new merge request.
<![if !supportLists]>· <![endif]>System Duplicates: From duplicate sets in a System Duplicate Identification (SDI) batch.
A SDI batch contains sets of duplicates that de-duplication identifies based on your criteria for the batch. You select duplicate sets from any batch to create one or more merge requests.
Note: To create a merge request of type Single, use any of the methods to create a request with only the party that you want to cleanse.
In your new merge request, you cannot include parties that already belong to either another merge request or a merge batch in Oracle Trading Community Architecture Party Merge. A message would inform you if you select such a party. See Creating Merge Batches, Oracle Trading Community Architecture User Guide.
Before you submit the new request for creation with the System Duplicates or Registry ID method, you can still remove parties from multiple type requests. You do not delete the party from the TCA Registry, and the party is available to be included in other SDI batches, duplicate sets, or merge requests.
After you submit a new merge request, the Create Merge Batch process runs to create the merge request. Depending on the request type, the name of your new merge request is:
<![if !supportLists]>· <![endif]>Multiple: The name of the master party.
<![if !supportLists]>· <![endif]>Single: The name of the one party in the request.
For merge requests of type Multiple, the HZ: Merge Master Party Defaulting profile option determines the master party, which remains after the merge. You can change the master party when you map the merge request. See Creating Merge Requests and Reviewing Merge Requests in Oracle Customer Data Librarian User Guide.
Use the Merge Requests sub tab on the Data Quality tab to create merge requests.
In case of Integrated Supplier Hub, where other Oracle E-Business Suite products like Purchasing, Accounts Payable are running in the same instance with Supplier Management, you must merge supplier transactions before supplier parties can be merged. Supplier transaction merge combines transaction data like invoices, POs for different supplier (supplier sites) into single supplier/site.
See Supplier Merge Program in Oracle Payable’s User Guide.
Supplier management administrators and data librarians can perform smart searches to find duplicate supplier party records in the system and can merge or cleanse to create the supplier master. Incase of Standalone Supplier Data Hub, as there are no PO or invoice transactions, there is no need to merge supplier transactions prior to submitting supplier party merge request. If there are no defined supplier sites, then you can submit the supplier party merge request. However, incase of Integrated EBS instance with both Supplier Data Hub and any of the other EBS products like Purchasing, Payables, Sourcing, the supplier management administrators and data librarians can perform smart searches to find duplicate supplier party records in the system and use the Merge Supplier button to first merge the transactions and then submit the supplier party merge request. This button is available if you have set the POS: SM: Supplier Data Hub Configuration profile option as Integrated EBS and defined supplier sites. If the profile is set to Standalone and there are no supplier sites defined, then the Merge Supplier button is not available.
Use the Supplier Data Librarian responsibility and Supplier Merge menu to merge supplier transactions. See Supplier Merge Program in Oracle Payable’s User Guide.
Example of Supplier Transaction Merge
This example explains the Supplier Transaction Merge process. In this example, two suppliers Computer Supplier Inc. and Computer Supply Inc. are merged into one golden record for Computer Supplier Inc. Supplier Transaction Merge is applicable in case of Integrated Supplier Hub, where other EBS products like Purchasing, Accounts Payable are running in a same instance with Supplier Hub. Supplier Transaction Merge merges transaction data like invoices, POs in for different supplier (supplier sites) into single supplier/site.
The following table shows how different invoices and POs for different sites are merged under single site after Supplier Transaction Merge applicable in integrated Supplier Hub installation only:
Supplier 1 – Computer Supplies Inc.
|
Supplier 2 – Computer Supply Inc.
|
Supplier Master – Computer Supplies Inc.
|
Invoice
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>10-3456
<![if !supportLists]>o <![endif]>10-3574
<![if !supportLists]>· <![endif]>Supplier site: CSITN
<![if !supportLists]>o <![endif]>10-6785
<![if !supportLists]>o <![endif]>10-9864
<![if !supportLists]>o <![endif]>10-4355
<![if !supportLists]>o <![endif]>10-4435
|
Invoice
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>40-6754
<![if !supportLists]>o <![endif]>40-4522
<![if !supportLists]>o <![endif]>40-4523
<![if !supportLists]>· <![endif]>Supplier site: CSITX
<![if !supportLists]>o <![endif]>40-9877
<![if !supportLists]>o <![endif]>40-9222
<![if !supportLists]>o <![endif]>40-5445
<![if !supportLists]>o <![endif]>40-9983
|
Invoice
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>10-3456
<![if !supportLists]>o <![endif]>10-3574
<![if !supportLists]>o <![endif]>40-6754
<![if !supportLists]>o <![endif]>40-4522
<![if !supportLists]>o <![endif]>40-4523
<![if !supportLists]>· <![endif]>Supplier site: CSITN
<![if !supportLists]>o <![endif]>10-6785
<![if !supportLists]>o <![endif]>10-9864
<![if !supportLists]>o <![endif]>10-4355
<![if !supportLists]>o <![endif]>10-4435
<![if !supportLists]>· <![endif]>Supplier site: CSITX
<![if !supportLists]>o <![endif]>40-9877
<![if !supportLists]>o <![endif]>40-9222
<![if !supportLists]>o <![endif]>40-5445
<![if !supportLists]>o <![endif]>40-9983
|
Purchase Order
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>20-5686
<![if !supportLists]>o <![endif]>20-4674
<![if !supportLists]>· <![endif]>Supplier site: CSITN
<![if !supportLists]>o <![endif]>20-7975
<![if !supportLists]>o <![endif]>20-6864
|
Purchase Order
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>60-7678
<![if !supportLists]>o <![endif]>60-4436
<![if !supportLists]>o <![endif]>60-6332
<![if !supportLists]>o <![endif]>60-6567
<![if !supportLists]>· <![endif]>Supplier site: CSITX
<![if !supportLists]>o <![endif]>60-7863
<![if !supportLists]>o <![endif]>60-9767
|
Purchase Order
<![if !supportLists]>· <![endif]>Supplier site: CSICA
<![if !supportLists]>o <![endif]>20-5686
<![if !supportLists]>o <![endif]>20-4674
<![if !supportLists]>o <![endif]>60-7678
<![if !supportLists]>o <![endif]>60-4436
<![if !supportLists]>o <![endif]>60-6332
<![if !supportLists]>o <![endif]>60-6567
<![if !supportLists]>· <![endif]>Supplier site: CSITN
<![if !supportLists]>o <![endif]>20-7975
<![if !supportLists]>o <![endif]>20-6864
<![if !supportLists]>· <![endif]>Supplier site: CSITX
<![if !supportLists]>o <![endif]>60-7863
<![if !supportLists]>o <![endif]>60-9767
|
Merge Dictionary Overview
The merge dictionary enables supplier management administrators and data librarians to merge supplier profile details like product and service category, business classifications, bank details, UDA, and other child entities. Supplier management administrators and data librarians can customize the merge dictionary. See: Merge Dictionary Overview in Oracle Trading Community Architecture Administration Guide.
<![if !supportLists]>· <![endif]>Assign requests to specific users
<![if !supportLists]>· <![endif]>Unassign requests
<![if !supportLists]>· <![endif]>Reject requests
See Merge Requests Overview in Oracle Customer Data Librarian User Guide.
For each merge request, you map the duplicate information to determine the results of the merge. For both Single and Multiple type requests, you map address and relationship information. De-duplication can provide default suggestions for either mapping.
For Multiple type requests, you also map party profile attributes, which describe the party. For example, for the D-U-N-S Number attribute, you specify which number from the duplicate set should remain after the merge. After reviewing your mapping, you can submit the merge request for the Party Merge process.
See Mapping Merge Requests in Oracle Customer Data Librarian User Guide.
Default Rules for Merging Extended Supplier Profile Attributes
The merge process copies the UDA defined at supplier party, party site, and supplier site levels into the target supplier. The merge includes the attribute groups associated at base/common, supplier type, business classification, product and services, general and industrial classification, country and address purpose.
The merge process uses the following rules while merging UDA details:
<![if !supportLists]>· <![endif]>If a valid UDA attribute group for the supplier does not have any value for the entire attribute group, then the value is copied fully from the source to target supplier for the entire attribute group. However, if there are some attribute values already defined for an attribute group in the target supplier, then in that case only the attribute values that are empty for the attribute group in the target supplier are populated with the source supplier record attribute value.
<![if !supportLists]>· <![endif]>When there are more than one source supplier records to be merged with a target supplier record for a given attribute group, then for the attribute value copying order, the source supplier UDA record for a given attribute group that is created latest is used to populate the target supplier UDA record for the same attribute group first. This is overlaid with the next latest supplier UDA record for the same attribute group in the merge source supplier list as the overlaying is done based on creation date of an attribute group in the descending order for all the source supplier records for a given attribute group.
<![if !supportLists]>· <![endif]>Incase of multi row attribute group, if the attribute group key information is matched then, the merge process applies the first two rules; else, it creates a new row.
<![if !supportLists]>· <![endif]>Incase of party site level UDA, if the source supplier party site is moved as a new party site for the target supplier from party merge, then the UDA information is transferred based on the above mentioned rules.
<![if !supportLists]>· <![endif]>Both incase of Standalone Hub and Integrated EBS, as part of the party merge process, if the target TCA party is currently not a supplier organization, then the target party organization is enabled as supplier.
Example of Supplier Party Merge
This example explains the Supplier Party Merge process. In this example, records of two supplier parties - Computer Supplier Inc and Computer Supply Inc, are merged to form a golden record. The merger creates one record for supplier Computer Supplies Inc. (selected as master) with all its detail and some additional detail added from other record Computer Supply Inc. The Supplier Party Merge process merges party profile, address, contact, general classifications, contact points, party relationships, supplier profile, supplier site, products and services, bank details, business classification, and user defined attributes at the 3 levels. Supplier Party Merge process is applicable in standalone and integrated Supplier Hub installation.
The following table shows how different supplier parties are merged to form a single source of truth:
Supplier 1 – Computer Supplies Inc. (target)
|
Supplier 2 – Computer Supply Inc. (source)
|
Supplier Master – Computer Supplies Inc.
|
Party Profile
<![if !supportLists]>· <![endif]>Registry ID: 1006
<![if !supportLists]>· <![endif]>Party Source System: PSFT
<![if !supportLists]>· <![endif]>DUNS Number:
<![if !supportLists]>· <![endif]>Organization Name: Computer Supplies Inc.
<![if !supportLists]>· <![endif]>Tax Payer ID: 3463465
<![if !supportLists]>· <![endif]>Tax Registration Number: AEF-12684
|
Party Profile
<![if !supportLists]>· <![endif]>Registry ID: 1142
<![if !supportLists]>· <![endif]>Party Source System: JDE
<![if !supportLists]>· <![endif]>DUNS Number: 02- 274-0997
<![if !supportLists]>· <![endif]>Organization Name: Computer Supply Inc.
<![if !supportLists]>· <![endif]>Tax Payer ID:
<![if !supportLists]>· <![endif]>Tax Registration Number:
|
Party Profile
<![if !supportLists]>· <![endif]>Registry ID: 1006
<![if !supportLists]>· <![endif]>Party Source System: PSFT, JDE
<![if !supportLists]>· <![endif]>DUNS Number: 02- 274-0997
<![if !supportLists]>· <![endif]>Organization Name: Computer Supplies Inc.
<![if !supportLists]>· <![endif]>Tax Payer ID: 3463465
<![if !supportLists]>· <![endif]>Tax Registration Number: AEF-12684
|
Address
<![if !supportLists]>· <![endif]>Party Site 1: 3OP
<![if !supportLists]>o <![endif]>Address: 300 Oracle Parkway, Redwood City, CA 94065, US
<![if !supportLists]>o <![endif]>Site Usage: Pay
<![if !supportLists]>· <![endif]>Party Site 2: 3SHD
<![if !supportLists]>o <![endif]>Address: 301 Summit Hill Drive, Chattanooga, TN 37401US
<![if !supportLists]>o <![endif]>Site Usage: RFQ Only
|
Address
<![if !supportLists]>· <![endif]>Party Site 1: 3OP
<![if !supportLists]>o <![endif]>Address: 300 Oracle Parkway, Redwood City, CA 94065, US
<![if !supportLists]>o <![endif]>Site Usage: Purchasing
|
Address
<![if !supportLists]>· <![endif]>Party Site 1: 3OP
<![if !supportLists]>o <![endif]>Address: 300 Oracle Parkway, Redwood City, CA 94065, US
<![if !supportLists]>o <![endif]>Site Usage: Pay
<![if !supportLists]>· <![endif]>Party Site 2: 3SHD
<![if !supportLists]>o <![endif]>Address: 301 Summit Hill Drive, Chattanooga, TN 37401US
<![if !supportLists]>o <![endif]>Site Usage: RFQ Only
|
Contact
<![if !supportLists]>· <![endif]>Contact (For Party Site 1): Joe
<![if !supportLists]>· <![endif]>Contact (For Party Site 2): Bryan
|
Contact
<![if !supportLists]>· <![endif]>Contact (For Party Site 1): Morris
<![if !supportLists]>· <![endif]>Contact (For Party Site 2): Allec
|
Contact:
<![if !supportLists]>· <![endif]>Contact (For Party Site 1): Joe, Morris
<![if !supportLists]>· <![endif]>Contact (For Party Site 2): Bryan
<![if !supportLists]>· <![endif]>Contact (For Party Site 3: Allec
|
General Classifications
<![if !supportLists]>· <![endif]>Preferred Supplier Category: Gold
|
General Classifications
<![if !supportLists]>· <![endif]>Supplier Business Type: Americas
|
General Classifications
<![if !supportLists]>· <![endif]>Supplier Business Type: Americas
<![if !supportLists]>· <![endif]>Preferred Supplier Category: Gold
|
Contact Points
<![if !supportLists]>· <![endif]>Email: joe.smith@csi.com
|
Contact Points
<![if !supportLists]>· <![endif]>Phone: 415-289-3762
|
Contact Points
<![if !supportLists]>· <![endif]>Email: joe.smith@csi.com
<![if !supportLists]>· <![endif]>Phone: 415-289-3762
|
Party Relationships
<![if !supportLists]>· <![endif]>Subsidiary Of: CompUSA
|
Party Relationships
<![if !supportLists]>· <![endif]>Employer Of: Joe Smith
|
Party Relationships
<![if !supportLists]>· <![endif]>Subsidiary Of: CompUSA
<![if !supportLists]>· <![endif]>Employer Of: Joe Smith
|
Supplier Profile
<![if !supportLists]>· <![endif]>Supplier Number: 3427
<![if !supportLists]>· <![endif]>NIC: TX24535
<![if !supportLists]>· <![endif]>Customer Number: 7785678
|
Supplier Profile
<![if !supportLists]>· <![endif]>Supplier Number: 3456
<![if !supportLists]>· <![endif]>NIC: TX24535
<![if !supportLists]>· <![endif]>Customer Number: 9678678
|
Supplier Profile
<![if !supportLists]>· <![endif]>Supplier Number: 3427
<![if !supportLists]>· <![endif]>NIC: TX24535
<![if !supportLists]>· <![endif]>Customer Number: 7785678
|
Supplier Site
<![if !supportLists]>· <![endif]>Supplier Site 1
<![if !supportLists]>o <![endif]>Name: CSICA
<![if !supportLists]>o <![endif]>OU: Vision SFO
<![if !supportLists]>· <![endif]>Supplier Site 2
<![if !supportLists]>o <![endif]>Name: CSITN
<![if !supportLists]>o <![endif]>OU: Vision LA
|
Supplier Site
<![if !supportLists]>· <![endif]>Supplier Site 1 Name: CSICA
<![if !supportLists]>· <![endif]>OU: Vision SFO
|
Supplier Site
<![if !supportLists]>· <![endif]>Supplier Site 1
<![if !supportLists]>o <![endif]>Name: CSICA
<![if !supportLists]>o <![endif]>OU: Vision SFO
<![if !supportLists]>· <![endif]>Supplier Site 2
<![if !supportLists]>o <![endif]>Name: CSITN
<![if !supportLists]>o <![endif]>OU: Vision LA
|
Bank Details
<![if !supportLists]>· <![endif]>Account Number 1: 224-125-09
<![if !supportLists]>· <![endif]>Account Number 2: 224-456-09
|
Bank Details
<![if !supportLists]>· <![endif]>Account Number 1: 223-137-09
<![if !supportLists]>· <![endif]>Account Number 2: 211-443-77
|
Bank Details
<![if !supportLists]>· <![endif]>Account Number 1: 224-125-09
<![if !supportLists]>· <![endif]>Account Number 2: 224-456-09
<![if !supportLists]>· <![endif]>Account Number 3: 223-137-09
<![if !supportLists]>· <![endif]>Account Number 4: 211-443-77
|
Supplier – Business Classification
<![if !supportLists]>· <![endif]>Minority Owned
|
Supplier – Business Classification
<![if !supportLists]>· <![endif]>Small Business
|
Supplier – Business Classification
<![if !supportLists]>· <![endif]>Minority Owned
<![if !supportLists]>· <![endif]>Small Business
|
Supplier – Product and Services
<![if !supportLists]>· <![endif]>Monitor
|
Supplier – Product and Services
<![if !supportLists]>· <![endif]>Keyboard
|
Supplier – Product and Services
<![if !supportLists]>· <![endif]>Monitor
<![if !supportLists]>· <![endif]>Keyboard
|
Supplier Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Insurance Policy Detail
<![if !supportLists]>o <![endif]>Insurance Company: AIG
<![if !supportLists]>o <![endif]>Contact Phone: 7462983489
<![if !supportLists]>o <![endif]>Experience Modification Rate: 0.3
<![if !supportLists]>o <![endif]>Contact Name: Jenna Smith
<![if !supportLists]>o <![endif]>Policy Number: 000021763821
<![if !supportLists]>· <![endif]>Multi row: Supplier Business References
<![if !supportLists]>o <![endif]>Reference Name
<![if !supportLists]>1. <![endif]>Sales Reference
<![if !supportLists]>2. <![endif]>Customer Ref
<![if !supportLists]>o <![endif]>Contact Name
<![if !supportLists]>1. <![endif]>Jim Hills
<![if !supportLists]>2. <![endif]>Steve Swank
<![if !supportLists]>o <![endif]>Contact Phone
<![if !supportLists]>1. <![endif]>9872653789
<![if !supportLists]>2. <![endif]>6279872651
<![if !supportLists]>o <![endif]>Contact Email
<![if !supportLists]>1. <![endif]>jim@vodafone.com
<![if !supportLists]>2. <![endif]>steve.swank@cat.com
<![if !supportLists]>o <![endif]>Business Volume
<![if !supportLists]>1. <![endif]>1.8
<![if !supportLists]>2. <![endif]>4.5
<![if !supportLists]>o <![endif]>Years of Business
<![if !supportLists]>1. <![endif]>7
<![if !supportLists]>2. <![endif]>8
|
Supplier Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Insurance Policy Detail
<![if !supportLists]>o <![endif]>Insurance Company: AIG
<![if !supportLists]>o <![endif]>Contact Phone: 7462983480
<![if !supportLists]>o <![endif]>Contact Name: Jake Murphy
<![if !supportLists]>· <![endif]>Multi row: Supplier Business References
<![if !supportLists]>o <![endif]>Reference Name
<![if !supportLists]>1. <![endif]>Sales Reference
<![if !supportLists]>o <![endif]>Contact Name
<![if !supportLists]>1. <![endif]>Jim Hills
<![if !supportLists]>o <![endif]>Contact Phone
<![if !supportLists]>1. <![endif]>9872653789
<![if !supportLists]>o <![endif]>Contact Email
<![if !supportLists]>1. <![endif]>jim@vodafone.com
|
Supplier Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Insurance Policy Detail
<![if !supportLists]>o <![endif]>Insurance Company: AIG
<![if !supportLists]>o <![endif]>Contact Phone: 7462983489
<![if !supportLists]>o <![endif]>Experience Modification Rate: 0.3
<![if !supportLists]>o <![endif]>Contact Name: Jenna Smith
<![if !supportLists]>o <![endif]>Policy Number: 000021763821
<![if !supportLists]>· <![endif]>Multi row: Supplier Business References
<![if !supportLists]>o <![endif]>Reference Name
<![if !supportLists]>1. <![endif]>Sales Reference
<![if !supportLists]>2. <![endif]>Customer Ref
<![if !supportLists]>o <![endif]>Contact Name
<![if !supportLists]>1. <![endif]>Jim Hills
<![if !supportLists]>2. <![endif]>Steve Swank
<![if !supportLists]>o <![endif]>Contact Phone
<![if !supportLists]>1. <![endif]>9872653789
<![if !supportLists]>2. <![endif]>6279872651
<![if !supportLists]>o <![endif]>Contact Email
<![if !supportLists]>1. <![endif]>jim@vodafone.com
<![if !supportLists]>2. <![endif]>steve.swank@cat.com
<![if !supportLists]>o <![endif]>Business Volume
<![if !supportLists]>1. <![endif]>1.8
<![if !supportLists]>2. <![endif]>4.5
<![if !supportLists]>o <![endif]>Years of Business
<![if !supportLists]>1. <![endif]>7
<![if !supportLists]>2. <![endif]>8
|
Supplier Address Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Party Site Quality Control Procedures
<![if !supportLists]>o <![endif]>Address Name: LOS ANGELES
<![if !supportLists]>o <![endif]>Follows Documented Quality Control Process: Y
<![if !supportLists]>o <![endif]>Quality Instructions Easily Accessible: Y
<![if !supportLists]>o <![endif]>Process Adherence Audits: Y
|
Supplier Address Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Party Site Quality Control Procedures
<![if !supportLists]>o <![endif]>Address Name: LOS ANGELES
<![if !supportLists]>o <![endif]>Follows Documented Quality Control Process: Y
<![if !supportLists]>o <![endif]>Quality Instructions Easily Accessible: Y
<![if !supportLists]>o <![endif]>Process Adherence Audits: Y
| |
Supplier Site Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Site Logistics Information
<![if !supportLists]>o <![endif]>Address Name: LOS ANGELES
<![if !supportLists]>o <![endif]>Standard Delivery Time Guarantee: 5 days
<![if !supportLists]>o <![endif]>Freight Forward Detail: 3PL
<![if !supportLists]>o <![endif]>Transport Insurance Type: Included
|
Supplier Site Level UDA
<![if !supportLists]>· <![endif]>Single row: Supplier Site Logistics Information
<![if !supportLists]>o <![endif]>Address Name: LOS ANGELES
<![if !supportLists]>o <![endif]>Standard Delivery Time Guarantee: 5 days
<![if !supportLists]>o <![endif]>Freight Forward Detail: 3PL
<![if !supportLists]>o <![endif]>Transport Insurance Type: Included
|
Supplier Management administrator and data librarian super users can enable an existing party record to be used as supplier. The party must be an organization and not an individual. The application enables the existing TCA party organization as supplier organization by setting up the appropriate supplier enablement setups (setup supplier party in iPayee, setup supplier party in EBiz Tax, setup supplier party in Oracle Payables.
Additionally, the application enables all the existing TCA party organization contacts/persons with 'supplier' usages, so that the TCA party organization contacts are available from the Supplier Profile Workbench pages as Supplier Contacts. However, instead of automatically enabling all the existing organization contacts with 'supplier' usage the application displays the 'Enable Supplier Contact' button from the Contact Directory page. This button enables you to add an existing party contacts as supplier contacts. If there are no organization contacts defined for the party, then the application does not display the Enable as Supplier Contact button. In such a case, you can click the Create Contact button and add the contact details for the newly enabled supplier. However, all the addresses associated with the TCA Party (Party Sites) are enabled as Supplier Party sites. Supplier sites are not created by default and they must be created manually by clicking on Manage Sites button against each party site and then selecting the associated operating units.
Use the Supplier tab and Enable as Supplier button to enable an existing organization as supplier.
To enable an existing party as supplier:
<![if !supportLists]>1. <![endif]>Search for an existing organization. If the party is already a supplier, then the selection check box is grayed out. Supplier Hub does not allow associating more than one suppliers with the same TCA party. The search results display explicit supplier and customer columns to indicate if the party is used as a customer or supplier or both in the system.
<![if !supportLists]>2. <![endif]>Select the required organization in the Search results area and click Enable as Supplier. The application displays the Update Organization page.
You need to enable the supplier contact for this organization.
To enable the supplier contact for the existing party:
<![if !supportLists]>1. <![endif]>Select Contact Directory link under the Company Profile information.
<![if !supportLists]>2. <![endif]>Click Enable Supplier Contact button to add a supplier contact. Enter the contact details in the Create Contact page and click Apply.
<![if !supportLists]>3. <![endif]>Click Address Book to view all the addresses associated with the supplier. All TCA addresses have been enabled as Supplier party sites. If required, create supplier sites by clicking on the Manage Sites button next to an address and selecting one or more operating units.
Party purge lets you permanently purge parties from the TCA Registry, for example duplicate or mistakenly entered parties. A party is available for purge only if it has no associated transactions, or if the party record has no references from other database tables. You cannot restore a party after you purge it. The purge functionality includes:
Click the Purge Requests subtab to open the Purge Requests page. See Party Purge in Oracle Customer Data Librarian User Guide.
You can also purge invoices, purchase orders and other supplier related records such as invoice payments, supplier schedules, and purchase receipts. See Resource Management in Oracle Payables User’s Guide.
<![if !supportLists]>· <![endif]>Assign a certification level and reason to the party.
<![if !supportLists]>· <![endif]>Indicate if the party is internal to your organization.
<![if !supportLists]>· <![endif]>Activate or inactivate the party.
Click the Party Maintenance subtab to open the Organization Party Maintenance page. Use this page to search for parties by organization. See Party Maintenance in Oracle Customer Data Librarian User Guide.
Oracle Supplier Management User's Guide
Release 12.1 Part Number E16534-01 |
This chapter covers the following topics:
- Overview of Supplier D&B Enrichment
- Searching for Suppliers in D&B
- Enriching New and Approved Suppliers
Oracle Supplier Management enables administrators to review, enrich, and update the supplier master data with data from Dun and Bradstreet (D&B). D&B maintains a growing global database of more than 70 million businesses worldwide. This database provides key information such as D&B's unique identifier, the D-U-N-S Number, and executive contacts, as well as demographic, financial, and credit risk data. D&B provides information in the form of data products and Business Information Reports that contain a variety of data elements.
D&B information is integrated with the party records to maintain accurate information that you can use to evaluate credit risks. The D&B information coexists with user-entered data. You can view and use information from different data sources, such as user entered and D&B.
Supplier Management leverages Third Party Integration features provided by Oracle Trading Community Architecture to purchase information from D&B. For information about purchasing data from D&B, see Third Party Data Integration in Oracle Trading Community Architecture User Guide. The diagram describes the process flow for purchasing D&B information online.
You must have a valid Supplier Hub license for using third party integration. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide. Also, See Setting Up Third Party Data Integration in Oracle Trading Community Architecture Administration Guide.
Prior to searching and purchasing data from D&B, ensure that you have requisite privileges to access D&B data and completed the required setup. See Setting up Supplier Data Enrichment in Oracle Supplier Management Implementation and Administration Guide.
Use the Supplier Data Librarian or Supplier Data Librarian Super User responsibility and Search D&B sub tab on the Suppliers tab. Search D&B tab is also visible from the Supplier Management User and Supplier Management Administrator responsibilities, but you must have a valid Supplier Hub license to search D&B. See Guidelines for Purchasing Required Licenses in Oracle Supplier Management Implementation and Administration Guide.
To search D&B for supplier data:
<![if !supportLists]>1. <![endif]>Specify the search criteria on the D&B Search and Results page, for example the DUNS Number.
<![if !supportLists]>2. <![endif]>Click Go. The application searches the D&B database and presents the details in the Search Results region.
<![if !supportLists]>3. <![endif]>Review the supplier data from D&B.
You can enrich data for a new supplier during supplier registration. See Managing New Supplier Qualification. This mitigates the risk of approving suppliers going out of business, suppliers on any type of debarment list or involved in fraudulent, bribery or money laundering activities.
For approved suppliers, you can buy D&B information either from the Search D&B page as shown above or directly from the Supplier’s profile details page. From the supplier’s profile page, click on Enrich button to open the Review: D&B Purchase Data page. This page shows a side-by-side view of user-entered, D&B and Single Source of Truth data. See Single Source of Truth Overview in Oracle Trading Community Architecture User Guide.
Supplier Data Publication provides integration of Supplier Hub with other spoke systems. It has the infrastructure to raise necessary business events. Supplier Hub provides the supplier profile publish event that enables publishing of supplier information. The Hub has the ability to track publish event history and to generate a report of the supplier profile. Additionally, Supplier Hub has APIs that can be used to integrate data from third party systems. Since Supplier Hub uses Oracle Trading Community Architecture as its foundation, various APIs provided by TCA can be used to perform supplier related operations. For TCA product APIs, see Oracle Trading Community Architecture Technical Implementation Guide.
Supplier Hub provides various APIs for extracting and publishing supplier information to third party systems. For automated publication, the business event framework, in conjunction with publication services, provides an integration infrastructure for publishing data in the Supplier Hub repository to consuming business process services and subscribing applications.
Publication services are a set of predefined APIs that extract supplier information from Supplier Hub. Synchronization APIs synchronize data in the Supplier Hub from third party systems.
See Using Supplier Hub APIs in Oracle Supplier Management Implementation and Administration Guide.
Whenever a supplier, supplier site or contact is created or changed within Supplier Hub, a business event is raised. These business events in Supplier Hub are pre-registered with the Oracle Workflow Event manager. A system registered in the Oracle Workflow Event manager can subscribe to an event, and use the event subscription logic to specify the processes to perform when the triggering event occurs.
A business event passes the primary identifier of the changed record plus the operation performed, such as create, update or delete. The subscriber can call the query services to extract the object definition from Supplier Hub using the entity identifier passed by the business event. The subscriber can specify what information they require about that entity based on the input parameters passed to the query service. The query service then returns the object definition to the subscriber.
See Setting up Business Events in Oracle Supplier Management Implementation and Administration Guide.
Export of supplier profile information into spreadsheet from the Advanced Search results page. Search for the supplier or suppliers who you wish to export. Then click on ‘Export All’ to export the entire result set to a spreadsheet. Set the display format to export the most relevant information.
Supplier management data librarians can publish supplier profile from the supplier search results. Supplier Hub enables data librarians to publish:
<![if !supportLists]>· <![endif]>Single or multiple supplier records from the Smart Search, Basic Search, and Advanced Search pages.
<![if !supportLists]>· <![endif]>Updated supplier records.
<![if !supportLists]>· <![endif]>Supplier UDA information.
<![if !supportLists]>· <![endif]>Using the Publish button on the search and organization details pages.
<![if !supportLists]>· <![endif]>Using the POS Supplier Publish Job concurrent program from the Schedule Request page. Data librarians can run this program when they need to publish large quantities of supplier data. This program publishes the whole supplier business object for all suppliers identified for publication. The program identifies suppliers for publication based on input parameters. Data librarians can run this program based on from and to dates, for specific hours, or schedule the program to run at specific date/time/frequency. If the data librarian has not specified any specific parameter, then the program runs from the last run date till the current date.
When you click the Publish button or run the concurrent program, the application raises the Publish Supplier business event. It also inserts data into the pos_supp_pub_history table. This table has the entire data of the supplier in xml format. This is a workflow business event and the spoke system must subscribe to the Publish Supplier business event. See, the relevant topic in the workflow guide to subscribe to the business event. On subscription to the business event, the spoke systems can get the publication event ID as a mail or an alert, based on how they have subscribed. The spoke systems can then use the event ID mentioned in their mail or alert to access the xml data in the table and update their systems.
To publish supplier information using the Publish button:
<![if !supportLists]>1. <![endif]>Search for the supplier.
<![if !supportLists]>2. <![endif]>Select the applicable supplier or multiple suppliers.
<![if !supportLists]>3. <![endif]>Click the Publish button.
To publish supplier information using the concurrent program:
<![if !supportLists]>1. <![endif]>Navigate to the Schedule Request page using the Concurrent Requests subtab on the Administration tab.
<![if !supportLists]>2. <![endif]>Enter POS Supplier Publish Job as the concurrent program name.
<![if !supportLists]>3. <![endif]>Select the applicable parameters.
Note: If the data librarian has not specified any specific parameter, then the program runs from the last run date till the current date.
Supplier Hub enables data librarians to track the publication history for information purposes. Use the Supplier Management Data Librarian Super User (get the name correct from the application) responsibility and the Publish Event History left pane navigation link on the supplier details page.
To track publication history:
<![if !supportLists]>1. <![endif]>Search Supplier, click on Update Pen icon and Go to Publish Event History side navigation link.
<![if !supportLists]>2. <![endif]>Enter search criteria based on Publication Date From and Publication Date To and click on Go button or enter published by and click Go.
Supplier Hub enables you to generate supplier profile reports using Oracle BI Publisher. Oracle BI Publisher is a template-based publishing solution delivered with the Oracle E-Business Suite. It provides a new approach to report design and publishing by integrating familiar desktop word processing tools with existing E-Business Suite data reporting. BI Publisher leverages standard, well-known technologies and tools, so you can rapidly develop and maintain custom report formats. You can design and control how the report outputs are presented in separate template files. At runtime, BI Publisher merges your designed template files with the report data to create PDF, RTF, HTML, or EXCEL output to meet a variety of business needs.
To generate the supplier profile report using BI Publisher:
Note: Ensure to set up applicable values for the POS: SM: Supplier Report Template and POS: SM: Supplier Report Output Type profile options. See: Setting up Supplier Profile Report in the Oracle Supplier Management Implementation and Administration Guide.
<![if !supportLists]>1. <![endif]>Search Supplier and click Update icon.
<![if !supportLists]>2. <![endif]>Click the Generate Report button.
No comments:
Post a Comment