Business Intelligence Specialist (SAP)

Purpose of the role

Ensure the PMIS solution becomes operationally successful by protecting SAP as the system of record, ensuring correct financial integration, preventing license and scope surprises, and enabling clean reconciliation and acceptance across OpCos and corporate oversight.
 

Key responsibilities

1. SAP integration & data correctness (primary)
   1. Own the SAP-facing integration workstream end-to-end:

• • Define and validate integration objects (budgets, commitments, actuals, payments, vendor data as applicable).
  • Approve interface method and design (API/IDoc/OData/middleware) with IT Apps.
  • Define reconciliation rules (what must match, tolerances, timing, cutoff, and error handling).

1. 1. Produce/validate an Interface Register (object, owner, frequency, triggers, payload, validation rules, error handling, logging).
2. Finance process fit & configuration assurance
   1. Validate that PMIS workflows align with SAP financial controls and processes:

• • WBS structure and coding governance compatibility
  • Cost object mapping and reporting hierarchies
  • Budget control points and approval logic alignment

1. 1. Review vendor functional design documents and confirm they are buildable without rework.
2. UAT/SIT readiness + acceptance gates
   1. Design the SAP-relevant SIT/UAT test strategy:

• • Test scenarios that mirror real lifecycle events (budget changes, commitments, invoices/payments, revisions, cancellations).
  • Define UAT entry/exit criteria and “definition of done” for SAP integration.

1. 1. Lead defect triage for SAP-facing issues:

1. • Identify root cause (SAP config vs interface vs data vs PMIS workflow)
   • Prioritize fixes and validate resolution.
2. Cutover & go-live risk management
   1. Define SAP-specific cutover plan inputs:

• • Data migration approach (what migrates, what stays, time windows)
  • Freeze periods and reconciliation during cutover
  • Go-live checklists and rollback criteria

1. 1. Ensure operational support readiness (hypercare model, incident triage rules).
2. License and hidden-cost prevention
   1. Review solution architecture from a SAP licensing and access exposure perspective.
   2. Challenge integration and user-access patterns that could create unplanned costs.
   3. Support contract management by distinguishing:

1. • “Required to meet baseline” vs “enhancement/new scope” items.
2. Stakeholder coordination (cross-functional)
   1. Act as the SAP counterpart to:

• • PMIS expert (project controls/workflow governance)
  • IT Apps/Infra (integration platform, security, environments)
  • P&TA (standard WBS governance and controls)
  • OpCos finance/project teams (data availability, UAT, adoption)