This appendix describes the profile options that affect the operation of Oracle Customer Data Librarian.
This appendix covers the following topics:
During implementation, set a value for each Oracle Customer Data Librarian profile option to specify how Customer Data Librarian controls access to and processes data.
See: Setting User Profile Options, Oracle Applications System Administrator's Guide - Maintenance
Profile options are grouped into one or more profile option categories enabling you to view only the profile options that pertain to your application or function.
Customer Data Librarian Categories
See: Profile Categories, Oracle Applications System Administrator's Guide - Maintenance
Customer Data Librarian Profile Options
This section describes profile options by category.
The tables in this section provide profile option information as follows:
The Default column displays either the default profile option value in italics, or No Default if none exists.
The User Access column indicates whether you can view or update the profile option.
The System Administration: Site, Application, Responsibility, and User columns indicate at which levels the system administrator can update these profile options.
The key for each table is:
Update: You can update the profile option.
View Only: You can view the profile option but cannot change it.
No Access: You cannot view or change the profile option.
The table below lists the profile options that are used for Data Librarian deployment.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Number of Workers for DQM Duplicate Identification Program | Update | Update | Update | Update | Update | Update |
| HZ: Protect Party Modeling Before Merge | Update | Update | Update | Update | Update | Update |
Determine the number of parallel workers to use for the DQM Duplicate Identification program. Workers are processes that run at the same time to complete a task that would otherwise take longer with a single process.
For each System Duplicate Identification batch, the DQM Duplicate Identification program generates sets of duplicates from which you can create merge requests.
Specify if users are warned if the merge request they are creating contains more than one party in the same relationship hierarchy. The warning states that merging such parties might affect party modeling decisions, and allows the user to edit the merge request or continue to create it.
The table below lists the profile options that are used for Data Librarian import setup.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Import Batch De-Duplication Match Rule | Update | Update | Update | Update | Update | Update |
| HZ: Import Registry De-Duplication Match Rule | Update | Update | Update | Update | Update | Update |
| IMC: Import Preview Processing Results | Update | Update | Update | Update | Update | Update |
| IMC: Import Run Address Validation | Update | Update | Update | Update | Update | Update |
| IMC: Import Run Batch De-Duplication | Update | Update | Update | Update | Update | Update |
| IMC: Import Run Registry Match | Update | Update | Update | Update | Update | Update |
| HZ: Preview Import Process Results | Update | Update | Update | Update | Update | Update |
| HZ: Run Import Address Validation | Update | Update | Update | Update | Update | Update |
| HZ: Run Import Batch De-Duplication | Update | Update | Update | Update | Update | Update |
| HZ: Run Import Registry De-Duplication | Update | Update | Update | Update | Update | Update |
| IMC: Automate CSV File Load into TCA | Update | Update | Update | Update | Update | Update |
| IMC: CSV Batch De-Duplication Action | Update | Update | Update | Update | Update | Update |
| IMC: CSV Batch De-Duplication Match Rule | Update | Update | Update | Update | Update | Update |
| IMC: CSV Batch Registry Match Rule | Update | Update | Update | Update | Update | Update |
| IMC: Run CSV Batch Address Validation | Update | Update | Update | Update | Update | Update |
| IMC: Run CSV Batch De-Duplication | Update | Update | Update | Update | Update | Update |
| IMC: Run CSV Batch Registry Match | Update | Update | Update | Update | Update | Update |
Specify the default match rule to use for batch de-duplication. This profile option determines the match rule default in the Define Import: Batch De-duplication page, the first step of defining an import.
Specify the default match rule to use for Registry de-duplication. This profile option determines the match rule default in the Define Import: Import to Registry page, the last step of defining an import.
Specify the default setting for the import option of previewing results before the actual import. This option appears in the Define Import: Import to Registry page, the last step of defining an import. Leaving this profile option blank is the same as setting it to No.
Specify the default setting for the option of running address validation as a preimport process. This option appears in the Define Import: Address Validation page, the second step of defining an import. Leaving this profile option blank is the same as setting it to No.
Specify the default setting for the option of running batch de-duplication as a preimport process. This option appears in the Define Import: Batch De-Duplication page, the first step of defining an import. Leaving this profile option blank is the same as setting it to No.
Specify the default setting for the option of running Registry de-duplication as a preimport process. This option appears in the Define Import: Import to Registry page, the last step of defining an import. Leaving this profile option blank is the same as setting it to No.
Determine whether or not to set the feature for previewing the import results.
Determine whether or not to run address validation for import.
Determine whether or not to run batch de-duplication for import.
Determine whether or not to run registry de-duplication for import.
Determine whether or not to run the data load process without inserting the file in the Data Librarian queue for manual run. The default CSV import options are used.
Specify the default action for de-duplication in the interface tables for a CSV batch.
Specify the default match rule for de-duplication in the interface tables for a CSV batch. The default value is a DQM Match Rule in the Bulk Duplicates ID match rule type.
Specify the default match rule for de-duplication between the interface tables and the TCA Registry for a CSV batch. The default value is a Match Rule in the Bulk Duplicates ID match rule type.
Determine whether or not to run address validation for a CSV batch for import.
Determine whether or not to run batch de-duplication for a CSV batch for import.
Determine whether or not to run registry de-duplication for a CSV batch for import.
Related Topics
Setting Up Import, Oracle Customers Online Implementation Guide.
Import Overview, Oracle Customer Data Librarian User Guide
The table below lists the profile options that are used for setup of the Data Librarian mapping process.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Default Profile Attributes for Merge Mapping | Update | Update | Update | Update | Update | Update |
| HZ: Default Secondary Profile Attributes for Merge Mapping | Update | Update | Update | Update | Update | Update |
| HZ: Enable DQM Merge Suggestion | Yes | Update | Update | Update | Update | Update |
| HZ: Match Rule for Address Mapping Suggestions | Update | Update | Update | Update | Update | Update |
| HZ: Match Rule for Address Search | Update | Update | Update | Update | Update | Update |
| HZ: Match Rule for Relationship Mapping Suggestions | Update | Update | Update | Update | Update | Update |
| HZ: Match Rule for Relationship Search | Update | Update | Update | Update | Update | Update |
| HZ: Merge Master Party Defaulting | Update | Update | Update | Update | Update | Update |
| HZ: Show Address Mapping Suggestions | Update | Update | Update | Update | Update | Update |
| HZ: Show Relationship Mapping Suggestions | Update | Update | Update | Update | Update | Update |
| IMC: Display Notes for Merge Request Mapping | Update | Update | Update | Update | Update | Update |
Specify the method for defaulting party profile attributes for merge. For each duplicate set with multiple parties, the selected method determines which profile attribute values default as the ones that remain after the merge. For Automerge, the defaulted attributes values automatically remain after merge.
For example, if Master Party is selected, the default value for each attribute comes from the master party. Likewise, attribute values are from the party with the latest update date, if that is the selected method.
The method from the HZ: Default Secondary Profile Attributes for Merge Mapping profile option is used instead if you select:
Master Party: But the master party does not have a value for the attribute.
Most Frequent Value: And multiple values fulfill this condition for the attribute.
Set this profile option if you select Master Party or Most Frequent Value for the HZ: Default Profile Attributes for Merge Mapping profile option. The selected secondary method is used if the method from the other profile option does not provide a conclusive default.
If there is still a tie using this secondary method, then a default value is randomly selected among the tied values. For example, you set this profile option to Party with Earliest Creation Date. If five parties have the same earliest creation date, then the value comes from any of the five parties.
Use this profile option to turn off DQM for merge suggestion. The merge process uses DQM for default suggestions during pre-processing due to which the Create Merge Batch process takes a longer time to complete.
Select 'No' to disable DQM at the time of merge suggestion so that the Create Merge batch program runs faster. This also disables the Change Grouping list in the Address Mapping and Relationship-Mapping window.
Select 'Yes' / 'Null' to enable DQM to suggest duplicate address and relationships automatically. The Change Grouping option is enabled if you select 'Yes'. The default value for this option is 'Yes'.
Define the match rule to use for generating default address mapping suggestions. You can use the DL ADDRESS DEFAULT seeded match rule. See: DL ADDRESS DEFAULT, Oracle Trading Community Architecture Reference Guide. If you leave this profile option blank, a default match rule is used to generate address mappings.
Note: The selected match rule also determines which addresses are merged together during Automerge. Make sure that the match rule makes sense for both purposes.
The records are automatically merged only if the HZ: Use DQM Suggested Groupings for Automerge profile option is set to Yes. If you do not set a match rule, then records are not merged, but transferred from duplicate candidates to the merge master party. See: Oracle Trading Community Architecture Administration Guide.
Define the match rule to use for address search in merge request mapping. Based on the user-entered search criterion, the match rule determines the addresses from which the user can select duplicates to merge.
You can use the DL ADDRESS AND RELATIONSHIP SEARCH seeded match rule. See: DL ADDRESS AND RELATIONSHIP SEARCH, Oracle Trading Community Architecture Reference Guide.
Note: No matter which match rule you select, the available search criteria for addresses remain the same. The match rule is used only for scoring and determining search results.
Define the match rule to use for generating default relationship mapping suggestions. You can use the DL RELATIONSHIP DEFAULT seeded match rule. See: DL RELATIONSHIP DEFAULT, Oracle Trading Community Architecture Reference Guide. If you leave this profile option blank, a default match rule is used to generate relationship mappings.
Note: The selected match rule also determines which relationships are merged together during Automerge. Make sure that the match rule makes sense for both purposes.
The records are automatically merged only if the HZ: Use DQM Suggested Groupings for Automerge profile option is set to Yes. If you do not set a match rule, then records are not merged, but transferred from duplicate candidates to the merge master party. See: Oracle Trading Community Architecture Administration Guide.
Define the match rule to use for relationship search in merge request mapping. Based on the user-entered search criterion, the match rule determines the relationships from which the user can select duplicates to merge.
You can use the DL ADDRESS AND RELATIONSHIP SEARCH seeded match rule. See: DL ADDRESS AND RELATIONSHIP SEARCH, Oracle Trading Community Architecture Reference Guide.
Important: No matter which match rule you select, the available search criteria for relationships remain the same. The match rule is used only for scoring and determining search results.
Specify the method to use to select a party as the default merge master for new merge requests that contain multiple parties. For Automerge, the default master is automatically the party that remains after merge.
If multiple parties fulfill the condition for these methods:
Party with Highest Certification
Party with Most Accounts
Party with Most Addresses
Party with Most Relationships
Enter Yes or No to determine whether address mapping suggestions are displayed by default or not. The match rule that is set for the HZ: Match Rule for Address Mapping Suggestions profile option determines the mapping suggestions.
Enter Yes or No to determine whether relationship mapping suggestions are displayed by default or not. The match rule that is set for the HZ: Match Rule for Relationship Mapping Suggestions profile option determines the mapping suggestions.
Enter Yes or No to determine if cumulative notes are displayed and used during mapping of merge requests in de-duplication.
Related Topics
De-Duplication Overview, Oracle Customer Data Librarian User Guide
The table below lists the profile options that are used for setup of Data Librarian process.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Match Rule for Identifying Duplicates with Smart Search | Update | Update | Update | Update | Update | Update |
| HZ: Match Rule for Organization Simple Search | Update | Update | Update | Update | Update | Update |
| HZ: Match Rule for Person Simple Search | Update | Update | Update | Update | Update | Update |
Specify the match rule to use for identifying duplicates by Smart Search. Based on the user-entered search criteria, the match rule determines the potential duplicates from which the user can select to create a merge request.
You can use the DL SMART SEARCH seeded match rule. See: DL SMART SEARCH, Oracle Trading Community Architecture Reference Guide. If you use a different match rule, the available search criteria for duplicates are based on the acquisition and scoring attributes of that match rule.
Note: If you select a match rule set, the displayed search criteria are the superset of all attributes in the set.
Specify the seeded or user-defined match rule for determining the search criteria and results for the organization simple search. Use match rules with the Search purpose. The profile option defaults to the HZ_ORG_SIMPLE_SEARCH_RULE seeded match rule. See: HZ_ORG_SIMPLE_SEARCH_RULE, Oracle Trading Community Architecture Reference Guide.
If you use a different match rule, the available search criteria are based on the acquisition and scoring attributes of that match rule.
Important: This match rule also applies to the organization simple search on the Home and Organizations pages. Select a match rule that works for both purposes.
If you select a match rule set, the displayed search criteria are the superset of all attributes in the set.
Specify the seeded or user-defined match rule for determining the search criteria and results for the person simple search. Use match rules with the Search purpose, but do not use a match rule that has the Organization Name attribute. The profile option defaults to the HZ_PERSON_SIMPLE_SEARCH_RULE seeded match rule. See: HZ_PERSON_SIMPLE_SEARCH_RULE, Oracle Trading Community Architecture Reference Guide.
If you use a different match rule, the available search criteria are based on the acquisition and scoring attributes of that match rule.
Important: This match rule also applies to the person simple search on the Home and Organizations pages. Select a match rule that works for both purposes.
If you select a match rule set, the displayed search criteria are the superset of all attributes in the set.
The table below lists the profile options that are used for setup of Data Librarian security.
| Profile Option | Default | User Access | System Administration: Site | System Administration: Application | System Administration: Responsibility | System Administration: User |
|---|---|---|---|---|---|---|
| HZ: Data Sharing and Security Rules for Data Librarians | Update | Update | Update | Update | Update | Update |
Select a method for applying Data Sharing and Security (DSS) rules to Customer Data Librarian users. The DSS rules assigned to the users' ID determine their privileges for updating parties. If the user cannot update all parties in a merge request, then the user cannot map or merge the request, depending on how this profile option is set. See: Data Sharing and Security Overview, Oracle Trading Community Architecture Administration Guide
If you select Apply Rules at Mapping and Show Access Column, then DSS rules determine privileges to map merge requests, and an Access column appears on the Merge Requests page to indicate the requests that the user has access to map. If you select Apply Rules at Merge Submission, then all users can map all requests; however, for a given request, only those with sufficient DSS privileges can submit it for merge.