B14 214 - GBP Data View Object - not showing PY

In the module B14 214
during the creation of the "GBP Data View Object" (please note the same happens on the "LC Data View Object"), after step 21 this is the expected resultfrom the training is as such:

while in my environment here is the actual result (showing the PY column completely empty):

for GBP

here for LC:

I checked my configurations for the whole module and they seems fine. Also previous modules have been completed with no problems.

Can you help me out? thanks

Find more posts tagged with

Board Academy

Configure

Dataview

Accepted answers

Jeff Williams

Thanks for sharing the environment details, cube screenshots, and the adjusted procedures that definitely helps.

Based on what you’ve shared, we noticed a couple of points that may explain why PY is not showing correctly and why totals differ:

Layout Editor – Selector configuration (GBP / LC)
In the Layout Editor for GBP and LC, the screen selectors currently include Year, Currency, and Country (United Kingdom).
For this scenario, the selector should be limited to Year and Currency only. Having Country selected can impact the data shown and lead to inconsistencies.

ACT – Sales Data Publish procedure (Account selection issue)
In the “PROFIT AND LOSS ACT” group, Step 12 (Selection) has an incorrect static Account selection.
Instead, this step should dynamically select Account members based on the UTIL - DE - Product - P&L Mapping cube.

Recommended setup:

In the PROFIT AND LOSS ACT group, create or update a Selection step.

Choose SELECT and enable dynamic selection on the Account entity.

Select UTIL - DE - Product - P&L Mapping from the Cubes dropdown.

Ensure this cube has Versions = Product Category, Account.

This is required for correctly populating the ACT - DF - Profit and Loss Statement GBP / LC cubes.

ACT – Expense Data Publish procedure (Year selection)
In the Main group – Step 2 (Selection), only Year 2022 is currently selected.
This step should include both 2021 and 2022, as per the expected data scope.

After applying these adjustments, we recommend re-running the ACT – Sales Data Publish and ACT – Expense Data Publish procedures and then rechecking the GBP Data View Object for PY values.

Hope this helps, let us know what you find after the update!

All comments

Jeff Williams

Hi @Matteo Dosmi

Thanks for sharing the details.

To better understand why the PY column is empty for both GBP and LC Data View Objects, could you please share a couple of screenshots from your environment?

Layout Editor → Profit and Loss Statement (for both GBP and LC)
Specifically the Overview / Data Blocks section showing:
- CY and PY blocks
- Cube used
- Time function / reference period (Previous Year)
Cube list view for:
- ACT - DF - Profit and Loss Statement GBP
- ACT - DF - Profit and Loss Statement LC
  with the file size column visible.

I’ve attached reference screenshots from a working setup so you can easily compare and capture the same views from your side.

Once we see these, it should be easier to spot what’s causing the difference.

Thanks!

Matteo Dosmi

Thank you Jeff.

Here is my env status:

and Cubes:

I see that the totals are different .

That's why here below I'm attaching the adjusted Procedures for ACT – Sales Data Publish (yellow) and ACT – Expense Data Publish (orange).

Hope this can give you some more insights.

Jeff Williams

Thanks for sharing the environment details, cube screenshots, and the adjusted procedures that definitely helps.

Based on what you’ve shared, we noticed a couple of points that may explain why PY is not showing correctly and why totals differ:

Recommended setup:

In the PROFIT AND LOSS ACT group, create or update a Selection step.

Choose SELECT and enable dynamic selection on the Account entity.

Select UTIL - DE - Product - P&L Mapping from the Cubes dropdown.

Ensure this cube has Versions = Product Category, Account.

This is required for correctly populating the ACT - DF - Profit and Loss Statement GBP / LC cubes.

After applying these adjustments, we recommend re-running the ACT – Sales Data Publish and ACT – Expense Data Publish procedures and then rechecking the GBP Data View Object for PY values.

Hope this helps, let us know what you find after the update!