Results for “asg_column_groups”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ASG_COLUMN_GROUPS table is a core configuration object within the ASG – CRM Gateway for Mobile Devices product (owner schema ASG) in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines named groups of columns that govern which fields of a mobile CRM snapshot are exposed, synchronized, or subject to conflict resolution when field devices communicate with the EBS back end. Because the table records the composition and lifecycle state of each column group rather than the transactional mobile data itself, the heuristic Data Vault classification mined from its foreign-key structure is satellite-leaning — a modeling suggestion that treats ASG_COLUMN_GROUPS as descriptive, time-stamped context hanging off parent entities such as snapshot logs and security groups.

Key Information Stored

The table is documented with 11 columns. The surrogate primary key is COLUMN_GROUP_ID, enforced by the ASG_COLUMN_GROUPS_PK constraint; it is the column most frequently referenced by external objects and the term users search on. Business-key candidates include COLUMN_GROUP (the human-readable group name) and the pairing of SNAPSHOT_LOG_ID with SECURITY_GROUP_ID, which together scope a group to a snapshot run and a responsibility.

• COLUMN_GROUP_ID – surrogate primary key; unique identifier of the group.
• COLUMN_GROUP – the descriptive name of the group.
• LIST_OF_COLUMNS – the enumerated column definitions contained in the group.
• SNAPSHOT_LOG_ID – foreign key to ASG_SNAPSHOT_LOGS, tying the group to a specific snapshot execution.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, restricting visibility by responsibility.
• STATUS – lifecycle or activation state of the group.
• RELEASE_VERSION – release context for the definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include auditing which columns were published to mobile devices during a snapshot, diagnosing conflict-resolution behaviour, and reviewing security-restricted field exposure per responsibility.

• Look up a group by primary key: SELECT column_group, list_of_columns, status FROM asg.asg_column_groups WHERE column_group_id = :p_id;
• Groups for a snapshot run: SELECT g.column_group_id, g.column_group, g.status FROM asg.asg_column_groups g, asg.asg_snapshot_logs s WHERE g.snapshot_log_id = s.snapshot_log_id AND s.snapshot_log_id = :p_log;
• Security-restricted groups: joining to FND_SECURITY_GROUPS on security_group_id to report exposure by responsibility.
• Conflict-resolution reporting: joining to ASG_CONF_RESOLUTION on column_group_id to see how each group resolved conflicting field values.

Because LIST_OF_COLUMNS and STATUS change as configurations evolve, reporting queries should filter on the audit columns to obtain the current definition.

Related Objects

• ASG_SNAPSHOT_LOGS – referenced via ASG_COLUMN_GROUPS.SNAPSHOT_LOG_ID; the parent snapshot run for the group.
• FND_SECURITY_GROUPS – referenced via SECURITY_GROUP_ID; controls responsibility-based visibility.
• ASG_CONF_RESOLUTION – references ASG_COLUMN_GROUPS.COLUMN_GROUP_ID; holds conflict-resolution outcomes per column group.
• ASG_COLUMN_GROUPS_PK – the primary key constraint on COLUMN_GROUP_ID.
• ASG schema objects and mobile gateway concurrent programs that read column-group definitions when assembling snapshot payloads.

Together these relationships position ASG_COLUMN_GROUPS as the configuration anchor between snapshot execution, security context, and conflict resolution in the CRM Gateway for Mobile Devices.