Smoothie imports the data from excel workbook and databases [MySQL and MS-SQL]. While importing from excel file it supports two formats (i) Tabular and (ii) Cross-Tabular, but only Tabular format is supported for the databases.
Here is a list of outbound ALDH external programs which are created to support the Smoothie model data export,
Following are the four different categories of the data which gets exported to Smoothie,
Smoothie attributes table is constructed based on the table mat_loc_cons or model_mat_loc_cons. The first priority is given to the table model_mat_loc_cons based on the value of the input parameter MODEL_NAMES exists in the model_mat_loc_cons table. Otherwise all the attributes will be exported from mat_loc_cons.
The values (1,2,3,...,20) passed through the parameter AGG_KEYS are internally resolved as Attribute_01, Attribute_02, Attribute_03,...,Attribute_20 against the table mat_loc_cons or model_mat_loc_cons. These aggregation keys will finally act as the base of the Smoothie model.
The exported Smoothie attributes are the fields Output_01, Output-02, Output_03,...,Output_20 in the table mat_loc_cons or model_mat_loc_cons and resolved based on the values (1,2,3,...,20) passed for the input parameter OP_SEQUENCE.
These attributes are exported in similar way for both (tabular/cross-tabular) type of export.
The quantity data exported from the ALDH table qty_staging are based on the configuration in the table ts_mapping_detail. The TS_Mapping table contains the basic information about all the record types, plan, class etc. which are to be exported from the Qty_Staging table and the mapping between the Smoothie and qty_staging record types. The value passed in for the input parameter MAPPING_SCN decides the selection of a particular set of mappings configured in the table TS_Mapping_Detail.
The value passed for the parameter TIME_BUCKET indicates that the quantity values are summarized based on WEEK or MONTH before exporting to Smoothie. The records should not be older than HISTORY_PERIODS from the PROCESS_DATE and should not be newer than FORECAST_PERIODS.
Mostly the date independent data like conversions, policies etc. are exported from these tables. The exporting of data from these table are based on the parameter CONV_LEVEL and POLICIES_FACTOR. The value passed for the parameter CONV_FACTOR takes the precedence if value for original parameter is empty.
Following is the way to select the factor table from where the data will be exported, based on the input parameter value:
| Parameter value | Factor Table |
|---|---|
| M | mat_factor |
| ML | matloc_factor |
| MC | matcons_factor |
| MLC | matloccons_factor |
The data exported from these table are filtered based on the parameters BOM_Name and BOM_VERSION and also validated against the parameter PROCESS_DATE which should fall under the date period as configured in table bom_version. The parameter LINKS_LEVEL governs whether to export the data from ML_Links or MLC_Links based on the value ML or MLC respectively. The value passed for the parameter CONV_FACTOR takes the precedence if the value for LINKS_LEVEL is empty.