Multiple Transaction assignments with different KPIs

[rachapudi]

I have two transactions with transaction assignment respectively as below -

Txn - 1

Txn Assignment 1 - Participant A, GA1 - KPI1

Which fires Credit Rule 1

Txn - 2

Txn Assignment 1 - Participant A, GA1 - KPI2

Which fires Credit Rule 2

Fields on Txn 1 and Txn 2 are exactly same with same participant\position at Transaction assignment except GAs which differ based on KPIs.

My goal is to avoid Multiple transactions and so Instead of creating duplicate transactions(Txn 1 and Txn 2 above), I tried to create as below and system did allow to add duplicate transactions assignments with same participant and different GAs

Txn - 1

Txn Assignment 1 - Participant A, GA1 - KPI1

Txn Assignment 2 - Participant A, GA1 - KPI2

My expectation after running the pipeline, CR1 should fire for Txn Assignment 1 and CR2 should fire for Txn Assignment 2. However after running the pipeline, none of my credit rules are firing.

Doesn't Pipeline fires Credit Rules when duplicate transaction assignments with same participant\position are present ?

Why does UI allows to add duplicate participants\positions\titles as preassignment ? Please share your feedback.

[former_member36904]

Hi Srinivas,

not sure about the issue, nut if both Credit Outputs have the same Credit Type, it could be that the system cannot create two Credits from the same transaction with the same Credit Type. Try changing the Credit Types and see, if that´s working.

Best

Daniel

[Lara]

Hi, Srinivas,

The issue is, that's not what duplicate Transactions does. The purpose of setting duplicate Transactions to False is to address a multiple Credits which originate from a single Transaction, and give you the choice to roll up to a single indirect Credit or just one. The system recognizes if two credits are based off the same Transaction if it has the same Order ID, Line, Subline and Event Type.

To clarify your questions at the end, there's no connection between Duplicate Transactions and the assigned Participant/Position. As far as the system is concerned, they are just two Transactions that are assigned to the same Payee. This is normal behavior.

As to why the Credit Rules aren't firing, there's something else going on. I'd start by removing any conditions and re-run Classify and Allocate to isolate the cause.