Query

General

Use Queries to select the group of parts you want to work with. You create a query either in the Conditions dialog box or you can write an SQL inspired query, we are talking about the WHERE Clause part of an SELECT statement. This will make it more flexible to find the parts you want to take a closer look at. It is also possible to get the query result aggregated so that you will get the Forecast Table and Forecast Graph show the aggregated result of the query. You can the manipulate all parts in the query the same way that you will manipulate a group selection. The other option is to list out all parts matching the query you can then click on one of the matching parts this will select this part and you can use the GUI to manipulate the forecast for this part. Below you can se witch operators and fields that are supported.

Operators

A unary operator uses only one operand. A unary operator typically appears with its operand in the following format:

operator operand

Supported TO_DATE format mask parameters

Fields

In addition you can use any of the user selected groups that are using in a query, the field name of the group is then used as query name. If you use the any of the standard available groups these will be the names.

PART_PRODUCT_FAMILY

PART_PRODUCT_CODE

ABC_CLASS

TYPE_CODE_DB

LEAD_TIME_CODE_DB

PLANNER_BUYER

ASSET_CLASS

PRIME_COMMODITY

SECOUND_COMMODITY

DEMAND_MODEL

LIFECYCLE_STAGE

FREQUENCY_CLASS

And any other that you include yourself is available.

Note that for the fields Forecast Model, Season Profile, Period Profile and Weekly Profile you must use the ID / number when you write your query. For group fields with description you most use the ID for the group when writing the query.

Custom Fields: This allows user to add custom fields both in the  detail view and  query  based on the users’ business requirements. In order to add custom fields, User needs to navigate to forecast_cust_field_ setup_tab and specify the following custom field related information in the table columns manually.

In order to appear the inserted/updated custom fields in the detail view and  query, User needs to commit the changes done in the forecast_cust_field_ setup_tab and restart the demand plan server

Note- The user needs to run the POST_Demand_DemandServerUser.sql script, Once the changes have been committed in the forecast_cust_field_ setup_tab. (The script is stored in the following file location demand\source\demand\database\POST_Demand_DemandServerUser.sql ")