Source: projects/identity-management/oim-kb-update/runs/2026-04-27-13.md
> Source: projects/identity-management/oim-kb-update/runs/2026-04-27-13.md
OIM KB Update — Run 2026-04-27 (13)
Goal
- Clarify what
ITShopInfo='SC'means (seen in shipped triggers/procedures but not observed in live subtree rows). - Verify whether service categories (
AccProductGroup) are required for requestable product nodes in the live sandbox.
What I did
- Live sandbox DB (SELECT-only):
- Counted
BaseTreeIT Shop subtree nodes byITShopInfo. - Extracted snippets from shipped QER procedures/triggers referencing
ITShopInfo='SC'. - Counted how many
ITShopInfo='PR'product nodes haveAccProduct.UID_AccProductGroupset. - Sandbox host (WinRM read-only):
- Located shipped SQL/XML references to
ITShopInfo='SC'and “shopping center template”.
Findings (new/confirmed)
ITShopInfo='SC'is “shopping center” (procedure error message + structure checks), even though this sandbox currently has no SC nodes inQER-V-ITShopOrg.- The sandbox’s live IT Shop subtree is rooted at
SHdirectly (no SC layer). Shipped code still supports an “SC → SH → BO” variant. - Service categories are not mandatory for product nodes here: 7/16 PR nodes have no
AccProductGroupassigned.
Evidence
- Live DB:
projects/identity-management/oim-kb-update/sandbox-db/2026-04-27-itshopinfo-sc-shopping-center-db-evidence.md - Host artifacts:
projects/identity-management/oim-kb-update/sandbox-host/2026-04-27-itshop-file-hints.md
Open questions / next experiment ideas
- In this environment, under which supported UI/API operations are SC (“shopping center”) nodes created, if ever?
- Do shopping centers matter only for multi-shop setups (grouping shops), or are they also used for decision-maker derivation in typical deployments?
- Which official docs describe SC (“shopping center”) and how it relates to shop/shelf/product/customer nodes?