Abraxio API - PowerBI Tutorial

Abraxio API - PowerBI Tutorial

Demo Power BI Reports

We provide Power BI models as attachments to this article (at the bottom of the page).



  1. DemoFinance_v2.3: Compared to the "v2.2" model, this new version includes two additional analysis tabs with treemaps (which work on the v2.2 data model) and a new consumption analysis tab (which requires updates present in the v2.3 data model).
  2. DemoPortfolios_v2: Compared to the "v1" model, this new version adds assignments to the model and a new tab that leverages this data.

Connect your data to Abraxio example files

  • Step 1

    • Download one of the models attached to this article (at the bottom of the page): DemoFinance_v2.pbit, DemoFinanceBasic_v1.pbit or DemoPortefeuilles_v1.pbit
      • DemoFinance_v2.2: If you were already using our previous model "v1", this new version allows you to also use the project/activity analytical axes (available in the model and in the "Budget Analysis" example tab)
      • DemoFinanceBasic_v1.1: Example without data transformation, with a model very close to the one exposed by our APIs

  • Step 2

    • When opening the model, the Abraxio API URL is already populated, you still have to fill in the authentication elements specific to your environment ( click here to access the documentation on authentication at (API):



To use these files, your API access must have at least the dataset.finance.read and dataset.portfolios.read scopes
  1. Choose Anonymous access:


  • Step 3

    1. When loading the data, you will need to check the box "Ignore privacy level controls for this file":




Error loading data
If you encounter the above error message when loading data, you must modify the confidentiality parameters in your file in the following configuration:



Description of Power BI Demo Models

DemoFinance Model

This file loads and transforms data retrieved from the Abraxio APIs to populate a model used for advanced reporting (comparisons between fiscal years, closings, and archives).

Example Reports

This report includes several tabs:

  1. Budget Analysis: breakdown of the budget by nature (Build/Run, OPEX/CAPEX, projects/activities).
  2. Detailed Budget: breakdown of the budget by analytical axis with a detailed table.
  3. Comparisons: comparison of multiple fiscal years, archives, or closings based on key budget indicators.
  4. Monthly Comparisons: monthly comparison of the budget (€ and man-days) across different fiscal years.
  5. Breakdown by Category and Type: treemaps of the budget by Cigref category and by type (Build/Run/Transversal).
  6. Breakdown by Axes: treemaps of the budget by analytical axis from the Finance module and the Portfolios module.
  7. Consumption Analysis: monthly tracking of actual consumption by project and supplier, and comparison between budget and consumption.

Description of the Example Data Model

Below is the schema of the data model powering the reports described above:


  1. Projects: list of projects with their attributes. Projects are linked to fiscal years and archives/closings, so this table contains one entry per project per fiscal year, archive, or closing.
  2. ProjectsDimensionsValues: details of analytical axis values for projects.
  3. ProjectsDimensionsDescription: descriptions of analytical axes for projects.
  4. Budgets: list of fiscal years.
  5. Snapshots: list of archives/closings, including an entry named “Budget” representing the “current” budget for each fiscal year. This is used to build the advanced selector for fiscal years/archives/closings in the “Comparisons” report.
  6. Lines: list of budget lines (originating from a fiscal year’s budget, a closing, or an archive).
  7. LinesSchedules: monthly schedule associated with a budget line.
  8. LinesDimensionsValues: details of analytical axis values for a budget line.
  9. BudgetDimensionsDescription: description of the analytical axis configuration for a budget line.
Info
Update – September 2024: version 2 of the model now loads detailed analytical axis values for projects and includes filters on the first two configured axes in the “Budget Analysis” example.

DemoFinanceBasic Model
This file loads a “raw” model (similar to the one exposed by the APIs) from the Abraxio APIs and provides some example reports.

Example Reports

This report includes several tabs:

  1. Budget Analysis: key indicators on budget allocation (Build/Run, OPEX/CAPEX, projects/activities, CIGREF categories) with filters for the fiscal year and main analytical axes from Finance and Portfolios.
  2. Detailed Budget: budget breakdown by analytical axis (in %) with quality indicators and a detailed table by project/activity.
  3. Monthly Comparisons: comparison of budgets (€ and man-days) across multiple fiscal years.
  4. Closing Analysis: same analysis as the “Budget Analysis” tab, applied to closings and archives.
  5. Detailed Closing Budget: equivalent of “Detailed Budget” for closings and archives.

Description of the Example Data Model

Below is the schema of the data model powering the reports described above:


  1. Budgets: list of fiscal years.
  2. Snapshots: list of closings/archives for a fiscal year.

The model then provides details for the entire budget of a fiscal year or archive/closing, using the following tables (prefixed with Snapshots for archives/closings):

  1. Projects: list of projects with their attributes. Projects are linked to fiscal years.
  2. ProjectsDimensionsValues: details of analytical axis values for projects.
  3. ProjectsDimensionsDescription: description of analytical axes for projects.
  4. BudgetLines: list of budget lines.
  5. BudgetLinesSchedules: monthly schedule associated with a budget line.
  6. BudgetLinesDimensions: details of analytical axis values for a budget line.
  7. BudgetDimensionsDescription: description of the analytical axis configuration for a budget line.
Info
For more details on the data provided by the Abraxio Finance APIs, refer to the dedicated article here
DemoPortefeuilles Model
This file loads data from the Portfolios module via the Abraxio APIs and provides functional example reports.

Example Reports

  1. Portfolios Summary: global KPIs by portfolio with breakdown of projects/activities by stage and status, latest flash report status, overdue milestones, unresolved critical risks, and comparison of budget vs. actual consumption (€ or man-days).
  2. Portfolios Budget: detailed budget view by project/activity with monthly tracking of budget, OPEX, and CAPEX.
  3. Portfolios Gantt: Gantt chart visualization of all projects/activities (start and end dates).
  4. Risks: global view with probability/severity matrix, total number of risks, unreviewed risks, breakdown by criticality, and summary table.
  5. Portfolio Evolution: monthly tracking of flash report status, risks by criticality, and budget vs. actual consumption.
  6. Project Evolution: detailed project/activity-level view of budget vs. actual consumption, overdue milestones, risks by criticality, total major risks, overdue milestones, consumption, and time allocation by stage.
  7. Assignments: tracking of assignments by portfolio and project/activity, Build/Run allocation, comparison with planned budget, and distribution by profile.

Description of the Example Data Model

Below is the schema of the data model powering the reports described above:



Data retrieved via APIs

  1. Projects: list of projects/activities.
  2. ProjectsBudgetSchedules: monthly schedule associated with a project.
  3. ProjectsDimensionsDescription: description of analytical axes for a project/activity.
  4. ProjectsDimensionsValues: details of analytical axis values for a project/activity.
  5. ProjectsMilestones: milestones of a project/activity.
  6. ProjectsReports: list of flash reports for a project/activity.
  7. ProjectsReportsBudgetSchedules: monthly schedule associated with a flash report.
  8. ProjectsReportsMilestones: list of milestones recorded during data capture (usually at publication) of a flash report.
  9. ProjectsReportsRisks: list of risks recorded during data capture (usually at publication) of a flash report.
  10. ProjectsRisks: list of risks for a project/activity.
  11. ProjectsRisksDimensionsDescription: description of analytical axes for project/activity risks.
  12. ProjectsRisksDimensionsValues: analytical axis values for a risk.
  13. ProjectsStatusHistory: history of project status changes.

Tables not available via the APIs

These are technical tables and cannot be retrieved through the APIs:

  1. AmountDisplay: technical table for displaying amounts (excl./incl. tax).
  2. Calendar: date table for centralized filtering across the model.
  3. MeasureMode: technical table for displaying cumulative or raw amounts.
  4. RiskProbabilities: technical table with probability values and scores for generating the risk matrix.
  5. RiskSeverities: technical table with severity values and scores for generating the risk matrix.

Tables built from multiple table

These tables are constructed from other tables and cannot be retrieved directly via the APIs:

  1. Risk Matrix: risk matrix generated from the RiskSeverities and RiskProbabilities tables.
  2. ProjectWeather: historical monthly flash report status per project. Table generated by combining multiple subtables to get the latest status per project/month (SourceMonthlyReports, SourceMaxSnapshotDateByProjetAndMonth)
DemoManagement Model
This file loads data from the Teams module via the Abraxio APIs and provides functional example reports.

Example Reports

This section allows tracking of team activity, planning, and resource usage:

  1. Employee Analysis: number of active employees, breakdown by type and profile, trends over time, and tracking of upcoming entries and exits.
  2. Workload Plan: workload table with color-coding based on allocation rate and chart showing assignment evolution relative to capacity.
  3. Timesheets: monthly tracking of entries, top 10 most used budget lines (in days), and treemap of projects/activities with the most recorded days.
  4. Absences: monthly absence table by department, team, and employee.

Description of the Example Data Model

Below is the schema of the data model powering the reports described above:


Data retrieved via APIs

  1. Assignments: assignment details (dates, lines, total assigned days).
  2. AssignmentsSchedules: assignment schedule by situation and line, with date and total days.
  3. Collaborators: employee information (identity, team, department, profile, email).
  4. CollaboratorsDimensionsDescription: description of possible dimensions for collaborators (labels, levels, multiSelect).
  5. Situations: list of employee situations (entry, exit, type, profile, supplier).
  6. SituationsDimensionsValues: dimension values associated with situations (attributes and codes).
  7. SituationsSchedules: schedule of situations with absences, assignments, capacities, and salaries.
  8. Timesheets: recorded timesheets per employee with date and employee ID.
  9. TimesheetsEntries: detailed entries per timesheet and budget line/project, with associated budget.

Tables not available via the APIs

  1. BudgetLineLabelList: list of budget line labels used in timesheets and budgets (used to display top 10 budget lines with most recorded days).
  2. Calendar: contains dates and time information (_YearMonth, MonthName) for tracking and data aggregation.
  3. DisplayMode: reference table for display codes and labels.
DemoFournisseurs Model

This file loads data from the Suppliers module via the Abraxio APIs and provides functional sample reports.

Sample Reports

This section enables you to monitor supplier activity through a financial perspective, track contracts and their deadlines, as well as manage evaluations.

  • Supplier analysis: Top 10 suppliers by budget, budget breakdown by supplier category, distribution by status, etc.

  • Finance: Budget evolution by fiscal year, with a focus on a specific supplier’s budget for a given year (employee-related and non-employee-related budget, committed, ordered, consumed, etc.).

  • Contracts / deadlines: Distribution of contracts by status, deadlines by type, list of deadlines to be processed and deadlines over the next 12 months.

  • Evaluations: Average evaluation score and radar chart allowing comparison of a supplier’s evaluation with its past evaluations, as well as with those of other suppliers.

Information retrieved via APIs

  1. Budgets: Budget headers defined by fiscal year and period.
  2. BudgetsLines: List of budget lines.
  3. BudgetsLinesSchedules: Monthly schedule associated with a budget line.
  4. CollaboratorsSituations: Monthly tracking of collaborator capacity, cost, and assignment.
  5. Contracts: General contract information (name, start/end dates, status).
  6. ContractsDimensionsDescription: Structure and levels of analytical axes applicable to contracts.
  7. ContractsDimensionsValues: Specific values and attributes linked to the analytical axes of contracts.
  8. ContractsTypes: Repository of the different types of contracts.
  9. Deadlines: Management of contractual deadlines, terminations, and renewals.
  10. InvoicesLines: Invoice line details, including net/tax amounts and invoice numbers.
  11. InvoicesLinesSchedules: Breakdown and actual consumption of invoices by period.
  12. OrdersLines: Order line details, including committed amounts and order balance.
  13. Ratings: Global ratings assigned to suppliers.
  14. RatingsCriterias: Detailed rating criteria with their respective weightings.
  15. SupplierDimensionsDescription: Nomenclature and hierarchy of analytical axes for supplier analysis.
  16. Suppliers: Main supplier repository (identity, country, currency, tax ID/SIRET, etc.).
  17. SuppliersDimensionsValues: Values of attributes and analytical axes assigned to each supplier.
  18. SupplierServices: Categorization of services and benefits provided by suppliers.

Tables that cannot be retrieved via APIs

  1. AllSupplierNames: Table used to list supplier names with their ranks and standings (Top 10).
  2. AmountDisplay: Technical table used to display amount indicators (e.g., Net vs. Gross).
  3. Calendar: Date table used for central filtering across all dates in the model.
  4. Mesures: Technical table used to display amount indicators as cumulative or raw.
  5. Paramètre: Configuration table for field and command parameters.

 

    • Related Articles

    • Abraxio API - Getting Started

      Preamble APIs allow you to interface your IS with Abraxio to automate processes, retrieve data from Abraxio or integrate data into Abraxio. API calls are secured using the OAuth2 protocol. Presentation of the scopes When creating your API accesses, ...

    • Abraxio API - General

      Two API categories are available in Abraxio: 1. Transactional APIs (creation and updating of Abraxio data from your tools) Goals : Fine and real-time integration of information or Bulk batch integration of certain information: Injection via API into ...

    • Change the Abraxio display language

      Go to My Profile Click on your name Change the language in the Account Information pop-up Click Save After registering, an alert message will appear in the selected language telling you that you will be logged out to take into account your language ...

    • How budgets work in Abraxio

      Definitions A Department budget (the ISD budget, for example) is managed by Fiscal year (2023, 2024 etc.). The budget will therefore be implemented over successive Fiscal years (ISD 2023, ISD 2024, etc.). It is made up of Projects and Activities. A ...

    • How do I initialize the management of planned absences?

      Introduction Abraxio allows you to manage your collaborator's planned absences in order to meet two objectives: Pre-populate timesheets and avoid double entry of absences for teams. Integrate future absences for a more accurate and accurate ...