Hello,
using IP 7.0 with BEx Analyzer we want to have different input ready queries for the input of plandata.
We want to plan a great set of positions for productgroups for different stores.
Planners are usually responsible for a whole productgroup for different stores, the combination which productgroup is sold in what store is maintained in a DSO, since we can not rely on any actual data due to changes for the future. Queries show productgroup and stores in columns.
Depending on a navigational attribute of the product group (category A or not) more positions (rows) are needed to be planned. It would be great if in the planning query only positions are shown, which are to be planned.
Question:
how can you show only positions to be planned in the query, if positions for product groups depend on nav.Attribute of product group?
Another factor in some planning queries is the period in which we are currently planning.
In certain periods there are more positions to be planned, like the input of all positions once a year or the change of the level of data input (6 month based only on level of productgroups, but next 6 month based on productgroups in combination with companies.)
Question:
How to change that the input ready cells for month 1 to 6 are shown for the product groups (each planning query would be restricted to one product group by variable selection) -
how to change the input ready cells for month 7 - 12 to the level of stores, were no input is allowed on productgroup level, but only on store level.
Question:
Since there is a whole set of positions to be planned, the positions should be shown in a formated way using headings vor a certain set of products. There are no sums to be shown for the headings.
What is the best way to do this in combination with only showing positions needed? Hierarchy or structure? Keeping in mind that for certain productgroups (nav.-attribute category) some positions are not to be planned at all.
Question:
The next question is that certain input queries are not needed at all depending on another nav.-attribute of the product group. Since plandata should be planned via BEx Analyzer Workbook is there a better way than VBA to hide the tabs of queries not needed for input for certain product groups (depending on the nav. attribute they have?)
Thanks for your ideas,
Angie