Anchoring an ASBO to a Database Table¶
Anchoring is the process through which an Application Specific Business Object (ASBO) is linked to a datasource and table, enabling the mapping of physical database columns to the logical attributes of the ASBO. It establishes the foundation for resource management, connecting your logical business model to a physical data source.
This section is organized into four parts:
1. Anchoring Concept & Table Selection Wizard¶
Start here to understand what anchoring is and how to begin it.
- What anchoring is and the master environment mapping it creates
- When to anchor an ASBO (new, imported, or re-anchored)
- Datasource prerequisites and how to access the Anchor function
- The Table Selection Wizard: choosing a datasource, schema, and table
- Inspecting table structure before committing to a selection
2. The Table Mapper¶
Once a table is selected, this is where you connect columns to attributes.
- The drag-and-drop interface for mapping columns to ASBO attributes
- Data type compatibility validation and resolving mismatches (Mutate Type)
- Creating new attributes directly from columns
- Preventing and resolving duplicate attribute names
- Removing mappings
- Automation with Auto-Map and Clear All
- Completing and saving the anchoring process
3. Anchoring Scenarios & Troubleshooting¶
Reference material for planning, common situations, and fixing problems.
- Best practices before, during, and after anchoring
- Common scenarios: anchoring a new ASBO, re-anchoring, anchoring to a view, minimal mappings, type transformations
- Troubleshooting: missing datasources, empty schema/table lists, unresolved type issues, drag-and-drop problems, failed imports, duplicate attributes, stuck mappings
- How anchoring impacts the ASBO lifecycle
- Anchoring vs. environment mapping, side by side
4. Editing Anchors¶
Once an ASBO is anchored, use this page to change the mappings later.
- Accessing the Edit Anchors button and the master datasource online requirement
- Modifying mappings in edit mode: adding, removing, changing, and creating attributes
- The mandatory two-step save process (Confirm Mappings + Save Changes)
- Automatic resource reconciliation when RN, RD, or PK mappings change