Skip to Content
0

BW planning - disaggregation - AfO - entry of new record is not possible

Feb 27, 2017 at 05:01 PM

543

avatar image
Former Member

Hello

We are at BW 7.5 sp 03.There is an input ready query with disaggregation activated. I have discovered that I am not able to entry a new record (Analysis for Office) unless all the chars are in the rows or columns of the query.

For example, if cost center is moved out from rows then system deactivates the entry of new rows (see screenshot01 - entry of new rows is active, screenshot02 - cost center has been moved out from rows and entry of new rows is deactivated).

I would like to entry new records at any level of chars/aggregation.

Thanks

screenshot01.png (131.9 kB)
screenshot02.png (145.9 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Gregor Dieckmann
Feb 28, 2017 at 10:24 AM
1

Hi Aleksandrs,

new lines are only supported on the lowest level, i.e. all characteristics from the used aggregation level have to be drilled-down or restricted to a single value. In other words, values in data cells in a new lines never have to be disaggregated.

What would you expect if you enter a new line not on the lowest level? In this case - by definition of a new line - there are no transaction data, so what should be the rule to generate data records for characteristics not drilled-down and not restricted to single values? The only rule that might work is all cases is to create all valid combinations.

Regards,

Gregor

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

see my extra question posted

0
Former Member

Huge thanks Gregory

0
Jyothirmayee A Feb 27, 2017 at 09:15 PM
0

Hi,

What does your settings in planning tab of Query properties please?.

Below link might give you more details:

Disaggregation (Also Known as Top-Down Distribution)

In input-ready queries, normally only cells at the detail level of the underlying aggregation level can be changed. Any cells that contains aggregated values, result cells or internal hierarchy nodes for example, are not input ready. To be able to change an aggregated value, this value must be disaggregated on all data records that contribute to it.

Note

It is not possible to disaggregate using the unit characteristic for a key figure or using characteristic 0INFOPROV. The unit characteristic for the key figure and 0INFOPROV are therefore also required characteristics for structural components with disaggregation, meaning that they always need to be set explicitly for the input-readiness of a cell.

Setting

Description

No disaggregationThe values in the structural component are not disaggregated. Cells containing values that are aggregated for the aggregation level cannot be changed.Disaggregate entered valueCells containing values that are aggregated for the aggregation level can be changed. The new entered value is distributed to all data records that contribute to the changed cell. The type of distribution depends on your entries, as described below.Disaggregate differenceCells containing values that are aggregated for the aggregation level can be changed. The difference between the old entered value and the hew one is distributed to all data records that contribute to the changed cell. The type of distribution depends on your entries, as described below.

Distribution type

Description

Equal distributionDistribution is peformed equally to all data records that contribute to the changed cell (inclusing data records with zero values).Analogous distribution (to self)Distribution is peformed analogously to all data records that contribute to the changed cell.Analogous distribution (to following structural element)You can specify a structural element as a reference. Distribution is peformed analogously to all data records that contribute to the relevant cell of this referenced structural element. You can choose a structural component from the same structure as the reference for the analogous distribution.

Input-Ready Formulas

To make it possible to enter values for formulas, Average Price as a quotient of Amount and Quantity for example, you can make the formulas input-ready. To do this, go to Change Data on the Planningtab page and select Input Ready (Lock Relevant) for the formula in question.

The input-ready formula becomes the carrier of a formula group . In our example, the quotient Average Price and the two operands Amount and Quantity belong to the formula group. A rule (in the form of an inverse formula) needs to be defined for every input-ready operand in the formula. This rule specifies how the system calculates back to this operand if the value for the Average Price is changed. To do this, choose Create Inverse Formulas in the context menu. By double-clicking on an inverse formula, you can call the Change Formula screen. Define the rule valid for the inverse calculation.

Result

Creation of Planning Applications

To plan business data, you create BI applications that use an input-ready query as a data provider. You can do this in either SAP BusinessObjects Analysis Edition for Microsoft Office Version 1.1, BEx Web Application Designer or BEx Analyzer.

Input Ready Queries at Execution

In BI applications that use input-ready queries as data providers, you can enter data manually at runtime.

Whether the cells in an input-ready query can be changed at execution depends on the query view and possibly on other settings (such as settings for data slices and characteristic relationships).

In terms of whether the cells of a query view are input ready, note the following rules:

  1. In a query that is used for manual planning, a cell is only input ready if each characteristic value of all the characteristics included in the aggregation level is unique. This means that any values aggregated for the aggregation level are not input ready: Totals, subtotals and internal hierarchy nodes are not input ready.
  2. To be able to change values for calculated key figures too ( Average Price as a quotient of Amount and Quantity for example), they must be based on formulas, and at least one operand must be input ready. More information: Inverse Formulas at Runtime and Examples: Inverse Formulas at Runtime .
  3. To be able to change aggregated values (for the aggregation value), these values must be disaggregated on all data records that contribute to them. For examples of how to use disaggregation, seeDisaggregation (Top-Down Distribution) .
  4. If a query used for manual planning includes a navigation attribute that is restricted using a fixed or dynamic filter or a restricted key figure, the system treats the navigation attribute as a normal characteristic. The rule under point 1 applies here. If the navigation attribute is not restricted, the system responds as if the navigation attribute was not part of the query.
  5. In a query that is defined on a MultiProvider or a complex aggregation level and is intended for use in manual planning, the cell is not input ready if the InfoProvider determined by this cell is:
    • Not a real-time InfoCube
    • A real-time InfoCube that has been switched to load mode
    • No DataStore object for direct updates in planning mode.
  6. If an input-ready query is executed in change mode, but the requested data is locked by another user, the query starts in display mode.

Thanks,

Jothi

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Feb 28, 2017 at 05:26 PM
0

Thank you Gregor for prompt and detailed answer.

What would you and SAP recommend for the following scenario :

Analysis for Office, BW 7.5, sp 03, adjustments to actual and planned data

users would like to enter records (lines 2, 3, 4) at any level of aggregation (see example attached ) based on existing record (line 1)

Users have at least 3 prefered levels of aggregation but might have more

Huge thanks in advance


screenshot03.png (11.0 kB)
Share
10 |10000 characters needed characters left characters exceeded
Gregor Dieckmann
Mar 01, 2017 at 11:51 AM
0

Hi Aleksandrs,

in your example you have 3 free characteristics, so when one enters a new line the system has to know the values 'asset number', 'profit center' and 'company code' to be used; if these characteristics are restricted to a single value everything is clear. But if some of these characteristics have a more general filter the only 'generic' option I see is to create all valid combinations from the filter of the free characteristics and the values specified in the new lines. This kind of functionality might be useful but does not exist yet.

So you have to ask the users what they expect here. Depending on the answer a planning function to create combinations using the filter from the free characteristics and the single values in the new line might do the job.

Regards,

Gregor

Share
10 |10000 characters needed characters left characters exceeded
Anand Kumar Mar 01, 2017 at 12:52 PM
0

Hi,

Use three variables( Asset Number, Proficit center, Com Code) and let the user input the values in that variable. Use all the characteristics from aggregation level in the query so that query will generate all the characteristics combination and it will be input ready.

Regards,

Anand

Share
10 |10000 characters needed characters left characters exceeded