3Sales and B2B Service Scheduled Processes

This chapter contains the following:

Customer Data Model

Audit Party Hierarchy

Use the Audit Party Hierarchy scheduled process to validate the party hierarchy setup. Party Hierarchy should adhere to validation rules. Most of the validations are performed inline from import or UI.

When to Use

This scheduled process:

  • Verifies that a party hierarchy setup is valid and logs the details if any validation fails.

Privileges Required

Verify that you have any of the following roles and privileges:

  • Roles:

    • ORA_AR_ACCOUNTS_RECEIVABLE_MANAGER_JOB

    • ORA_AR_ACCOUNTS_RECEIVABLE_MANAGER_SOD_JOB

    • ORA_AR_BILLING_MANAGER_JOB

    • ORA_AR_CUSTOMER_ACCOUNT_ADMINISTRATOR_JOBORA_ZCA_CUSTOMER_RELATIONSHIP_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

    • ORA_ZCH_DATA_STEWARD_MANAGER_JOB

    • ORA_ZCH_MASTER_DATA_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

    • ORA_ZCH_TRADING_COMMUNITY_DATA_STEWARD_JOB

    • ORA_ZPM_CHANNEL_ACCOUNT_MANAGER_JOB

    • ORA_ZPM_CHANNEL_ADMINISTRATOR_JOB

    • ORA_ZPM_CHANNEL_OPERATIONS_MANAGER_JOB

    • ORA_ZPM_CHANNEL_PARTNER_PORTAL_ADMINISTRATOR_JOB

    • ORA_ZPM_CHANNEL_SALES_DIRECTOR_JOB

    • ORA_ZPM_CHANNEL_SALES_MANAGER_JOB

  • Privileges:

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_BATCH_DUTY

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_PROCESS_DUTY

Before You Start

Review the following before scheduling this scheduled process:

  • Compatibility:

    • No compatibility considerations or dependencies.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Notes

Hierarchy Type

Mandatory

Specifies the types of hierarchy.

Customer Hierarchy

Duns and Bradstreet Hierarchy

Partner Hierarchy

Trading Community Partner Hierarchy

None

This parameter is List of Values driven.

PARTY_HIERARCHY_TYPE

Hierarchy Name

Optional

Name of a hierarchy

Any

None

Search and Select

Hierarchy Version

Optional

Version of the hierarchy.

Default: Active version

None

List of Values

Hierarchy Status

Mandatory

Status of the hierarchy.

Active

Inactive

Default: Active status

None

List of Values

HZ_TREE_STATUS

Batch ID

Optional

Batch identifier

N/A

None

Text Input Field

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Modified hierarchy aren't validated and displayed. Any gaps are put into logs. No change is made to the tree.

  • You must monitor the status of scheduled process to know that it was successfully completed.

Classification Hierarchy Generation

Use the Classification Hierarchy Generation scheduled process to flatten the trading community classification hierarchies defined using Manage Classification Categories setup task.

When to Use

Typically, any changes done to classification hierarchies using Manage Classification Categories setup task would be flattened immediately. This scheduled process should be run manually on demand, only when customer has identified issues with flattened data of classification hierarchies. In other words, run this scheduled process whenever changes are made to the classification category. You can run this scheduled process from the Manage Classification Categories setup task or from the schedule process UI.

Privileges Required

Verify that you have the following roles and privileges:

  • Role:

    • Administrators who have access to Manage Classification Categories setup task.

  • Privilege:

    • Run Trading Community Classification Hierarchy Generation (HZ_RUN_TRADING_COMMUNITY_CLASSIFICATION_REPORTING_HIERARCHY_GENERATION_PRIV)

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can execute or schedule this scheduled process when needed.

    • We recommend that you execute or schedule this scheduled process off-peak times.

  • Compatibility:

    • No known dependencies with other scheduled processes.

    • We recommend that you trigger multiple instances of this scheduled process simultaneously because this scheduled process is incompatible with itself.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Notes

Classification Category

Optional

Pick class category to be flattened. If not selected, all categories would be flattened.

Valid values from HZ_CLASS_CATEGORIES table

None

This parameter is List of Values driven.

Flattening method, could either incremental flattening or force flattening. Default is incremental

INCREMENTAL_FLATTENINGFORCE_FLATTENING

None

This parameter is List of Values driven.

Cleanse Addresses Against Postal Reference Files

Standardizes and validates a batch of addresses against country specific postal reference files.

When to Use

This scheduled process is used to generate cleansed records for input data.

Privileges Required

Verify that you have the following privileges or roles:

  • Application Implementation Consultant

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • This batch cleansing scheduled process should be invoked by Address Cleansing jobs.

Parameters

Batch cleansing parameter are passed by parent Address Cleansing jobs.

Delete Master Geography Data for the Selected Country

You can use this scheduled process to delete the master geography data for a particular country. On deleting master geographies, all the related references like territory, tax zone, shipping zone, jurisdiction and so on become invalid. No notifications are sent.

When to Use

This scheduled process is used to delete the geography data for a country.

Privileges Required

Verify that you have the following privileges or role:

  • Role:

    • Application Implementation Consultant

  • Privileges:

    • Run Trading Community Resource Reporting Hierarchy Generation

    • HZ_RUN_TRADING_COMMUNITY_RESOURCE_REPORTING_HIERARCHY_GENERATION_PRIV

    • HZ_RUN_TRADING_COMMUNITY_GEOGRAPHY_NAME_REFERENCING_MAINTENANCE_PRIV

    • HZ_RUN_TRADING_COMMUNITY_IMPORT_BATCH_PROCESS_PRIV

    • ORA_HZRESOURCE_ORGANIZATION_ADMINISTRATOR_DUTY

    • ORA_ZX_TAX_ADMINISTRATION_DUTY_CRM

    • ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

    • ORA_ZCH_MASTER_DATA_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_BATCH_DUTY

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_PROCESS_DUTY

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You must create a support request with proper justification to delete the master geography data for a country.

      Note: When you delete the master geography data, the geography and its children are deleted and all the related territory, tax, and shipping zone references become invalid. So, you must back up this master geography data before deleting the master geography data.
  • Compatibility:

    • This scheduled process is self-incompatible and also incompatible with the Group Territory Geographies. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until status until the first instance is completed.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Country Code

Mandatory

If the country code isn't passed, the job fails with an error message.

Specifies the Country for which data must be deleted.

Example: IN India

None

This parameter is List of Values driven.

Delete or Truncate Interface Tables

You can use this scheduled process to clean up the interface tables to improve the import performance. These import interface tables are for Account, Contact, and Household import.

When to Use

This scheduled process is used to delete or truncate the interface tables, after an import job is completed and the data is moved to the base tables from the interface tables.

Privileges Required

Verify that you have the following privilege or role:

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process based upon your need. This is to remove data from HZ interface tables. If import is used to load high volume data, you can use this scheduled process to clean the data from interface table at regular intervals.

  • Compatibility:

    • This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until the first instance is completed.

Parameters

You might need to specify some of the following parameters:

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Action Code

Mandatory

Action to be performed in interface or table.

Any

No

N/A

Truncate Interface

Optional

Truncate interface.

Any

No

Truncates Interface tables

Note: If there are no values passed this process exits and doesn't delete any tables. This scheduled process doesn't process any data when an active import is in progress.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Check the log or output file.

  • If the scheduled process didn't run successfully, you can re-submit the process after rectifying the error.

  • This scheduled process is idempotent, which means, this scheduled process can be restarted if it failed in the initial run. No cleanup is required.

  • To verify that this scheduled process ran successfully from the application (and not from logs or pages), you can use the count of data deleted or truncated from interface table.

Flatten HZ_GEO_HIERARCHY_CF Columns

You can use this scheduled process to populate column flattened data into the HZ_GEO_HIERARCHY_CF table. 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.

When to Use

Use this scheduled process to:

  • Populate column flattened data into the HZ_GEO_HIERARCHY_CF table. This is useful for the following:

    • Restore missing data in HZ_GEO_HIERARCHY_CF table.

    • Recover from territory assignment errors arising due to missing data in HZ_GEO_HIERARCHY_CF table.

Privileges Required

Verify that you have the following privilege or role:

  • Role:

    • Application Implementation Consultant

  • Privilege:

    • Run Trading Community Resource Reporting Hierarchy Generation

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process on need basis.

  • Compatibility:

    • This scheduled process is self-incompatible and also incompatible with these processes:

      • Group Territory Geographies

      • Territory Geography Import

      • Territory Geography Migration Import

      • Delete Master Geography Data for the Selected Country

      If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until status until the first instance is completed.

Parameters

None.

Generate Data Quality Keys

Generates key values for new or updated accounts, contacts and addresses which are used for duplicate prevention and identification.

When to Use

This scheduled process:

  • Generates all record keys for account, contact, and address in rebuild for current active configuration.

  • Generates new created or updated record keys for account, contact, and address in incremental key generation job for current active configuration.

  • Generates record keys for account, contact, and address for a period of time for any selected configuration when required.

Privileges Required

Verify that you have the following privilege or roles:

  • Application Implementation Consultant

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency

    • You can run this scheduled process when required or schedule it for appropriate frequency, such as minutes in repeat.

  • Compatibility:

    • This scheduled process is self-incompatible for configuration code. If multiple instances are submitted for the same configuration code, the first instance runs and subsequent instances remain in Wait status.

Parameters

The following table describes the list of parameters when the scheduled process must be run immediately.

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Match Configuration

Mandatory

Specify the configuration code.

Any

No

N/A

Start Time

Mandatory

Specify when the scheduled process must start.

Any

No

N/A

End Time

Mandatory

Specify when the scheduled process must end.

Any

No

N/A

The following table describes the list of parameters when the scheduled process must be scheduled to run at regular intervals. Use the Using a Schedule option in the Schedule tab to schedule to run the process.

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Frequency

Mandatory

Specify how frequently the scheduled process must be run.

Any

No

N/A

Time Between Runs

Mandatory

Specify the time between two scheduled process runs.

Any

No

N/A

Start Date

Mandatory

Specify the start date of the schedule.

Any

No

N/A

End Date

Mandatory

Specify the end date of the schedule.

Any

No

N/A

Identify Duplicate Organization Person or Location Records

Identifies duplicates within a batch of records or against existing records in the database instance.

When to Use

This scheduled process is used to generate matched records for candidates with current active configuration.

Privileges Required

Verify that you have the following privilege or roles:

  • Application Implementation Consultant

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • This batch match scheduled process should be invoked by Duplicate Identification or import jobs

Parameters

Batch match parameter are passed by parent duplication Identification or import jobs.

Import Bulk Customer Data

You can use this scheduled process to import customer data. You can use the Data Import UI to check if the data was imported.

When to Use

This scheduled process is used to import customer accounts data into the application.

Privileges Required

Verify that you have the following privileges or role:

  • Role:

    • Master Data Management Application Administrator

  • Privileges:

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_BATCH_DUTY

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_PROCESS_DUTY

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process on need basis or schedule it for appropriate frequency, such as daily once.

  • Compatibility:

    • This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until the first instance is completed.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Batch ID

Optional

Batch ID of the import flow.

Any

No

N/A

Batch Name

Optional

Name of the batch

Any

No

N/A

Source System

Optional

Source System or Origination System of the batch data.

Any

No

N/A

Batch Object

Optional

Import object of the Batch.

Any

No

N/A

Maintain Party and Location Current Record Information

You can use this scheduled process to create parties with party usage of HR_EMPLOYEE or HR_CONTINGENT_WORKER for a person record in Human Capital Management (HCM). Person record of type pending worker (future dated) and non-workers, defined in HCM, are processed if the party doesn't exist. This scheduled process can be augmented to process other types of Person like employee and contingent worker along with pending workers and non-workers by changing the value of the ORA_HZ_ENABLE_MPLCRI_ACTIVE_WORKER profile option to Y. Ensure that you don't schedule to run this scheduled process and the HCM TCA Sync scheduled process at the same time. This scheduled process doesn't update existing records.

When to Use

This scheduled process is used to:

  • De-normalize the future dated current location profile, party sites, and contact points based on today's date with extended support to future end-dated records.

  • Create a party record for an Human Capital Management person record, if the party doesn't exist. This enables direct payment methods creation for non-workers.

  • Synchronize only the first name and the last name of the HR person of the record.

  • Support both future and terminated workers.

Privileges Required

Verify that you have the following privileges or roles:

  • Application Implementation Consultant

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • When there is a requirement to create future or terminated workers as TCA person parties to complete business flows such as setting up direct payment methods, then run this ESS job.

    • The scheduled process must be run when HCM workers are created from HCM interfaces like HDL loader and then to sync workers into TCA person parties. HCM and TCA don't sync when this scheduled process isn't running.

  • Compatibility:

    • This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs and subsequent instances remain in Wait status.

    • This scheduled process is also incompatible with Employee Resource File Import scheduled process but not with any other scheduled processes. The Maintain Party and Location Current Record Information scheduled process is skipped if the Employee Resource File Import scheduled process is already running.

Parameters

None.

Party Hierarchy Generation

Use the Party Hierarchy Generation scheduled process to execute Flatten Party Hierarchy Rows and Columns.

When to Use

You must run this scheduled process in the following scenarios:

  • If there is a change in tree hierarchy using any channel, such as import, REST, SOAP UI, custom groovy, OIC integration and so on. By default, the tree flattening gets executed automatically.

  • After changes are made to the hierarchy, viewing or fetching of hierarchical data, you may run this scheduled process if the hierarchical data appears to be inaccurate.

Privileges Required

Verify that you have any of the following roles or privileges:

  • Roles:

    • ORA_ZCA_CUSTOMER_RELATIONSHIP_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

    • ORA_ZCH_MASTER_DATA_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB

  • Privileges:

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_BATCH_DUTY

    • ORA_MANAGE_TRADING_COMMUNITY_IMPORT_PROCESS_DUTY

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • On need basis post any changes made to the hierarchical data.

    • Run this scheduled process if hierarchical data appears to be inaccurate.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Notes

Hierarchy Type

Mandatory

Specifies the types of hierarchy.

Customer Hierarchy (default)

Duns and Bradstreet Hierarchy

Partner Hierarchy

Trading Community Partner Hierarchy

None

This parameter is List of Values driven.

PARTY_HIERARCHY_TYPE

Hierarchy Name

Optional

Name of a hierarchy.

Any

None

Search and Select

Hierarchy Version

Optional

All active versions

Version of the hierarchy.

Default: Active version

None

List of Values

Flattening Method

Mandatory

Method to be applied for flattening.

  • Incremental Flattening (default)

  • Force Flattening

None

List of Values

HZ_TREE_FLATTENING_METHODS

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • You must monitor the status of scheduled process to know that it was successfully completed.

  • If the scheduled process fails, it restarts from the beginning.

Purge Cleanse and Match Batch Data

This scheduled process purges all data quality batches.

When to Use

This scheduled process purges all data quality batches created from hub to find duplicate or cleanse address data. This scheduled process is triggered when the user selects one or more batches in the duplicate identification or address cleansing UI with status new, completed, error, or completed with error.

Privileges Required

Verify that you have the following privilege or role:

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency

    • It's recommended to run this scheduled process on need basis. This process is submitted internally after you select the list of batches to be deleted permanently using the UI. We don't recommended that you schedule this process to run on regular intervals.

  • Compatibility:

    • This scheduled process is self-incompatible. No two jobs can be run at the same time. The scheduled process goes into wait state if there is already one running.

    • We recommend that this scheduled process is run in off peak hours when there is very minimal activity.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • The end user must monitor the status of the purge job from schedule process UI using job ID displayed when a batch data is purged.

  • Download the scheduled process server logs from schedule process UI to analyze root cause of failure.

  • A new scheduled process can be submitted from the schedule process UI. This scheduled process takes batch identifier for an existing cleanse or match batch as parameter that should be deleted, this parameter is optional and isn't required for scheduling the job.

Purge Data Quality Keys

This scheduled process purges keys.

When to Use

This scheduled process purges keys generated by the Enterprise Data Quality server for organization or contact entities. This process is triggered when the user selects a cloned inactive match and configuration, and deletes it.

Privileges Required

Verify that you have the following privilege or role:

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency

    • It's recommended to run this scheduled process on need basis. This process is submitted internally after you select the list of batches to be deleted permanently using the UI. We don't recommended that you schedule this process to run on regular intervals.

  • Compatibility:

    • This scheduled process is self-incompatible. No two jobs can be run at the same time. The scheduled process goes into wait state if there is already one running.

    • We recommend that this scheduled process is run in off peak hours when there are no new accounts or contacts getting created using import, fuse UI and so on.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • You must monitor the schedule process UI to check the status of the purge keys process once created using ID displayed when user selects match configuration for purging.

  • Download the scheduled process server logs from schedule process UI to analyze the root cause of failure.

  • A new scheduled process can be submitted from schedule process UI. Internally it resumes from the point of failure.

This scheduled process purges inactive data. This scheduled process reads the configuration information such as age of inactive record and filter criteria. It then purges parent and child records that meet the filter criteria.

When to Use

You can use this scheduled process to purge sales contact information that meet the specified filter criteria. There are no processes that must be run after running this process.

Privileges Required

Verify that you have the following privileges or role:

  • Privilege

    • ORA_ZBS_SALES_ADMINISTRATOR_JOB

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process on need basis or schedule it for appropriate frequency, such as daily once.

  • Execution Time

    • The execution time for a single data record is 1 to 2 minutes.

    • The execution time for a batch job or certain volume of data say 10k is around 1 hours 30 minutes to 2hours.

  • Compatibility

    • This scheduled process is incompatible with itself and any other scheduled process.

Parameters

Parameter Optional or Mandatory Parameter Values Description Special Combinations Required Notes

Name

Mandatory

Sales Contact

Purges inactive party records based on defined filter criteria for Name parameter.

No

N/A

Troubleshooting Information

You will be notified about the scheduled process completion once that particular process ID status becomes succeeded.

Populate Location Latitude and Longitude Information

You can set up geocoding for countries to use in applications that use geography data. Geocoding finds the latitude and longitude coordinates from geographic data such as street addresses or Postal Codes. For example, on a mobile phone you can view which customer and contact addresses are close to your current location. The application integrates the geocoding with eLocation, which is a geocoding service provided by Oracle. After you enable geocoding, you run this scheduled process at regular time intervals so that newly created or updated locations are selected and geocoded.

When to Use

You can use this scheduled process to populate latitude and longitude information for addresses in the HZ_LOCATIONS table.

Privileges Required

Verify that you have the following privilege or role:

  • Role:

    • Application Implementation Consultant

  • Privilege:

    • Run Geocode Loader

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this process as needed or schedule it to run once a week.

  • Compatibility:

    • This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until the first instance is completed.

Note: For more information about the steps to be performed before running this scheduled process, see the Related Topics section.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Country Code

Optional

Country Code of locations for which latitude and longitude are to be populated.

Example: IN

None

N/A

Start Date

Optional

Specifies the begin Location Effective Start Date.

Date

Format : mm/dd/yy

Example: 12/31/19

Start Date must be earlier than End Date

N/A

End Date

Optional

Specifies the begin Location Effective End Date.

Date

Format : mm/dd/yy

Example: 12/31/19

End Date must be later than Start Date

N/A

Regenerate Geocode

Optional

Specifies if coordinates must be regenerated for existing ones.

Y

N

No

N/A

Batch Size

Optional

Specifies the number of locations to be processed in a single sub-process.

Numeric Value

Maximum value 1000

N/A

Note: All the parameters are optional. If this scheduled process is run without any parameters, the process picks all addresses of countries for which geocoding is enabled. This scheduled process can populate a maximum of 10,000 address locations. If the total number of addresses to be geocoded are more than 10,000, you may have to run this scheduled process many times. This scheduled process populates Latitude and Longitude values in the HZ_LOCATIONS table. This scheduled process continues to pickup already processed addresses for which the latitude or longitude parameters are null.

Reporting Hierarchy Generation

You can use this scheduled process to generate the resource reporting hierarchy for a given internal resource organization hierarchy, a sales, or a marketing organization hierarchy. This scheduled process also updates the reporting hierarchy when changes occur in the organization hierarchy.

You can run this scheduled process when new resources are created using File-based Data Import or the Employee Resource Import Management when the profile option Automated Resource Hierarchy Generation Enabled (HZ_AUTO_RES_HIERARCHY_GEN) is set to No.

When to Use

This scheduled process:

  • Updates the reporting hierarchy in accordance to the changes in internal resource or partner organization hierarchy. This scheduled process updates the reporting hierarchy in accordance with the changes in internal resource hierarchy. The resource's reporting manager isn't updated unless you run this scheduled process.

  • Must be run after you make any changes to the hierarchy such as changing the manager or the organization.

Privileges Required

Verify that you have the following privilege or roles:

  • Roles:

    • Application Implementation Consultant

    • Master Data Management Application Administrator

  • Privilege:

    • Run Trading Community Resource Reporting Hierarchy Generation

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process when the hierarchy has been rebuilt using Employee Resource File-based Data Import and when hierarchy profile option Automated Resource Hierarchy Generation Enabled (HZ_AUTO_RES_HIERARCHY_GEN) is set to No.

    • You can run this scheduled process after Resource User REST API or Employee Resource Import Management is executed.

    • You can run this scheduled process when the same resource is visible multiple times in Team Members tab of Opportunity.

    • You can run this scheduled process as needed or at appropriate intervals, such as daily.

  • Compatibility:

    • This scheduled process is self-incompatible. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until the first instance is completed.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Tree Structure Code

Mandatory

Specifies the type of resource hierarchy.

RESOURCE_ORG_TREE_STRUCTURE PARTNER_ORG_TREE_STRUCTURE

None

This parameter is List of Values driven.

Selecting RESOURCE_ORG_TREE_STRUCTURE builds the internal resource hierarchy.

Selecting PARTNER_ORG_TREE_STRUCTURE builds the corresponding partner tree.

Tree Code

Mandatory

Specifies the tree code.

GLOBAL_SALES_MARKETING

None

This parameter is List of Values driven.

Select 'GLOBAL_SALES_MARKETING' for internal resource hierarchy.

Select corresponding tree code for Partner Hierarchy.

Tree Version ID

Mandatory

Specifies the version ID of the Tree.

Any

None

This parameter is List of Values driven.

Select corresponding Tree Version ID for the hierarchy that must be re-generated.

Synchronize Financials Accounts and Contacts with CX Cloud

Customer accounts and contacts in Oracle Financials Cloud are an integral part of the billing process. Users create or import account and contact records in Financials Cloud. After they're in Financial Cloud, a synchronization process synchronizes the records to Oracle CX Cloud, thus making sales representatives aware of the details of sales accounts that exist in Financials Cloud. Without this synchronization, sales representatives may not know when their sales accounts become actual billing accounts.

When to Use

After users create customers in Financials Cloud, use a scheduled process to sync the records from Financials to CX Cloud.

Users can find and create customers in the Manage Customers UI in Financials Cloud. New organization customers are created by providing the customer name, address details, and the address purpose, such as sell-to or bill-to. Similarly, users can update existing customers in the same UI.

After a customer is created or updated, you run the process to sync the records, which includes customers and contacts.

Privileges Required

Verify that you have the following privileges or roles:

Role:

  • Sales Administrator

Privileges:

  • ZCM_CREATE_SALES_PARTY_CONTACT_PRIV

  • ZCM_CREATE_SALES_ORGANIZATION_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can execute or schedule this scheduled process when needed.

  • Compatibility:

    • This scheduled process is self-incompatible. No two jobs can be run at the same time. The scheduled process goes into wait state if there is already one running.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • You must monitor the schedule process UI to check the status of the synchronization.

  • Note any errors that indicate any failures.

Synchronize User GUID

You can use this scheduled process to synchronize the user GUID of users including Employees, Contingent Workers, and Partner Contacts in CRM database.

When to Use

This scheduled process is used to:

  • Update the user GUID in CRM database for users.

  • Remove the user GUID from CRM database for inactive parties.

  • Remove invalid user GUID from CRM database that doesn't exist in HCM database.

Privileges Required

Verify that you have the following privileges or roles:

  • Application Implementation Consultant

  • Master Data Management Application Administrator

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency

    • You can run this scheduled process when some users aren't properly connected to Person Parties.

    • You can run this scheduled process on ad hoc basis or schedule it for appropriate frequency, such as daily once.

  • Compatibility

    • No self-incompatibility defined.

Parameters

None.

Validate Geographies of Addresses Against Master Geographies

This scheduled process helps you validate an address against master geography data and generates geography naming references.

When to Use

This scheduled process to validate address data against master geographies.

Privileges Required

Verify that you have the following privilege or role:

  • Role:

    • Application Implementation Consultant

  • Privilege:

    • Run Trading Community Resource Reporting Hierarchy Generation

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • Invoked whenever the geography naming references data for a location is generated or refreshed..

  • Compatibility:

    • You can run this scheduled process for the following reasons:

      • When you must generate or refresh the geography naming references data for a location.

      • After creating new locations or updating existing locations using import and when geography naming references generation at the time of creation is turned off.

      • When the master geography hierarchy has changed after the geography naming references data is computed and we require to re-compute the geography naming references data.

      • Group Territory Geographies

      • Delete Master Geography Data for the Selected Country

      If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until status until the first instance is completed.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Location Table Name

Mandatory

Specifies the location table.

HZ_LOCATIONS

PER_ADDRESSES_F

None

N/A

Run Type

Mandatory

Specifies the Run Type.

ALL

ERROR

NEW

None

ALL-Validates all Locations

Error-Re-validates erroneous records

NEW-Validates new locations

Usage Code

Optional

Specifies the validation usage code

GEOGRAPHY TAX

None

N/A

Country Code

Optional

Specifies the ISO Country Code for which the process is run

Example: US

None

N/A

From Location ID

Optional

Specifies the beginning Location ID from which validation should be run

Numeric Value

From Location ID should be less than To Location ID

N/A

To Location ID

Optional

Specifies the ending Location ID till which validation should be run

Numeric Value

To Location ID should be greater than From Location ID

N/A

Start Date

Optional

Specifies the begin Location Effective Start Date

Date

Format : YYYY/MM/DD

Example: 2019/12/24

Start Date should be lower than End Date

N/A

End Date

Optional

Specifies the begin Location Effective End Date

Date

Format : YYYY/MM/DD

Example: 2019/12/24

End Date should be higher than Start Date

N/A

Knowledge Management

Knowledge Article View Aggregation

Use this scheduled process to aggregate data on the number of articles that have been viewed.

This scheduled process takes data from action capture tables, moves them to analytics staging tables for processing, and writes them to analytics aggregate tables. The end result is that reporting tables named cso_article_stats and cso_popular_answers are populated.

When to Use

This process can be run anytime after you have configured the knowledge management functional area. This process has no dependencies on other processes.

Privileges Required

Verify that you have the following privilege or role:

  • Role

    • Knowledge Manager

  • Privilege

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • Once started, this process runs continuously and aggregates new data every hour. This process can be auto scheduled to run every hour.

  • Execution Time:

    • Within one hour

  • Compatibility:

    • You can't run more than one instance of this scheduled process at the same time. If multiple instances are submitted, the first instance runs and subsequent instances remain in blocked status until the first instance is completed.

Parameters

None.

Troubleshooting Information

You can use the scheduled process page or logs to verify the status of the scheduled process.

Knowledge Content Batch Process

You can use this scheduled process to update Knowledge categories and products to reflect recent changes to Service and Human Capital Management products and categories.

When to Use

This scheduled process must be run periodically whenever a customer implements the Knowledge Management functional area. This scheduled process ensures that the Knowledge Management functional area uses current product and category information.

Privileges Required

Verify that you have the following privilege or role:

  • Role

    • Knowledge Manager

  • Privilege

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency

    • Schedule the job to run once daily.

    • You can schedule this job at any time of the day.

  • Execution Time:

    • The execution time depends on the number of changes made to categories and products since the previous execution.

  • Compatibility:

    • You can't run this scheduled process while another instance of the scheduled process is running.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • You can use the notification settings of the scheduled process to be notified for any combination of error, warning, or success statuses.

  • If this scheduled process fails, you can restart the process without any additional cleanup activity.

Knowledge Search Batch Process

You can use this scheduled process to update Knowledge search to reflect any changes to knowledge base content.

This scheduled process updates the Knowledge search index so that new, modified, or deleted knowledge articles or web content is available to Knowledge search users.

When to Use

This scheduled process must be scheduled to run periodically whenever a customer implements the Knowledge Management functional area. This scheduled process must be run so that the latest changes to the knowledge articles are available to Knowledge users.

Privileges Required

Verify that you have the following privilege or role:

  • Role

    • Knowledge Manager

  • Privilege

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • The job should be scheduled to run every fifteen minutes

    • We have no recommended time to schedule the process

  • Execution Time

    • The execution time for single data record is 5 minutes

    • The execution time of the scheduled process depends on the amount of changed knowledge articles and the size of the product tree. The execution time ranges from 5 minutes to 2 hours.

  • Compatibility:

    • Knowledge Content Batch Process must be run before Knowledge Search Batch Process for product sync.

    • There may be potential impact on the server performance while running this scheduled process.

    • Running multiple instances of this scheduled process in parallel may create issues.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • If the scheduled process isn't successful, then the xtext process resumes and continues to run.

  • You can restart the scheduled process if it failed in the initial run. No clean up is required before the restart.

  • You can go to the Search Dictionary Manage page and click the Content Processing tab to check the status of the scheduled process. You can verify the results from the Search results by asking a question from My Knowledge page.

Service Request Management

Aggregate Service Requests

Use the Aggregate Service Requests scheduled process to create Business Intelligence reports on service performance that provide an aggregated view as it relates to interactions, compliance, and knowledge article usage.

It runs an Extract, Transform, Load (ETL) job to aggregate both transactional service request data and interaction data to populate tables at the back end. Business Intelligence reports created using the CRM - CRM Service Request Summary and CRM - CRM Interaction Aggregate subject areas query the back end aggregate tables.

When to Use

The scheduled process must be run to use the CRM - CRM Service Request Summary and CRM - CRM Interaction Aggregate subject areas for creating Business Intelligence reports when needed. Ready-to-use reports dependent on these subject areas don't show any data or show stale data unless this process is run.

For a list of ready-to-use reports dependent on these subject areas, refer to the reports list in the Related Topics section.

Privileges Required

Verify that you have the following privilege or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • The recommended frequency is hourly

  • Execution Time:

    • The execution time for single data record is less than 1 minute.

    • The execution time for batch job on volume of 50K records is less than 5 minutes.

  • Compatibility:

    • When run for the first time, the process will take significantly longer to execute, since all data in the relevant tables will be loaded.

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There should be only one instance of the job running at any one time, otherwise there will be issues.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself, therefore only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If the scheduled job doesn't run successfully, the next scheduled instance processes data from both jobs.

  • This scheduled process idempotent, and no cleanup activity is required if the job fails.

  • Check the Business Intelligence reports from the following subject areas to verify that this scheduled process is successful:

    • CRM - CRM Service Request Summary subject area with the following metrics and look for recent data:

      • Time

      • Facts > Service Request Summary Compliance Facts

      • Facts > Service Request Summary Interaction Facts

      • Facts > Service Request Summary Knowledge Article Facts

    • CRM - CRM Interaction Aggregate subject area with the following metrics and look for recent data:

      • Time

      • Facts > Interaction Aggregate Facts

Fully Loads Action Plan Actions Data for Reporting

Use the Fully Loads Action Plan Actions Data for Reporting scheduled process to create Business Intelligence reports using the Service - CRM Service Request Action Plans Real Time subject area.

The goal of the process is to provide a consolidation of the action owner from service requests and activity related records.

When to Use

This process must be executed when there are owners assigned or updated for service requests or for activities records. This is an on-demand job. You must run this job in the following scenarios:

  • Any time action plan actions data must be fully refreshed

Privileges Required

Verify that you have the following privilege or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • Based on need

  • Execution Time:

    • For single data record, less than 1 second

    • For batch job on volume of 10K records, less than 1 minute

  • Compatibility:

    • No other processes are triggered when this job runs

    • No potential impact on the server performance while this job is running

    • There should be only one instance of the job running at any one time, otherwise there will be issues

    • There are no issues with business processes executing in parallel with this job

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system

  • If the scheduled job doesn't run successfully, the next scheduled instance processes data from both jobs

  • This scheduled process idempotent, and no cleanup activity is required if the job fails

  • To verify that this scheduled process is running successfully, run a Business Intelligence report from the Service - CRM Service Request Action Plan Actions Real Time subject area with the following metrics and search for recent data:

    • Time

    • Facts > Service Request Action Plan Action Facts

Execute Full Load of Cross-Channel Interaction Data for Reporting

Use the Execute Full Load of Cross-Channel Interaction Data for Reporting scheduled process to create business intelligence reports using the CRM - CRM Interaction Aggregate subject area.

Fully loads cross-channel interaction data, or refreshes the data based on a particular date, for reporting using the CRM - CRM Interaction Aggregate subject area.

When to Use

You must run this scheduled process in the following scenarios:

  • This process must be executed when there are interactions crossing channels and agents. This is an on-demand scheduled process.

  • Any time interaction data must be refreshed from a specific date.

Privileges Required

Verify that you have the following roles or privilege:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job, the following privilege is required

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You can run this scheduled process based on need

  • Execution Time:

    • For single data record, less than 1 sec.

    • For batch job on volume of 10K records, less than 1 minute.

  • Compatibility:

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There should be only one instance of the job running at any one time, otherwise there will be issues.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time.

Parameters

You might need to specify some of the following parameters:

Parameter Optional or Mandatory Description Parameter Value Special Combinations Required Notes

RefreshDate

Mandatory

Date from which data must be loaded or refreshed in the cross channel interaction table.

Date Values

None

This parameter is date which is List of Values driven.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If the scheduled job doesn't run successfully, you must run the job again manually.

  • This scheduled process idempotent, and no cleanup activity is required if the job fails.

  • To verify that this scheduled process is loaded with the correct data, use a business intelligence report from the CRM - CRM Interaction Aggregate subject area with the following metrics and check for recent data:

    • Time

    • Facts > Interaction Cross Channel Aggregate Facts.

Incrementally Loads Action Plan Actions Data for Reporting

Use the Incrementally Loads Action Plan Actions Data for Reporting scheduled process to create business intelligence reports using the Service - CRM Service Request Action Plans Real Time subject area.

The goal of the process is to provide a consolidation of the action owner from service requests and activity related records.

When to Use

This process must be executed when there are owners assigned or updated for service requests or for activities records.

Privileges Required

Verify that you have the following privilege or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • The recommended frequency is hourly

  • Execution Time:

    • For single data record, less than 1 second

    • For batch job on volume of 10K records, less than 1 minute

  • Compatibility:

    • Before scheduling this job, it's recommend that the job Fully Loads Action Plan Actions Data for Reporting is run once to fully populate the data

    • No other processes are triggered when this job runs

    • No potential impact on the server performance while this job is running

    • Only one instance of the job must be running at a time to avoid any potential issues

    • There are no issues with business processes executing in parallel with this job

    • This scheduled process is incompatible with itself, therefore only one instance of the job should be running at any particular time

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system

  • If the scheduled job doesn't run successfully, the next scheduled instance will process data from both jobs

  • This scheduled process idempotent, and no cleanup activity is required if the job fails

  • To verify that this scheduled process is running successfully, run a Business Intelligence report from the Service - CRM Service Request Action Plans Real Time subject area with the following metrics and search for recent data:

    • Time

    • Facts > Service Request Action Plan Facts

Execute Incremental Load of Cross-Channel Interaction Data for Reporting

Use the Execute Incremental Load of Cross-Channel Interaction Data for Reporting scheduled process to create Business Intelligence reports using the CRM - CRM Interaction Aggregate subject area.

Incrementally loads cross-channel interaction data, for reporting using the CRM - CRM Interaction Aggregate subject area.

When to Use

This process must be executed when there are interactions crossing channels and agents.

Privileges Required

Verify that you have the following privilege or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • The recommended frequency is hourly

  • Execution Time:

    • For single data record, less than 1 sec.

    • For batch job on volume of 10K records, less than 1 minute.

  • Compatibility:

    • Before scheduling this job it's recommend that the job Execute Full Load of Cross-Channel Interaction Data for Reporting is run once to fully populate the data.

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself, therefore only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If the scheduled job doesn't run successfully, the next scheduled instance processes data from both jobs.

  • This scheduled process idempotent, and no cleanup activity is required if the job fails.

  • To verify that this scheduled process is running successfully, create a Business Intelligence report from the CRM - CRM Interaction Aggregate subject area with the following metrics and search for recent data:

    • Time

    • Facts > Interaction Cross Channel Aggregate Facts

Execute Incremental Load of SR Audit Data for Reporting

Use the Execute Incremental Load of SR Audit Data for Reporting scheduled process to create business intelligence reports using the Service - CRM Service Request Lifecycle subject area.

Incrementally loads SR audit data added since the previous run of the process, transforming the raw source data into a model that's better suited for ad-hoc Business Intelligence reporting.

When to Use

The scheduled process must be run to use the Service - CRM Service Request Lifecycle subject area for creating ad-hoc Business Intelligence reports. Ready-to-use reports dependent on these subject areas don't show any data or show stale data unless this process is run regularly.

For a list of ready-to-use reports dependent on these subject areas, see the reports list in the Related Topics section.

Privileges Required

Verify that you have the following roles or privilege:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job, the following privilege is required

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • The recommended frequency is hourly.

  • Execution Time:

    • The execution time for single data record is less than 2 seconds.

    • The execution time for batch job on volume of 50K records is less than 1 minute.

  • Compatibility

    • When run for the first time, the process will take significantly longer to execute, since all audit data for SRs created since the start of the previous month will be loaded. Before running the process for the first time, ensure that SR auditing is enabled. If no SR audit data is available, the process will exit without creating any data for the Service - CRM Service Request Lifecycle subject area.

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There can be only one instance of the job running at any one time, otherwise there will be issues. A built-in locking mechanism prevents a second instance of the job from being started before the current instance has finished.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If no fact data is available in the Service - CRM Service Request Lifecycle subject area, but the scheduled process is running successfully, check to ensure the SR auditing is enabled.

  • This scheduled process is idempotent, and no cleanup activity is required if the job fails.

  • When the scheduled process starts it will attempt to obtain a process lock. If no other instance of the process is running, it will be successful. Upon successful completion or in the event the process fails gracefully, the lock will be released.

  • If the scheduled process is unable to obtain a process lock, and no other instance of the process is running, the lock will automatically expire after 24 hours. To manually release the lock sooner, run the process Unlock Scheduled Process that Incrementally Loads SR Audit data.

  • To verify that this scheduled process is loaded with the correct data, use a business intelligence report from the Service - CRM Service Request Lifecycle subject area with the following metrics and check for recent data:

    • Time

    • Facts > Service Request Lifecycle Facts.

Monitor Action Plan Actions

Use the Monitor Action Plan Actions scheduled process to initiate Action Plans as well as evaluate and update the Status and Due Dates of actions within Action Plans.

An agent can add one or more Action Plans to Oracle CX Sales and B2B Service objects and each Action Plan can have a list of actions to be performed by the agent or other Oracle CX Sales and B2B Service users.

  • On Initialization of an Action Plan, the process starts all initial actions in the plan and calculates the projected dates for the Action Plan and all actions in the plan.

  • As actions in the plan are performed by users, the status of the Action Plan and the status of actions in the plan are updated.

  • If an action requires an object be created (such as a new Service Request), the process creates the object for that step in the Action Plan.

  • If an action is added or deleted from a plan, the process updates the plan's projected dates.

  • In all of these scenarios, the process also executes all related Attribute Mappings.

When to Use

This process must be executed when objects (such as Service Requests) have related Action Plans.

  • This process doesn't have any prerequisite processes.

  • This process is used to initiate Action Plans as well as evaluate and update the status and due dates of actions within Action Plans.

  • Action Plans, as well as any associated objects, may be impacted if this process isn't executed as recommended.

Privileges Required

Verify that you have the following privilege or role:

  • Sales Administrator job role.

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency: Every 15 minutes.

  • Execution Time:

    • Execution Time varies based on the complexity and number of Action Plans being evaluated.

  • Compatibility:

    • There are no dependent scheduled process that should be considered before or after running this scheduled process.

    • There are no other scheduled process, business processes, integration processes, or events that the execution of the current scheduled process triggers.

    • No potential impact on the server performance while running this scheduled process.

    • Only a single instance of this scheduled process can be executed.

    • Any business processes can't be executed in parallel with this scheduled process execution.

    • This scheduled process is incompatible with itself.

Parameters

Every time the scheduled process runs, it queries a specific number of plans to be processed. The scheduled process divides these plans into equal batches of sub requests, with each batch processed by an asynchronous sub process.

Name Optional or Mandatory Description Values Notes

SVC_AP_JOB_MAX_RECORDS

Optional

Total number of plans that the scheduled job will process.

1000

Maximum value is 1000; any value greater than 1000 is treated as 1000.

SVC_AP_JOB_THREADS

Optional

Maximum number of asynchronous sub processes in which all plans will be equally divided.

1 to 10

None.

SVC_AP_JOB_BATCH_SIZE

Optional

Minimum number of plans for each sub process.

greater than 20

No maximum value; any value less than 20 is treated as 20.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • On the Scheduled Processes page, the process status changes to Succeeded on completion of the job.

  • If the scheduled process didn't run successfully, on the Scheduled Processes page, the process status changes to Error and the scheduled process restarts automatically. If the error status persists, an administrator should contact Oracle Support.

  • This scheduled process can be restarted after a failure, but it's recommended that an administrator investigate the issue causing the failure.

Monitor Service Request Milestones

Use the Monitor Service Request Milestones scheduled process to periodically check open milestones on service requests to see whether they have passed either the warning threshold or expiration date and time.

This process reviews all service request milestones that are open and not paused. For each milestone, the process does the following:

  • raises a warning for milestones that have passed the warning threshold identified in the coverage, without being completed

  • sets expiry of milestones that have passed the due date and time without being completed

When to Use

You can run this scheduled process when you're using service request milestones to track service level agreements and other commitments. If you don't schedule this process to run, service request milestones aren't in warning or expired states. The downstream processes that rely on these states may be impacted. An example of such downstream processes is workflow e-mail that you may have configured.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles

    • Application roles such as Service Request Administrator, HR Service Request Administration role

  • Privilege

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • It is recommended to schedule this process to run every 15 minutes, if business requirements permit. If business requirements dictate, the process can be scheduled for every 5 minutes depending on volume.

  • Execution Time:

    • Less than 10 seconds for a single record

    • Less than 3 minutes for 10k records (open milestones)

  • Compatibility:

    • No compatibility considerations or dependencies.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • While scheduling the job, there is an option to provide recipient details for notification of the process completion.

  • If the scheduled process didn't run successfully, the compliance of outstanding milestones and warnings aren't updated, and no compliance nor warning notifications are sent.

  • If the job fails for some reason, there is no additional cleanup required; the next time the job runs, all pending records are found and processed accordingly.

  • You can identify if the job has run successfully by confirming that non-compliant milestones have been marked as Expired by setting ComplianceFlag to N within the expected time frame. Similarly, milestones within the warning threshold time to expiration is marked as Warned by setting WarnedFlag to Y.

Purge Interactions

Use the Purge Interactions scheduled process to purge the SVC_INTERACTIONS, SVC_INTERACTION_REFS, and SVC_MCA_INTERACTION_SUMMARY tables.

This process deletes records in the SVC_INTERACTIONS, SVC_INTERACTION_REFS and SVC_MCA_INTERACTION_SUMMARY tables that are older than the specified number of days, are in a closed status and not associated with any open business objects. The retention period is specified using the profile option SVC_INTERACTION_RETENTION_DAYS.

When to Use

This process is used to reduce space in the database consumed by interactions. Running this scheduled process removes interactions that are older than the specified period. To be deleted, interactions must adhere to all the following criteria:

  • They must be older than the specified number of days.

  • They must be in a closed state.

  • They must not be associated with an open business objects.

  • If they have a parent interaction, the parent must be in a closed state.

  • If they have child interactions, the child interactions must all be in a closed state.

Note: Removing interactions removes entries from the Interaction History page. This page can be used to view corresponding chat transcripts and wrap-up details.

Privileges Required

Verify that you have the following privileges:

  • FUSION_APPS_CRM_ESS_APPID

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • The frequency is dictated by your data retention requirements.

  • Execution Time:

    • This scheduled process should complete quickly. But the execution time is dependent on the amount of data being deleted.

  • Compatibility:

    • This scheduled process doesn't affect the performance.

Parameters

There are no parameters for this scheduled process. This scheduled process uses the SVC_INTERACTION_RETENTION_DAYS profile option to control the size of the retention window.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • If this scheduled process fails, the next run should pick up and delete any data older than the specified retention period.

  • If an interaction doesn't get purged, verify that there are no open business objects associated with the interaction. Also verify that all child or parent interactions are closed.

Purge Omnichannel Events

Use the Purge Omnichannel Events scheduled process to purge the SVC_OMNI_EVENTS table.

This process deletes records in the SVC_OMNI_EVENTS table that are older than the specified number of days. The retention period is specified using the profile option SVC_OMNI_EVENTS_RETENTION_DAYS.

When to Use

This process is used reduce space in the database consumed by Omnichannel events. Running this scheduled process removes all events that are older than the specified period. Scheduling this process effectively limits the Omnichannel reports to the time window represented by the number of days passed into the process.

Privileges Required

Verify that you have the following privilege or role:

  • FUSION_APPS_CRM_ESS_APPID user

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • The frequency is dictated by your data retention requirements.

    • If you must retain only 30 days of data, you can run the job every day.

  • Execution Time:

    • This job should complete fairly quickly. But the execution time is dependent on the amount of data being deleted.

  • Compatibility:

    • This job doesn't affect the performance of the running system.

Parameters

There are no parameters to run this scheduled process. This process uses the SVC_OMNI_EVENTS_RETENTION_DAYS profile option to control the size of the retention window.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • If the job fails, the next run should pick up and delete any data older than the specified retention period.

Refresh SVC_BI_QUEUE_RESOURCES Table

Use the Refresh SVC_BI_QUEUE_RESOURCES table scheduled process to create business intelligence reports using the Service - CRM Service Queue Resources Real Time subject area.

It loads Business Intelligence queue resources data for reporting using the Service - CRM Service Queue Resources Real Time subject area. This process truncates SVC_BI_QUEUE_RESOURCES table and then perform a full load. Therefore, this process has two roles: fully load and incremental load.

When to Use

This process must be executed when there are queue resources and team members data. This is an on-demand job. You must run this job in the following scenarios:

  • Any time Business Intelligence queue resource team data must be fully refreshed

  • Any time when you want to make an incremental update of BI queue resource team data

Privileges Required

Verify that you have the following privilege or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended frequency:

    • On regular interval: hourly

    • Based on need

  • Execution Time:

    • For single data record, less than 1 second

    • For batch job on volume of 10K records, less than 1 minute

  • Compatibility:

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • Only one instance of the scheduled process can run at any one time to avoid any potential issues.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification process.

  • If the scheduled job doesn't run successfully, you must run the job again manually.

  • This scheduled process idempotent, and no cleanup activity is required if the job fails.

  • To verify that this scheduled process has loaded the data successfully, run a Business Intelligence report from the Service - CRM Service Queue Resources Real Time subject area with the following metrics and search for the recent data:

    • Time

    • Facts

Refresh Service Categories for Reporting

Use the Refresh Service Categories for Reporting scheduled process to create new BI reports involving Service Request (SR) Category.

Generates the service category hierarchy and stores it in the SVC_CATEGORIES_CF table in a flattened form for easy reporting. Service category attributes in all service request subject areas obtain data from this table.

When to Use

This process must be executed for several Infolets and ready-to-use Business Intelligence reports to show data for SR Category. In addition, any report that uses the SR Category attribute either as a flat column or in a hierarchical fashion displays data for SR Category only after this scheduled process is run. Otherwise, SR Category is blank.

Privileges Required

Verify that you have the following privileges or roles:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job the following privilege is required

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • The recommended frequency is hourly.

  • Execution Time:

    • For single data record, less than 1 second.

    • For batch job on volume of 1K records, less than 30 seconds. The relevant data comes from the table SVC_CATEGORIES, which doesn't usually have many rows.

    • Compatibility:

      • There are no prerequisites to run this scheduled process.

      • No other processes are triggered when this scheduled process runs.

      • No potential impact on the server performance while this job is running.

      • Only one instance of the scheduled process must run at any one time to avoid any potential issues.

      • There are no issues with business processes executing in parallel with this job.

      • This scheduled process is incompatible with itself, therefore only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process notification system.

  • If the scheduled job doesn't run successfully, the next scheduled instance will process all relevant data.

  • This scheduled process idempotent, and no cleanup activity is required if the job fails.

  • To verify this scheduled process is running successfully, perform a Business Intelligence report dimensional query on Service Category from any subject area that has the dimension. Commonly if the process hasn't run, the report returns no data. If a custom category was recently added, it may be present in the report if the process has run successfully recently. For example, in the Service CRM Service Requests Real Time subject area, select elements from the Service Category folder.

Service Request Queue Assignment

Use the Service Request Queue Assignment scheduled process to assign service requests to queues.

This scheduled process:

  1. Finds unassigned service requests.

  2. Executes queue assignment rules.

  3. Assigns matching service requests to appropriate queue.

When to Use

Use this scheduled process to make sure every service request is assigned to a queue.

Privileges Required

Verify that you have the following privilege or roles:

  • Roles

    • ORA_SVC_HELPDESK_ADMINISTRATOR

    • ORA_SVC_SR_ADMINISTRATOR

  • Privilege

    • MOW_RUN_BATCH_ASSIGN_PROCESS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • On regular intervals, for example, hourly, daily or weekly depending on volume of service requests.

  • Execution Time:

    • This scheduled process should run within seconds for a single service request, but could take few minutes or longer for multiple service requests depending on the number of unassigned service requests and number of queue assignments rules.

  • Compatibility:

    • For this scheduled process to assign service requests to queues correctly, queue assignment rules must have been defined and published using the Manage Service Assignment Rules task.

    • This scheduled process modifies service request objects by populating the Queue field.

    • This scheduled process could be configured to work on Customer Relationship Management service requests or Human Capital Management service requests.

    • If you need a scheduled process to handle both Customer Relationship Management service requests and Human Capital Management Service Requests, you must configure two separate instances of this job with different parameters. Out of the two instances, one instance is for Customer Relationship Management service requests and another one is for Human Capital Management service requests. See the Parameters section.

Parameters

You can specify some of the following parameters for Customer Relationship Management Service Requests:

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Work Object_Code

Mandatory

Indicates business objects that get assigned to agents, such as, service requests.

ORA_Service_Request_Work_Object

None

None

Candidate Object Code

Mandatory

Indicates objects that are the possible pool of assignment candidates, such as queues.

ORA_Queue_Candidate_Object

None

None

Assignment Mode

Mandatory

Indicates the type of assignment processing. Matching is the only mode that is supported.

Matching

This value is driven by List of Values. Only Matching is supported.

None

View Criteria Name

Mandatory

Indicates the view criteria used to identify the service requests to be assigned.

OpenSRsUnassignedToQueueByStripeCd

None

None

View Criteria Bind Values

Mandatory

Indicates the bind variable used to select Customer Relationship Management Service Requests compared to Human Capital Management Service Requests.

BindStripeCd=ORA_SVC_CRM

No spaces are allowed in the value.

None

Rule Category ID

Optional

Not applicable for this process. Indicates the type of rule-processing that must be performed. For example, matching, scoring or classification, and so on.

Must be blank.

None

None

Rule Category Name

Optional

Indicates the type of rule-processing that must be performed. For example, matching, scoring or classification, and so on.

Must be blank.

None

None

Grouping Attribute

Optional

Not applicable for this process.

Must be blank.

None

None

Replace Team

Optional

Not applicable for this process.

Must be blank.

None

None

Number of Work Objects per Sub Process

Optional

Indicates number of records each sub job processes.

Default value is 1000.

This parameter (along with Max Sub Processes per Process) helps tune the performance of the scheduled process.

None

Maximum Sub Process per Process

Optional

Indicates max number of sub jobs to be spawned for the given scheduled process.

Default value is 10.

This parameter (along with Number of Work Objects per Sub Process) helps tune the performance of the scheduled process.

None

Metrics Logging Interval

Optional

Indicates the number of work objects in a subprocess before logging assignment metrics, such as update metrics after processing 100 service requests. This is used if your object support Enterprise logging for assignment.

100

None

None

Test Data Parameters

Optional

Not applicable for this process.

Must be blank.

None

None

Diagnostic Mode

Optional

Indicates if the process must be run in diagnostic mode to view the details of assignment processing in an output log.

Not selected by default.

None

None

You can specify some of the following parameters for Human Capital Management Service Requests:

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Work Object_Code

Mandatory

Indicates business objects that get assigned to agents, such as, service requests.

ORA_Service_Request_Work_Object

None

None

Candidate Object Code

Mandatory

Indicates objects that are the possible pool of assignment candidates, such as queues.

ORA_Queue_Candidate_Object

None

None

Assignment Mode

Mandatory

Indicates the type of assignment processing. Matching is the only mode that is supported.

Matching

This value is driven by List of Values, but only one value, that is, Matching is supported.

None

View Criteria Name

Mandatory

Indicates the view criteria used to identify the service requests to be assigned.

OpenSRsUnassignedToQueueByStripeCd

None

None

View Criteria Bind Values

Mandatory

Indicates the bind variable used to select Customer Relationship Management Service Requests compared to Human Capital Management Service Requests.

BindStripeCd=ORA_SVC_HCM

No spaces in the value.

None

Rule Category ID

Optional

Not applicable for this process. Indicates the type of rule-processing that is performed. For example, matching, scoring or classification, and so on.

Must be left blank.

None

None

Rule Category Name

Optional

Indicates the type of rule-processing that is performed. For example, matching, scoring or classification, and so on.

Must be left blank.

None

None

Grouping Attribute

Optional

Not applicable for this process.

Must be left blank.

None

None

Replace Team

Optional

Not applicable for this process.

Must be left blank.

None

None

Number of Work Objects per Sub Process

Optional

Indicates number of records each sub job processes.

Default value is 1000.

This parameter along with Max Sub Processes per Process helps tune the performance of the scheduled process.

None

Maximum Sub Processes per Process

Optional

Indicates max number of sub jobs to be spawned for the given scheduled process.

Default value is 10.

This parameter along with Number of Work Objects per Sub Process helps tune the performance of the scheduled process.

None

Metrics Logging Interval

Optional

Indicates the number of work objects in a subprocess before logging assignment metrics, such as update metrics after processing 100 service requests. This is used if your object support Enterprise logging for assignment.

100

None

None

Test Data Parameters

Optional

Not applicable for this process.

Must be left blank.

None

None

Diagnostic Mode

Optional

Indicates if the process must be run in diagnostic mode to view the details of assignment processing in an output log.

Not selected by default.

None

None

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • To submit the job, you must enter all the mandatory parameters and click Submit. The scheduled process's main user interface page would show the process that was scheduled.

  • The main job starts the sub processes depending on the number of records to process and waits until all sub process are completed.

  • If a particular run for service request queue assignment job fails, next run should pick up unassigned service requests.

Unlock Scheduled Process that Incrementally Loads SR Audit Data

Use the Unlock Scheduled Process that Incrementally Loads SR Audit Data process to remove the process lock created by the Execute Incremental Load of SR Audit Data for Reporting scheduled process if there's no instance of that scheduled process running, but you're unable to start a new instance.

Removes the process lock created by the Execute Incremental Load of SR Audit Data for Reporting process when that process fails to remove its lock automatically.

When to Use

The process should only be run if the Execute Incremental Load of SR Audit Data for Reporting scheduled process is unable to start and no other instance of the process is currently running. Don't run it under any other circumstance.

Run this process only if the Execute Incremental Load of SR Audit Data for Reporting process is aborted (either manually or through some unexpected system event, such as a server stopped working) and doesn't get a chance to clean up before exiting.

Privileges Required

Verify that you have the following roles or privilege:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job, the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this on demand process:

  • Don't run this process if the Execute Incremental Load of SR Audit Data for Reporting process is currently running.

  • Execution Time:

    • The execution time is less than 2 seconds.

  • Compatibility:

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There can be only one instance of the job running at any one time.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If the scheduled job doesn't run successfully, it should be submitted again.

  • This scheduled process is idempotent, and no cleanup activity is required if the job fails.

  • To verify that this scheduled process has been successful, schedule the Execute Incremental Load of SR Audit Data for Reporting process and confirm it's successfully able to load data.

Work Management

Perform Object Sharing Rule Assignment Processing

Use the Perform Object Sharing Rule Assignment Processing scheduled process to assign access group object sharing rules to assignment objects each time you add an access group and share rules.

When to Use

Use this scheduled process in the following cases:

  • After creating an access group, you can create rules to provide the group with access to an object's records. You can define rules for both standard and custom objects. To create an object sharing rule, you specify the type of object access to be provided, the conditions under which the access is provided, and the groups to share the rule with. You then publish the rule to Assignment Manager. Finally, you run the Perform Object Sharing Rule Assignment Processing task to enable the resources in the associated access group to have access to the object data records. This scheduled process ensures that the access group sharing rules for each object are assigned properly.

  • You can edit, delete, or inactivate object sharing rules at any time from either the Object Sharing Rules page or from the Edit Access Group: Object Sharing Rules subtab. Any changes you make are applied when the Perform Object Sharing Rule Assignment Process scheduled process is next run.

  • Create access extension rules to extend the access defined for an object in an object sharing rule to a related object. For example, if you have secured access to an object such as Account using object sharing rules, you can extend the access defined for the Account object to a related object, such as Activity, by creating an access extension rule. All members of an access group who can access account data will then have access to activity data for the account with the access level you choose in the access extension rule. Run the Perform Object Sharing Rule Assignment Processing scheduled process to ensure that the access extension rule is assigned.

  • You can also run this scheduled process to assign a batch of access group object sharing rules for all the available assignment objects. You can schedule these jobs to run regularly to ensure that all access group object sharing rules, records, and object data for your selected access groups are assigned and available to you.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles:

    • System Administrator

  • Privileges:

    • No special privileges required

Before You Use

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • You must run this process periodically as per your business requirements to ensure you have the required access to all records and object data for your selected access groups.

    • If you require immediate access to new records and objects, you can manually submit the Perform Object Sharing Rule Assignment process to run immediately on need basis. For example, a rule already exists for the account object and you create a new account record. You won't have real time access to this record based on the existing object rule until the next scheduled run of the Perform Object Sharing Rule Assignment job. If you want to access the new account record immediately, you can submit the job on need basis.

    • We recommend that you run this scheduled process every hour.

  • Compatibility:

    • No known dependencies with other scheduled processes.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Work Object

Mandatory

Select the work object you want from the drop-down list.

Parameter

Not applicable

None

Record Selection

Mandatory

You can run the assignment process on a subset of records.

  • All records

    Note: You might want to run the object sharing rule assignment process for an individual record (for each type of object) and confirm the access group rule processing is correct before processing all records for an object.
  • Enter a record selection value for these options:

    • Records updated in last 'X' days

    • Records updated in last 'X' hours

    • Records updated between dates

    • Single record

Not applicable

None

Record Selection Value

Optional

Applicable if you select any value in the Record Selection field except All.

None

Not applicable

None

Number of Work Objects per Sub Process

Optional

It is recommended that this value isn't changed. This number depends upon the Maximum Sub Processes per Process parameter's value.

Thousand is the default value.

Not applicable

None

Maximum Sub Processes per Process

Optional

If the number objects created is less than 500 thousand, then leave the default option of 2 as the maximum number of sub processes per process. The following recommendation is only applicable for when this process is run for the first time or for a complete run for all objects. However, the next time you run the process, only the changed objects are processed. If you're executing incremental runs at periodic scheduled times, then there's no need to update the default value of 2.

We recommend that changing this value if the number of objects is:

  • Between 500 thousand and 1 million objects enter 5

  • Greater than 1 million objects, enter 10

  • Greater than 5 million objects, enter 20

  • Greater than 10 million objects, enter 30

Two is the default value.

Not applicable

None

Diagnostic Mode

Optional

Used for troubleshooting purposes.

Not applicable

None

None

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Warning or errors are displayed and details are captured in the scheduled process.

  • Use the Diagnostic mode for detailed analysis.

  • Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about these reports, see the Related Topics section.

Request Account Assignment

Use the Request Account Assignment scheduled process to request territory assignments for specified accounts.

When to Use

Use this scheduled process in the following cases:

  • By default accounts are assigned automatically when the account is created or updated. Alternatively, sales people with access to the account team can run assignment for a specific account. You can use this scheduled process to run account assignments in bulk.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles:

    • System Administrator

  • Privileges:

    • Run Sales Party Batch Assignment

Before You Start

Review the following before scheduling this scheduled process:

  • Compatibility:

    • This scheduled process is incompatible with itself. These scheduled processes should not be requested to run in parallel against the same opportunity batch, to avoid potential locking issues.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Work Object

Mandatory

Specify a predefined work object or the one you created.

Account

None

Not applicable

Candidate Object

Mandatory

Specify the candidate object.

Account Territory

None

Not applicable

Assignment Mode

Mandatory

Specify the assignment mode.

Territory

None

Not applicable

Rule Category Name

Optional

Specify if you're using rule-based assignment.

Don't select any value.

None

Not applicable

View Criteria Name

Mandatory

Specify a view criteria name from the View Criteria table.

See the View Criteria table.

None

Not applicable

View Criteria Bind Values

Optional

Specify the view criteria bind values of the associated view criteria name from the View Criteria table.

See the View Criteria table.

None

Not applicable

Replace Team

Optional

Specify the replace team information.

Yes or No

None

Not applicable

Number of Work Objects per Sub Process

Optional

It is recommended that this value isn't changed. This number depends upon the Maximum Sub Processes per Process parameter's value.

Thousand is the default value.

None

Not applicable

Maximum Sub Processes per Process

Optional

If the number objects created is less than 500 thousand, then leave the default option of 10 as the maximum number of sub processes per process. The following recommendation is only applicable for when this process is run for the first time or for a complete run for all objects. However, the next time you run the process, only the changed objects are processed. If you're executing incremental runs at periodic scheduled times, then there's no need to update the default value of 10.

Oracle recommends changing this value if the number of objects is:

  • Between 500 thousand and 1 million objects enter 5

  • Greater than 1 million objects, enter 10

  • Greater than 5 million objects, enter 20

  • Greater than 10 million objects, enter 30

Ten is the default value.

None

Not applicable

Metrics Logging Interval

Optional

Used for internal purpose only.

Don't change this value. 100 is the default value.

None

Not applicable

Test Data Parameters

Optional

Used for internal purpose only.

Don't change this value.

None

Not applicable

Diagnostic Mode

Optional

Used for troubleshooting purposes.

Not applicable.

None

Not applicable

View Criteria Name View Criteria Description View Criteria Bind Values

SalesAccountsUpdatedSinceVC

Use this view criteria to assign accounts which haven't been previously assigned and have LAST_UPDATED_DATE is greater than or equals the specified date and (LAST ASSIGNED DATE is empty or LAST ASSIGNED DATE is less than or equal to the specified date.

BindLastUpdateDate= [YYYY-MM-DD HH:MM:SS]

SalesAccountsAssignedBeforeVC

Use this view criteria to reassign accounts which have been previously assigned and have LAST_ASSIGNED_DATE (in the ZCA_SALES_ACCOUNTS table) less than the specified date.

BindLastAssignedDate= [YYYY-MM-DD]

BindReassignment BatchId=[Territory Reassignment Batch ID]

SalesAccountBulkImportVC

Use this view criteria to assign accounts created in a given customer import batch.

This view criteria is also used internally to initiate immediate/automatic assignments after customer import.

BindReassignment BatchId=[Import Activity ID]

SalesAccountDimsForPartyVC

Use this view criteria to assign the account with the specified account ID.

BindPartyId= [Sales Account ID]

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Warning or errors are displayed and details are captured in the scheduled process.

  • Use the Diagnostic mode for detailed analysis.

  • Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about these reports, see the Related Topics section.

Request Opportunity Resource Assignment

Use the Request Opportunity Resource Assignment scheduled process to run rule-based assignment on opportunities. During this process, assignment processing executes a set of rules, as defined in the profile option, Sales Team Member Assignment Rule Set Group, to find matching candidates for opportunities. If matching candidates are found, they're added to the opportunity team. Note that team members for whom lock assignment is disabled will be replaced if they no longer match the assignment rules.

When to Use

This scheduled process:

  • Assign sales resources to an opportunity based on a set of rules such as assigning sales team members, including the opportunity owner.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles:

    • Sales Administrator

    • Setup User

Before You Start

Review the following before scheduling this scheduled process:

  • Compatibility:

    • This scheduled process is incompatible with itself. These scheduled processes should not be requested to run in parallel against the same opportunity batch, to avoid potential locking issues.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

View Criteria Name

Mandatory

Specify a view criteria name from the View Criteria table.

See the View Criteria table.

None

Not applicable

View Criteria Bind Values

Optional

Specify the view criteria bind values of the associated view criteria name from the View Criteria table.

See the View Criteria table.

None

Not applicable

Number of Work Objects per Sub Process

Optional

Specify the number of work objects per sub process.

We recommend that you use the default value.

None

Not applicable

Maximum Sub Processes per Process

Optional

Specify the maximum number of sub processes per process.

We recommend that you use the default value.

None

Not applicable

Metrics Logging Interval

Optional

Specify the metrics for logging interval.

We recommend that you use the default value.

None

Not applicable

Refresh Forecast Automatically

Optional

Specify if the forecast must be refreshed automatically.

We recommend that you use the default value.

None

Not applicable

Diagnostic Mode

Optional

Used for troubleshooting purposes.

Not applicable

Not applicable

Not applicable

View Criteria Name View Criteria Description View Criteria Bind Values

OpenOpportunitiesUpdated InLastNDays

All open opportunities which were updated in the last 30 days. Optionally, the user can enter a different number of days.

  • BindOptyUpdatedSince=[30]

  • For example, opportunities updated in last 15 days: BindOptyUpdatedSince=15

OpportunityForImport BatchVO

All opportunities imported through the given bulk import batch ID. Value for BatchId is mandatory.

  • BindBatchId

  • For example: BindBatchId=5618782

OpenOpportunities ByCreationDate

Open Opportunities created in the last 90 days. Optionally, the user can pass a different date range.

  • BindOptyCreation DateTo [sysdate], BindOptyCreation DateFrom [sysdate-90]

  • For example: BindOptyCreation DateTo=2015-02-29, BindOptyCreation DateFrom=2015-01-01 or BindOptyCreation DateFrom=2015-01-01. This second example processes all open Opportunities created between January 1, 2015 and the current date.

OpenOpportunities ByEffectiveDate

Open opportunities that have an expected close date in the last 90 days. Optionally, the user can pass a different date range.

  • BindEffective DateFrom [sysdate], BindEffective DateTo[sysdate [90]

  • For example: BindEffective DateFrom=2015-01-01, BindEffective DateTo=2015-02-29

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Warning or errors are displayed and details are captured in the scheduled process.

  • Use the Diagnostic mode for detailed analysis.

  • Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about the reports, see the Related Topics section.

Request Revenue Territory Assignment

Use the Request Revenue Territory Assignment scheduled process for territory-based opportunity assignment. This scheduled process evaluates opportunity revenue lines and matches eligible territories and their salespeople to the revenue lines.

When to Use

This scheduled process:

  • Run territory-based assignment on opportunity product lines. During this process, the application evaluates every product line in the opportunity batch. Territories whose dimensions match the dimensional attributes of a given product line are then assigned to that line.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles:

    • Sales Administrator

    • Setup User

Before You Start

Review the following before scheduling this scheduled process:

  • Compatibility:

    • This scheduled process is incompatible with itself. These scheduled processes should not be requested to run in parallel against the same opportunity batch, to avoid potential locking issues.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

View Criteria Name

Mandatory

Specify a view criteria name from the View Criteria table.

See the View Criteria table.

None

None

View Criteria Bind Values

Optional

Specify the view criteria bind values of the associated view criteria name from the View Criteria table.

See the View Criteria table.

None

None

Number of Work Objects per Sub Process

Optional

Specify the number of work objects per sub process.

Recommend that you use the default values.

None

None

Maximum Sub Processes per Process

Optional

Specify the maximum number of sub processes per process.

Recommend that you use the default values.

None

None

Metrics Logging Interval

Optional

Specify the metrics for logging interval.

Recommend that you use the default values.

None

None

Refresh Forecast Automatically

Optional

Specify of the forecast must be refreshed automatically.

Recommend that you use the default values.

None

None

Diagnostic Mode

Optional

Used only for troubleshooting purposes.

Not applicable

None

None

View Criteria Name View Criteria Description View Criteria Bind Values

OpenOpportunities ByCreationDate

Revenue lines of open opportunities created in the last 90 days.

Note: The view criteria bind values aren't required for the default date range, 90 days. You can pass a different date range by entering View Criteria Bind Values.
  • BindOptyCreationDateTo= [date],BindOptyCreation DateFrom=[sysdate-90]

  • For example: BindOptyCreationDateTo= 2015-02-29, BindOptyCreationDateFrom =2015-01-01

  • For example: BindOptyCreationDateFrom=2015-01-01. This second example processes all open opportunities created between January 1, 2015, and the current date.

OpenOpportunities ByEffectiveDate

Revenue lines of open opportunities that have an expected close date in the last 90 days. Optionally, the user can enter a different date range.

  • BindEffectiveDateFrom =[sysdate], BindEffectiveDateTo =[sysdate [90]

  • For example: BindEffectiveDateFrom =2015-01-01, BindEffectiveDateTo =2015-02-29

SalesAccountUpdated InLastNDays

Revenue lines of all open opportunities whose sales account was updated in the last 30 days. Optionally, the user can enter a different number of days.

  • BindSalesAccountUpdated Since=[30]

  • For example, opportunities whose sales account was updated in last 15 days: BindSalesAccount UpdatedSince=15

OpenOpportunitiesUpdated InLastNDays

Revenue lines of all open opportunities updated in the last 30 days. Optionally, the user can enter a different number of days.

  • BindOptyUpdatedSince =[30]

  • For example, open opportunities updated in last 15 days: BindOptyUpdated Since=15

FilterByBatchTag

Revenue lines of all open opportunities that contain a specific value in the Batch Tag field.

  • BindBatchTag =[text]

  • For example, open opportunities that have EMEA in the Batch Tag field: BindBatchTag =EMEA

RevenueImportCriteria

Revenue lines of all opportunities imported through the given bulk import batch ID. The view criteria bind value, BatchId, is mandatory.

  • BindBatchId

  • For example: BindBatchId=5618782

ClosedOpportunitiesBy CreationDate

Revenue lines of closed opportunities created in the last 90 days. Optionally, the user can enter a different date range.

  • BindOptyCreationDateTo =[date], BindOptyCreation DateFrom =[sysdate-90]

  • For example: BindOptyCreationDateTo =2015-02-29, BindOptyCreationDateFrom =2015-01-01

OpportunitySearchbyOptyNumber

Revenue lines of an opportunity with a specific number.

  • BindOptyNumber=<xyz>

  • BindOptyNumber=17001

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Warning or errors are displayed and details are captured in the scheduled process.

  • Use the Diagnostic mode for detailed analysis.

  • Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about these reports, see the Related Topics section.

Run Access Group Membership Rule

Use the Run Access Group Membership Rule scheduled process to ensure that the access group membership rules are assigned and resources are added to a newly created group. After this process is run, all resources that meet the specified condition criteria are added to the access group.

When to Use

This scheduled process:

  • To ensure that the access group membership rules are assigned and resources are added to the group.

Privileges Required

Verify that you have the following roles or privileges:

  • Roles:

    • Sales Administrator

    • IT Security Manager

  • Privileges:

    • ZCA_MANAGE_GROUP_ACCESS_PRIV

Before You Start

Review the following before scheduling this scheduled process:

  • Recommended Frequency:

    • It's best practice to schedule the process to run every 24 hours for all records updated in the previous 24 hours.

    • We recommend that you run this schedule process immediately after you edit the access membership rules.

  • Compatibility:

    • Don't schedule or start the Run Access Group Membership Rules process at the same time as the Reporting Hierarchy Generation scheduled process. The Reporting Hierarchy Generation process updates the reporting hierarchy in accordance with changes to the internal resource or partner organization hierarchies and impacts the assignment of access group membership rules if both processes run at the same time.

Parameters

Parameter Optional or Mandatory Description Parameter Values Special Combinations Required Notes

Record Selection

Mandatory

Specify the record.

Select a value.

None

None

Record Selection Value

Optional

Specify the record value.

Select a value.

None

None

Number of Work Objects per Sub Process

Optional

Specify the number of work objects per sub process.

Recommend that you use the default values.

None

None

Maximum Sub Processes per Process

Optional

Specify the maximum number of sub processes per process.

Recommend that you use the default values.

None

None

Diagnostic Mode

Optional

Used only for troubleshooting purposes.

Not applicable.

None

None

Troubleshooting Information

Use this information to troubleshoot the scheduled process:

  • Warning or errors are displayed and details are captured in the scheduled process.

  • Use the Diagnostic mode for detailed analysis.

  • Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about these reports, see the Related Topics section.