What are Agreement Rules?

An agreement rule is a collection of patterns and conditions that are defined to determine whether a merge request should be vetoed by the application or not. Merge requests that violate these rules are either rejected or end in error.

Agreement rules let you check a merge request for any veto conditions that can prevent a merge from occurring. These rules save resources and time by obviating the need to review merge requests to prevent undesired merge from being processed. Besides, agreement rules prompt you to consider alternative duplicate resolution mechanism such as linking.

Agreement rule can be of the following two types:

Predefined
User-defined

Predefined Agreement Rules

These are agreement rules that are predefined in the application. You can only view the predefined agreement rules.

The following table describes the predefined agreement rules shipped with the application for Oracle Sales Cloud. Merge requests that violate these rules are automatically rejected.

Name	Description
`HR_APPLICANT_VETO`	Prevents a person party with an active party usage of `HR_APPLICANT` from merging with another party.
`HR_EMPLOYEE_VETO`	Prevents a person party with an active party usage of `HR_EMPLOYEE` from merging with another party.
`HR_CONTINGENT_WORKER_VETO`	Prevents a person party with an active party usage of `HR_CONTINGENT_WORKER` from merging with another party.
`HR_PARTY_SITE_VETO`	Prevents a party site with active original system reference from Oracle Fusion Human Capital Management system from merging with another party site.
`RESOURCE_PERSON_VETO`	Prevents a person party with an active party usage of `RESOURCE` from merging with another party.
`BANK VETO`	Prevents an organization party with an active party usage of `BANK` from merging with another party.
`CLEARINGHOUSE_VETO`	Prevents an organization party with an active party usage of `CLEARINGHOUSE` from merging with another party.
`BANK_BRANCH_VETO`	Prevents an organization party with an active party usage of `BANK_BRANCH` from merging with another party.
`BRANCH_CLEARINGHOUSE_VETO`	Prevents an organization party with an active party usage of `CLEARINGHOUSE_BRANCH` from merging with another party.
`LEGAL_EXTLEGAL_PARTYUSGRULE_VETO`	Prevents an organization party with active party usage of `LEGAL_ENTITY` from merging with another organization party with active party usage of `EXTERNAL_LEGAL_ENTITY`.
`IC_PARTICIPANT_PERSON_VETO`	Prevents a person party with an active party usage of `INCENTIVE_COMP_PARTICIPANT` from merging with another party.
`IC_PARTICIPANT_ORG_VETO`	Prevents an organization party with an active party usage of `INCENTIVE_COMP_PARTICIPANT` from merging with another party.
`PARTNER_VETO`	Prevents an organization party with an active party usage of PARTNER from merging with another party.
`INACTIVE_PARTNER_VETO`	Prevents an organization party with an active party usage of `INACTIVE_PARTNER` from merging with another party.
`CUST_CONTACT_DIFF_RESOURCE_ORG_VETO`	Prevents two partner owned contacts belonging to different resource organizations from being merged.
`CUST_CONTACT_INTERNAL_PARTNER_VETO`	Prevents a partner owned contact that doesn't belong to a resource organization from merging with another partner owned contact that belongs to a resource organization.
`CUST_CONTACT_INTERNAL_PARTNER_ORG_VETO`	Prevents a contact owned by an internal user from merging with a contact owned by a partner user.
`CARD_ISSUER_VETO`	Prevents an organization party with an active party usage of `CREDIT_CARD_PROVIDER` from merging with another party.
`LEGAL_ENTITY_VETO`	Prevents an organization party with an active party usage of `LEGAL_ENTITY` from merging with another party.
`ESTABLISHMENT_VETO`	Prevents an organization party with an active party usage of ESTABLISHMENT from merging with another party.
`HIERARCHY_CYCLE_PREVENTATION_VETO`	Prevents merge from happening when the master party record is at a level lower than the `nonmaster party record` within the same active tree version.
`NAMEDACCOUNT_UNNAMEDACCOUNT_VETO`	Prevents merge from happening when the master party record isn't a named account whereas the `nonmaster party record`is a named account and these are in active hierarchies.

The following table describes the predefined agreement rules shipped with the application for other Fusion applications. Merge requests that violate these rules are automatically rejected.

Functional Area	Name	Description
Distributed Order Orchestration	DOOPartyMerge	Prevents the customer account and customer account sites from getting merged when an open Distributed Order Orchestration (DOO) order is associated with either of them.
Distributed Order Orchestration	POZSUPPLIER	Prevents the party merge process from being completed, when any of the following conditions are met: The corresponding supplier isn't merged Few purchase orders aren't transferred for the corresponding From Supplier The merged-from party and merged-to party aren't correlated with the same merged-from supplier and merged-to supplier The corresponding supplier site haven't been merged Few purchase orders aren't transferred for the corresponding supplier site The merged to party site doesn't have an associated supplier site The merging contact parties aren't valid supplier contacts The merging contact parties don't belong to same supplier
Tax	ZX_PARTY_MERGE	Prevents the party from merging when any of the following conditions are met: The 'From Party Tax Profile type' is not the same as 'To Party Tax Profile type' The 'From Party Tax Profile type' equal to 'THIRD PARTY' The From party tax attributes (Registration Type code, Registration Number, Rule code, Self-assess flag, Inclusive tax flag) aren't same as the To party tax attributes (Registration Type code, Registration Number, Rule code, Self-assess flag, Inclusive tax flag)
Accounts Payable	AP_PARTYVETO	Prevents party merge in the unprocessed invoices or unprocessed payments.
Accounts Receivable	AR_FinArCustomersVeto	Prevents the customer merge when either of the following conditions are met: The merging customer has any Balance Forward Bill (BFP) in draft mode in the application The merging customer site has any BFB in draft mode in the receivables application
CSE Assets	CSE_SELLING_BUSINESS_UNIT_VETO	After the customer account site merge, CSE party merge will check if the new account site + the sold from business unit combination that we have in our cse_assets_b table is a valid combination using hz_cust_acct_sites_all. If not valid, we will veto the party merge.
Service	SVC_CSS_CONT_PENDING_REG_VETO SVC_CSS_ACT_PENDING_REG_VETO SVC_CSS_ACT_USERS_VETO	Validate that contacts can't be merged if the victim contact has a self-service registration record Don't allow account merge if the account has contacts with pending registrations Do not allow account merge if the account has active ODCS users
Grant/Award Management	GMS_SPONSOR_NOT_EXIST_VETO GMS_TOSPON_NOTLOC_VETO	The master party doesn't exist as a grants sponsor. The sponsor LOC of the master and target party isn't same. Ensure the LOC is same for both sponsors. Either the LOC for both is enabled or both is disabled.

User-defined Agreement Rules

These are additional agreement rules that you can define to determine whether a merge request should be vetoed by the application. You can create, view, update, and delete user-defined agreement rules.

Note: The application doesn't support changing agreement rules inside the Application Composer sandbox. Therefore, the merge engine doesn't pickup the changes made to these rules inside the Application Composer sandbox.