# `Sp_Check_SaveOeeReportAAA` (procedure)


- **Type:** PROCEDURE
- **Deterministic:** NO
- **SQL data access:** CONTAINS SQL

## Parameters

_No parameters._

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `Sp_Check_SaveOeeReportAAA`'`._

## Narrative

**Business context:** Developer scratch copy of `Sp_Check_SaveOeeReport`. The body cursors `viw_mftproductionreport` filtered by the hard-coded test brand `sBrandsId='1111111111'` (the dev sandbox tenant) and the `AAA` suffix marks it as a throwaway. Per wiki convention, scratch/backup objects are not narrated for business behaviour.

**What it does:** Same OEE back-fill logic as [`Sp_Check_SaveOeeReport`](Sp_Check_SaveOeeReport.md) — pulls `plc_machinedata` samples and writes `dAdjustableQty`/`dHour`/`dOtherHour`/`dAllHour`/`dEmpHour` onto `mftproductionreportslave` — but takes no parameters and runs against the test tenant only.

**Invocation:** Status: appears orphaned. No `gdsmodule` binding, no other routine references the name, no `xly-src` hit. Not expected to be called from production; verify before relying on it.
