Default Cost Type Field on the Project does not match New UX
search cancel

Default Cost Type Field on the Project does not match New UX

book

Article ID: 205812

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

User sets the default Cost Type in the Project Object as Capital but the New UX shows Planned Cost as Operating after creating a manual cost plan.

Steps to Reproduce

  1. Go to Project Object
  2. Set Cost Type attribute default to Capital
  3. Create a new project
  4. Create a new manual Cost Plan
  5. Add an amount for Cost line item
  6. Go to new UX
  7. Go to Project List page
  8. Click Column Panel and add Planned Operating Cost and Planned Capital Cost

Expected Result - Cost that was added shows under the Planned Capital Cost

Actual Result - Cost that was added shows under the Planned Operating Cost

 

Environment

Release : All Support Releases

Component : CA PPM SAAS APPLICATION

Cause

The Cost Plan has its own attribute called Cost Type in the Cost Plan Detail Object that it uses when creating manual Cost Plans

Resolution

  1. Go to Cost Plan Details object
  2. Click on Attributes>>Cost Type
  3. Change default cost type to Capital