Access Control Model Extension Limitations for aP Analytics

Limitations for Component Roll-Up and Assembly Reports

Some Out-of-Box (OOB) reports, such as Value Tracking and DTC Metrics reports, use rollups to group components. If some of the components in a rollup are not accessible to a user due to access control rules, the results displayed by the report may not add up correctly. This disparity occurs because the aggregated results may not reflect what the user sees on the screen. In the aPriori client, the aggregated cost fields for rollups and assemblies are re-calculated when the scenario is opened. The aggregated values for the roll-up are persisted in the reporting database during the scenario export process and cannot be changed when reports are run. Assembly reports, such as assembly cost and assembly details, could show partial results for the same reason.

Limitations for Deployment Leader Reports

User Activity Reports access the usage records in the Operational Database. They do not access the reporting database or look at scenario records, so they do not need to be adjusted with access control conditions in the underlying SQL queries.

Scenario Activity Reports access the reporting database and use tables, including the scenario and scenario_facts tables. The activity reports do not show any scenario data; they count things like Digital Factories, Process Groups, Processes, and Materials. Since there is no scenario information displayed, their queries are not adjusted  for access control purposes.

Limitations for Ad Hoc Views

When users create ad hoc views, the views can only reach scenarios the user has access to. An ad hoc report that counts scenarios, for example, will only count the scenarios that the user has access rights for. Therefore, using the OOB scenario activity reports could produce different results than a similar ad hoc report that is created by an end user.

In addition, the problem of rollups and assemblies containing aggregated cost fields that do not match the child scenarios (due to some child scenarios not being accessible), will also be present in ad hoc views.