EPM Perfomance

[former_member229754]

Hello,

I got a quick question:

What are the most fast option or combination from EPM template, in ascendent order. hide/supress

1. Filter (by EPM  Report Editor - Filtering)

2. Rows Empty / Zero Values

3. Exclude Members.

I know everyone got different functionality, but, I would like to know the performance wise what would be the order, or combinations...etc... the best practices

See.. the exclude member is taking too much time when i'm doing CALC = Y or N for two Dimension... and I would like to replace it.

Thanks.

Regards,

[former_member186338 · Accepted solution]

The question is - what do you want to achieve?

1st and 2nd options can do more or less the same things but 3rd is absolutely different!

2nd is fastest.

Vadim

P.S.

Enable:

User option -> Others -> Select Force Symmetric Refresh for Large Asymmetric Axis.

[former_member229754 · Accepted solution]

Hi Vadim,

thanks.

What I want to achieve is something like this

when Product.Calc.Is = Yes, Vendor.Calc.is = Yes

when Product Calc.is = No, Vendor calc.is = No

The logic I implemented in Exclude is:

(1) Product calc = YES, Vendor.Calc = NO

(2) Product.calc = NO, Vendor.Calc = YES.

This works well.. and I can achieve my requirement. The issue is.. this very heavy for perfomance point of view.

Thanks.

Regards,

PS. That options is there enabled

[former_member186338 · Accepted solution]

Sorry, but what do you mean by:

when Product.Calc.Is = Yes, Vendor.Calc.is = Yes

when Product Calc.is = No, Vendor calc.is = No

Product?

Calc?

Is?

Yes?

...

[former_member229754 · Accepted solution]

Ok.

Product - Hierarchy_node, Vendor - Hierarchy_Node

Product - Base, Product - Base

[former_member186338 · Accepted solution]

Unclear, what dimension you are talking about? How the hierarchy is organized?

Sample screenshot?

[former_member229754 · Accepted solution]

I'm talking with

Dimension: Product and Supplier.

[former_member186338 · Accepted solution]

OK, I see asymmetrical report that can be created by Exclude member or statically...

What do you want to be selected by user?

[Former Member · Accepted solution]

I would agree with Vadim that Exclude is the easiest way to perform this operation, though as you note it is taxing on performance.

Depending on how your hierarchies are setup you can get the similar results if you restrict your supplier hierarchy to the base members and then restrict your product hierarchy to the base members but enable member sorting and grouping and group on the property PARENTH1 of your product with a Before group.

[former_member186338 · Accepted solution]

Hi Ryan,

Yes, it's possible! But the question is: "What do you want to be selected by user?" And the hierarchy order for Product will be replaced by PARENTH1 sorting...

Vadim

[Former Member · Accepted solution]

We're enabling Sorting and Grouping only to take advantage of the auto summing that can be leveraged with a group.  No sorting would be performed. This method is only going to work if his intention is to show the 1 aggregate level above base product members. This won't suffice to show more than one parent level.

However Vadim has a point and how would this be leveraged while still allowing a user interact with this report to achieve the desired results. I personally would:

1. Set up an EPMSelectMember formula to choose a starting point for the Product Hierarchy
2. Use an EPMDimensionOverride and replace the Product dimension with the BAS( ) of the selected member to setup the query for the grouping
3. Using the grouping option would product the results depicted above

A little more complex by adding additional controls, but very "do-able"

[former_member186338 · Accepted solution]

Sorry, but Product base members will be sorted based on alphabetical order of PARENTH1 property of base Product members...

[Former Member · Accepted solution]

Sure enough.  Too bad the sorting part can't be disabled.

[former_member229754 · Accepted solution]

Initially will be:

The PowerUser(administrator) will select the Products and the Suppliers

after that the sheet is fixed and sent to budget holder (and the planning exercise start, they are allowed to enter the values after that).

Keep in mind the the The product can be same but the suppliers can be different for each region.

For example

For New York (Entity)

Product1 - Supp1

For Miami (Entity)

Product 1 - Supp1

Product 1 - Supp2

Thanks

[former_member186338 · Accepted solution]

"The PowerUser(administrator) will select the Products and the Suppliers" - how? And how it's related to the region?

[former_member229754 · Accepted solution]

Sorry, let me correct, its PowerUser/Sales Manager will define the structure of Products and Suppliers to be planned next year based on Entity (Region (reading by context))

They will see the Products hierarchy and select the suppliers that they want plan.

[former_member186338 · Accepted solution]

Still the process is unclear...

What do you mean by:

"will define the structure"

"select the suppliers that they want plan"

?

[former_member229754 · Accepted solution]

They will select the Products and The Supplier means Define the structure.

They have the Products there, and select which suplier (with EPMInsertMember) which supplier and plan (with value against it)

Thanks

[former_member186338 · Accepted solution]

Line by line? Then it will be a static report....

[former_member229754 · Accepted solution]

Maybe I explaining incorrectly:

When you say Static Report its means the template is same for another Entity?

for example, when I select (Product/Supplier) for New York, same (Product/Supplier) will be for Miami? or the static in this case the (products/supplier) will be different when I switch entity.

The New york is selling product1 supplier1 but, miami is not selling product1, only product2 with supplier5.

[former_member186338 · Accepted solution]

The issue is that the combination of Region and Product - Supplier is not defined somewhere...

Then the person responsible to prepare the input schedule has to create it manually - line by line.