7Common Components

This chapter contains the following:

Several common components provide core functionality for the applications. Common components provide functionality that spans multiple applications, such as the accounting calendar or application messages. This chapter describes many of the common components. Where appropriate, other common components have their own individual chapters or are described in other guides or help topics.

Actionable Infolets

Overview of Actionable Infolets

Actionable infolets are transactional infolets that can co-exist on the same page as business intelligence (BI) infolets. Actionable infolets give salespeople a quick overview of pending tasks in a single place. Salespeople can quickly act from the infolets themselves, without having to navigate to different detail views.

The following actionable infolets are available by default:

  • My Tasks

  • My Appointments

  • My Accounts

  • My Leads

  • My Opportunities

You can also view a graphical representation of the actionable infolets. The summary charts display data based on the selected filters.

The predefined, actionable infolets let salespeople quickly navigate to relevant areas to perform quick actions on individual records. The infolets can improve sales performance by prioritizing tasks and filtering data. Filtering reduces the number of searches required to view any outstanding items that might require attention.

Salespeople can personalize actionable infolets, refresh data, and create and edit data as required. Built in configuration features help salespeople effectively plan their day, thus saving valuable time. For example, they can choose to select or hide predefined filters that they want to make available on the actionable infolets so that they see only the data they need to see at any given time.

About the Sales Infolets Page

The Sales Infolets page displays key sales information in containers called infolets. Some infolets provide you with an overview, but others make it possible for you to take direct action. These actionable infolets summarize key sales data and let you take immediate action on the tasks presented. The Sales Infolets page is enabled by default. Ensure that you have access to the job roles for which you're enabling the page.

To understand how to configure the springboard and home page to fit your unique business needs, see these guides on Oracle Help Center:

  • Oracle Applications Cloud Configuring Applications Using Application Composer

  • Configuring and Extending Applications

Note: Actionable infolets are secured through the "View Sales Homepage pagination dot one" and the "View Sales Representative Dashboard" privileges. Ensure users have these two privilege. For more information, see the Securing CX Sales and B2B Service and Security Reference for CX Sales and B2B Service guides on Oracle Help Center.

Set the Actionable Infolet Personalization Enabled Profile Option

Sometimes salespeople want to modify the default settings and personalize their actionable infolets so that they can set up their own filters and modify how they want to display the details of the records.

Here's how to enable users to personalize actionable infolets:

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

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. In the search region of the Manage Administrator Profile Values page, enter the profile option code name ZBS_ENABLE_ACTIONABLE_INFOLET_PERSONALIZATION in the Profile Option Code field.

  3. Click Search.

  4. In the list that's returned, click on the profile option code link.

  5. Set the profile option value to Yes.

  6. Click Save and Close.

Modify Actionable Infolets

As an administrator, you can choose to modify or remove existing predefined fields (attributes) or select additional user-defined attributes to display on actionable infolets for salespeople. You can apply different setting for salespeople by role or at the site level.

If you want to modify the My Tasks and My Appointments actionable infolets, then the Date, Time, and Subject attributes must be noneditable. This means that the drill-down option isn't available on these fields.

Salespeople can improve their sales performance tasks by prioritizing tasks and using filters. Record-count filters selected by salespeople take precedence over the record count setting that you specify. For example, if you set 10 as the record count for the My Tasks actionable infolet, and if the salesperson selects the Overdue Tasks filter, then 10 records, if applicable, are displayed.

Salespeople can also view a graphical representation of the actionable infolets. The summary charts display data based on the selected filters.

Before You Modify the Infolets

Before modifying the predefined actionable infolets, do the following:

  • Understand the typical workflows for working with runtime application changes.

  • Ensure that you can modify the infolet by checking if the Edit Pages menu item is available in the Settings and Actions menu available from the global header region. If the menu item isn't available, then you can't modify the page.

    Note: Actionable infolets are secured through the "View Sales Homepage pagination dot one" and the "View Sales Representative Dashboard" privileges. Ensure users have these two privilege. For more information, see the Securing CX Sales and B2B Service and Security Reference for CX Sales and B2B Service guides on Oracle Help Center.
  • Confirm that your privilege is sufficient for modifying the page.

  • Create or activate an existing sandbox.

    When configuring actionable infolets, make sure the sandbox has only the Page Composer tool selected. If you want to make changes in a context layer other than the default Site layer, you must create a separate sandbox and use only Page Composer in it. You can then change the context layer from Site to other layers. For example, to create or edit infolets for a user with a specific job role, you must select the Job Role context layer.

Caution: If you delete an infolet, you can't easily retrieve it. Contact your help desk if you accidentally delete one.

Edit Actionable Infolet Visibility

Actionable infolets are available to predefined roles. However, you can set the availability of actionable infolets so that they become visible to other user-defined roles by editing the visibility settings for the infolet:

  1. Navigate to the actionable infolets page.

  2. From Settings and Actions in the global header region, select Edit Pages.

  3. Click the infolet repository (gears) icon and select the check box next to the actionable infolet you want to make available.

  4. Click the Actions icon on the top right corner of the infolet, and select Edit Visibility.

  5. Select one of the following:

    • Yes: The actionable infolet is available for selection in the infolet repository.

    • No: The actionable infolet isn't available for selection in the infolet repository.

    • EL expression: The evaluation of the EL expression decides whether the actionable infolet is available from the infolet repository. The predefined expression is #{securityContext.userInRole['ORA_ZBS_SALES_REPRESENTATIVE_JOB,ORA_ZBS_SALES_MANAGER_JOB,ORA_ZBS_SALES_VP_JOB,ORA_MKL_SALES_LEAD_QUALIFIER_JOB']}

  6. Edit the EL expression to suit your requirements.

  7. Click Save and Close when you have finished making the changes.

  8. Verify your changes and publish the sandbox.

Modify Actionable Infolet Attributes

You can select and replace any of the predefined attributes that are displayed on the actionable infolets with alternate available attributes of your choice.

Note: If you want to hide one of the predefined attributes, enter a blank value, in which case nothing is displayed in the corresponding drop-down list position you select.

This table shows the attributes that you can modify and represents the order as they appear on the UI.

Actionable Infolet Attributes

My Tasks

  • Subject

  • Activity Type

  • Due Date

My Appointments

  • Activity Time

  • Subject

  • Primary Address

My Accounts

  • Name

  • Primary Contact

  • Primary Address

My Opportunities

  • Sales Stage

  • Name

  • Close Date

  • Amount

My Leads

  • Rank

  • Lead Name

Here's how to modify the attributes of an actionable infolet:

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

  2. Navigate to the actionable infolet that you want to modify.

  3. From Settings and Actions in the global header region, select Edit Pages.

    The Edit Pages window appears.

  4. Select one of the following:

    • Site to make your changes available to everyone.

    • Job Role to target a specific job role you select from the list.

  5. From the actionable infolet that you want to modify, for example, My Opportunities, select Configure from the Actions menu.

    The My Opportunities actionable infolet screen is displayed with the predefined fields selected.

  6. From the Layout tab, select the attributes that you want to edit from the respective drop-down lists.

  7. Set and adjust the two-column table widths in percentage terms by sliding your mouse along the Column Width ruler.

  8. Make the changes that you want to the attribute and select another attribute to edit, if required.

  9. In the Drill Down Field, select the item that you want to use for drilling down to the detail page of the opportunity object.

    Tip: If dynamic choice list fields are added to actionable infolets, then the drill-down capability is automatically enabled.

    This table shows the field names and associated attribute names that you can select for drill-down for each of the actionable infolets:

    Actionable Infolet Drill Down Field Attribute

    My Opportunities

    Name

    Amount

    Close Date

    Sales Stage

    My Leads

    Lead Name

    Rank

    My Accounts

    Name

    Primary Contact

    Primary Address

    My Appointments

    Subject

    Primary Contact Address

    My Tasks

    Subject

    Primary Contact

    Type

    Due Date

  10. Click Save and Close when you have finished making the changes.

  11. Verify your changes and publish the sandbox.

Modify Record Counts

You can also change the predefined number of records to display on the infolet. By default, 10 records display. You can change the default to 10, 20, 25, or 30, as required.

Here's how to modify record counts for an actionable infolet:

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

  2. From the actionable infolet that you want to modify, for example, My Opportunities, select Configure from the Actions menu.

    The My Opportunities actionable infolet screen is displayed.

  3. From the Record Count tab, select the number of records that you want to display on the infolet from the drop-down list.

  4. Click Save and Close.

  5. Verify your changes and publish the sandbox.

Modify Filters

Filtering reduces the number of searches required to view any outstanding items that might require attention. For example, you can choose to select or hide predefined filters that you want to make available on the actionable infolets.

You can show or hide filters, rearrange filters, and add custom filters. You can multiselect and double-click filters in the Available list to move them to the Selected list. You must select at least one filter for the actionable infolet filter list.

You can include saved searches created in Workspace as filters to quickly access relevant records by selecting the Include Workspace Saved Searches check box. It's deselected by default but when selected, all the Workspace saved searches associated with the specified object appear as filters for your actionable infolet. For more information, see the related topic Switch Actionable Infolets to Use Workspace Saved Searches as Filters available from the Getting Started with Your Sales Implementation on Oracle Help Center.

To access a different set of data, create a new saved search in Workspace and then expose the relevant saved search in the Actionable Infolets UI. Selecting available Workspace saved-search filters allows for a more dynamic, effective, and targeted view of the records that salespeople want to update and take immediate action on.

Note: Predefined saved searches are available for selection. However, any custom saved searches that you create must include Record Set values selected for either any records that you own or for records where you're on the team. In addition, when saving your saved search, you must select the Run Automatically check box to run the search automatically when your saved search is loaded. Otherwise, the custom saved search won't display in the available filters list in the Configure UI for your actionable infolet.

This table shows the filters that you can modify.

Actionable Infolet Filter Filter Description

My Tasks

  • Today's Tasks

  • Tomorrow's Tasks

  • Overdue Tasks

  • Beyond Tomorrow's Tasks

  • All Tasks

  • Open Tasks

  • High Priority Open Tasks

  • Display all my tasks scheduled for today

  • Display all my tasks scheduled for tomorrow

  • Display all my tasks that are now overdue

  • Display all my tasks that are scheduled for the day after next and beyond

  • Display all my assigned tasks

  • Display all my assigned tasks that are currently open

  • Display all my high priority tasks that are currently open

My Appointments

  • Today's Appointments

  • Tomorrow's Appointments

  • Display all my appointments scheduled for today

  • Display all my appointments scheduled for tomorrow

My Accounts

  • My Accounts

  • My Favorite Accounts

  • My Team Accounts

  • Display only the accounts that I own

  • Display my accounts that I've marked as favorites

  • Display all the accounts that I can view

My Opportunities

  • Closing in Next 7 Days

  • Closing This Month

  • Closing This Quarter

  • Closing Next Quarter

  • Open opportunities where I am on the team

  • My Open Opportunities

  • Display my open opportunities that are due to close in the next 7 days

  • Display my open opportunities that are due to close this month

  • Display my open opportunities that are due to close within the current quarter

  • Display my open opportunities that are due to close within the next quarter

  • Display my open opportunities where I'm on the team

  • Display only those open opportunities that I own

My Leads

  • Unaccepted Leads

  • My Open Leads

  • Recent Open Leads

  • Open Leads where I am on the team

  • Display a list of all unaccepted leads that are assigned to me

  • Display only those open leads that I own

  • Display a list of my leads that have recently been opened

  • Display a list of open leads where I'm on the team

Here's how to modify the filters of an actionable infolet:

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

  2. Navigate to the actionable infolet that you want to modify.

  3. From the actionable infolet that you want to modify, for example, My Opportunities, select Configure from the Actions menu.

    The My Opportunities actionable infolet screen is displayed with the predefined fields selected.

  4. From the Filters tab, select the filters that you want to modify.

  5. Click Save and Close when you have finished making the changes.

  6. Verify your changes and publish the sandbox.

Modify Quick Actions

You can navigate to the relevant areas in your sales process where you can perform quick actions at the record level. For example, you can easily complete or defer tasks without having to drill down to view the record, or you can accept or reject new leads at the click of a button.

You can show or hide actions, rearrange actions, and add custom quick actions. You can multiselect and double-click any quick actions in the Available list to move them to the Selected list. However, you must select at least one action for the actionable infolet quick actions list.

This table shows the quick actions that you can modify and represents the order as they appear on the UI.

Actionable Infolet Quick Actions

My Tasks

  • Mark as Complete

  • Defer by 1 Day

  • Defer by 2 Days

  • Defer by 1 Week

  • Create Note

My Appointments

  • Create Note

  • Create Call Report

My Accounts

  • Create Lead

  • Create Opportunity

  • Create Appointment

  • Create Task

  • Create Note

  • Create Call Report

  • Log a Call

  • Create Service Request

My Opportunities

  • Create Task

  • Create Appointment

  • Create Note

My Leads

  • Accept

  • Reject

Here's how to modify the quick actions of an actionable infolet:

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

  2. Navigate to the actionable infolet that you want to modify and make sure that the infolet displays in expanded view.

  3. From the actionable infolet that you want to modify, for example, My Opportunities, select Configure from the Actions menu.

    The My Opportunities actionable infolet screen is displayed with the predefined fields selected.

  4. From the Quick Actions tab, select the quick actions that you want to modify.

  5. Click Save and Close when you have finished making the changes.

  6. Verify your changes and publish the sandbox.

Example of Creating Actionable Infolet Custom Actions

You can create custom smart action for actionable infolets to update sales information but the actions can't open pages or navigate to them. For example, you can create a smart action to update the stage of an opportunity or postpone the opportunity close date by one day, but you can't have the action open the edit opportunity page.

Here's how to create a custom smart action to postpone an opportunity close date by one day for My Opportunities actionable infolet.

Note: While you can create the action directly, this example has you create a server script first. That's because the server script includes the Expression Palette to help you write and validate your EL Expression script.
  1. Create and enter a sandbox with Application Composer and Page Composer as your tools.

  2. Create the Groovy script as an object function server script in Application Composer:

    1. In Application Composer, open the object node in the left portion of the page, Standard Objects > Opportunity in this example.

    2. Click Server Scripts.

    3. In the Server Scripts page, click Object Functions.

    4. Enter a function name, no spaces permitted. For example: Defer_1_Day.

    5. Enter the EL Expression script in the Edit Script box. You can use the Expression Palette to find the technical names of fields and insert elements of your script. Here's how to find the technical name for the opportunity Close Date field:

      1. Click Show/Hide Expression Palette (the function icon highlighted in the screenshot).

        Detail of the Server Scripts page, highlighting
the Show/Hide Expression Palette button.
      2. Click Fields.

      3. Select the object, Opportunity in this example, and scroll down.

        Detail of the Server Scripts page, showing the technical
name for Close Date.
      4. In Opportunity: Fields section, search for the technical field name by the display label: Close Date.

        The technical name displays in the API Name column.

      5. You can insert the technical name into your script by clicking Edit Script > Insert.

      To learn more about how to best use the features available in the expression builder when writing scripts, see "Groovy Tips and Techniques" in the Groovy Scripting Reference guide.

  3. When your script is complete, click Validate.

    Here's an example of the script to postpone the due date by one day: setAttribute("EffectiveDate",EffectiveDate + 1);

  4. When your script validates without errors, click Save and Close.

  5. In the object list in the left side of the Application Composer page, click Actions and Links.

  6. In the Opportunity: Actions and Links page, click Create.

  7. In the Create Action or Link page, Display Label field, enter the action name that users see in the infolet actions list.

  8. Select the After the Script: Save the record and return to the previous page option.

  9. In the Script section, click Method Name and select the script name from the list.

  10. Click Save.

  11. While still in the sandbox, click Home to get back to the Welcome page.

  12. From the sandbox Tools menu, select Page Composer. The Page Composer toolbar displays underneath the sandbox toolbar.

  13. Scroll down to the My Opportunities infolet.

  14. Make sure you're in the Expanded View. This is the view of the infolet showing the different filters.

  15. Click Actions (the triangular icon at the top right corner of the infolet) and select Configure.

  16. Move the action you created, Defer 1 Day, to the Selected column.

  17. Click Save and Close.

  18. In the Page Composer toolbar, click Close to save your work.

    The Page Composer toolbar disappears.

  19. To see the new action you created, the infolet must display at least one opportunity. A setup user generally can't access opportunities, so you must publish the sandbox without testing. From the sandbox Action menu, select Publish.

  20. After publishing is complete, sign out and sign in again as a salesperson or another user who owns an opportunity.

  21. With at least one opportunity displayed in the My Opportunities infolet, you can view the new action in the list.

Why are some fields missing when I include Workspace saved searches as my filter?

You must enable any missing fields in the Workspace saved searches to use those fields as filters in your actionable infolets. Occasionally, some fields are exposed on an actionable infolet but if you select the Include Workspace Saved Searches as your filter, the same fields may not be available in the applicable Workspace saved searches. For example, you can edit the Workspace My Appointments filter to enable fields that are exposed in the Layout tab of the actionable infolet. See the topic, Example of How to Make a Field Searchable in Workspace, in this guide, for more information.

Application Toolkit

Overview of Oracle Application Toolkit

Oracle Application Toolkit is a foundation application that provides some features, including including the Oracle Business Intelligence Reports and Analytics pane and the Watchlist in the global header. In the Setup and Maintenance work area, you access the Define Application Toolkit Configuration task list to set up these components.

Attachments

You can use attachments to provide supplementary information to specific business objects. Attachments can be URLs, desktop files, text, or repository folders. For a business object you may view, create, delete, or edit attachments, depending on your role and granted privileges. For more information on attachments, see the Oracle Fusion Applications Developer's Guide.

Repository

Attachments are stored in a content management repository provided by Oracle WebCenter Content Server. Users managing attachments can't interact with the repository unless the repository mode is enabled. When enabled, users can share attachments among objects, update attachments, and perform other tasks. Access to the attachment files is controlled by a digital signing mechanism.

All attachments are scanned for viruses before they're stored on the content management repository. If a virus is detected at the time of upload, the attachment request fails and the user is notified about it.

Security

Data security applicable to a specific business object also applies to its attachments For example, if a user has no access to a specific expense report, then that user can't access its attachments. You can also use attachment categories to control access and actions on attachments, based on roles associated with that category. For more information on securing attachments, see the Oracle Fusion Applications Developer's Guide.

What's the size limit for attachment files in the sales applications?

Users can attach files, such as PDFs and Word docs, to both standard and custom objects. By default, the file size limit for an individual, attached file is 2 G. You can decrease this limit, but you can't increase it. There are no limits placed on the number of files. The size of the files is controlled centrally by the File Upload Maximum Size (FND_FILE_UPLOAD_MAX_SIZE) profile option.

Also note:

  • The only limit on the total file size that can be uploaded is the amount of available space that you have purchased for the content server.

  • There are no restrictions on the type of files you can attach.

Attachments UIs are very user-friendly and easy to work with. You may encounter issues in certain cases such as you modify the attachments, for example create additional attachment categories, or implement data security on them.

Issue: Can't View, Add, Update, or Delete Attachments

You may encounter the following issues when trying to view attachments or perform actions such as adding attachments.

  • You can no longer see specific attachments that were earlier visible.

  • You can no longer update or delete attachments.

  • You get an error stating that you don't have permission to add attachments.

Resolution

Use the Manage Attachment Entities page to ensure that attachment categories are associated to the relevant attachment entity. You might need to check with your system administrator or help desk to determine the exact entity used on the page with the expenses attachments or what categories to assign.

If data security is implemented on the categories for the attachment entity, verify that the Enable Security check box is selected in the Manage Attachment Entities page for that entity. Also, make sure that users have a role that has the necessary privileges. The following table lists the privileges required to view, add, update, or delete attachments with a specific attachment category.

Action Privilege

View

Read Application Attachment (FND_READ_APPLICATION_ATTACHMENT_DATA)

Add or Update

Update Application Attachment (FND_UPDATE_APPLICATION_ATTACHMENT_DATA)

Delete

Delete Application Attachment (FND_DELETE_APPLICATION_ATTACHMENT_DATA)

For example, if users have the Read Application Attachment privilege for all categories associated with the expense report attachment entity, except the Receipts attachment category, then they can view all expense report attachments except those created with the Receipts category. Likewise, if users don't have the Update Application Attachment privilege for any attachment categories tied to the expense report attachment entity, then they can't create any attachments for the expense reports.

For more information on attachment category data security, see the Oracle Fusion Applications Developer's Guide.

Certain attachments UI have predefined restrictions for users on categories. Your developers can also introduce additional filters to determine which document categories are available for a specific page. Check with your developers or help desk.

Issue: Missing Attachment Category

You can view existing attachments but the attachments no longer have an attachment category associated with them.

Resolution

When the attachment was added, at least one category existed for the corresponding attachment entity. Since then, the entity was edited so that it no longer has any assigned categories, so the user can't see the category associated with that attachment.

Use the Manage Attachment Entities page to reassign attachment categories to the relevant attachment entity. For example, if users can no longer see the Receipts attachment category for an attachment to an expense report, then search for the expense report attachment entity and assign to it the Receipts category. You may need to check with your system administrator or help desk to determine the exact entity used on the page with the expenses attachments or any additional categories to assign.

Certain attachments UI have predefined restrictions for users on categories. Your developers can also introduce additional filters to determine which document categories are available for a specific page. Check with your developers or help desk.

Calendar

You usually create a single accounting calendar as part of your implementation. The accounting calendar defines the time periods used in the applications. When you create the calendar, you specify the exact dates for each period. These defined periods, often called enterprise periods, are used for many purposes in the applications. Examples include:

  • Reports that provide amounts by enterprise period, such as a sales pipeline analysis

  • Metrics calculations by period for territory analysis

  • The ability to adjust forecast amounts by time period

  • Distribution of quota amounts by time period

Note: If you used the Getting Started with Your Sales Implementation guide to create your accounting calendar, then you don't need to do the steps listed here.

Here are the high-level steps:

  1. Plan your calendar periods and start year. See the Implementation Considerations section in this topic for more information.

  2. Create the first-year calendar periods and generate the periods for each additional year. See the Create the Calendar section in this topic for more information.

  3. Set the accounting calendar profile option. See the Set the Calendar Profile Option section in this topic for more information.

  4. Run a scheduled process. See the Run the Time Dimension Process section in this topic for more information.

Caution: After your calendar is being used in transaction, you can't change the calendar options. For example, after you have generated forecasts, you can't change the calendar options.

Implementation Considerations

Since you can't change the calendar after it's in use, ahead of time, you need to:

  • Plan which periods your calendar will use.

  • Decide which year you want the calendar to start. consider setting the date to the first date that your company was created. Then you can upload historical data later, if necessary.

Period frequency is an important decision for your calendar, because the period frequency set in your fiscal calendar is the shortest period you can use. Here are some examples:

  • Let's say you set the period frequency to yearly. Then, your reports and activities can be for each year, but can't be broken down by month.

  • If you set the period frequency to monthly, then you can break down activities and reports by month and summarize by quarter and year.

  • Say you want to set the period frequency to weekly. In this case, then you can perform activities and reports by week, quarter, and year, but not by month because the number of weeks per month varies.

Create the Calendar

When you create the accounting calendar, you're establishing the exact start and end dates for each period, for each year. Here's a procedure that uses the fictitious Vision Corporation to guide you through the steps:

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

    • Offering: Sales

    • Functional Area: Company Profile

    • Task: Manage Accounting Calendars

  2. On the Manage Accounting Calendars page, click Create.

  3. In the Create Accounting Calendar: Calendar Options page:

    1. Name your calendar, for example, Sales Calendar.

    2. Leave the Adjusting Period Frequency set to None.

    3. For Start Date, Vision Corporation uses 1/1/10.

    4. For Period Frequency, select the shortest time period you want to use for reports and activities. Vision Corporation is using Monthly. The period starts on the first of the month and ends on the last day of the month, regardless of the number of days or weeks in each month.

    5. Vision Corporation selects None for the Separator.

    6. Select the Format to use for period names.

  4. Click Next. The Create Accounting Calendar: Period Details page appears, showing the generated periods. The image shows multiple columns, including:

    • Period name, which is month name, one for each month of the year

    • Year, which is 2010

    • Period number, one for each month

    • Quarter number for each period, assuming four quarters in the year

    • Start and end dates for the periods

    • A check box used to indicate whether a period is an adjusting period

    Here's an example of the Create Accounting Calendar: Period Details page:

    The Period Details page shows the calendar periods
for the first year.
  5. If you need to, manually change the details for each period.

  6. Click Save and Close.

  7. Now you need to generate the periods for each additional year, including the current, or coming year. Open the calendar.

  8. Click Add Year.

  9. Click Save and Close.

  10. Repeat the last three steps for each year you want to add.

  11. Click Done.

Note: You can't change your calendar options after you start using the calendar, such as by generating forecasts.

Set the Calendar Profile Option

After you finish creating your calendar, set the accounting calendar profile option. This profile option setting tells the applications which calendar to use. Use these steps:

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

    • Offering: Sales

    • Functional Area: Company Profile

    • Task: Manage Calendar Profile Option

    • Option: Manage Calendar Profile Option

  2. Select the Accounting Calendar Default profile option.

  3. In the Profile Values table, click New.

  4. For Profile Value, select Site.

  5. Click the Profile Value list, and select the name of the calendar you created.

  6. Click Save and Close.

Run the Time Dimension Process

You need to run the Refresh Denormalized Time Dimension Table for BI process to make calendar time periods available for analytics and reports. Use these steps:

  1. Click Navigator > Scheduled Processes.

  2. In the Scheduled Processes page, click Schedule New Process.

  3. In the Schedule New Process dialog box, click the menu next to the Name field and click Search.

  4. In the Search dialog box, enter %Refresh%, and click Search.

  5. Select the Refresh Denormalized Time Dimension Table for BI process in the results that are returned and click OK.

  6. Click Ok again, if needed.

  7. In the Process Details window, click Submit.

Click to Edit

About Click to Edit

The click-to-edit feature lets salespeople edit records directly from landing pages of work areas. By simplifying data entry, the click-to-edit feature improves usability and efficiency when working with business transactions. Salespeople can change attributes for records directly in the landing pages without navigating to the edit pages. This feature is enabled through the Click-to-Edit on Landing Page Enabled (ZBS_ENABLE_CLICK_TO_EDIT) profile option.

This profile option isn't enabled by default. Administrators must set the profile option to enable the click-to-edit feature on the landing pages for the following sales objects:

  • Accounts

  • Contacts

  • Opportunities

  • Leads

  • Activities

  • Assets

  • Territories

The click-to-edit feature is also available for company-defined objects.

Enable Click to Edit

Administrators enable the click-to-edit feature by setting the Click-to-Edit on Landing Page Enabled (ZBS_ENABLE_CLICK_TO_EDIT) profile option. This profile option isn't enabled by default.

The click-to-edit feature is available from the Accounts, Contacts, Opportunities, Leads, Activities, and Assets landing pages. The feature is also supported for custom objects.

Use the following procedure to enable click-to-edit functionality on the landing pages of supported sales objects:

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

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. In the search region of the Manage Administrator Profile Values page, enter the profile option code name ZBS_ENABLE_CLICK_TO_EDIT in the Profile Option Code field.

  3. Click Search.

  4. In the list that's returned, click on the profile option code link.

  5. Set the profile option value as needed.

  6. Click Save and Close.

Favorites

How Users Mark Favorite Records

Salespeople can mark records as favorites so that they can find them more easily. To mark a favorite record, salespeople:

  • Click the favorite icon in the edit page of a record.

  • In Workspace, click the favorite icon for the record in the list page of an object.

    Note: You must enable the favorites functionality in Workspace. See the related topic, Enable the Favorite Field for Quick Access to Records.

To view a list of all their favorites, salespeople can click the Favorites and Recent Items icon in the global header.

Currently, salespeople can mark favorites for:

  • Accounts and contacts

  • Assets

  • Activities

  • Campaigns

  • Deal registrations

  • Leads

  • Opportunities

  • Partners and partner contacts

  • Territories

  • Custom objects

Favorites are also available in CX Sales Mobile and in Sales for Microsoft 365.

Languages

A language pack contains artifacts that are translated to a specific language. Translated artifacts include UI text, predefined data, messages, BI catalog data, and so on. Here are the supported languages other than American English:

  • Arabic

  • Chinese (Simplified)

  • Chinese (Traditional)

  • Czech

  • Danish

  • Dutch

  • Finnish

  • French (Canadian)

  • French (European)

  • German

  • Hebrew

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Portuguese (Brazilian)

  • Polish

  • Romanian

  • Russian

  • Slovak

  • Spanish

  • Swedish

  • Thai

  • Turkish

How to Install Language Packs

To install language packs on all your environments, contact your help desk. For more information about language packs, see Oracle Applications Cloud Service Definition - Language Packs (2073202.1) on My Oracle Support at https://support.oracle.com. There's no limit to the number of language packs you can ask for in one service request. But you must only install the language packs you need to conduct your day-to-day business because of these reasons:

  • Once you request a language pack, the installation will be scheduled for all your environments, including production, staging, and test environments, so that they're all in sync.

  • It takes time and resources to install language packs. So you might get extended outages during updates, especially if you have four or more language packs installed in your environments.

  • Once you install any language, you can't uninstall it later.

You can view all available languages, whether they're already installed or available for installation and translation. In the Setup and Maintenance work area, use the Manage Languages task in the Application Extensions functional area. Each dialect is treated as a separate language. Generally, you don't need to edit any of the fields on the Manage Languages page, unless absolutely necessary.

How to Set the Preferred Language

Here's how to set the preferred language in the sales applications:

  1. Navigate to the Manage Administrator Profile Values task in Setup and Maintenance.

  2. Search for the Profile Option Code FND_LANGUAGE.

  3. Modify the profile value at the site or user level to the preferred language.

  4. Save your changes.

Note: Keep in mind that user preferences set in the Preferences screens (located under the user name in the global header) override any site-level setting.

Lightbox Content Library

Considerations When Setting Up Sales Lightbox

Sales Lightbox is a content library that you can use to store, access, and share files, such as slide decks, web-based content, images, and .pdfs. Lightbox lets users store, access, and share content with individuals, accounts, and opportunities.

You can find more information about Lightbox end user tasks and capabilities in the Using Sales guide.

Supported File Types

Sales Lightbox supports the following file types:

  • Microsoft Powerpoint (.pptx): If you install the Microsoft Office Compatibility Pack, and save a presentation in the Open XML format (.pptx 2007), then those presentations are fully compatible with Sales Lightbox.

  • Portable Document Format (.pdf): Standard .pdf files are supported.

  • HTML: HTML in the form of microsites: See the topic, Use Microsites in the Lightbox Content Library, for more information.

  • .jpg and .png: Image files in the .jpg and .png formats are supported.

For information about the actions that can be performed on different content types, see the topic, Available Actions for Different Content Types.

Upload File Size

The maximum file size for a presentation to be uploaded is 100 MB.

Salespeople Access

Salespeople can access Sales Lightbox without any setups required. All of the default sales user roles (for example, Sales Representative, Sales Manager, and Sales VP) can access the feature using the Sales > Lightbox menu. In addition, the Sales Administrator user has all of the same permissions that sales users do. For additional details on sales user tasks for Sales Lightbox, see the Using Sales guide.

Lightbox Administrator Access

In addition to the sales user permissions, the supplied Application Implementation Consultant (a type of setup user) and Customer Relationship Management Application Administrator job roles have additional privileges to:

  • Access the All Content view: This view lets the administrator see all content in the application, not just his own. Sales users can't see this view.

  • Delete content: Only the administrator can delete content not owned by him.

Add Lightbox Presentation Feedback Subtab

The Lightbox presentation feedback resource is used to view, create, update, and delete the ratings and comments from the attendees at a Lightbox presentation session. The feedback may apply to an individual, Lightbox document page, or to an overall Lightbox document presented during a presentation session. You can create a Lightbox presentation feedback for a Lightbox document.

Here's how to add a feedback 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 then expand Lightbox Presentation Feedback.

  4. Click the Pages node.

  5. Ensure that the Application Pages tab is selected.

  6. In the Details Page Layouts section, select Default Layout and click the Edit icon.

  7. In the Subtabs Region, click the Hide Show icon.

    The Configure Subtabs shuttle window opens.

  8. Move Feedback from the Available Fields window to the Selected Fields window.

  9. Click OK, then click Done to exit the layout editor.

  10. Verify the changes by viewing the subtab when drilling into a document.

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

Mass Update of Records

Enable Mass Update of Records

Let salespeople update fields on multiple records at once with the mass update feature. For example, a salesperson can update the sales stage on multiple opportunities at the same time with just a few clicks. Or, a salesperson can update rank and deal size on several leads at once.

Here's the setup flow:

  1. Add the Update action to the landing pages of the work areas where you want to enable the feature. Landing pages are the only pages that support the mass update feature.

  2. Optionally, configure which fields salespeople can update. You can use the default fields already set if you want. Or you can configure the list yourself.

  3. Optionally, set profile options to specify how many records salespeople can update at once. You can use the default value of 25 records if you want.

Supported Objects for Mass Update

These are the predefined, standard business objects that support mass update:

  • Activities

  • Accounts

  • Assets

  • Contacts

  • Sales Leads

  • Opportunities

Custom objects also support mass update.

Add the Update Action

Salespeople access the mass update feature using the Update action that you enable in the work area landing pages. The action appears as Actions > Update on the landing page toolbar.

Remember, make all Application Composer changes in a sandbox and publish the sandbox according to your company's processes.

These steps use the Opportunity object's landing page as an example. The basic steps are the same for all objects, but the navigation can be different for different objects. See the Landing Page Names in Application Composer section in this topic for the page names and navigation.

  1. Navigate to Configuration > Application Composer.

  2. Expand the Standard Objects tree and then expand the object you want to modify. For example, expand the Opportunity object.

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

  4. Ensure that the Application Pages tab is selected.

  5. In the Landing Page Layouts region (use the Activities region for the Activities object), select the Standard layout, and then click the duplicate layout icon to duplicate and edit the resulting copy. Alternatively, you can edit an existing, custom layout.

  6. Now, edit the new layout. For example, to edit the Opportunities landing page, click the edit (pencil) icon on the Fuse Opportunity Overview Table.

  7. In edit mode for the landing page, navigate to the Configure Detail Form: Buttons and Actions region.

  8. In the Available Actions window, double-click the Update action to move it to the Selected Actions window.

  9. Click Save and Close, then Done.

  10. Test the changes using the steps in the Test the Changes section later in this topic.

Set the Updatable Fields

Now that you have enabled the Update action, configure the fields salespeople can update using mass update. Each object already has several fields enabled for the mass update feature. If you want, configure this list to include other standard fields, or even custom fields. Keep in mind that if you're setting up the mass update feature for custom objects, then you must configure the list of fields that can be updated by users -- it's not optional like with standard objects.

You configure the list of mass update fields using the same custom landing page layout where you manually displayed the Update action:

  1. In Application Composer, navigate to the Pages node for the object you're configuring.

  2. Edit the same landing page layout where you manually displayed the Update action in the above procedure.

  3. Navigate to the Configure Mass Update Fields region.

  4. In the Available Fields box, double-click the fields that you want to make available for the mass update feature at runtime. Or, use the arrows to move the items that you want to make available. See the Rules for Certain Field Types below for some details on field types and limitations or behavior.

  5. After you're done making changes, click Save and Close, then Done.

Rules for Certain Field Types

Consider these rules for certain field types as you set up the feature:

  • You can use both standard and custom fields. However, read-only fields, such as formula fields, and fields that can be conditionally updated, aren't included in the list.

  • Some fixed-choice list fields are related in a parent-child relationship. This simply means that the values displayed in the child field are dependent on whatever is selected in the parent field. If you want to make a child fixed choice list field available for the mass update feature, then you must also include its parent field.

Configure the Number of Updatable Records

You can configure the maximum number of records that users can update at once by setting profile options.

Here's the behavior:

  • The default value of the profile options is 25, meaning the maximum number of records that salespeople can update at once for those objects is 25.

  • The maximum number of records that can be updated at once is 500.

  • If a profile option value has a null value, the application sets the number of records that can be updated at once to 10.

  • For custom objects, the threshold value is set at 25 and can't be changed using a profile option.

Here are the mass update threshold profile options. The profile option codes are listed in parentheses.

Object Profile Option

Activity

Activity Mass Update Threshold Value (ZMM_MASS_UPDATE_THRESHOLD)

Account

Asset

Contact

Sales Lead

Opportunity

Custom objects

Mass Update Threshold Value (ZBS_MASS_UPDATE_THRESHOLD)

Set the Profile Options

  1. In Setup and Maintenance, go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. In the search region of the Manage Administrator Profile Values page, enter the profile option name in the Profile Display Name field. Or, enter the code in the Profile Option Code field.

  3. Click Search.

  4. In the list that's returned, click the profile option name link.

  5. Set the profile option value as needed.

  6. Save your changes.

Test the Changes

It's a good idea to test the changes. For example:

  1. Sign in as a user who has access to the object you just modified, such as a sales representative or sales manager.

  2. Go to the landing page and click the Actions menu to verify that the Update action is available.

  3. Go through the mass update flow with some records to be sure it's working as you expect. See the Related Topics for the procedures.

Landing Page Names in Application Composer

As you modify the landing pages, it's helpful to know their names in Application Composer. Here are the pages, along with the navigation steps to get to them:

Object in Application Composer Navigation to Landing Page Layout Name of the Landing Page You Need to Edit

Activity

Activity > Pages > Application Pages > Landing Page Layouts > Activities region

My Activity Overview Table

Account

Account > Pages > Application Pages > Landing Page Layouts

FUSE Account View List Table

Asset

Asset > Pages > Application Pages > Landing Page Layouts

Asset Overview Table

Contact

Contact > Pages > Application Pages > Landing Page Layouts

Fuse Contact List Table

Sales Lead

Sales Lead > Pages > Application Pages > Landing Page Layouts

Fuse Lead Overview Table

Opportunity

Opportunity > Pages > Application Pages > Landing Page Layouts

Fuse Opportunity Overview Table

Configure Mass Update for Different User Roles

You can show a different set of mass update fields to different users in the same work area, in cases where you want users with different roles to be able update different fields. You accomplish this by using separate custom page layouts for different user roles.

If you want users with different job roles to see a different set of fields in mass update, then create different custom landing page layouts for them. For each landing page layout, you:

  1. Manually display the Update action.

  2. Configure a different set of mass update fields in each landing page layout that's intended for each role.

  3. Assign a different role to each layout.

Here are the high-level steps add a role to a custom layout:

  1. Follow the steps in the Enable Mass Update of Records topic to create the custom landing page layouts you need.

  2. Navigate to the landing page layouts table for the object in Application Composer.

  3. Select your custom layout.

  4. Click the Role Name arrow in the row.

  5. In the Select: Roles window, select CRM - Job Roles in the Role Category Filter.

  6. Click the Specific role radio button in the Role field.

  7. Click the Show available predefined roles check box.

  8. Move the applicable role from the Available Roles shuttle region to the Selected Roles shuttle region.

  9. Click OK.

  10. Repeat for the other custom layouts you're using.

Example Use Case

Let's say that you don't want salespeople to be able to mass update the Sales Channel fields during mass update on a partner opportunity. But you still want channel managers to be able to mass update those fields. So you remove the Sales Channel field from the mass update list on your custom Sales Representative landing page layout. Then, add the Sales Channel field to the mass update list on your custom Channel Manager landing page layout.

Messages

Messages provide users with information about business or application errors or warnings.

Typically, messages inform the users about the following:

  • Missing or incorrect data

  • Status of an application, page, or a business object

  • Status of an ongoing process

  • Result of a user action

Besides notifying users about the problem, messages provide guidance to users on taking corrective action. Messages also warn users about the consequences of a certain action.

Oracle provides a set of predefined messages that are stored in a message dictionary. You can create additional messages or modify the existing ones using the Manage Messages task in the Setup and Maintenance work area.

Note: Don't delete predefined messages unless you're sure that they aren't used anywhere.

Message Dictionary

The message dictionary stores messages that the application requires at run time. Messages are predefined for specific applications and modules, but a few are common messages that can be used in any application or module.

When you create messages, use the message text and the following components to cover additional details addressing users and help desk personnel:

  • User Details: A detailed explanation of the message short text meant for users.

  • Administrator Details: Details of the identified problem meant for the help desk personnel. The end users don't see this text.

  • Cause: An end-user version of the cause of error.

  • User Action: Instructions to users for addressing the identified problem. Where there is no guidance for end users, they must approach the help desk.

  • Administrator Action: Corrective action that help desk personnel must take to correct the problem. This information isn't available to the end users.

Message names that begin with FND_CMN are common messages. Each common message can appear in multiple places in any product family across Oracle Applications Cloud. For example, the FND_CMN_NEW_SRCH message can be used for any search to indicate that no results were found. Common messages of type error or warning are part of the message dictionary.

Creating and Editing Common Messages

You can create common messages for use in multiple places. However, ensure that you follow the predefined naming convention and numbering series associated with the application or module.

Note: Don't use FND_CMN as the prefix for the messages you create because all the predefined common messages begin with it.

Common messages can be used in any application. Therefore, consider the ramifications if you edit any aspect of the message, including incident and logging settings. Changes would be reflected in all instances where the message is used. For example, if you change the message text, ensure that the text is generic and applies to the entire site of Oracle Applications Cloud implementation.

Notes

A note is a record attached to a business object. Notes capture nonstandard information received as you do business. When setting up notes for your application, you should consider the following points:

  • Which new note types you want to add.

  • How you want to map these new note types to business objects in your area.

Note Types

Note types are assigned to notes when they're created, to categorize them for future reference. During setup you can add new note types, and use a process called note type mapping to restrict them by business object type. When deciding which new note types you want to add, keep in mind how you want your users to search for, filter, and report on these notes.

Note Type Mappings

If you add new note types, you must map them to the business objects you use in your product area. Here are some points to consider when mapping note types:

  • When you select a business object other than Default Note Types, you only see the note types that apply to that object.

  • If no other note types appear, then note type mapping doesn't exist for that object and the default note types are used. Select Default Note Types to see which default note types exist in the application.

  • If you modify a default note type, it affects all the business objects that don't have a note type mapping.

Suppose you decide to add a new note type of Analysis for your product area of Sales-Opportunity Management. You use note type mapping to map Analysis to the Opportunity business object. Now, every time you create or edit a note for an opportunity, you see Analysis as an available note type option.

When deciding which note types to map to business objects, you should keep the same considerations in mind that you did when you decided which note types to include.

Privacy Statement

A privacy statement is legal content that tells you how a company collects and manages user data. You can add a link to your company's statement in the About This Application dialog box.

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

  2. Search for the Privacy Statement URL (PRIVACY_PAGE) profile option.

  3. In the Profile Values section, update the Profile Value field with the full URL of the web page that has the privacy content. By default, this profile value is N.

    Caution: Don't enter any other value, such as Y, because that causes a broken link.
  4. Click Save and Close.

And that's it! Your users can now view the Privacy Statement link by clicking their user image or name in the global header and selecting About This Application.

Public Unique IDs

When users create records in the database, the applications use document sequencing as they generate a unique ID for each business object record. Understandably, these numbers aren't easy to read or use because of their length and complexity. To overcome the issue of long IDs, you can set up the applications to make these IDs more user-friendly and readable. This user-friendly value is called the public unique ID (PUID).

These PUID are used in:

  • The data model

  • Unique sequence generation when you use advanced setup

  • Global search by PUID attributes

"Advanced setup" means you have set up the unique sequence generation of PUIDs that's a specific prefix and radix configuration. You set these for each business object. In addition, keep in mind that PUID specifications mandate that users can search for all supported business objects by PUID and Party Number.

Many of the business objects support PUIDs, as described here:

Top-Level Object Name Model Support (PUID Attribute Name) Object PUID Generation Global Search By PUID PUID Exposed in List Management

Account

PartyNumber (RegistryID)

Supported

Supported

Supported

Action

ActionNumber

Supported

NA

NA

Action Plan

ActionPlanNumber

Supported

NA

NA

Activity

Activity_Number

Supported

Supported

Supported

Asset

AssetNumber

Supported

Supported

Supported

Business Plans

BusinessPlanNumber

Supported

Supported

Supported

Campaign

CampaignNumber

Supported

Supported

Supported

Competitor (called Sales Competitor in Application Composer)

PartyNumber

Supported

Supported

Supported

Contact

PartyNumber (RegistryID)

Supported

Supported

Supported

Custom Objects

Custom Attribute

Supported

Supported

Supported

Deal Registration

Deal Number

Supported

Supported

Supported

Interaction

InteractionNumber

Supported

Supported

Supported

Lead (called Sales Lead in Application Composer)

Lead_Number

Supported

Supported

Supported

MDF Budget, MDF Claim, MDF Claim Settlement, MDF Request

MDF Claim: Code (ClaimCode)

MDF Request: Code (FundRequestCode)

MDF Budget: Code (BudgetCode)

MDF Claim Settlement: Code (ClaimSettlementCode)

Supported

Supported

Supported

Objective

ObjectiveNumber

Supported

NA

NA

Opportunity

Opty_Number

Supported

Supported

Supported

Partner

Company_Number

Supported

Supported

Supported

Quote (called Sales Orders in Application Composer)

OrderHeaderNumber

Supported

Supported

Supported

Price Book

PriceBook_Code

Supported

Supported

Supported

Product

ItemNumber

Supported

Supported

Supported

Product Group

Reference_Number

Supported

Supported

NA

Program Enrollment

Enrollment Number

Supported

NA

Supported

Promotion

Sales Promotion Code

Supported

NA

Supported

Resource

Party Number

Supported

Supported

Supported

Service Request

SRNumber

Supported

Supported

Supported

Template Action Plan

TemplateNumber

Supported

NA

NA

Territory (called Sales Territory in Application Composer)

Supported (Unique Territory Number)

Supported

NA

Supported

Territory Proposal (called Sales Territory Proposal in Application Composer)

Supported (Proposal Number)

Supported

NA

Supported

Work Order

WO_NUMBER

Supported

Supported

Supported

Setup Options

You have these options for setup:

  • Use the default setup, where no implementation steps are required.

  • Use the basic setup, which is configurable to a certain degree. If you use this setup, the default setup isn't used.

  • Use an advanced setup which is more complex and configurable. The default and basic setups apply to all objects. Advanced setup is on a per-object basis.

Here's a list of setup options and where to find more information about the setup.

Setup Option Description Where to Find More Information

Default Setup

In this setup, no implementation steps are required. The application automatically generates a unique 15-digit numeric ID for each record. The document sequencing begins with a 1.

No additional documentation, other than this introduction

Basic Setup

In this setup, you set two profile options where you configure the radix (or base numbers and characters) and prefix to use. The application generates an alphanumeric public unique ID instead of the default numeric public unique ID for each record.

See the Public Unique ID Basic Setup section in this topic

Advanced Setup

In this setup, you define a radix and prefix for each object. It isn't required for the radix and prefix to be different for each object.

See the Public Unique ID Advanced Setup section in this topic

Public Unique ID Basic Setup

In the basic setup, you can define a single prefix that's shared across all business objects in the implementation. In addition, you have several different radix values that can be used. Together these values form the PUIDs.

To perform the basic setup, you set two profile options:

  • CRM Public Unique ID String Encoding profile option: Controls the characters used in the encoding of the public unique ID based on a radix, or base number.

  • CRM Public Unique ID Prefix profile option: Defines the optional prefix value for the public unique ID.

CRM Public Unique ID String Encoding profile option (ZCA_PUID_RADIX):

This profile option determines the set of numbers and letters used in creating the public unique ID. The default value is null. After you set the radix, the application converts the public unique ID into user-friendly IDs, using alphanumeric characters instead of numeric digits.

These base values are available:

  • Numbers 0-9, letters A-F

  • Letters A-Z, upper case

  • Numbers 2-9, letters BCDFGHJKLMNPQRSTVWXYZ

  • Numbers 0-9, letters ABCDEFGHJKLMNPQRTUWXY

  • Numbers 0-9, letters A-Z, upper case

  • Numbers 0-9, letters A-Z, letters a-z

  • No alphanumeric conversion

The values for the radix are stored in the lookup type, ZCA_PUID_ENCODING. This lookup type is accessible using the Manage Standard Lookups task in Setup and Maintenance.

CRM Public Unique ID Prefix profile option (ZCA_PUID_PREFIX):

In this profile option, you optionally define the prefix for the public unique ID at the site level. After you set this profile option to the prefix you want, the application inserts the prefix before the public unique ID base encoded document sequence value. For example, you may want the records for the pharmaceutical divisions of your company to be denoted with public unique IDs and the prefix Pharma or Pharma1, Pharma2, and so on. By default, the prefix has no value.

Keep these points in mind:

  • If you enter a prefix value, then you must set a radix value. The length of a prefix value is 5. You can't use the prefix setting by itself.

  • If you require a delimiter, then include it as part of the prefix.

  • The concatenated public unique ID and prefix must not exceed the defined field length, which is usually 30 characters.

Here's how to set the profile options.

  1. Sign in as a setup user.

  2. In Setup and Maintenance, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Public Unique Identifier Profile Options

  3. On the Manage Public Unique Identifier Profile Options page, click the ZCA_PUID_RADIX option.

  4. In the ZCA_PUID_RADIX: Profile Values section of the page, click the Profile Option Values list of values and select the base numbering value.

  5. Click Save and Close.

  6. Optionally, click the ZCA_PUID_PREFIX option.

  7. In the ZCA_PUID_PREFIX: Profile Values section of the page, in the Profile Value box, enter the prefix and the delimiter you want, if any. For example, enter CDRM_.

  8. Click Save and Close.

Public Unique ID Advanced Setup

In the advanced setup, you can define a different prefix and numbering radix for each business object, for example, Accounts, Contacts, and Opportunities. Oracle recommends that you do this to avoid PUID clashes when populating object records via import while also creating records in the UI or via REST.

Keep these points in mind:

  • If you enter a prefix value, you must set a radix value. You can't use the prefix setting by itself. The length of a prefix value is 5.

  • If you require a delimiter, then include it as part of the prefix.

  • The concatenated public unique ID and prefix must not exceed the defined field length, which is usually 30 characters.

Use these steps to configure the radix and optionally, the prefix in the advanced setup.

  1. Sign in as a setup user.

  2. In Setup and Maintenance, go to the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Public Unique Identifier Sequence Generation

  3. On the Manage Public Unique Identifier Sequence Generation page, if you're configuring these values for the first time, add a row to the table.

  4. In the Object list of values, select the object for which you're configuring the public unique ID.

  5. In the Radix list of values, select the base numbering to use. This list of possible radix values is the same list of values that are provided in the ZCA_PUID_RADIX profile option.

  6. In the Prefix box, enter the prefix you want to use for the object and unique ID.

    • Enter a maximum of five characters.

    • The allowed characters are: 0-9, A-Z, a-z, and these special characters: period, hyphen, comma, and underscore.

  7. Repeat for other objects.

  8. Click Save and Close.

This table lists options for RADIX in the Manage Public Unique Identifier Sequence Generation task. For example, the sequence looks as follows if a Lead Number is in the format of "LeadNumber":

  • "CDRM_2452" if the advanced setup for the Lead object isn't set up.

  • If the advanced setup for the Lead object is set up, then the LeadNumber is created in the form of "LeadNumber" = "LEAD_106065",

  • PREFIX is LEAD_ and RADIX is "106065", which is in the format of "No Alphanumeric Conversion".

  • RADIX is in the format of "Letters A-Z, Upper Case". "LeadNumber": "LEAD_GAXM".

Prefix Radix

NULL

NULL

NULL

Numbers 0-9, letters A-F

NULL

Numbers 0-9, letters A-F

A-

Numbers 0-9, letters A-F

A-

Numbers 0-9, letters A-F

Null

No alphanumeric conversion

A-

Numbers 0-9, letters A-Z, letters a-z

A-

Numbers 0-9, letters A-Z upper case

A-

Numbers 0-9, letters ABCDEFGHJKLMNPQRTUWXY

A-

Numbers 2-9, letters BCDFGHJKLMNPQRSTVWXYZ

A-

Letters A-Z, Upper Case

A-

Numbers 0-9, letters A-F

Public unique ID is a value defined for business objects, such as accounts and opportunities, by the implementor or calling program. For example, when you integrate your sales application and certain other external applications, you can use the PUIDs from those applications in the sales application as well. Who's calling depends on whether an application in the external application is calling the sales application, or whether a person is using their PUIDs. You specify PUIDs when you create objects. For example, Party_Number is the PUID for accounts and contacts. When a new account is created, the PUID value can be automatically created by a central routine or supplied by the end user.

You can migrate administration- and configuration-related objects from a test to production instance, or the other way around. The migration is essentially exporting the data in one instance using the ready-to-use bulk export process in the sales application and then importing the data into another instance using the import process.

Select a Migration Approach

Consider the following points before selecting a migration approach:

  • If your organization frequently uses the bulk data load (migration) functionality, then use the document sequence approach. For more information, see the related topics.

  • If your organization doesn't use the bulk data load frequently, then use Oracle's standard import process to import the data from one instance to another. When PUIDs are rejected in the process, manually define new PUIDs for the rejected PUID values and repeat the import process until all the data is imported. For more information on how to import, see the Getting Started with Your Sales Implementation guide.

Note: You can't migrate transactional data.

Manually Override PUID Values

You can manually override the PUID value during the import process. After a PUID is rejected in the import process, a new PUID value should be defined. For example, let's say SMTTXT-002 is rejected because the record already exists in the test instance. So, a new PUID value of SMTTXT-003 is defined and used in the import process.

Set Up Document Sequencing

Every object team defines a document sequence number for objects as part of PUID implementation. When a new PUID is created in the database, the PUID functionality uptakes the value from the document sequence process. For example, if the document sequence initial value is 0, when a PUID is created in the production instance, then the sequence generation creates the PUID starting from 0. If the document sequence has a different initial value between the test and production instances, then the possibility of PUID clashes between the test and production instance is removed completely.

Organizations know how many objects are typically created in a test instance versus a production instance. Therefore, defining an appropriate initial value for document sequence in the test and production instances should resolve the PUID clashes. For more information about setting up document sequences, see Set Up Document Sequences in the Oracle Fusion Applications Developer's guide.

Maintain Different Prefixes

You define the prefix information for specific objects in the Manage Public Unique Identifier Sequence Generation task in Setup and Maintenance. You can enter a uniquely identifiable prefix in the test instance to signify that the PUID values belong to the test instance. Similarly, while the same objects are defined in the same task flow in the production instance, enter a prefix to signify the PUID values belong to a production instance. Therefore, the PUID value as a whole never clashes when the migration occurs from the test to production instance or the other way around.

Recent Items

About Recent Items

The Recent Items API provides a list of a salesperson's recently accessed or updated records in the Find search boxes, in the Recent Items list (accessible from the favorites icon in the global header), and in other lists as the salesperson works in the application.

Scenarios for When Recent Item Relationships Occur

The application captures recent items any time a sales user interacts with a record, whether that be creating, updating, or simply viewing the record. That record then shows up in the Find box for that object. Note that recent items don't appear in other objects' Find lists. Say, for example, a salesperson creates an opportunity, that record's creation won't show up in the Activities Find list. But, they can show up in lists of values within a record, such as an account recent item showing up in the list of accounts in an opportunity.

Note: By default, the application keeps recent items in the database for 30 days. You can configure this time frame, however. See the Specify How Long to Keep Recent Items topic for more information.

These simple scenarios illustrate events that cause the Recent Item API to establish a recent items relationship with a record or with the application itself:

  • A user creates a record, such as a lead, an opportunity, or an activity like a task or appointment.

  • A user drills into the edit page of a record that's not among the recent items, for example, the user opens a task.

  • A user signs out of the application.

This scenario is a little more complex and illustrates how recent items can appear in other objects:

  • An appointment has Opportunity 1 associated with it.

  • The user edits Opportunity 2 and saves the opportunity.

  • The user goes into the same appointment and removes Opportunity 1 and clicks on the drop-down list for opportunities, to associate a different opportunity with the appointment.

  • In the appointment's drop-down list for opportunities, the application shows the last opportunity (Opportunity 2) first in the list.

If a record is created, the CREATION_DATE and CREATED_BY attributes are captured accordingly. If a record is updated, then the LAST_UPDATE_DATE and LAST_UPDATED_BY attributes are modified accordingly.

But, remember that users don't have to update a record for it to be recorded as a recent item. Whether the record is updated or not, the application always records even the viewing of a record as a recent item.

Specify How Long to Keep Recent Items

You can configure how long to keep recent items in the database. The default is 30 days, and you can change that time by setting the profile option, Days to Keep Recent Items (ORA_ZCA_RECENT_ITEMS_PRESERVE_DAYS). Use the Manage Administrator Profile Values task in Setup and Maintenance to access the profile option.

The process Purge Application Metrics runs weekly to automatically purge and optimize the list of recent items. You can also schedule the process manually in the Scheduled Processes UI.

Note: If recent items aren't deleted periodically, the application stores the data, and storing large amounts of recent items data can impact performance.

Service Request Management

Overview of Service Request Management

Using the Oracle Service Request functionality, sales and service representatives can create and manage service requests. Several tasks are involved in setting up the functionality.

Service Request Capabilities

Service request management lets sales and service professionals:

  • Create service requests

  • Enter summary information into service requests

  • Add products and product groups to service requests

  • Organize service requests into queues

  • Compose and send messages from service requests

  • Add contacts to service requests

  • Add team members to service requests

  • Automatically or manually assign service requests to other users

  • Create activities for service requests

  • Associate and view items in the knowledge base

  • Integrate with the partners application to capture and resolve issues reported by your partner accounts

See the Using B2B Service guide for more information about sales user tasks for service requests.

Summary of Setup Tasks

Here's a summary of the setup tasks:

  • Enable the Service offering

  • Understand the predefined service request job and duty roles

  • Define service request assignment rules

  • Enable the sales catalog for service requests

  • Enable outbound email messages for service requests

  • Configure service request categories

  • Configure knowledge base settings for service requests

  • Modify service request lookups

See the Implementing B2B Service guide for more information about service requests setup tasks.

Watchlist

Overview of the Watchlist

The Watchlist is a portlet that displays a list of a user's transaction-related items, such as expenses. It's available using the Watchlist icon in the global header. For all users across the site, you can disable or enable predefined Watchlist categories and items, edit their names, and determine how often item counts refresh.

For more information, see the related topics.