cancel
Showing results for 
Search instead for 
Did you mean: 

BPC Account Type - AST

Former Member
0 Kudos

Fellow BPC'ers

We are looking for a work around to the standard EPM behavior  when reporting using AST accounts. Consider the scenario below:

Here we have two records, the first using an AST type account and the 2nd an EXP type account.

Standard behavior when reporting on these records via either EPM report (refer report 000 below) or even using an EPMRETRIEVEDATA when using a hierarchy time node is to use the value in the last member sibling among descendants of 2014.TOTAL, i.e 2014.12 in the scenario below. 

The EXP record will show a value in 2014.TOTAL, while the AST record will show nil. I understand the reasoning behind this, however am searching for method to report on this as an exception (without changing the master data ACCTYPE or the measure program.)

Any thoughts much appreciated,

Glen

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186338
Active Contributor
0 Kudos

Hi Glen,

AST accounts are YTD by design, independent of cube default storage type. It means that AST figures are stored and presented as YTD. I do not understand the business reason to present a sum of YTD monthly balances... or what do you want to have in the parent member?

"The EXP record will show a value in 2014.TOTAL, while the AST record will show nil." - what do you want to have instead of null?

Vadim

Former Member
0 Kudos

Hi Vadim and Dinesh

Thanks for the reply.

'what do you want to have instead of null?' We want to show $340 here, ie the same as if the account type were EXP.

In this BPC solution, all inbound transactions from BW infoprovider are received as periodic flows...irrespective of the account type. However, in BPC, all accounts have been set up with traditional 4 account types. We plan to switch AST & LEQ account types back to EXP so that the type reflects the periodic nature of the transaction. Any planned data will also be of a periodic/flows nature. In the interim, as there are some dependencies, we are looking for any work arounds.

Thanks & Regards

Glen

former_member186338
Active Contributor
0 Kudos

Hi Glen,

"all inbound transactions from BW infoprovider are received as periodic flows" - this is the issue to be fixed.

Vadim

dinesh_veluru
Active Participant
0 Kudos

Hi Glen,

Please create a Local member insert before column axis.

use the formula = SUM(A1:L1)

Hide the 2014.total column.

Thanks,

Dinesh.V