Browser version scriptSkip Headers

Oracle® Fusion Applications Customer Data Management Implementation Guide
11g Release 5 (11.1.5)
Part Number E20433-05
Go to contents  page
Go to Feedback page

Go to previous page
Go to previous page

14 Common Customer Data Management Configuration: Define Party Usages

This chapter contains the following:

Party Usage Explained

Party Usage Filter Rules Explained

FAQs for Define Party Usages

Party Usage Explained

Party usages describe how a party is used in the context of the implementing organization. For example, a person in the business community may be a consumer or contact. Rules can be associated to a party, and these rules determine when a party usage can and cannot be used.

These are the following rules that can be defined for a party usage:

Assignment rules

Assignment rules are used to define how the party usage can and cannot be assigned to parties. You can choose to allow unconditional party usage assignment, enabling the assignment to be manually created, or updated, by an administrator.

Alternatively, you can restrict the manual assignment and update of a party usage, which will mean that the party usage can only be created, or updated, by a business event. For example, creating an account for a party record can automatically assign the Customer party usage to that record.

You can also specify whether the party usage assignment can also be created or updated by the assignment of a party relationship. For example, the party relationship Contact Of can assign a party usage of Organization Contact.

Exclusivity rules

Exclusivity rules enable you to restrict party usage assignment, so that between a specified date range the party usage can be the only usage allowed to be assigned to a party. For example, you can set up an exclusivity rule that between January 1 2011 and February 1 2011 parties that have the Manufacturer party usage cannot have any other party usage assigned to them.

Incompatibility rules

You can specify which party usages cannot be assigned concurrently to a party between a defined date range. For example, you can specify that you cannot assign a Sales Account usage to a party with a Sales Prospect usage, during January 1 2011 and December 31 2030.

Transition rules

You are able to define which party usages can transition to the party usage you are creating or editing. Once a party has transitioned to the current party usage, the previous party usage is set with an end date. For example, when a party with the Prospective Partner party usage is assigned the Partner party usage, the Prospective Partner usage is set with an end date.

Party Usage Filter Rules Explained

Party usage filter rules are a grouping of party usages that are used for searching and filtering in user interfaces. You can specify which party usages you want to include and exclude, and whether the party usage assignments are active or inactive.

For example, an Eligible Customers filter rule can include the Sales Prospect party usage, Sales Account , Legal Entity, and Customer party usages. The Eligible Customers filter rule can then be used in transactional UIs to filter out parties with party usages that are not included in the rule.


Once a party usage filter rule is created you need to compile the filter rule before you can use the filter rule in a User Interface.

FAQs for Define Party Usages

How can I compile a party usage filter rule?

In the Party Usage Filter Rule page click Actions in the header section, and then click Compile Filer Rule.