Main analysis scenarios are:
To see which dimensions that can be used with each fact in, for example Excel pivot analysis, see section Fact and Dimension Connections below.
Cube Fact (DSV name) | Measure Group | Referenced Information Source | BI Access View | Access Type |
FACT_PURCHASE_ORDER_CHARGE | PURCHASE ORDER CHARGE | FACT_PURCHASE_ORDER_CHARGE | FACT_PURCHASE_ORDER_CHARGE_BI | On Line |
FACT_PURCHASE_ORDER_LINE | PURCHASE ORDER LINE | FACT_PURCHASE_ORDER_LINE | FACT_PURCHASE_ORDER_LINE_BI | On Line |
FACT_REPORTING_CURRENCY RATES | CURRENCY RATES | FACT_CURRENCY_RATES | FACT_CURRENCY_RATES_BI_OPT | On Line |
Each measure in the facts is described in section Measures. Corresponding Information Sources are described below. Detalled infomation about Information Sources can be found in IFS Online Documentation.
FACT_PURCHASE_ORDER_LINE
Purchase Order Line information source is based on IFS\Purchase Orders. This
information source can be used to design reports and queries about suppliers and
purchase order lines. Main focus is on purchase amounts and delivery
performance.
FACT_PURCHASE_ORDER_CHARGE
Purchase Order Line information source is based on IFS\Purchase Charges. This
information source can be used to design reports and queries about carges
connected to purchase orders.
Cube Dimension | Note |
ACTIVITY | |
COMPANY | |
COMPANY REPORTING PERIOD | |
CONDITION CODE | |
CREATED DATE | |
EXTERNAL SERVICE TYPE | |
FORWARDER | |
INSPECTION CODE | |
INTERNAL DESTINATION | |
INVENTORY LOCATION | |
INVENTORY PART | |
ORDER CANCEL REASON | |
ORDER COORDINATOR | |
ORDER DELIVERY TERM | |
PROJECT | |
PURCHASE BUYER | |
PURCHASE CHARGE TYPE | |
PURCHASE GROUP | |
PURCHASE ORDER CHARGE | This is a cube-only dimension, i.e. not supported by a standard dimension. |
PURCHASE ORDER LINE | This is a cube-only dimension, i.e. not supported by a standard dimension. |
PURCHASE PART | |
QUALITY CONTROL ANALYST | |
REPORTING CURRENCY | |
REPORTING DATE | |
REQUISITIONER | |
SHIP VIA | |
SITE | |
SUPPLIER | |
SUPPLIER STAT GROUP | |
TECHNICAL COORDINATOR | |
WANTED DELIVERY DATE |
The Sales cube supports calculation of base currency amounts to a reporting currency. To make this work it is necessary to create/select a currency rate type in one company as the rate source. The relevant configuration lookup must also be defined.
Refer technical documentation for more information.
The Procurement cube is using the Company Reporting Period dimension, which means that it is necessary to create a specific Reporting Period Definition to be used by this cube. The created/selected identity must also be defined in the lookup configuration for the ETL process, using Source = 'Procurement'.
The cube supports calculation of base currency amounts to a reporting currency. To make this work it is necessary to create/select a currency rate type in one company as the rate source. The relevant configuration lookup must also be defined.
Please refer technical documentation for more information
The following picture shows how different facts in the cube are connected to the available dimensions.
Aggregation of measures is based on SUM if not explicitly noted.
This sections describes the basic measures in the cube. These are either measures defined in the core Information Source or in the ETL process. The columns have the following meaning:
Measure | Measure Group | Core Measure | ETL Measure | Cube Measure | Measure Expression | Reporting Currency Measure | Aggr. Method | Note |
Qty Invent | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Base Price | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Discount Amount Base | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Discount Amount Curr | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Additional Cost Amount Curr | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Net Amount in Base Curr POL | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Net Amount in Order Curr POL | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | |
Qty Pegged | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Arrived | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Invoiced POL | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Scrapped | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Scrapped Credit | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Scrapped at Supplier | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Returned | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Returned Credit | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Count Purchase Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Number of Orderlines not cancelled. |
Count Early Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Early Orderline: Latest delivery date < Promised Delivery Date |
Count Order Lines On Time | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | On Time Orderline: Latest delivery date = Promised Delivery Date |
Count Late Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Late Orderline: Latest delivery date > Promised Delivery Date |
Count Damaged Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Scrapped and/or Returned Order Lines |
Count Complete Order Lines | PURCHASE ORDER LINE | NO | YES | NO | NO | NO | SUM | Revised Qty = Arrived Qty |
Count Incomplete Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Arrived Qty < Revised Qty |
Count Perfect Order Lines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Complete Order Lines On Time |
Count Cancelled Order Lines | PURCHASE ORDER LINE | NO | NO | YES | NO | NO | SUM | |
Count Agreement OrderLines | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Orders which have a Blanket Order number |
Qty Purchase | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Net Amount POL RC | PURCHASE ORDER LINE | NO | YES | NO | YES | YES | SUM | Net amount (Purchase Order Line) in reporting currency |
Discount Amount RC | PURCHASE ORDER LINE | NO | YES | NO | YES | YES | SUM | Discount amount (Purchase Order Line) in reporting currency |
Inv Qty Arrived | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty On Order | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Invoiced | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Scrapped | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Scrapped Credit | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Scrapped No Credit | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Scrapped at Supplier | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Returned | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Returned Credit | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Returned Rework | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Damaged | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Inv Qty Incomplete | PURCHASE ORDER LINE | YES | NO | NO | NO | NO | SUM | Qty in Inventory UoM |
Qty Charged POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Qty Invoiced POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | Qty in Purchase UoM |
Net Amount in Base Curr POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | |
Net Amount in Order Curr POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | |
Count Charge Lines | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | |
Charge Amount in Base Curr POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | |
Charge Amount in Order Curr POC | PURCHASE ORDER CHARGE | YES | NO | NO | NO | NO | SUM | |
Charge Amount POC RC | PURCHASE ORDER CHARGE | NO | NO | NO | YES | YES | SUM | Charge amount (purchase order charge) in reporting currency |
Net Amount POC RC | PURCHASE ORDER CHARGE | NO | NO | NO | YES | YES | SUM | Net amount (purchase order charge) in reporting currency |
Currency Rate | CURRENCY RATE | YES | YES | NO | NO | NO | Average of Children |
Currency rate used to calculate amounts to reporting currency. The core measure is modified in ETL |
Calculated measures are in the cube calculated with respect to other measures. The table below defines the general meaning/definition of each calculated measure.
Measure | Meaning |
Avg Delivery Days Early | Sum Delivery Days Early/Count Early OrderLines |
Avg Delivery Days Late | Sum Delivery Days Late/Count Late OrderLines |
Avg Delivery Days Off Time | Sum Delivery Days Off Time/(Count Late OrderLines + Count Early OrderLines) |
Perfect Orderlines % | Count Perfect OrderLines/Count Purchase OrderLines |
Orderlines on time % | Count OrderLines On Time/Count Purchase OrderLines |
Incomplete Orderlines % | Count Incomplete OrderLines/Count Purchase OrderLines |
Complete Orderlines % | (Count Purchase OrderLines-Count Incomplete OrderLines)/Count Purchase OrderLines |
Time based measures are calculated in the cube with respect to other measures. The table below defines the meaning/definition of the different time measures. These measures need to be used with a specific time dimension defined in the table below.
Measure | Meaning |
Ytd | Aggregated value for current month in current year. E.g.
for period 201210 Ytd represents sum of periods 201200-201210. Based on [REPORTING_DATE].[Month Hierarchy] |
R12 | For a given period, the sum all months from one year back up to the
previous month. E.g. Rolling 12 for 201210 is the sum of months 201110
- 201209 Based on [REPORTING_DATE].[Month Hierarchy] |
PY | Previous Year The value of the corresponding month one year back. E.g. for month 201210, the value of month 201110. Based on [REPORTING_DATE].[Month Hierarchy] |
YTD PY | Year to Date Previous Year Aggregated value for corresponding month one year back. E.g. for month 201210 YTD Previous Year represents sum of months 201101-201110. Based on [REPORTING_DATE].[Month Hierarchy] |
R12 PY | Rolling 12 (completed) Months Previous Year For a given month, first going one year back, then taking the sum of all months from one (more) year back up to the previous month. E.g. for month 201210 the sum of month 201010-201109 Based on [REPORTING_DATE].[Month Hierarchy] |
Avg XXX Ytd | Sum XXX Ytd/Count XXX Ytd |
Avg XXX Rolling 12 | Sum XXX Rolling 12/Count XXX Rolling 12 |
XXX % Ytd | Count XXX Ytd/Count YYY Ytd |
XXX % Rolling 12 | Count XXX Rolling 12/Count XXX Rolling 12 |
This section lists dashboards and reports in the example content for the BI Analysis Package that is using this cube:
UI Name | Type |
Supplier Performance | Excel Dashboard |
Supplier Reliability | Report |
Amount per Purchase Group | APC - Analysis Panel Component |
Delivery Precision - Number of Order Lines | APC - Analysis Panel Component |
Purchasing Amount Last 12 Months | APC - Analysis Panel Component |
Purchasing History Last 12 Months | APC - Analysis Panel Component |
Shipping Quality | APC - Analysis Panel Component |
Supplier Reliability Last 12 Months | APC - Analysis Panel Component |
The BI specific and also related core components listed in this section are required, i.e. they must along with other dependent components, be part of the customer installation to successfully use this cube.
Note that only directly used components are listed. Each such component can have its own list of dependent components. Please refer to the Component Deployment Profile File for each component to get the full picture.
Component | Type | Component Name | Product |
BISEDI | BI | BI Services Dimensions | Business Intelligence |
APTOOL | BI | Common scripts and utilities, BI Anapac | Business Intelligence |
APPSDI | BI | Application Services Analysis Package Dimension | Business Intelligence |
ENTEDI | BI | Enterprise Analysis Package Dimensions | Business Intelligence |
ACCRDI | BI | Accounting Rules Analysis Package Dimensions | Business Intelligence |
ACCRFT | BI | Accounting Rules Analysis Package Fact | Business Intelligence |
PROJDI | BI | Project Analysis Package Dimensions | Business Intelligence |
MPCCDI | BI | Gen Inventory and Distr BI Anapac Dimensions | Business Intelligence |
PARTDI | BI | Part Catalog Analysis Package Dimensions | Business Intelligence |
INVEDI | BI | Inventory Analysis Package Dimensions | Business Intelligence |
PURCDI | BI | Purchasing Analysis Package Dimensions | Business Intelligence |
PURCFT | BI | Purchasing Analysis Package Facts | Business Intelligence |
PCSUPC | BI | Procurement Supplier Cube | Business Intelligence |
ENTERP | CORE | Enterprise | Financials |
ACCRUL | CORE | Accounting Rules | Financials |
PROJ | CORE | Project | Projects |
MPCCOM | CORE | General Inventory and Distribution | Supply Chain |
PARTCA | CORE | Part Catalog | Supply Chain |
PURCH | CORE | Purchasing | Supply Chain |
INVENT | CORE | Inventory | Supply Chain |
Note: BI Component used will be PCSUPC