search cancel

Financial Plan Defaults in the Entity not taken into account in MUX

book

Article ID: 215142

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The Period Type default from Financial Plan Defaults in the Entity is not taken into account in Modern UX

STEPS TO REPRODUCE

  1. In Finance - Setup - Entities - Entity - Plan Defaults - set Period Type to Monthly
  2. Now go to Projects in Classic, open a project with this entity/department
  3. Create a cost plan
  4. Note Monthly is selected as default upon creation
  5. Now go in Modern UX - open a project - Financials module
  6. Ensure Period Type is not in the list view
  7. Now click on + and add a new Cost plan

Expected Results: The plan to be added

Actual Results: Error CMN-0007: Attribute 'period_type_code' is required.

Workaround: Add Monthly as default in the attribute in Studio OR add Period Type in the View

 

Note: If you set the Studio attribute default to be Quarterly, then the value from Studio is taken in MUX and the value from Financial Defaults is taken in Classic.

Environment

Release : 15.9.2

Component : CA PPM FINANCIAL MANAGEMENT

Resolution

This is DE60949, Not a Bug

Working as designed:

The entity defaults in Classic weren't used in Modern UX intentionally.

Please use Studio attributes, also blueprints and templates for your default values as appropriate.