Upload 2 files

table_desc.csv

@@ -4,16 +4,17 @@ HISTORY_AVAVBAIL,"Any questions related to AV (sub-assemblies, sub-assembly or m
 HISTORY_BUFamilyAvailability,"This table summarizes the availability of the SKU's (Products) at a family and business unit level. The taxonomy is the following. A family or families belong to a Business Unit (BU) AND SKU's (Products) belong to a family or families AND AV's (sub-assemblies, sub-assembly or modules) belong to SKU's AND Parts belong to AV's. Only Parts have a ""One to Many"" relationship with AV's. The rest of the relationships are ""Many to one"". Given this context. this table consists columns that have the ""Business Unit"" availability and ""Family"" Availability. This table contains current and historical data based on the file date or history date. Any question related to Family or BU (Business Unit) availability should be queries from this table"
 HISTORY_OpenOrderShortage,"This table contains the part level and the cause (root cause) of the shortage for both current and historical dates. It also contains the SKU (product) that is being ordered by the customer for which there is a ""Part"" level shortage. It also contains the customer order number (Customer PO) and the internal HP order number (HP Order number) associated with the SKU(Product) that is in shortage. Furthermore, it has the ""commodity"" classification associated with the ""Part"" and the ""Part description"". It also has the ""Family"" associated with the SKU that is in shortage. In summary this table has SKU's that are in ""Shortage"", where there are valid ""customer orders"" and the specific ""parts"" that go into the SKU that are in shortage and the root cause or reason for the shortage. Along with this mapping of shortage SKU and shortage part of the specific SKU, there is also the classification information about the SKU and Part. Furthermore, there is information about the specific order numbers as well. Critically, this table only contains information about orders (customer orders) that are in shortage. It does NOT contain information about all orders. For queries related to all orders please refer to table SMF_WT_BASE (Forecast and Orders)"
 MasterSkuAvBom_PA,"This table explains the taxonomy between AV (sub-assemblies, sub-assembly or modules) , SKU (product), Family(group of products) and Business Unit (group of families). A family or families belong to a Business Unit (BU) AND SKU's (Products) belong to a family or families AND AV's (sub-assemblies, sub-assembly or modules) belong to SKU's AND Parts belong to AV's. Only Parts have a ""One to Many"" relationship with AV's. The rest of the relationships are ""Many to one"". Given this context. this table consists columns that map the relationship between AV's with SKU's, SKU's with Families and Families with the Business unit. This table also contains the Business unit code called as ""PL"" or ""product line"""
-SMF_WT_BASE,"This table contains the list of all ""Customer Orders"" or ""Orders"" with respective order numbers, customer names and customer groups that they belong to. The Orders are associated with SKU's and their respective families and business units. Furthermore, this table contains the RTM (Route to Market), that the specific order belongs to. It also has columns which identify the Category Type (Unit or Display or Accessories). The ""Category Type"" is generally queried by its contents which are ""Units"" or ""Displays"" or ""Accessories"". 
+daily_inventory,"This table contains detailed information about ""Parts"" that have inventory or Stock currently. It also has information about ""Parts"" that had inventory or Stock in the past based on the file date or history date. Therefore, it contains detailed information about all parts. Its primary use is to track and monitor inventory at a part level. It contains the ""commodity"" classification that the part belongs and the ""Part description"". It also contains the ""unit price"" of the part and the ""Inventory or Stock value"". It also contains the business unit that the part belongs to. It also explains whether the Part is a ""Make"" or ""Buy"" part based on the MakeBuy column. "
+HISTORY_Sku_Shortage,"This table contains the shortage at an SKU (Product) level where there are active Customer orders. This table summarizes the SKU's and the quantity that is in shortage as well as the count of customer orders that are in shortage for that specific SKU. It shows current shortage and historical shortage based on the file date or history date. 
 
-This table also contains the ""forecast"" details. It contains the Forecast entry month (Fcst Month) which is the month IN which the forecast has been entered into the table. It also contains the Forecasted month (Month) which is the month FOR which the forecast has been entered. In general the forecast is made 6 to 9 month ahead for upcoming months and is refreshed month on month. 
+Any questions exclusively related to ""SKU Shortage"" should be queried from this table. "
+SMF_WT_BASE_ORDER,"This table contains the list of all ""Customer Orders"" or ""Orders"" with respective order numbers, customer names and customer groups that they belong to. The Orders are associated with SKU's and their respective families and business units. Furthermore, this table contains the RTM (Route to Market), that the specific order belongs to. It also has columns which identify the Category Type (Unit or Display or Accessories). The ""Category Type"" is generally queried by its contents which are ""Units"" or ""Displays"" or ""Accessories"". 
 
-The column that identifies whether the record is an ""order"" or a ""Forecast"" is TYPE. This column ""TYPE"" explains whether the line is an ""Order"" or a ""Forecast""
+Any questions related to ""Customer Orders""(Orders) or should be queried from this table. "
+SMF_WT_BASE_FORECAST,"This table contains the ""forecast"" details. It contains the Forecast entry month (Forecast_Month) which is the month IN which the forecast has been entered into the table. It also contains the ""Demand or Order month"" (Demand_Month) FOR which the forecast has been entered. In general the forecast is made 6 to 9 months ahead for upcoming months and is refreshed month on month. The ""Demand month"" or ""Order month"" is the month for which the forecast or prediction is being entered, where the order or demand is expected to appear. The ""Forecast month"" is the month in which the prediction or forecast is being made. This is done every month for the upcoming few months, depending on the type of product.
 
-This table also contains different forecasts, which helps see the change in month on month forecast for the same SKU or Product or Family based on the different between the ""Fcst Month"" and ""Month"" columns
+Furthermore, this table also contains a column ""M_Series"" to identify the count of months prior to which the forecast or prediction is being made. For example ""M1"" means that the prediction is being made 1 month before, ""M3"" means that the prediction is being made 3 month before, ""M6"" means that the prediction is being made 6 month before the actual ""Demand or Order"" month.
 
-Any questions related to ""Customer Orders""(Orders) or ""Forecast"" should be queried from this table. "
-daily_inventory,"This table contains detailed information about ""Parts"" that have inventory or Stock currently. It also has information about ""Parts"" that had inventory or Stock in the past based on the file date or history date. Therefore, it contains detailed information about all parts. Its primary use is to track and monitor inventory at a part level. It contains the ""commodity"" classification that the part belongs and the ""Part description"". It also contains the ""unit price"" of the part and the ""Inventory or Stock value"". It also contains the business unit that the part belongs to. It also explains whether the Part is a ""Make"" or ""Buy"" part based on the MakeBuy column. "
-HISTORY_Sku_Shortage,"This table contains the shortage at an SKU (Product) level where there are active Customer orders. This table summarizes the SKU's and the quantity that is in shortage as well as the count of customer orders that are in shortage for that specific SKU. It shows current shortage and historical shortage based on the file date or history date. 
+This table also contains a column to identify different levels of forecasts (Forecast_level), which helps identify whether the forecast is being made for an ""SKU"" or a ""Base unit"" or at a ""Family level"".
 
-Any questions exclusively related to ""SKU Shortage"" should be queried from this table. "
+Any questions related to ""Forecast"" should be queried from this table. "