Troubleshooting Guide

Follow these troubleshooting guidelines for Supplier Directory Services:

S.No.	Issue	Cause	Resolution
1	Can’t see user defined attributes (UDAs) for Suppliers	After definition, UDAs need to be associated with different classifications and included in Attribute pages to be displayed. And pages are only displayed for associated classifications.	Associate the UDAs to certain classifications and define UDA pages that include the UDAs. To display UDA pages for Suppliers, please check if the Suppliers have those associated classifications.
2	Can’t see defined Search Criteria/Display Format in Advanced Search	Search Criteria/Display Formats are defined for a certain combination of classification context. Choosing incorrect classification will cause no display of the Criteria/Formats.	Before conducting Advanced Search, make sure to select the intended classification context, and then Search Criteria/Display Format defined under this context will be displayed properly.
3	Profile option “POS: SM: Default Role for Internal Users” doesn’t have the list of value	There are no pre-defined roles and privileges during the implementation	Create the following default privileges and roles: Role Name: Supplier Profile Administrator, Role Code: POS_SUPPLIER_PROFILE_ADMIN. Including the following 3 default privileges: Privilege Name: View Supplier, Code: POS_VIEW_SUPPLIER, Object Name: Parties Privilege Name: Edit Supplier, Code: POS_Edit_SUPPLIER, Object Name: Parties Privilege Name: Grant/Revoke Profile Access Roles on the Supplier, Code: POS_EDIT_SUPPLIER_ACCESS, Object Name: Parties Role Name: Standard Buyer, Role Code: POS_STANDARD_BUYER. Including the following 1 default privilege: Privilege Name: View Supplier, Code: POS_VIEW_SUPPLIER, Object Name: Parties Role Name: Supplier User, Role Code: POS_SUPPLIER_USER. Doesn’t include any privileges, customers can add any pre-defined or self-defined privileges according to business requirements
4	Simple Search doesn’t return any results	The supplier doesn’t exist, or POS:SM: Enable Data Security for Supplier is set to ‘Yes’, but the default roles are not set up correctly.	Setup POS: SM: Default Role for Internal Users with a role having ‘View Supplier’ privilege, such as the pre-defined “Standard Buyer” or any new self-created roles with “View Supplier” privilege.
5	Some UDAs of Advanced Search results show the lock icon	The particular attribute group has been setup with a View Privilege by the administrator, and user does not have that required privilege to see the UDAs.	See Step 6: Setting up Profile Access in Setting up Supplier Profile.

Follow these troubleshooting guidelines for Supplier Qualification and Evaluation:

S.No.	Issue	Cause	Resolution
1	Data Type Mismatch: ⟨Attribute⟩- ⟨Attribute⟩	Data Type of the RFx attribute and that of the mapping UDA do not match.Note: Even though the mapping page validates the mappings, if the data type is changed at a later date, the mappings will error.	Change UDA data type to match RFI attribute or pick a matching UDA for Mapping setup
2	Error is thrown during RFx completion: “⟨Attribute Value⟩ is not a valid value for Attribute ⟨Attribute Name⟩in attribute Group ⟨Attribute Group Name⟩"	RFx attributes have value sets that don’t match the value sets of the corresponding UDA so the RFx attribute responses fail the UDA validation during synchronization process. The error message will look like UDA validation failure.	Change UDA value set definition to accommodate RFx attribute response values. Application Admin should make sure during mapping setup that value sets of RFx attributes and UDA are compatible. See Mapping RFI Responses with User Defined Attributes in Implementing Supplier Registration and Qualification Management.

Follow these troubleshooting guidelines for Supplier Registration:

S.No.	Issue	Cause	Resolution
1	Cannot find RFI Template in Onboarding Configuration	The RFI Template does not have the negotiation control ‘Supplier Registration and Pre Qualification in RFI’ enabled. The RFI Template is created for a different Operating Unit than the Operating Unit selected in the Onboarding Configuration	Verify all above and correct the missing setup
2	New Supplier Request page does not have the ‘Apply Template’ button	The profile option ‘POS: SM: Enable Supplier Profile Management Extension’ is not set to Yes The supplier registration status is not ‘Supplier to Provide Details’ or ‘Pending Approval’ No RFI Template has been configured in the Onboarding Configuration for the OU The prospective supplier is already associated with an RFI generated from the RFI Template configured in the Onboarding Configuration.	Verify all above and correct the missing setup
3	Prospective supplier user cannot create RFI response	The profile option POS: SM: Prospect Supplier Proxy Login User is not setup correctly	Verify that the above profile option has a proper user login for the value
4.	Cannot Find the DQM region with matching Organizations even though there exists duplicates	DQM Match rule is not setup properly	Verify that the profile option HZ: Match Rule for Organization Duplicate Prevention has a valid match rule value
5	Cannot find Enrich button on Registration Approval Page	Enrich button is available only when Profile POS: SM: Enable Buyer D&B Enrichment in Prospective Supplier Registration set to ‘Yes’ After a TCA Party has been associated to the registration request	Verify the profile value Using DQM region, create new or link existing Party to the registration request
6	Cannot find GI classification region on Registration Approval Page	General and Industrial classification region is enabled only after a Party has been associated to the registration request	Using DQM region, create new or link existing Party to the registration request
7	Unable to Enrich Data From Search D&B Page. Error “Unable to connect to the D&B Data base” is displayed	D&B setup could be wrong	Set these profile options: HZ : Allow Access to D&B Online Purchase – Yes HZ : Display D&B button in customer form - Yes HZ : D&B URL - https://toolkit.dnb.com/access/scripts Host Address for D&B Adapter : https://toolkit.dnb.com/access/scripts'

Diagnostics: Use this SQL query to find the TCA party associated with the registration request select vendor_party_id from pos_supplier_registrations

Follow these troubleshooting guidelines for Supplier Data Import:

S.No.	Issue	Cause	Resolution
1	Import request errors out.	This typically occurs due to some missing or incorrect data inserted into the interface tables. For example the source system or the source system references are incorrectly provided or some mandatory data is not supplied.	To identify the cause of the issue, click the errored out batch name on the batch details region and then click the “View Party Errors” button. This would open up a report that would display the rows that have errored out and the cause.
2	Batch De-Duplication doesn’t identify the duplicate records	This would happen if the de-duplication rule that is chosen, makes use of attributes that are not duplicated across the records entered.	To resolve this issue, the attributes that are defined in the de-duplication rule have to be verified and the corresponding data that has been inserted into the interface table has to be checked.