Results for “confirm_flag”

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

Overview

The ASG_FLASH_RECIPIENTS table resides in the ASG schema and belongs to the Oracle E-Business Suite product ASG — CRM Gateway for Mobile Devices. It stores all recipients for all flash messages dispatched through the mobile CRM gateway. A flash message in this context is a short, near-real-time notification pushed to a mobile device user, and this table provides the association between each such notification and the device user who is intended to receive it. In releases 12.1.1 and 12.2.2 the table carries the same nine-column structure and the same foreign key topology, with the physical definition documented in the ETRM repository for 12.2.2.

From a heuristic Data Vault modeling perspective, the metadata classification is link. The table is not a descriptive hub of a single business entity but rather an associative construct that resolves many-to-many relationships between flash messages and device users. This is consistent with its unique business-key index ASG_FLASH_RECIPIENTS_U2 (DEVICE_USER_ID, FLASH_ID), which expresses the grain of the association.

Key Information Stored

The table contains nine columns. The most significant are:

• MOBILE_FLASH_SUBS_ID — the surrogate primary key, enforced by ASG_FLASH_RECIPIENTS_PK and by the unique index ASG_FLASH_RECIPIENTS_U1. This is a system-generated identifier for the recipient subscription record rather than a business identifier.
• FLASH_ID — the foreign key to ASG_FLASH_MESSAGES, identifying the flash message being delivered. This is a business-key component in the composite unique index.
• DEVICE_USER_ID — the foreign key to ASG_DEVICE_USERS, identifying the mobile device user receiving the message. This is the other business-key component in the composite unique index.
• CONFIRM_FLAG — a flag capturing whether the recipient has confirmed or acknowledged receipt of the flash message. This is the principal operational-status column.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, applying the standard multi-org/security-group partitioning used across EBS applications.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard EBS audit columns, recording who created and last modified the row and when.

The pair (DEVICE_USER_ID, FLASH_ID) is documented as a unique business-key candidate via ASG_FLASH_RECIPIENTS_U2, meaning a given device user appears at most once per flash message.

Common Use Cases and Queries

Typical use cases include auditing flash-message fan-out, identifying unconfirmed deliveries, and reporting the recipient population for a specific message or user. For example, to list all recipients of a given flash message:

• SELECT r.DEVICE_USER_ID, r.CONFIRM_FLAG, r.CREATION_DATE FROM ASG.ASG_FLASH_RECIPIENTS r WHERE r.FLASH_ID = :p_flash_id;

To find users with unconfirmed notifications:

• SELECT r.MOBILE_FLASH_SUBS_ID, r.FLASH_ID, r.DEVICE_USER_ID FROM ASG.ASG_FLASH_RECIPIENTS r WHERE r.CONFIRM_FLAG = 'N' AND r.LAST_UPDATE_DATE >= :p_since;

Joining to the message and user tables produces a full delivery report:

• SELECT m.FLASH_ID, m.MESSAGE_TEXT, u.USER_NAME, r.CONFIRM_FLAG FROM ASG.ASG_FLASH_RECIPIENTS r JOIN ASG.ASG_FLASH_MESSAGES m ON m.FLASH_ID = r.FLASH_ID JOIN ASG.ASG_DEVICE_USERS u ON u.DEVICE_USER_ID = r.DEVICE_USER_ID;

Because all three joins use indexed foreign-key columns, such reports perform well even at scale, and the uniqueness of (DEVICE_USER_ID, FLASH_ID) makes the result set deterministic.

Related Objects

The table participates in three documented foreign-key relationships and is referenced through them as follows:

• ASG_FLASH_MESSAGES — joined on ASG_FLASH_RECIPIENTS.FLASH_ID = ASG_FLASH_MESSAGES.FLASH_ID; the parent of each recipient row.
• ASG_DEVICE_USERS — joined on ASG_FLASH_RECIPIENTS.DEVICE_USER_ID = ASG_DEVICE_USERS.DEVICE_USER_ID; identifies the receiving device user.
• FND_SECURITY_GROUPS — joined on ASG_FLASH_RECIPIENTS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; provides the security partitioning used throughout EBS.

The table is accessed within the ASG CRM Gateway for Mobile Devices module, and reporting typically traverses the two ASG parent tables outlined above. No EBS view or public API is documented in this metadata excerpt; direct SQL against the ASG schema is therefore the primary access path, subject to the standard restrictions on writing directly to EBS application tables.