Stats
Actions
Tags
From crisp-tc
Category Knowledge Base (CKB) database schema reference — table structure, database creation/upgrade, account management, configuration, Space Planning and Floor Planning data storage, SQL Server and Oracle support
How this skill is triggered — by the user, by Claude, or both
Slash command
/crisp-tc:ckb-schemaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Category Knowledge Base (CKB) is a relational database (SQL Server or Oracle) that stores product, planogram, floor plan, and category management data shared across the Category Management Suite applications (Space Planning, Floor Planning, Data Manager, Open Access, etc.).
The Category Knowledge Base (CKB) is a relational database (SQL Server or Oracle) that stores product, planogram, floor plan, and category management data shared across the Category Management Suite applications (Space Planning, Floor Planning, Data Manager, Open Access, etc.).
The database schema uses a consistent ix_ prefix naming convention for all tables, with sub-prefixes that identify the functional area.
| Platform | Authentication |
|---|---|
| SQL Server | SQL Server auth or Windows NT Authentication |
| Oracle | Schema-based (schema owner = username) |
All CKB tables use the prefix ix_ followed by a two-to-three letter area code:
| Prefix | Area |
|---|---|
ix_ao_ | Assortment / Object |
ix_bp_ | Business Planning / Agent |
ix_ca_ | Category / Cube / Analysis |
ix_flr_ | Floor Planning |
ix_mtl_ | Material / Part |
ix_spc_ | Space Planning (planograms, positions, pegs) |
ix_sys_ | System / Framework tables |
ix_spc_*)Store planogram structure, fixtures, positions, and related data synced from ProSpace.
| Table | Contents |
|---|---|
ix_spc_drawing | Planogram drawing / project records |
ix_spc_peg | Peg definitions |
| (additional spc tables) | Positions, fixtures, segments, performance data |
ix_flr_*)Store floor plan structure synced from ProFloor.
| Table | Contents |
|---|---|
ix_flr_drawing | Floor plan drawing / project records |
| (additional flr tables) | Fixtures, sections, departments, floorplan metadata |
ix_ao_*)| Table | Contents |
|---|---|
ix_ao_assortment_node | Assortment tree nodes |
ix_ao_product_level | Product hierarchy levels |
| (additional ao tables) | Product attributes, category assignments |
ix_bp_*)| Table | Contents |
|---|---|
ix_bp_agent | Agent / workflow definitions |
| (additional bp tables) | Business planning rules, approval workflows |
ix_ca_*)| Table | Contents |
|---|---|
ix_ca_cube | OLAP cube definitions |
| (additional ca tables) | Category definitions, analysis configurations |
ix_mtl_*)| Table | Contents |
|---|---|
ix_mtl_part_key | Material part key lookup |
| (additional mtl tables) | Part/product master identifiers |
ix_sys_*)Framework tables managed by Builder. Do not modify directly.
ix_sys_<schema#>_* during upgradesix_sys_status retains user-configured statuses (DBKey 5–199) during upgradeCKB supports an optional Account object that scopes all database objects to named accounts.
During database creation (Builder): check Enable Accounts on the Build Options page. During upgrade: check Enable Accounts on the Upgrade Options page. When enabled, account-specific interfaces and tables are created in CKB.
Note: Original objects remain associated with their original account. This is a copy operation.
In the Account Manager: double-click a row → Object Relationship page shows parent/child objects and actions to be performed.
Accessed via: Data Manager → Tools → Settings Configuration → Local Settings
| Field | Description |
|---|---|
| Use NT Security | Enable Windows NT Authentication for this user |
| Never Show Login Dialog | Auto-connect without prompting (single-database setups only) |
| Show Login Dialog Next Time | Show once then remember |
| Always Show Login Dialog | Always prompt (useful for multi-database users) |
| Server | Default database server |
| Database | Default database name |
Accessed via: Console → Tools → Database Tasks → Global Settings Or: Data Manager → Tools → Settings Configuration → Database Settings
Data Manager → Framework pane → Advanced → Configure Home
During database creation (Builder wizard):
Set during database creation — cannot be changed after build.
| Option | Notes |
|---|---|
| ID | Use product ID as primary key |
| UPC | Use UPC as primary key. Required for Planogram Exchange Management. |
| Both | Use both ID and UPC |
Important: If ID is selected but some products have only UPC data, those planograms cannot be saved to the database.
| Option | Description |
|---|---|
| Create database, framework and interfaces | Full single-step creation (default) |
| Generate database script only | Generates SQL script for manual execution; allows custom schema adjustments; requires a second Builder pass for framework/interfaces |
| Create framework and interfaces | Run after manual script execution to complete setup |
| Option | Description |
|---|---|
| Generate a File Containing Scripts | Save .SQL file of all creation procedures |
| Create Encrypted Procedures | Encrypt stored procedures during build |
| Support for unicode characters | Enable multi-byte character storage (required for Asian languages or Unicode-encoded project files) |
| Enable Accounts | Create account-scoping infrastructure |
| Database Storage (Oracle) | Configure tablespaces per table |
Oracle tablespace rule: Total Initial value per tablespace should not exceed 2000 MB. Use the CKB_Sizer spreadsheet to calculate requirements.
| Option | Description |
|---|---|
| Upgrade database, framework and interfaces | Full single-step upgrade (default) |
| Generate upgrade database script only | Generates one .SQL file per upgrade increment; enables incremental/backup-friendly upgrades |
| Upgrade framework and interfaces | Run after script execution to complete framework update |
ix_sys_*) are backed up to ix_sys_<DB Schema #>_* before replacementGenerated upgrade scripts are named: <FileName>_<SchemaVersion>.sql
After database creation, Builder supports:
| Operation | Description |
|---|---|
| Import product information | Import from product libraries |
| Import Space Planning planograms | Bring existing .prj planogram files into the database |
| Categorize product and planogram data | Organize imported data into the category structure |
| Create/upgrade Category Advisor fact database | Time-based performance data store for multi-store analysis |
SaveToDataBaseEx / ProjectSaveDatabaseChangesLoadFromDataBaseEx / LoadProjectPogsFromDatabaseFetchProductIKBDBKeys)IKBLifeCycleManagementOverrideFloorplan.OverwriteDatabaseFloorplan()Project.SaveToDataBase() / Project.LoadFromDataBase()Data Manager is the primary user interface for browsing and managing CKB database objects. It provides:
Builder is the administrative tool for:
Shortcut icons on the left panel provide step-by-step access to each workflow phase.
| Field | Description |
|---|---|
| Title Text / Title Formula | Chart title and subtitle text or formula |
| F | Field or formula for chart data |
| Roll Up | None / Sum / Count / Mean Avg / Midpoint / Min / Max / First / Last / Range / List |
| Cumulative | Running total |
| Percent | Show as % of total |
| Sort Descending | Sort columns descending by this field |
| Formula on Total | Apply roll-up to each formula operand before calculating |
| Group by Key | Group elements by key field |
| Stacked | Stack bars/columns |
| Grand Totals | Include grand total row in data table |
| Number Axes | Show numeric axis values |
| Separate Axes | Independent Y-axis per data field |
| Show Grid / Legend / Labels / Values | Display toggles |
| Show Top _ Groups Only | Filter to top N groups |
| Show Others | Consolidate filtered groups as "Others" |
| Use Persistent Color | Consistent colors per field value across all charts using this option |
| Field | Description |
|---|---|
| Specific Name | Assign a specific value to a legend color (field value, or field name if Group by Key used) |
| Explode | Explode a pie chart wedge |
| Title 1 / Title 2 | Background colors for chart title/subtitle |
| Headings | Background color for chart headings |
| Rows | Background color for data rows and legend |
| Grand Totals | Background color for grand total row |
| Chart Background | Overall chart background color |
| Others Rows | Background color for "Others" group row |
Set independent midpoints for the X and Y axes:
| Field | Description |
|---|---|
| Method | Midrange (halfway between min/max) / Mean (average) / Median (middle of sorted list) |
| Midpoint | Auto-calculate or manually enter |
| Calculate | Preview endpoint/midpoint values based on current data |
Complete database schema details, all table definitions, stored procedures, and SQL scripts are in: CKB Schema\CKB Schema.htm and CKB Schema\CREATE_CKB.sql
npx claudepluginhub gocrisp-proservices/techteam_skills --plugin crisp-tcProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.