Brief operating procedure

File-based report automation

The downloaded ERP file is the integration boundary. The process does not rely on database access and does not modify the ERP.

01ERP reportExisting saved report
02PAD workstationScheduled download
03ProcessingOneDrive boundary
04Local workTransform + validate
05Receipt + archiveCompleted / Raw Data

Daily operating flow

Seven controlled steps

  1. 01PAD PC
    Download the daily export

    Open the saved SyteLine-style ERP report, download XLSX to a local temporary name, then validate extension, size, and schema. No SQL, API, or ERP database access is assumed.

  2. 02PAD PC
    Publish one finalized raw file

    Rename atomically to RAW_<run_id>.xlsx in OneDrive Processing. Refuse to start when Processing is not empty.

  3. 03Cloud · integrated last
    Detect and request processing

    After the local foundation is accepted, a cloud flow watches Processing, validates the filename, records the run, and invokes the licensed PAD flow.

  4. 04PAD + Excel
    Transform outside the sync folder

    Copy raw, template, and rules to a non-OneDrive work folder. Run the approved Power Query workbook or HTML engine against the same report contract.

  5. 05Control
    Reconcile before release

    Stop on missing columns, timeout, wrong totals, or hash mismatch. Confirm 1,800 source rows equal 30 output plus 1,770 suppressed rows and retain the audit.

  6. 06PAD
    Publish output, then receipt

    Write the completed workbook atomically to Completed. Write the .done.json receipt last, with the run ID, hashes, counts, and normalized business digest.

  7. 07Cloud · integrated last
    Verify, archive, and reset

    Verify the receipt and files, archive the immutable raw export under Raw Data/YYYY/MM/DD, and require Processing to be empty. Any failure goes to Exceptions without releasing a report.

Ownership

Independent first. Integrated later.

PLANNING CAN OWN
  • Report template and presentation format
  • Column selection, names, order, filters, and sort
  • Derived fields and static summaries
  • Recipients and routine revision cycle
WORK WITH IT WHEN
  • Credentials, gateway, service account, or unattended VM are needed
  • The ERP screen or export schema changes
  • Regulated or controlled data enters scope
  • The workflow becomes business-critical or organization-wide

Seven-minute interview walkthrough

Presenter run sheet

Open workbench →
Set the business problem

Planning needs different report shapes faster than the corporate IT request cycle.

Show the retrieval edge

Run the fictional ERP export and explain that PAD performs the clicks on an available PC.

Run Scenario 1

Create Report A from the raw 1,800-row export and show the 30-row exception queue plus audit.

Run Scenario 2

Turn Report A into Report B with fewer columns, renamed headers, urgency, ownership, and a new layout.

Run Scenario 3

Create the static site-by-status summary and explain the separate Office Script route for a native PivotTable.

Close on ownership

Planning can revise template and rules now. IT is a partner when credentials, gateway, governance, or scale enter scope.

PIVOTTABLE TRUTH

The browser can generate the grouped numbers and format them as a normal worksheet matrix. A true interactive Excel PivotTable object should be created with Excel automation, such as the included Office Script, and can be called from Power Automate Cloud.