A sales question sounds simple until different teams define sales differently. One report uses invoices, another booked orders and another receipts. Agree the business definition and supporting records before adding a conversational interface.

THE IDEA

Owned metric definitions

To apply this workflow in your business, explore our AI business analytics service and implementation approach.

Choose a question the owner can verify

Start with a specific measure, such as invoiced sales by product for a closed period. Document posting basis, organisational scope, currency and returns. Make those definitions visible alongside the result.

Compare with an approved report. If two reports disagree, investigate their filters and definitions before asking an assistant to explain the difference.

Confirm the actual integration path

Review the supported interfaces and access available in the SAP environment. Identify the approved reporting source, refresh behaviour and ownership of joined ERP or manufacturing fields.

Do not assume every installation exposes the same interfaces. Confirm source availability and integration scope before promising a report. Preserve lineage when a result combines SAP with local ERP or MES records.

References: SAP Architecture Center: SAP Business AI Platform

Separate calculation from explanation

Calculate totals using defined reporting logic, then let the assistant explain the result and retrieve permitted supporting records. Show period, filters and source context. Surface stale or incomplete data explicitly.

Provide a drill-down that a reviewer can use to inspect the transactions behind a figure. A confident explanation cannot repair an incorrect join or a duplicated transaction.

Validate entity and user boundaries

Ask the same question as users in different roles and entities. Check both the summary and its transaction drill-down; an aggregate should not bypass record-level access restrictions.

For groups with several operating entities, agree currency conversion, reporting calendars and date presentation with the report owner. Keep metric definitions consistent while documenting legitimate entity differences.

TAKE THIS INTO YOUR NEXT DISCUSSION

A practical starting checklist

  • Owned metric definitions
  • Approved SAP data path
  • Traceable calculation
  • Role and entity testing

Start with an agreed scope, test the exceptions and keep the responsible people in control.

Original implementation guide by IOT Software and Solutions. Examples describe proposed workflows, not measured customer results.

Put the idea into practiceExplore AI Business Analytics