Agreement Rule Is Not Selecting The Correct Master Based On The Agreement Rule

(Doc ID 2165546.1)

Last updated on JULY 27, 2016

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Goal

On : 11.1.10.0.0 version, Accounts, Contacts, Households

The requirement is the following:

A SAP Account cannot be a nonmaster record in merge.

There is a custom field 'Source'. If this field is filled with the value 'SAP' the Account is a SAP Account.

I have tried two different definitions of the agreement rule. I have tried the following use cases:

1) merge two SAP Accounts
2) merge SAP Account with non SAP Account
3) merge two non SAP Accounts

For Option A the duplicate request passes for all three cases. For Option B all three cases are rejected.

Option A
===================
(for each case where) OrganizationPartyVO TermA AND
there is a case where OrganizationDVO termB

Conditions:
termA.MergeType=='Nonmaster'
termB.Source_c == 'SAP' AND
termB.PartyId == TermA.PartyId
===================

Option B
===================
(for each case where) OrganizationPartyVO TermA AND
there is no case where OrganizationDVO termB

Conditions:
termA.MergeType=='Nonmaster'
termB.Source_c == 'SAP' AND
termB.PartyId == TermA.PartyId
===================
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms