16Accounts and Contacts

This chapter contains the following:

Overview of Accounts, Contacts, and Households

After you enable the capabilities of account data management, salespeople can use their Accounts pages to manage their sales accounts. The sales account information includes their customers, prospective customers, individual contacts, and households.

Here's what salespeople can do with the account data management capabilities:

  • Create and update accounts, prospective accounts, contacts, and households.

  • Maintain account data and view data in hierarchical fashion.

  • View household relationships.

  • Enrich customer data.

Use the customer data management capabilities to:

  • Prevent and identify duplicate data: Administrators identify duplicates during real time or in a preconfigured batch. They search and match real-time accounts and contacts to prevent the creation of duplicate data. Potential duplicate data is identified based on preconfigured matching configurations.

  • Verify and standardize addresses: Administrators perform real-time and batch address cleansing for account or contact address information. They verify and cleanse addresses within an import batch during import. Address validation is used in context of master geography data, address cleansing in context of Customer Data Management, address cleansing batch and address verification in real-time on account or contact pages.

  • Resolve duplicate data: Administrators merge and link duplicate records to create master records that are the single source of truth. They can de-duplicate within an import batch and within the entire database. Customer data management uses a data quality engine to consolidate high-quality account and contact data from multiple sources, manage duplicate data, enhance data with third-party content, standardize addresses, and monitor data quality. These data quality checks ensure cleansed, enriched, and complete customer information that can be trusted by the sales team.

For more details on implementation of customer data management, see the Implementing Customer Data Management for CX Sales and B2B Service guide. Also see the account topics in the Getting Started with Your Sales Implementation guide.

Data Management

Enable Display of Multiple Addresses

The edit pages for accounts, contacts, households, and partners automatically display a primary address region. However, you can change the view to display a table that lists multiple addresses.

How Address Details Display

Address details for accounts, contacts, households, and partners display on their respective Profile subtabs in edit mode.

The Primary Address region displays on the Profile subtab for an account record. This is the default view of address details. Use Application Composer to display multiple addresses instead of just one primary address region.

Considerations for Configuring Address Display Tables

Consider these points before you let the table display multiple addresses.

  • In Application Composer, you must ensure that only one of the address regions is exposed at a time in the Detail pages layout. For example, expose Primary Addresses or Multiple Addresses on the page, but not both at the same time.

  • The default type for Address is bill-to. You can configure the default address type using Default Address Type for Account and Default Address Type for Contacts profile options.

  • An account can have one or more sell-to addresses (or address type as sell-to). Account territory assignment is based on the primary address, and the primary address can be any type, such as sell-to or bill-to.

  • The default type when creating an account is Prospect. You can change the default type using the Account Type Default profile option. Similarly, you can use the Contact Type Default profile option to configure the default type when creating a contact.

Enable the Multiple Addresses Table

Use this procedure to enable the table that displays multiple addresses:

  1. Ensure you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the Objects navigation tree, expand Standard Objects and then expand the object whose pages you want to modify. For example, select the Account object.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected for either the account, contact, household, or partner object.

  6. In the Details Page Layouts region, edit the relevant layout.

    If none exists, then duplicate the standard layout using the duplicate layout icon, and edit the resulting layout.

  7. In the Details Layout page, click the Profile tab.

    In the Primary Address region and Multiple Address region, do one of the following:

    1. Click Hide to hide the region at runtime.

    2. Click Show to show the region at runtime.

      For example, to enable the display of multiple addresses, click Hide in the Primary Address region, and click Show in the Multiple Address region.

  8. Click Save and Close, then Done.

  9. Publish the sandbox according to your company's business practices.

Enable Address Usage Types for Accounts

You can assign usage types, such as bill to, sell to or ship to, to the account addresses. For that you must enable the Type field in the Creation layout of the Address page.

You can assign address usage types to the following account types:

  • Account

  • Contact

  • Household

The following address usage types can be assigned:

  • Bill to

  • Ship to

  • Sell to

Enable Address Usage Type on Creation Layout

Here are the steps to enable the address usage type on the Creation Layout:

  1. Ensure you're working in an active sandbox.

  2. Go to Application Composer > Objects > Standard Objects > Address > Pages.

  3. In the Application Pages tab, click the duplicate icon under the Creation Page Layouts section.

  4. In the Duplicate Layout window, give a name to the custom layout and click Save and Edit.

  5. On Creation Layout, click the edit icon beside Create and Edit Address.

  6. Under Configure Detail Form, select Type from Available Fields and move it to Selected Fields.

  7. Click Save and Close.

  8. Publish the sandbox. Salespeople can now see the Type field that shows the three address usage types in the Create Contact page. They can mark a contact address as Bill to, Ship to, or Sell to, based on the usage of the address.

Set a Default Address Usage Type

You can set one of the address usage types (Bill to, Sell to, and Ship to) as a default value for the Type field shown in the Create and Edit pages of Accounts, Contacts, and Households, using these profile options:

  • Default Address Type for Accounts (ZCA_ADDRESS_PURPOSE_DEFAULT)

  • Default Address Type for Contacts (ZCA_CONTACT_ADDRESS_PURPOSE_DEFAULT)

  • Default Address Type for Households (ZCA_HOUSEHOLD_ADDRESS_PURPOSE_DEFAULT)

Let's look at the steps to add a default address type for Accounts. The procedure is same for the other profile options.

  1. In the Setup and Maintenance work area, use the Manage Administrator Profile Values task:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. On the Manage Administrator Profile Values page, search for the profile option code, ZCA_ADDRESS_PURPOSE_DEFAULT.

  3. Choose a suitable profile value for Site: Bill to, Sell to, and Ship to. Save the changes.

  4. Sign in again for the changes to take effect.

Configure Address Regions

You can configure the primary address region or multiple address regions for accounts and contacts. You can add or remove custom fields or standard fields (such as Type, D-U-N-S Number, Site Name, Site Number, and so on) in the address region. Use the Address object in Application Composer to make the changes. Location specific fields (such as Address Line1, Address Line2, City, State, Postal Code, and so on) need to be managed using the Manage Address Formats task. These fields that are configured in the Manage Address Formats can't be managed using the Application Composer.

Set Up the Mapping Service for Contextual Addresses

A contextual address is marked with an orange triangle, the More icon. When users hover over the triangle, an icon appears, which they can click to display the address on a map.

Set Up Mapping Service

You can specify the mapping service to be used to display the map.

  1. In the Setup and Maintenance work area, go to the Manage Application Toolkit Administrator Profile Values task in the Application Extensions functional area.

  2. Search for the Mapping Service for Contextual Addresses (ATK_CONTEXT_ADDRESS_MAP_OPTION) profile option.

  3. In the Profile Values section, enter a full URL of a mapping service in the Profile Value field.

    Caution: By default, the Profile Value field is blank. Until you enter a valid value for this profile option, users continue to get an error when they try to open a map for any contextual address.

    Here are a few examples of mapping service URLs:

    • http://maps.google.com/maps?output=embed&q=

    • http://maps.live.com/default.aspx?where1=

    • http://bing.com/maps/?v=2&encType=1&where1=

    Tip: You can include parameters in the URL. For example, to avoid a locator box in Google Maps, you can add &iwloc=& to the URL. So, the mapping service URL you would enter in the Profile Value field is:

    http://maps.google.com/maps?iwloc=&&output=embed&q=

Display Account Currency for Opportunities on Account Overview Page

The opportunity summary box on the account overview tab displays the total amount of open opportunities in the corporate currency by default. However, for salespeople to view the amount in the currency where that account is located, you must perform a few setup steps. Salespeople can associate the currency when they create an account. They can also view and update the currency from the edit account profile tab.

Here are the high-level setup steps:

  1. Opt-in to the feature using the Change Feature Opt In link.

  2. Set the profile option Use Object Currency for Account to Yes. The default value is No.

  3. Add the currency field to the create and edit account pages using Application Composer.

Here's how to opt in and change the profile option.

  1. Sign in as a setup user.

  2. In the Setup and Maintenance area, go to the Sales offering.

  3. Click the Change Feature Opt In link in the Functional Areas row.

  4. On the Opt In: Sales page, click the pencil icon in the Features column in the Accounts and Contacts row.

  5. On the Edit Features: Accounts and Contacts page, select the Enable check box for Use Account Currency for Opportunity Summary on Account Overview Page feature.

  6. Click Done.

  7. Click Done on the Opt In: Sales page and return to the Setup: Sales page.

  8. To change the profile option, go the following:

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  9. Search for the profile option, Use Object Currency for Amount in the Profile Display Name field.

  10. Select Yes in the Profile Option Value field.

  11. Click Save and Close.

  12. Enable the currency field on the create account page and the account profile tab using Application Composer.

  13. Verify that the currency field is enabled on the create account and the edit account pages.

Enable the Currency Field

Enable the currency field on the create account page and the account profile tab using Application Composer.

  1. In an active sandbox, click Navigator > Configuration > Application Composer.

  2. In the Objects navigation tree, expand Standard Objects, Account, click the Pages node and ensure that the Application Pages tab is selected.

  3. Edit the creation and details layouts to open the Configure Detail Form page. Here's how you edit the layouts.

    1. On the Creation Page layouts region, duplicate the standard layout by highlighting the standard layout and clicking the duplicate icon.

    2. Enter a new layout name and click Save and Edit.

    3. On the Creation Layout page, click the Edit icon.

    4. On the Details Layout page, click the Profile subtab for the field to display on the profile page.

    5. In the Subtabs Region, click the Edit Summary Subtab icon.

  4. On the Configure Detail Form page, move Currency from the Available Fields window to the Selected Fields window.

  5. Click Save and Close.

  6. On the Details Layout page and the Creation Layout page, click Done.

Resolve Duplicate Records

This feature lets salespeople resolve duplicate records when creating accounts and contacts.

When duplicate accounts or contacts are found, they're displayed on the Notifications page. When salespeople create a record, they can either ignore the duplicates or select the correct record from the list.

Search Deduplication

When creating an account or a contact, duplicates are found based on one of these conditions:

  • Data quality management configuration for accounts and contacts

  • Exact name match profile options

Here's a list of profile options for account and contact deduplication.

Profile Option Code Profile Display Name Description

ZCM_ACC_DUP_NOTIFICATION

Show Duplicate Account Notification

Controls the display of the account duplicate notification page. Enabled by default.

ZCM_CON_DUP_NOTIFICATION

Show Duplicate Contact Notification

Controls the display of the contact duplicate notification page. Enabled by default.

ZCM_ACC_EXACT_NAME_MATCH

Exact Account Name Match

Controls the display of potential duplicate accounts based on an exact name match, when Oracle Enterprise Data Quality doesn't present duplicate accounts. Disabled by default.

ZCM_CON_EXACT_NAME_MATCH

Exact Contact Name Match

Controls the display of potential duplicate accounts based on an exact name match, when Oracle Enterprise Data Quality doesn't present duplicate contacts. Disabled by default.

Note: If data quality isn't configured in your application and you require an exact name only match, then you must enable the ZCM_ACC_EXACT_NAME_MATCH and ZCM_CON_EXACT_NAME_MATCH profile options.

How Account and Contact Deduplication Is Performed

Here's a list of the impact of different combinations of the deduplication profile options.

Show Duplicate Account or Contact Notification Exact Account or Contact Name Match Description

Disabled

Disabled

The application doesn't display potential duplicate accounts or contacts.

Enabled

Enabled

When creating an account or a contact, the application shows a list of potential duplicate accounts or contacts, based on the data quality configuration or an exact name match.

Disabled

Enabled

The duplicate notifications page is hidden.

Enabled

Disabled

This is the default setting.

When creating an account or a contact, the application shows a list of potential duplicate accounts or contacts based only on the data quality configuration.

Enable Source System Reference in Accounts

Source system reference is an identifier where the combination of source system and Source system reference is unique that lets you maintain a record of the source of the data in sales applications.

Reference System Overview

Sales applications may use data from disparate systems running on different databases. When such data is consolidated, the source system reference is maintained using a unique reference key for cross-referencing. You can query the source system using the reference key (unique ID) to get more information about an account from the source system.

Here is an image of the Edit Account: Reference Systems page from where you can add or view reference systems.

The image shows the view or add reference systems
for accounts.

In accounts, you can enable the source system reference by enabling a subtab that contains such cross-references if any.

Enable Source System References

You use the Reference Systems subtab to view or add source systems. This tab isn't enabled by default, which means that you must explicitly enable the Reference Systems subtab.

Here's how to enable the Reference Systems subtab:

  1. Ensure you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the Objects navigation tree, expand Standard Objects and then expand Account.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. On the Details Layout page, click the Reorder Subtabs icon.

  7. In the Configure Subtabs dialog box that appears, move the Reference Systems subtab to the Selected Subtabs box.

  8. Click OK, and then click Done.

  9. Publish the sandbox according to your company's business practices.

  10. Edit a record on the Accounts page and verify the reference systems subtab.

Configure Lists for Accounts and Assets

You can configure the lists of values that appear for accounts, contacts, households, and assets. Extensible lists of values let salespeople search and associate records using data that's relevant to their business needs. Salespeople can search using standard fields, view the fields in the search results, and then select relevant records.

Here's a list of the configuration options:

  • Create dynamic, role-based lists of value layouts

  • Enable hidden standard fields for searching within a list of values

  • Re-arrange fields in the search and result sections

  • Define default values for search fields

  • Mark certain fields as read-only or required

For more information on extending lists of values, see the Configuring Applications Using Application Composer guide.

Data Enrichment and Verification

Three Services to Enrich and Verify Your Data and Save Salespeople Time

Perhaps nothing is more important for your sales effort than having up-to-date and actionable information about your customers and contacts and minimizing the time salespeople spend entering data. Oracle provides three services that enrich your customer data, improve its accuracy, and eliminate data entry time. For account and contact information, you can choose between two services that provide you with information for millions of companies worldwide: Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) and Oracle DataFox. A third service, Oracle Address, Email, and Phone Verification, ensures that you have the correct postal addresses, that your emails don't bounce, and your calls go through.

Note: Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) is the new name for Data as a Service (DaaS).

Here's an overview of the three services:

Service Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) Oracle DataFox Oracle Address, Email, and Phone Verification

Purpose

Account and contact search, enrichment, and prospecting.

Account prospecting, enrichment, and alerts to important developments.

Address, phone, and email address verification.

What It Does

Instead of entering data themselves when they create accounts, salespeople can look up the organizations they sell to from Dun & Bradstreet Corporation, one of the premier sources of business information. The service provides access to more than 347 million account records and more than 135 million contact records worldwide. Included is information about more than 90 different company attributes, including sales volume, growth data, hiring trends, competitors, and so on.

Users can also filter the data by using over 60 company or contact attributes such as industry, revenue, company hierarchy, private or public indicator, contact title, contact department.

The service also provides information about account hierarchies, showing the linkages between a corporation's subsidiaries, branches, and divisions. You can also schedule account or contact enrichment on thousands of records at the same time.

Oracle licenses account and contact enrichment separately. You subscribe to the Oracle Account Enrichment Cloud Service and the Oracle Contact Enrichment Cloud Service.

Salespeople get the timely information they need to prospect and sell effectively from an intelligence platform that aggregates content from all over the web. They can filter several millions of companies by keyword, location, headcount, the tech stack the company uses (technographics) and other factors.

Salespeople get automatic alerts on important news in the companies they sell to. You can get alerts whenever a company gets approval for new patents, obtains new rounds of financing, or opens a new location, for example.

You can set up account scoring to prioritize accounts using the information you care about. The service provides account information only.

Salespeople can search and validate addresses in more than 248 countries using data from Loqate.

They can verify addresses when creating or editing an account: correct misspellings, add missing elements (such as the postal code), and standardize elements (for example, changing "Drv" to "Dr"). You can also schedule address verification on thousands of records at the same time.

The service automatically checks if phone numbers and email addresses exist and informs you if they're invalid. No more bounced emails or calls that don't go through.

How It Works

Salespeople start typing the account name, and the application suggests possible matches straight away. Selecting a match automatically fills in all the rest of the information.

Salespeople can add contacts to accounts by job role. Selecting the Enrich action for existing accounts gets the latest information.

The account and contact information continues to be updated automatically based on synchronization rules setup by your administrator.

You prospect for accounts in the Oracle DataFox UI and import them into Oracle CX Sales. You link up the accounts you want to keep updated, set an update frequency, and your account information continues to be updated automatically.

Salespeople start typing the street address in the search field and the application starts suggesting possible matches. Selecting one of the suggestions fills in the rest of the address fields.

You can also enable a Verify Address button that salespeople can use to verify addresses for a particular country. That's useful if you added nonstandard fields to the address or if salespeople don't always use the search field to look up an address.

You can also verify and update addresses in bulk.

The service informs salespeople if phone numbers and email addresses are invalid as soon as they enter them. They can also verify any existing ones to make sure they're still valid.

Setup

After you activate the service, and complete the simple setup described in this chapter in your sales application, salespeople can start looking up and enriching their data right away.

To get the most out of the application, however, you must add fields to the UI to expose the additional information you're getting. While most of the information maps onto fields you can expose using Application Composer, you must create some custom fields to map the rest.

After you connect with Oracle DataFox, find the company you want and link it up with your account in Oracle CX Sales using the account registry ID.

To get most out of the application, you must add fields and create a mashup in the sales UI to expose the additional information you're getting.

After you activate the service, and complete the simple setup described in this chapter in your sales application, salespeople can start looking up street addresses and verifying phone numbers and email addresses. You can expose the Verify Address button with a few extra steps.

Where to Get More Information

This guide includes the information you need to get started. You can get the full scoop in the Using Account and Contact Enrichment by Dun & Bradstreet guide.

See the Using DataFox for Sales and Marketing guide.

This guide includes the information you need to get started. You can get the full scoop in the Using Oracle Address, Email, and Phone Verification guide.

Where to Find Information on Implementing Enrichment and Verification Services

Information on how to set up the integrations between CX Sales and the three enrichment services is covered in multiple guides.

Information on How to Started with the Integrations

The Account Data Enrichment and Verification chapter in the Getting Started with Your Sales Implementation guide provides you with the basic information on how to enable the integrations. If you're an existing customer and you are adding services, then you can skip some of the initial steps.

Implementing the Oracle DataFox Integration

Integrating and using Oracle DataFox is covered in a separate Using DataFox guide.

Implementing Integration with Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B)

For details on setting up the service and using the native application UI is covered in the Using Account and Contact Enrichment by Dun & Bradstreet guide.

Integration with the Address, Email, and Phone Verification Service

For information on this service, especially on the REST API information, see the Using Oracle Address, Email, and Phone Verification guide.

If you have an existing integration with Oracle DataFox, you can enable salespeople to search for an account they want to create in DataFox and autopopulate all relevant account information automatically. To enable the Smart Data feature, select the Enable Smart Data for Account from DataFox option in the Manage DataFox Data Enrichment Integration page. In the future, this functionality will be made available to all customers, not just customers with existing DataFox integrations.

What You're Enabling

Your setup enables a search field (also referred to as Smart Data) in the Create Account page (highlighted in the screenshot).

Create Account page with the account search field
highlighted.

When salespeople create an account, they can use the field to search for the account in DataFox. Selecting an account copies over account information from DataFox and links the new sales account to the selected DataFox account. Linking the account makes it possible for DataFox to automatically update account information in the future and provide timely account news.

Note: You can use the Smart Data feature only with one service. So, if you're already using Smart Data with the Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B), enabling DataFox disables your existing integration.

Setup Steps for Customers with Existing DataFox Integrations

  1. In Setup and Maintenance, open the Manage DataFox Data Enrichment Integration task:

    • Offering: Sales

    • Functional Area: Integrations

    • Task: Manage DataFox Data Enrichment Integration

  2. In the Manage DataFox Data Enrichment Integration page, the integration information should be already populated for existing customers.

  3. If you want to enable salespeople to manually enrich individual accounts from the Edit Account page at will, then select the Enable Data Enrichment from DataFox option.

    If you leave the option unselected, the account data gets enriched by Oracle DataFox sync jobs when they run.

  4. To enable the search field on account create page, select the Enable Smart Data for Account from DataFox option.

  5. Click Save and Close.

Let your salespeople use DataFox's smart data when they're creating a new account in the sales application. The DataFox-powered smart data helps salespeople get quality information and near real-time data about the companies. This makes account creation faster and more accurate.

Here's how you enable smart data for accounts:

  1. In the Setup and Maintenance work area, use the Manage DataFox Data Enrichment Integration task:

    • Offering: Sales

    • Functional Area: Integrations

    • Task: Manage DataFox Enrichment Integration

  2. On the DataFox Data Enrichment Integration page, select Enable Smart Data for Account from DataFox.

  3. Enter the DataFox configuration. See the Enable Oracle DataFox Features in CX Sales topic for more details.

  4. Save and Close.

We recommend you select the Enable Data Enrichment from DataFox check box along with smart data so that your users get the best search results with the latest high-quality data related to the accounts.

Contact Preferences

Salespeople capture and modify preferences about whether accounts and contacts want to be contacted, such as selecting a Do not email or Do not call check box while editing a contact. As an administrator, you have several setup options for modifying the pages used to capture such information.

Overview of the Options

You can set up the application to be as simple as including a Do Not Contact check box on a page, or as complex as letting salespeople enter Do Contact and Do Not Contact preferences for multiple contact methods, such as phone, email, and so on. You can also display a Reason field next to the do not and do contact options.

You use a combination of Application Composer and Page Composer to set up contact preference UIs.

Privilege to Tag a Reason Code as Legal

Contact restriction information is captured as a Reason Code. Salespeople can create and edit contact preference information with any Reason Code that's not identified as Legal. To create and edit contact restriction information using a Reason Code that's tagged as Legal, add the HZ_LEGAL_CONTACT_PREFERENCES_PRIV privilege to the required role.

You can set up a reason code as legal by tagging the Reason Code lookup value. Tag the lookup type REASON_CODE with the value LEGAL using the Manage Trading Community Common Lookups task.

Set Up Contact Preferences

You can set up the Accounts and Contacts profile pages so that salespeople can capture contact preferences, such as do not call preferences.

Use Application Composer to expose the Manage All Phones and Manage All Emails dialog windows. Then use Page Composer to expose the OK to Call, Do Not Call, and (optional) Reason fields.

Set Up UI Elements to Capture Preferences

Enable Manage All Phones and Manage All Emails dialog windows so that salespeople can set contact preferences for accounts and contacts. You can enable them on the Create Contact and Edit Contact: Profile pages and on the Create Account page (Manage All Phones only) and Edit Account: Profile page.

Set up OK to Contact preference for a specific phone, email, or address of a contact. Identify if a contact has made a choice to be contacted, or has made no choice. The OK to Call and OK to Email options are mutually exclusive with the Do Not check box. Only one can be enabled for a given contact.

Here's a procedure that uses the Contacts pages as an example. Modify it for Accounts by navigating to the Accounts object in Application Composer and editing the Creation Page and Details page layouts.

Here's how to enable all phones and emails.

  1. Ensure that you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the navigation tree, expand Standard Objects, Contact, and then Pages.

  4. Ensure that the Application Pages tab is active.

  5. In the Creation Page Layouts section, in the Create Contact table, duplicate the Standard Layout. Name the new layout and edit it.

  6. In the Creation Layout page, click the Edit icon that appears next to Create Contact.

  7. Select and move fields from the Available Fields column to the Selected Fields column, depending on your requirements.

    This table shows the fields:

    Fields Description

    Do not contact

    Enables the Do not contact check box in the contact Profile page. Lets salespeople set a blanket do not contact preference at the contact level. This signifies that this contact must not be contacted at all.

    Do not call

    Enables the Do not call check box in the contact Profile page. Lets salespeople set the contact preference at the phone level for a contact.

    Do not email

    Enables the Do not email check box in the contact Profile page. Lets salespeople set the contact preference at the email level for a contact.

    Do not mail

    Enables the Do not mail check box in the contact Profile page. Lets salespeople set the contact preference at the physical mailing address level for a contact.

    All phones

    Enables the All phones icon in the Create or Edit Contact page, and enables the Manage All Phones dialog window that appears when users click this icon.

    All emails

    Enables the All emails icon in the Create or Edit Contact page, and enables the Manage All Emails dialog window that appears when users click this icon.

  8. Click Save and Close.

  9. Click Done.

    Note: If you want the contact preference fields to appear in the Create Contact page, then you must perform steps 1 to 9. If you want the fields to appear in the Edit Contact page, then you must also perform steps 10 to 15.
  10. In the Details Page Layouts section, in the Edit Contact table, copy the Standard Layout. Name the new layout and edit it.

  11. In the Details Layout page, click the icon that resembles the Profile icon.

  12. Click the Edit icon that appears next to Edit Subtab: Summary.

  13. Select and move fields from the Available Fields column to the Selected Fields column, depending on your requirements.

  14. Click Save and Close.

  15. Click Done.

  16. Publish the sandbox according to your company's business practices.

Set Up UI Elements to Capture Preferences for Different Phones and Email Addresses

You can enable UI elements that let salespeople capture preferences for contacts and accounts at the phone and email level. You can also enable a Reason field for the preference.

Note: You must first enable the All phones and All emails fields in Application Composer (see the previous procedure). Then you enable the additional UI elements using Page Composer.

This procedure uses the phone contact method as an example. Modify it for the email contact preference UI elements:

  1. Ensure you're working in an active sandbox the supports Page Composer.

  2. Navigate to Sales > Contacts.

  3. Activate Page Composer: From the drop-down list under your user name in the global header, select Edit Pages.

    When Page Composer is active, the phrase Editing: User Interface displays at the top of the page.

  4. In the Contacts landing page, search for and select a contact.

  5. Click the name of the contact to open the edit page. In the Edit Contact page, click the Profile icon.

  6. In the Profile page for the contact, click the edit icon for All phones.

  7. In the Editing: User Interface dialog window, click the Select tab at the top of the page.

  8. In the Manage All Phones dialog window, click any one of the columns, such as Primary, Type, or Number columns and select the Edit Parent Component option in the dialog box.

  9. In the Component Properties dialog window, click the Children tab.

  10. Select the Do Not Call or OK to Call options, and, optionally, the Reason.

  11. Click Apply and then OK. Notice that the Do Not Call, OK to Call, and Reason columns (if selected) are now visible in the Manage All Phones dialog window.

  12. In the Editing: User Interface window, click the Add Content tab.

  13. In the Manage All Phones dialog window, click OK.

  14. Click the edit icon next to the All phones field to verify your changes.

  15. Click Close to close Page Composer.

  16. Publish the sandbox according to your company's business practices.

Personally Identifiable Information

Manage Personally Identifiable Information

Any piece of information that can potentially be used to uniquely identify, contact, or locate a single person is called personally identifiable information (PII). Administrators use PII to access information such as social security numbers, addresses, bank account numbers, phone numbers, and so on. PII is used to distinguish one person from another. The information includes both sensitive and nonsensitive data. PII is protected to prevent unauthorized use of personal information.

As a sales administrator, you can manage PII information. You can add or update PII data for your contacts. You must expose PII attributes from Application Composer or Page Composer in an active sandbox. For more information about how to enable the PII attributes, see topic, Manage Personally Identifiable Information in the Implementing Customer Data Management for CX Sales and B2B Service guide.

Data Removal

Delete Accounts, Contacts, and Households

By default sales administrators can delete accounts, contacts, and households. Other setup or administrative users, as needed, can be set up to delete these entities.

Here's a description of the privileges you must have to delete accounts, contacts, and households:

Object Privilege Additional Information

Account

Delete Sales Party

You can't delete an account if it's a partner or competitor account, or if the account is the topmost tier in the account hierarchy.

Contact

Delete Sales Party Contact

You can delete standalone contacts. You must also have full access to all of the accounts associated to the contact. When you delete a contact, you remove the entire person record of the contact, including profile data, account usages, household memberships, and relationships to other accounts.

Household

Delete Sales Party Duty

When you delete a household, you break the association between the household and all of its household members. However, you can still view the members as individual accounts or contacts.

Note: When you delete an account or a contact, all the child entities may not become inactive. Run the Delete Child Entities of Inactive Party Records scheduled process to deactivate them.

When you delete a party record which can be a sales account or a sales contact in your application, it becomes an inactive record. Inactive records may get accumulated in your application and you may want to purge them. Purging inactive records helps you free space and comply with data protection regulations. Note that only inactive records that are available in the sales context can be purged. For example, an inactive Partner record can't be purged. Also, along with the purge of the inactive accounts or contacts, references of these purged records, such as identifier or name, are also removed in other applications like opportunities, leads, campaigns, territories, assets, deals, quotes, activities (tasks and appointments), notes, forecasts, business plans, and contracts. For these flows, purged accounts and contacts don't appear on application pages, web service responses, and BI reports.

How You Enable Purge of Inactive Records

You can use the following profile options to help you enable and manage purging of inactive records:

  • ORA_HZ_ENABLE_PURGE: This profile option enables purging of inactive records. By default, this profile option is enabled and is set to No.

  • ORA_HZ_PURGE_MIN_AGE: This profile option specifies the number of days after which inactive records can be purged. By default, the value of this profile option is 30 days.

You can enable these profile options by clicking the Setup and Maintenance area and going to the following:

  • Offering: Sales

  • Functional Area: Sales Foundation

  • Task: Manage Administrator Profile Values

You must specify filter criteria to select the inactive records that you want to purge. The value of the profile ORA_HZ_PURGE_MIN_AGE is displayed as the Minimum Age on the Manage Party Purge Activities page and the default value of the Age By field on the Create Purge Filter page. Modify the value of the profile option ORA_HZ_PURGE_MIN_AGE to change the default value of the Age By field.

Create and Edit Filters and Purge

You must create a filter criterion to purge records. The records that are to be purged are selected based upon the filter criteria. So, you can't skip creating filters and proceed to purging records. You can either immediately purge the selected records or schedule the Purge Inactive Party Records scheduled process to purge inactive records later. You must create a filter criterion to purge records. The records that are to be purged are selected based upon the filter criteria. So, you can't skip creating filters and proceed to purging records.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Party Purge Activities

    Note: The Purge Enabled field on Manage Party Purge Activities page indicates whether inactive records can be purged, and the Minimum Age field indicates the minimum number of days after which inactive records can be purged. Use the profile options discussed earlier in the topic to change these profile option values, if needed.
  2. Click Actions > Create to create a purge filter.

    You can click Actions > Edit to edit the existing filter criteria or click Actions > Remove to remove an existing filter.

  3. Specify the purge filter criteria or change the existing filter criteria as required.

    Note: You can't specify a number less than the number specified in the Age By field. If you want to reduce this Age By value, change the value of the profile option ORA_HZ_PURGE_MIN_AGE to a smaller number.
  4. Select the Enabled option to make the filter criterion available for filtering and purging records. If you don't select this option and continue to save the filter, the filter criteria is saved but isn't available to filter and purge records.

  5. Click Save and Close.

    The Final Result section displays the first 500 records that match your filter criteria.

  6. Click Purge to immediately purge all the records that currently match your filter criteria.

    Else, click Save and Close to save the filter criteria and purge the records in the next cycle of running the Purge Inactive Party Records scheduled process.

    Note: If you want to automatically purge records in the next cycle of running the scheduled process, the purged records may not be the same records that appeared in the preview section of the Manage Party Purge Activities page. The records purged are the ones that match the filter criteria when the scheduled process is run.

Additional Configurations

Make the Account Field Required for Contacts

You may want to make the Account field required when salespeople create a contact, so that you can be sure an account always gets associated with a contact. By default, the Account field isn't required when creating a contact. Use Application Composer to set the field as required.

Here's how to set a field as required:

  1. Ensure you're working in an active sandbox.

  2. Navigate to Configuration > Application Composer.

  3. In the navigation tree, expand Standard Objects, and then expand Contact.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. In the Create Contact layouts region, duplicate the standard layout and edit the resulting layout.

  7. In the Creation Layout page, click the Account link.

  8. In the Edit UI Properties: Account dialog box, Layout Properties section, set the Required field to Yes.

  9. Click Save and Close.

  10. Click Done on the Creation Layout page.

  11. Publish the sandbox according to your company's business practices.

Set Up Required Address Option for Accounts and Contacts

Administrators can set an address as required or optional depending on the type of account or contact. You can specify that an address is required and determine how the address appears on the UI.

Manage Profile Values

Use the Manage Administrator Profile Values task to specify that an address is required while creating an account. Profile options let you enable or disable address options for accounts and contacts. Use these profile options to specify that an address is required while creating an account.

Profile Option Code Profile User Name Description

ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED

Account Address Required

Specify whether an address is required while creating an account.

ZCA_CONTACT_ADDRESS_REQUIRED_ENABLED

Contact Address Required

Specify whether an address is required while creating a contact.

This table lists the profile values and which types of accounts require the address to be entered. By default, the profile option setting is Required for customer.

Profile Value Description Required for Account Type

Yes

The address is required.

All types of accounts.

No

The address isn't required.

The address is optional, regardless of the account type.

Required for customer

The address is required only for the account type that's set to this profile value.

The address is required only for customers.

To make the address required while creating an account:

  1. In the Setup and Maintenance area, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. Click the Manage Administrator Profile Values link.

    The Manage Administrator Profile Values page appears.

  3. Enter the code in the Code field, and click Search.

    The application displays the profile option information.

  4. In the Profile Values section, select Yes in the Profile Value field.

  5. Click Save and Close.

Manage Address Formats

Use the Manage Address Format task to set up address attributes. The address format lets you manage the appearance of the address for accounts and contacts. For example, you can change the case of letters in an address, or mark a specific address attribute as required.

To specify which fields in an address are required:

  1. In the Setup and Maintenance area, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Address Formats

  2. Click the Manage Address Formats link.

    The Manage Address Formats page appears.

  3. Select a country from the drop-down list.

  4. In the Format Variation Layout area, select the fields that you want to set as required in the Required column.

  5. Click Done.

Groovy Support for Numbering Management

You can automatically generate the site ID of an address while creating a contact or an account using a groovy script. Before you can use the groovy script, you must verify that the value for HZ_GENERATE_PARTY_SITE_NUMBER profile option is set to Auto numbering, update allowed (AUTONUM_UPDATE).

Enable the Photo Field for a Contact

You can enable users to upload and show photos on a contact's profile.

Here's how to display the Photo field on the contacts pages:

  1. Ensure you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the Objects navigation tree, expand Standard Objects and then expand Contact.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. In the Details Page Layouts region, duplicate the standard layout by highlighting the standard layout and clicking the duplicate icon.

  7. Enter a new layout name and click Save and Edit.

    The Details Layout page appears.

  8. Click Subtab Profile for the field to display on the Profile page.

  9. In the Subtabs Region, click the Edit Summary Subtab icon.

    The Configure Detail Form page appears.

  10. Move Photo from the Available Fields window to the Selected Fields window.

  11. Click Save and Close.

  12. From the Details Layout page, click Done.

  13. Make sure that the layout status for your layout is set to Active, and that it's associated to your application user role.

  14. Test the changes as follows:

    • Navigate to Sales > Contacts > select a contact > Edit Contact page > Profile subtab > Photo field > upload photo.

    • On the Contacts landing page, in the card view, you can see the photo for the contact you selected.

  15. Publish the sandbox according to your company's business practices

Manage Contact Views

Set the list view as the default view for the Contacts landing page. By default, the contact view is set to card view. Salespeople can use either the card view or list view.

Caution: If you use both card view and list view, then a blank list of contacts appears.

To enable the list view:

  1. Ensure you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the navigation tree, expand Standard Objects, and then expand the Contact object.

  4. Within the object you're modifying, click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. The Landing Page Layouts region, duplicate the standard landing page layout.

  7. Edit the new layout. In edit mode of the Landing Page Layout page, click the edit icon on the Default Contact View.

  8. Select List View in the Select Default View dialog box.

  9. Click OK.

  10. Click Done on the Landing Page Layout page.

  11. Publish the sandbox according to your company's business practices.

After you have enabled the functionality, salespeople can view the relationships that exist among related contacts in a household. Salespeople use the Relationships subtab within the Accounts pages to view the hierarchy of the contacts related to households.

Enable Relationship Views

You can show or hide panels or regions in the Households pages.

Here's how to show or hide the views:

  1. Ensure you're working in an active sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. In the Objects navigation tree, expand Standard Objects and then expand Household.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. In the Details Page Layouts region, edit the relevant layout.

    If none exists for editing, then duplicate the standard layout using the duplicate layout icon, and edit the resulting layout.

  7. Edit the duplicate layout.

  8. Select the Relationships subtab, in the Details Layout area.

  9. Show or hide the following:

    • Relationship Diagram Panel:

      This panel shows the graphical representation of the relationships in a household.

    • Household Contacts:

      This panel provides a list view of the contacts in a tabular format.

    • Other Relationships:

      Any other relationship appears in this section.

  10. Click Done.

  11. Publish the sandbox according to your company's business practices.

Configure Event Tracking

You can track changes to your accounts, contacts, or household data by configuring the following profile options:

  • HZ_INVOKE_OBJ_WF_ON_TRACKING: Enable this profile option to indicate that there are changes to parent records. That is, whenever a child is updated, the parent record is marked as updated. For example, if the email address or phone number of a contact was updated, the contact is marked as updated which in turn indicates that the contact requires synchronization.

  • HZ_ENABLE_EVENT_TRACKING: Use this profile option to enable event tracking of records. This profile option facilitates tracking of changes to records and raises an event whenever there is a change.

Note: If you don't plan to integrate your application with data quality, extensibility, object workflow, or Oracle Eloqua, you can turn off the HZ_INVOKE_OBJ_WF_ON_TRACKING profile option. This helps to avoid locking issues. But you must carefully review the implications of turning off this profile option in your application.

You can enable these profile options by clicking the Setup and Maintenance area and going to the following:

  • Offering: Sales

  • Functional Area: Sales Foundation

  • Task: Manage Administrator Profile Values

Enable Contracts for Accounts, Contacts, and Households

You can enable the Contracts tab within the Accounts pages using Application Composer. From the Contracts tab, salespeople can view and download contracts associated with accounts.

Groovy Support for Team Member Notifications

You can add or delete team members for accounts, contacts, and households using the respective UI pages or REST APIs. When you add or delete team members, notifications are prompted for the parent record. These notifications enable you to define Groovy prompts on the parent object.

For more information on Groovy scripting, see Oracle Applications Cloud Groovy Scripting Reference guide, available on Oracle Help Center. For more information about REST APIs, see the REST API for CX Sales and B2B Service guide.

Groovy Support for Email Address Format Validation

You can add email addresses for accounts or contacts using the respective UI pages or REST APIs. While entering these email addresses the format of the email address should be validated. You can use groovy scripts to specify the rules to validate email address formats.

For more information on Groovy scripting, see Oracle Applications Cloud Groovy Scripting Reference guide, available on Oracle Help Center.

The following code is a sample for validating email addresses:

def regex = /(?i)^([\w-]+(?:\.[\w-]+)*)@((?:[\w-]+\.)*\w[\w-]{0,66})\.([a-z]{2,6}(?:\.[a-z]{2})?)$/ 
def email = getAttribute('ListEmailAddress'); 
def EmailCollection = Email ;
EmailCollection.reset();

if (email == null)
{
while(EmailCollection.hasNext()){
def emailRec = EmailCollection.next() 
email = emailRec.EmailAddress
if (!(email =~ regex)){ 
throw new oracle.jbo.ValidationException("Populate email in the appropriate format (example someone@oracle.com)") 
}  
} 
}
else
if (!(email =~ regex)){ 
throw new oracle.jbo.ValidationException("Populate email in the appropriate format (example someone@oracle.com)") 
}

Trading Community Model Profile Options

Trading community profile options configure various features such as geographies, Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B), address formats, and so on. The following table lists trading community profile options, descriptions, default values, and the impact these profile options have on different parts of the application.

To view the details of these profile options:

  1. Click Navigator > My Enterprise > Setup and Maintenance work area.

  2. Click the Tasks menu and click Search. Search for Manage Administrative Profile Values task and open it.

  3. Search using the profile option code.

To change the default values of these profile options:

  1. Click Navigator > My Enterprise > Setup and Maintenance work area.

  2. Click the Tasks menu and click Search. Search for Manage Administrative Profile Values task and open it.

  3. Search using the profile option code.

  4. Change the profile value.

Profile Option Code Profile Option Name Default Value Description Impact

HZ_UPDATE_STD_ADDRESS

Update Standardized Addresses Enabled

No

Enable to allow the update addresses that are already standardized using postal information.

Application UI and REST

HZ_POST_IMPORT_GNR_INVOKE

Address Validation After Import

Y

Runs the Geography Name Referencing process after import.

File-based Import (used in high volume import) and Import Management

HZ_ORGANIZATION_PROFILE_INDEX_THRESHOLD

Organization Profile Index Threshold

10

Specify the number of profile history records above which organization profile history information will be automatically denormalized into a secondary table for improved performance.

REST

HZ_INVOKE_OBJ_WF_ON_TRACKING

Child Entity Rollup Enabled

Yes

Enable rollup of the child entity changes to the root object during event tracking. This invokes the root object workflow whenever the child entities change.

Scheduled Process, Application UI, REST

HZ_GENERATE_PARTY_NUMBER

Party Number Generation

Auto numbering, update allowed

Select how a party number will be generated, and if you can update the number when creating or editing a person or organization party.

Application UI, REST

HZ_ENABLE_EVENT_TRACKING

Composite Event Tracking Enabled

Yes

Enable composite event tracking for customer and contact entities. This tracks changes to the entities, and raises an event whenever there is a change to the entities.

Scheduled Process, Application UI, and REST

HZ_AUTO_SITE_NUMBERING

Site Use Identifier Generation

Auto numbering, update not allowed

Select how the site use identifier will be generated, and if you can update it when creating or editing an account site use.

Application UI and REST

HZ_AUTO_LOG_INTERACTIONS

Call Interaction Logging Enabled

No

Enable adding phone calls to the interactions log when the call action is used.

Application UI and REST

ORA_HZ_RES_ENABLE_MGR_END_UNCOND

Enable End Dating Resource Manager Unconditionally

N

Allows organization membership end date for resource with managerial role without any validation. You need not move out all reports before moving manager out. Set the value to Y to enable this option.

Application UI, REST, and Import Management (only Resource object)

ORA_HZ_PURGE_MIN_AGE

Minimum Threshold Value for Purge of Inactive Data

30

Specify the minimum number of days after which inactive records are to be purged.

Application UI

ORA_HZ_INCLUDE_REGIONAL_COUNTRY

Regional Country in Address Formats Included

No

Enable address format functions to include regional country. You must set the value to yes to include regional country.

Application UI

ORA_HZ_GEO_HIERARCHY_LIMIT

100000

Specify the maximum number of nodes that each parent node can handle for any geography element.

Application UI and Import Management (only for geography object)

ORA_HZ_ENABLE_PURGE

Purging of Inactive Data Enabled

N

Enables the purging of data that are in inactive state using the Manage Party Purge Activities task. You must specify filter criteria to purge inactive data using Manage Party Purge Activities task.

Application UI

ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER

Enable Current Active Worker Sync For MPLCRI Job

No

Enable current active worker sync for Maintain Party and Location Current Record Information batch job. If set to N, then current active workers won't get synced to person party.

Note: This profile option is associated with the Maintain Party and Location Current Record scheduled process. This profile option ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER must be set to Y and the HRC_DISABLE_HCM_EVENTS_PROCESSING profile option must be set to Yes to sync active workers. For more information topic, see the Maintain Party and Location Current Record Information topic in the Understanding Scheduled Processing Guide.

Scheduled Process

ORA_HZ_ENABLE_DAAS_LOQATE

DaaS GBG | Loqate Data Import Enabled

Yes

Enable the import of DaaS GBG | Loqate geography information.

Scheduled Process, Application UI, and Import Management

ORA_HZ_DAAS_GEO_ENDPOINT

DaaS Geography Server Endpoint Information

https://geo.daas.us-phoenix-1.ocs.oraclecloud.com

Specify the endpoint information, such as the host name and the port number, of the DaaS geography server.

Application UI and REST

HZ_TIMEZONE_POPULATION_ENABLED

Time Zone Population Enabled

No

Enable update of contact records with time zone details from the Populate Location Latitude and Longitude Information scheduled process.

Scheduled Process

HZ_SHARE_LOCATIONS

Location Sharing Mode

Share among all parties

Select if location can be shared among different persons and organizations.

File-based Import

Note: This profile option isn't applicable in Import Management.

HZ_RS_DEF_START_DATE

Resource Start Date Default

Current date

Select if the default start date will be the date when the resource is created, or the employment start date of the resource.

Application UI

Note: This profile option isn't applicable in Import Management and resource user REST.

HZ_RESOURCE_ALLOW_CUSTOMIZATION

Application Composer for Resource Desktop Pages Enabled

No

Enable access to Oracle CX Sales Resource desktop pages in the Application Composer.

Application UI

HZ_LANG_FOR_COUNTRY_DISPLAY

Language for Country Display

Specify the default language used to translate the country name for international addresses. This is typically the language of the country where an item is mailed from.

Application UI and REST

HZ_GEOCODING_BATCH_SIZE

Geocoding Subprocess Batch Size

1000

Specify the maximum number of locations that each batch subprocess can handle for geocoding.

Scheduled Process

HZ_GENERATE_PARTY_SITE_NUMBER

Party Site Number Generation

Auto numbering, update not allowed

Select how a party site number will be generated, and if you can update the site number when creating or editing a party site address.

Application UI, and REST

HZ_GENERATE_CUSTOMER_NUMBER

Customer Account Number Generation

Auto numbering, update not allowed

Select how a customer account number will be generated, and if you can update the number when creating or editing a customer account.

Application UI, and REST

HZ_GENERATE_CONTACT_NUMBER

Contact Number Generation

Auto numbering, update not allowed

Select how the contact number will be generated, and if you can update the number when creating or editing a contact.

Application UI, and REST

HZ_ENABLE_VO_SECURITY

Enable VO-Based Security

No

Enable VO-based security and override the default EO based security for all objects that use the secured PartyEO.

Application UI and REST

HZ_ENABLE_MULTIPLE_BU_CRM

Multiple Business Units Enabled

Yes

Enable the multiple business units feature for Oracle Fusion Customer Relationship Management.

Application UI

HZ_ENABLE_ENTITY_EVENTS

Entity Level Events Enabled

Yes

Enable entity level events for account, contact, and household entities.

Scheduled Process, Application UI, and REST

HZ_ENABLE_CLICK_TO_DIAL

Click to Dial Enabled

Yes

Enable automated dialing by clicking on a phone number.

Application UI

HZ_ENABLE_BUSI_VALID

Business Key Validation Enabled

No

Enable the business key validation rule to check for duplicate contact points, such as mobile, URL, and Email.

REST

HZ_DEFAULT_NAME_STYLE

Name Style Default

Concatenated Name

Specify a default style for name formatting.

Scheduled Process, Application UI, and REST

HZ_DEFAULT_BU_CRM

Customer Relationship Management Business Unit Default

Vision Operations

Specify the default business unit for Oracle Fusion Customer Relationship Management.

REST

HZ_DEFAULT_ADDR_STYLE

Address Style Default

Postal Address

Specify a default style for address formatting.

Application UI and REST

HZ_AUTOMATE_RESOURCE_CREATION

Automated Resource Creation Enabled

No

Enable automatic creation of resource from employee creation process without user intervention.

Application UI

HZ_ALLOW_MULTIPLE_SELLTO

Multiple Sell-to Addresses Enabled

No

Enable multiple sell-to address creation for a party, using the Data Import program. This profile option should not be used by customers.

Application UI, and REST

HZ_ADDRESS_DISABLE_ALT_NAMES

Hide Alternate Address Names

No

Hide alternate names in the Address list of values. This option, when enabled, displays only the primary geography names for the address.

Application UI

HZ_GNR_NUM_OF_WORKERS

Number of workers for a given Geography Name Referencing request

1

Determines the number of sub-processes for Validate Geographies of Addresses Against Master Geographies scheduled process.

Scheduled Process

ZCA_SA_AUTO_ASSIGN_ON_UPDATE

Sales Account Automatic Assignment on Update Enabled

No

Enable automatic territory based assignment processing after a sales account is updated.

Scheduled Process, Application UI, and REST

HZ_GNR_COMMIT_SIZE

Batch Size for committing records in Geography Name Referencing process

N/A

The Batch Size for committing records in Geography Name Referencing process

Application UI, Scheduled Process, File-based Import, and Import Management.

ORA_HZ_IMPORT_MULTI_ADDRESS_TYPE

Import Processing for Multiple Address Types Enabled

Yes

Enable the processing of multiple address types for Account, Contact, Address, Organization, and Person objects.

Import Management

ORA_HZ_RES_ENABLE_SKILLS

Skills Section in Resource Detail Page Enabled

No

Enable the skills section in the Resource Detail page of the Resource Directory and Manage Resources task. The valid values are YES and NO, and the default value is NO.

Application UI

Integration with Financials

Overview of Oracle Financials Cloud

Oracle Financials Cloud delivers a complete solution that includes:

  • General Ledger

  • Intercompany Accounting

  • Payables

  • Receivables

  • Payments

  • Cash Management

  • Tax

  • Expenses

  • Assets

Use these applications with business intelligence, compliance reporting, and mobile data access for:

  • Financial accounting

  • Transaction processing

  • Payment delivery

  • Cash reconciliation

  • Employee expense processing

  • Asset management

The figure shows the activities that Oracle Financials
Cloud facilitate, including financial accounting, asset management,
employee expense processing, cash reconciliation, payment delivery,
and transaction processing.

Access data through pages that contain:

  • Navigation tools in the global area of the Home page.

    The screenshot shows the navigation icon bar. The
navigation bar includes the navigator menu, logo, home, global search,
favorites and recent items, watchlist, notifications, and settings
and actions menu icons.
  • Icons to navigate to pages.

    The screenshot shows the Home page with a group
of icons to use to go to your tasks. The Home page also consists of
the global area, a row of dots taking you to infolet pages, and a
home panel where you can collaborate with your colleagues.
  • Infolets in an Infolets page or work area.

    The screenshot is an example of the General Accounting
infolets that display key information on areas, such as open subledgers,
revenues, AP reconciliation, AR reconciliation, and journals.The screenshot shows the Invoices work area that
displays a row of infotiles and a table of related details.
  • Panel tabs for tasks, searching, and analytics accessed by icons on the page.

    The screenshot shows the tasks in the Invoices
work area accessed by the Tasks icon. These tasks are categorized
by invoices, accounting, assets, and Payables periods.
  • Transaction details in a work area.

    The screenshot shows transactions in the Accounts
Receivables work area. Infotiles appear with key information, along
with the related details in a table.
  • Transaction details as a separate page.

    The screenshot shows the Create Journal transaction
page. Relevant fields are included in the Journal Batch, Journal,
and Journal Lines sections.

From the application pages, access:

  • Embedded analytics, which enables you to complete a transaction or analyze data.

  • Interactive infolets and work areas to view:

    • Information summaries for a high-level overview.

    • Information monitoring and drill-down capability.

    • Transaction information that's central to one or more business processes.

    • Business intelligence content that's complementary to one or more business processes.

  • Real-time reporting for:

    • Viewing reports and analytics for each individual work area.

    • Exploring predefined analyses.

    • Creating and editing analyses from the Reports and Analytics panel tab or work area.

    • Accessing the Oracle Business Intelligence (BI) Enterprise Edition through the Reports and Analytics panel tab. See the new objects and changes to existing objects that you made in Oracle BI Enterprise Edition, which are then available from Oracle Financials Cloud.

    • Viewing and running financial reports from the Financial Reporting Center, which is a single point of entry for general ledger financial reporting functions. The Financial Reporting Center includes:

      • Tools to create and format financial reports, including Financial Reporting Studio and Workspace.

      • Live and interactive financial reports with multiple output options, including HTML, PDF, Excel, or Excel in Query Ready mode using Smart View Enabled formats.

      • Drill downs to underlying journals and subledger transactions with the Account Inspector.

      • Multiple reporting methods for ad hoc analysis, efficient monitoring, and tracking of key account balances in real time with the Account Monitor.

Synchronize Financials Accounts

After users create accounts and contacts in Oracle Financials, use the scheduled process, Synchronize Financials Cloud Accounts and Contacts, to synchronize the data into the sales application.

Here's how the process works:

  1. The scheduled process checks for all party records (organization and person) that have the Customer usage in Oracle Financials and that don't have a record in the Sales Accounts table (ZCA_SALES_ACCOUNTS) in the sales application.

  2. For the identified records, the process inserts new records in the Sales Accounts table, and in the Party Usages table (HZ_PARTY_USG_ASSIGNMENTS), for Organization, Sales Account, and Person.

Keep these points in mind as well:

  • The process supports the addresses associated with customer accounts and contacts, and supports address purposes, such as "bill-to".

  • After the billing process finishes, the application creates billing accounts and contacts in Oracle Financials.

    Note: Enable the Billing Accounts sub-tab from Application Composer to let your users see the customer account number and the description.
  • If you need your data to refresh regularly, it's a good idea to set up a schedule for the process using the advanced option in the scheduled processes window.

To synchronize accounts and contacts data from Oracle Financials to your sales application:

  1. Click Navigator > Tools > Scheduled Processes.

  2. Click Actions > Schedule New Process and search for the Synchronize Financials Accounts and Contacts with CX Sales process.

  3. Verify that the data is synchronized in your sales application: Sign in to the Accounts pages as a user who has access to the sales pages, such as the sales administrator or a sales representative, and view the new data.

Integration with Third Parties

Overview of Third-Party Integrations for Accounts

You can use the Account, Contact, and Household interfaces to gain a comprehensive view of your customer information. This functionality utilizes sales data, as well as relevant third-party content.

Third-Party Integrations for Sales Customers

OneSource and Siebel CRM are two third-party integrations that you can configure in sales applications. This topic explains how you map third-party customer data to sales customers.

Map OneSource Data Sales Application

You access OneSource data directly from the OneSource node on Sales Account, Contact, and Household information trees.

The sales application searches for OneSource company data in the following order:

  1. Search based on the mappings defined in the HZ_ORIG_SYS_REFERENCES table, where orig_system is ONESOURCE.

  2. Search based on the sales customer stock symbol, checked if no mapping is found in HZ_ORG_SYS_REFERENCES.

  3. Search based on the sales customer name, checked if no mapping is found by the stock symbol lookup. If multiple OneSource companies match the sales customer name, you can choose from the list of matching OneSource companies.

Mapping Siebel CRM Service Data to Sales Application

You access mappings for Siebel CRM accounts, contacts, and groups to sales customers in the HZ_ORIG_SYS_REFERENCES table, where orig_system is SIEBEL.

Note: The sales application doesn't include licenses for OneSource and Siebel CRM. You must acquire third-party application licenses separately. If you want to enable OneSource and you have a web proxy for external HTTP(S) traffic, you must select Enable Web Proxy on the Web Proxy Configuration screen and specify your web proxy configuration.

FAQs for Accounts and Contacts

Frequently Asked Questions (FAQs) for Accounts and Contacts

This section contains some frequently asked questions (FAQs) when setting up and maintaining accounts and contacts. Scroll or search to find answers to common questions.

How can I set Customer as the default account type?

You can set the default account type to Customer on the create account page by changing a profile option.

To change the profile option:

  1. In the Setup and Maintenance area, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. Enter ZCA_ENABLE_SELLTO_ADDR_CHECKBOX in the Profile Option Code field.

  3. Click Search.

  4. In the Profile Option: Profile Values region, set the Profile Value to Yes.

    You have now set the default value of the account type to Customer.

    Tip: To hide the Type field, use Application Composer. For more information about how to hide or show fields in application pages, see the Configuring Applications Using Application Composer guide.

What happens when I delete an account?

When you delete an account, the entire record is removed from the sales application and can't be restored.

In general, when you delete an account:

  • The account party status becomes inactive in the database.

  • The deleted account doesn't appear in the accounts list, account search, account list of values, account data quality match, segmentation, and recent items.

  • The deleted account's profile and children, such as attachments and notes, can no longer be viewed.

  • The account's contact relationships, if any, are deleted. The contact can still be viewed, but deleted contact relationships aren't shown in the contact.

  • Deleting an account doesn't delete account-related objects, such as opportunities, leads and tasks. You can still view related objects and the account name on these objects, but you can no longer access the deleted account's details.

What happens when I delete a contact?

When you delete a contact, the record is removed and can't be restored.

In general, when you delete a contact:

  • The person record of the contact is removed , including all profile data, customer usages, and group memberships.

  • Relationships with associated customers or sales accounts are deleted.

  • Contact points or other child objects specific to the customer-contact relationship aren't shown.

  • A deleted contact isn't shown or available in any other contact or customer lists. A deleted contact isn't visible to all contact types (standalone, single, or multiple) including a customer-contact, a consumer or prospect, or in cases where the contact is both a customer contact and a consumer or prospect.

  • Even if you have the functional privilege to delete a contact, you can't delete contacts unless you have full or edit access to at least one of the accounts associated with the contact.

By default sales administrators can delete households.

In general, when you delete a household:

  • Any associations with members of the household are severed, but users can still see members as individual organizations or contacts.

  • Users can't see contact points for the household.

  • Users can't see deleted households in any account or contact lists.