Goal

Add fresh live-DB evidence around:

service categories (AccProductGroup) and what is actually required in this sandbox
why AccProductInBaseTree is empty (yet still referenced by multiple views)
which DBQueue tasks are the real IT Shop troubleshooting entry points here

Sandbox activity (live DB)

Mode: SELECT-only, via scripts/sandbox/Invoke-SandboxSql.ps1 (no DML).
Evidence note:
projects/identity-management/oim-kb-update/sandbox-db/2026-04-27-service-categories-and-accproductinbasetree-db-evidence.md

AccProductGroup required columns mirror AccProduct: only UID + XObjectKey are NOT NULL.
AccProductInBaseTree is still 0 rows and has no matching DBQueue task; it has at least one generic trigger (delete/simulation bookkeeping) and multiple views depend on it.
The IT Shop subtree still uses BaseTree PR nodes + BaseTree.UID_AccProduct and ShoppingRack tasks; service categories are not enforced (PR-linked products can have NULL UID_AccProductGroup).

In OneIM 10, when (if ever) is AccProductInBaseTree supposed to be populated, and by which supported operation (UI/API vs direct SQL)?
Are service categories purely a portal grouping/filtering construct in this sandbox, or do some workflows enforce them when enabling additional modules/parameters?