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 scr
AccProductInBaseTree
Generated table/view profile from relation entities, typed edges, trigger evidence, source references, and object-layer metadata.
Typed Edges
| Type | Source | Target | Evidence |
|---|---|---|---|
| No typed edges matched. | |||
Related Evidence
OIM KB Update Run 24 Goal Clarify the sandbox specific “availability wiring” around AccProductInBaseTree / AccProductInITShopOrg , and record the concrete trigger/procedure hooks that fire when: ADSGroup IT Shop flags change, ADSGroup.UID AccProduct changes, AccProductGroup service category hierarchy/decision method ch
Sandbox DB Evidence — AccProductInBaseTree, views, and trigger hooks 2026 04 27 Scope This note captures live sandbox DB evidence about: why some “availability” views can appear empty AccProductInITShopOrg , which views back common troubleshooting queries ITShopOrg , ITShopOrgHasADSGroup , which triggers/procs are dire
Goal Capture live DB evidence for: the service category shape AccProductGroup and required columns why AccProductInBaseTree is empty in this sandbox and what still references it the DBQueue tasks that actually drive IT Shop "ShoppingRack" checks in this sandbox Evidence 1 IT Shop subtree snapshot: counts by BaseTree.IT
Sandbox Host Evidence — AccProductInBaseTree schema + IT Shop flag validation hooks 2026 04 27 Scope Read only evidence gathered on 2026 04 27 from the sandbox host im.sandbox.local via WinRM file inspection: shipped DB schema for AccProductInBaseTree , shipped relationship metadata for AccProductInBaseTree , shipped t