Planning is about changing and creating new data. As a result a concept to control the objects to be changed/created is essential. This section deals with this kind of problem in the PlanQuery, i.e. with the question: When is a cell in a query view input ready?
This page will help you to understand how to make a planning query cell input ready (inputable).
SAP Online Documentation
Input Ready Queries at Runtime : Here are the 6 rules to make a cell input ready are explained.
To create an input ready query the query must be based on Aggragation level. Following part providers are supported: DSO/ADSO (direct update), Cube-Like ADSO, Infocube (realtime).
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 / direct update ADSO
A real-time InfoCube that has been switched to load mode
- All key characteristics of ADSO (including time-characteristics) must be mapped to ALVL. However, this does not apply for infocubes and cube-like ADSOs.
- The query must be flagged as follows: "Start Query in Input Mode". Furthermore, at least one key figure must be selected as input ready.
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 or added into drill down including 0INFOPROV. Thus, any values aggregated for the aggregation level are not input ready: Totals, subtotals and internal hierarchy nodes are not input ready.
If drill down or set a single value filter on a characteristic (except 0unit, 0currency and 0infoprov, they need unique restriction anyway) is not possible, then set the disaggregation for the key figure itself. Please note that time characteristics can be derived from another time characteristic are not necessary in the query.
To enable 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.
To be able to change aggregated values (for the aggregation value), these values must be disaggregated on all data records that contribute to them.
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. If the navigation attribute is not restricted, the system responds as if the navigation attribute was not part of the query.
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.
Rule 8 explains when a query using a navigation attribute, how the system works:
8. 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. If the navigation attribute is not restricted, the system responds as if the navigation attribute was not part of the query.
If a input ready query is using navigation attribute A__B with a filter, although A__B value can be derived from A, such derivation is not checked when the filter on A__B contains more than one value.
More details see: Input Ready Query with Nagivation Attributes
For a multiprovider contains a aggregation level, or a multi-aggregation level, you need to put 0infoproivider into drill down or set a single value filter on 0infoprovider to make the cell inputable
Rule 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.
- If you have set "calculate result as..." on the formula, the result line won't be inputable even though disaggregation is set.
It is possible to make a key figure with currency translation input ready, however the value can get some rounding issue after transfer or save the data. This is a system behavior that can't be avoided. So it is not recommended to directly plan on a key figure with currency conversion. When you do need to use this feature, please take the rounding effect into consideration.
See a simple example of: Input ready key figure with currency translation.