Results for “asg_conf_resolution”

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

Overview

ASG_CONF_RESOLUTION is a transactional configuration table owned by the ASG schema and delivered with the CRM Gateway for Mobile Devices product in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores conflict resolution rules that govern how the CRM Gateway reconciles data discrepancies encountered while processing mobile device synchronization requests. Each row defines a resolution strategy — a method, function, or parameterized action — that the gateway applies when a conflict of a given type is detected against a snapshot load and a specific column group.

In Data Vault modeling terms, the mined foreign-key structure suggests a link classification. The table sits between ASG_SNAPSHOT_LOGS and ASG_COLUMN_GROUPS, resolving the many-to-many association between a synchronization snapshot and the column groups whose values require conflict handling. The presence of SECURITY_GROUP_ID also positions it as a security-scoped configuration artifact. This classification is a heuristic modeling suggestion derived from the documented referential structure, not a declared Data Vault design.

Key Information Stored

The table contains 16 documented columns. The surrogate primary key is CONF_RESOLUTION_ID, enforced through the ASG_CONF_RESOLUTION_PK constraint. No separate unique business key index is documented in the ETRM metadata, so the resolution identity is expressed through the combination of its foreign-key context and rule attributes.

• CONF_RESOLUTION_ID — surrogate primary key; the value commonly referenced in integration and support lookups.
• SNAPSHOT_LOG_ID — foreign key to ASG_SNAPSHOT_LOGS, tying the rule to a specific synchronization run or snapshot.
• COLUMN_GROUP_ID — foreign key to ASG_COLUMN_GROUPS, identifying the set of columns to which the rule applies.
• CONFLICT_TYPE — the category of conflict the rule resolves.
• METHOD — the resolution approach or strategy assigned to the conflict.
• FUNCTION_NAME — the callable routine invoked to perform the resolution.
• PARAMETER_COLUMN_NAME — the column supplying runtime parameters to the resolution function.
• SEQUENCE_NO — ordering of rule evaluation when multiple resolutions apply.
• STATUS — activation state of the resolution record.
• CONF_RESOLUTION_COMMENT — free-text description of the rule's purpose.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the rule to a security group.
• RELEASE_VERSION — the EBS release against which the record was created or migrated.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns.

Common Use Cases and Queries

Support and implementation teams query this table to determine why a particular mobile synchronization conflict resolved in a given manner. A frequent pattern joins the resolution back to its snapshot log and column group:

• Retrieve all active resolutions for a snapshot: SELECT r.conf_resolution_id, r.conflict_type, r.method, r.function_name FROM asg_conf_resolution r WHERE r.snapshot_log_id = :p_snapshot_log_id AND r.status = 'Y' ORDER BY r.sequence_no;
• Enumerate rules per column group for a given security group: SELECT * FROM asg_conf_resolution WHERE column_group_id = :p_group AND security_group_id = :p_sec_group;
• Audit recent rule changes: SELECT * FROM asg_conf_resolution WHERE last_update_date > SYSDATE - 30;

Reporting use cases include documenting configured conflict-handling logic per column group, verifying that each CONFLICT_TYPE has at least one active METHOD, and confirming that FUNCTION_NAME values resolve to valid deployed package routines before promoting configuration between environments.

Related Objects

• ASG_SNAPSHOT_LOGS — joined via ASG_CONF_RESOLUTION.SNAPSHOT_LOG_ID = ASG_SNAPSHOT_LOGS.SNAPSHOT_LOG_ID.
• ASG_COLUMN_GROUPS — joined via ASG_CONF_RESOLUTION.COLUMN_GROUP_ID = ASG_COLUMN_GROUPS.COLUMN_GROUP_ID.
• FND_SECURITY_GROUPS — joined via ASG_CONF_RESOLUTION.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, controlling visibility of the rule.
• FND_USER — related through CREATED_BY and LAST_UPDATED_BY for accountability reporting.
• ASG_CONF_RESOLUTION_PK — the primary key constraint indexed on CONF_RESOLUTION_ID that anchors all referential lookups.