budget_submit_option in fin_plans not updated with XOG

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The budget_submit_option in fin_plans table does not get updated when XOG is used to create a Budget Plan

Steps to Reproduce:

1. Use the following XML and XOG IN (preferably through a XOG Client). It uses project PR1005 from the demo data. Note that "forceReplace" attribute has a value populated

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_budgetPlan.xsd">
 <Header action="write" externalSource="NIKU" objectType="budgetPlan" version="15.9.1.44"/>
 <BudgetPlans>
  <BudgetPlan benefitPlanCode="BN1095" code="BP333" finishPeriod="2021-02" forceReplace="true" investmentCode="PR1005" investmentType="project"
  name="Budget Plan by Cost Type and Transaction Class" periodType="MONTHLY" revision="0" sourceCostPlanCode="CP1856" startPeriod="2020-11" status="APPROVED">
   <Description>Budget Plan by Cost Type and Transaction Class</Description>
   <GroupingAttributes>
    <GroupingAttribute>cost_type_id</GroupingAttribute>
    <GroupingAttribute>transaction_class_id</GroupingAttribute>
   </GroupingAttributes>
   <Details>
    <Detail>
     <Cost>
      <segment finish="2020-11-30T00:00:00" start="2020-11-01T00:00:00" value="64800.0"/>
      <segment finish="2021-02-28T00:00:00" start="2021-02-01T00:00:00" value="14400.0"/>
     </Cost>
     <Units>
      <segment finish="2020-11-30T00:00:00" start="2020-11-01T00:00:00" value="360.0"/>
      <segment finish="2021-02-28T00:00:00" start="2021-02-01T00:00:00" value="80.0"/>
     </Units>
     <Revenue>
      <segment finish="2020-11-30T00:00:00" start="2020-11-01T00:00:00" value="64800.0"/>
      <segment finish="2021-02-28T00:00:00" start="2021-02-01T00:00:00" value="14400.0"/>
     </Revenue>
     <GroupingAttributes>
      <GroupingAttribute code="cost_type_id" value="OPERATING"/>
      <GroupingAttribute code="transaction_class_id" value="INTLABOR"/>
     </GroupingAttributes>
    </Detail>
   </Details>
  </BudgetPlan>
 </BudgetPlans>
</NikuDataBus>

2. Use the following query to check on the value of budget_submit_option field

select budget_submit_option
from fin_plans
where code = 'BP333'

3. Navigate to the same project mentioned in Step 1
4. Navigate to the Financial Plans tab -> Actions -> Submit Plan of Record for Approval
5. provide "Plan ID" as "BP444"
6. Use the following query to check for the budget_submit_option field's value

select budget_submit_option
from fin_plans
where code = 'BP444'

Expected Results: Value is not null in Steps 2 and 6
Actual Results: Value is null in Step 2, but not in Step 6. That is, when XOG is used, no value is populated in the budget_submit_option field

Environment

Clarity version: 15.9.0, 15.9.1

Cause

Due to a defect with ID DE58994

Resolution

• The defect is fixed in 15.9.2.
• When XOG is used budget_submit_option is always set to "REPLACE". This is as per design.