Give business queries a defined data boundary
Sequel Data Access is an IBM i data-access enquiry. Begin with the information users need and the business definitions behind it. A query returning rows successfully does not establish that its joins, filters and totals represent the intended measure, or that the audience is entitled to see every field.
Identify the source files, existing queries, user roles and expected output formats. Confirm current Sequel compatibility and the supported way to reuse or replace retained query work. Separate read access from authority to change source information, and review whether extracts create additional copies that need their own retention and access rules.
Reconcile the result with the business owner
Choose representative reports or questions and compare results with an independently approved baseline. Test restricted access, empty results and relevant date or company filters. A useful rollout gives users understandable definitions and an escalation route when results appear inconsistent.
For a UAE group reporting across entities, validate legal-entity and currency or period boundaries where they affect the requirement. Handover should include query ownership, definitions, permissions and change control. MMC can scope selected data-access setup and user enablement; correcting source data or redesigning an application’s data model needs explicit inclusion.
Evidence to request for this scope
- Validate representative query totals and joins against approved source evidence.
- Demonstrate the access available to each intended audience, including restricted fields or records.
- Record query ownership, output handling and the process for reviewing definition changes.