Aankda
Data office: a steward for every master, duplicate flags that record a decision, an index of every report, and live figures on data quality and process health.
This office is not open to you
Nothing here was changed.
Master Data Governance
One correct record per thing. A steward answers for each master. A duplicate flag records that one record is the same thing as a golden record - confirming it changes nothing in Items or Parties. Physically merging records is deliberately not built here.
Stewards
Duplicate flags
You are the steward of this master, so you may decide these.
Reports Library
Every report, one place: an index of the reports that already exist across the ERP - what each is for, who owns it, where it lives and how often it refreshes. A catalogue you maintain, not a second dashboard; it starts empty on purpose.
Data Quality Monitor
Blanks, duplicates, mismatches. Computed from the masters as they are right now - nothing here is entered. Show the records behind any number. Duplicate phones use the same last-ten-digits rule the party trigger already enforces.
Process Health
Where the business is stuck. Five processes, read live from each one's own status and date - nothing here is entered. A recommendation appears only when a process actually has something waiting.
Not on this screen
Detail: a steward, a flag and a report are each a few fields, all shown on their row, so there is nothing more to open; a report is opened where it lives. Approval: a duplicate flag is decided by the master's steward or an Aankda admin, not routed for approval, and the database alone decides who may. Activity and the audit trail: who flagged, who decided, when and why are kept on the flag itself and shown on its row; a steward's note and the date it was set are on the steward's row; a retired report keeps its reason. Documents: this office holds no files. Nothing here is ever deleted; a report is retired, a flag is dismissed, and no record is merged.