Clarity

Hi

We recently upgraded from 15.1 to 15.5. We are in process of testing 15.5. We have a process which writes a costplan. The process is working on 15.1 But it is NOT working on 15.5. The error it throws is 

<ErrorInformation>
<Severity>ERROR</Severity>
<Description>Duplicate Grouping Attributes combination {charge_code_id=Unapproved, transaction_class_id=736043} in Plan Details.</Description>

Does anyone noticied this issue when you upgraded? What could be the reason. I have also checked the Library. The "costPlan_write" file is same on both the instances. 

Can you please help?

Thanks,

Ravi V

For issues like this it is always worth attaching the errant file, suitably anonymised of course 

Hi Stuart, do you mean to check the log file?

No, I meant attach the XOG file so other eyes can take a look

<?xml version="1.0" encoding="UTF-8"?>
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_costPlan.xsd">
<Header action="write" externalSource="NIKU" objectType="costPlan" version="13.2.0.472"/>
<CostPlans>
<CostPlan benefitPlanCode="" code="CP9042" finishPeriod="Jun 2019" investmentCode="AASASOC1" investmentType="project" isPlanOfRecord="true"
name="Cost Plan" periodType="MONTHLY" revision="0" startPeriod="Jul 2018">
<Description/>
<GroupingAttributes>
<GroupingAttribute>charge_code_id</GroupingAttribute>
<GroupingAttribute>transaction_class_id</GroupingAttribute>
</GroupingAttributes>
<Details>
<Detail>
<Cost>
<segment finish="2018-09-30T00:00:00" start="2018-09-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="736043"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-09-30T00:00:00" start="2018-09-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="754400"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-08-31T00:00:00" start="2018-08-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="736043"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-08-31T00:00:00" start="2018-08-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="754400"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-07-31T00:00:00" start="2018-07-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="736043"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-07-31T00:00:00" start="2018-07-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="754400"/>
</GroupingAttributes>
</Detail>
<Detail>
<Cost>
<segment finish="2018-10-31T00:00:00" start="2018-10-01T00:00:00" value="0"/>
</Cost>
<Units/>
<Revenue/>
<GroupingAttributes>
<GroupingAttribute code="charge_code_id" value="Unapproved"/>
<GroupingAttribute code="transaction_class_id" value="736043"/>
</GroupingAttributes>
</Detail>
</Details>
<CustomInformation>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
<ColumnValue name="q_proc_upd">02-Nov-2018 14:47:46</ColumnValue>
</CustomInformation>
</CostPlan>
</CostPlans>
</NikuDataBus>

Looking at the file I am surprised it worked on the previous PPM version as the error message is correct - you have duplicate Detail elements for the combination reported in the error - you need to place all of the segment elements for Unapproved / 736043 into a single Detail element.