Results for “message_length”

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

Overview

ASG_FLASH_MESSAGES is a table owned by the ASG schema and is part of the ASG - CRM Gateway for Mobile Devices product within Oracle E-Business Suite 12.1.1 and 12.2.2. As its description indicates, the table stores all flash messages — short, transient notifications intended to be surfaced to users through the CRM Gateway for Mobile Devices. These messages typically carry alerts, confirmations, or informational prompts that mobile device users must acknowledge or simply view.

The table is classified as VALID in the EBS data dictionary. From a data modeling perspective, the mined metadata suggests a hub-leaning classification within a Data Vault heuristic: the table captures a distinct business entity (a flash message) identified by a surrogate key, with minimal descriptive attributes that lend themselves to a satellite structure. This classification is a modeling suggestion rather than a functional definition; the table's practical role is as the master repository for flash message definitions that are subsequently distributed to recipients.

Key Information Stored

The physical schema documented for 12.2.2 contains eleven columns. The most significant include:

• FLASH_ID — The surrogate primary key, defined by the constraint ASG_FLASH_MESSAGES_PK and reinforced by the unique index ASG_FLASH_MESSAGES_U1. This column uniquely identifies each flash message and is the referenced key for related recipient records.
• MESSAGE — The textual content of the flash message delivered to the mobile user.
• MESSAGE_LENGTH — The length of the message payload, useful for validating content against device or gateway limits.
• MESSAGE_TYPE — A classification of the message (for example, informational or alert), which may drive presentation behavior on the device.
• CONFIRM_REQUIRED_FLAG — Indicates whether the recipient must acknowledge the message before proceeding.
• ACTIVE — Controls whether the message is currently enabled for delivery.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, enforcing the standard EBS security group isolation model.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — The standard audit columns maintained across EBS transactional and setup tables, capturing who created or modified a message and when.

FLASH_ID is the true surrogate key. No separate business-key column set is documented beyond the unique index on the same column, so FLASH_ID serves both purposes in practice.

Common Use Cases and Queries

Typical reporting and support scenarios center on identifying active messages, auditing message content changes, and reconciling which messages have been dispatched. Common query patterns include listing all currently active messages, examining message type distributions, and joining to recipients to confirm delivery scope.

• Retrieve active flash messages: SELECT flash_id, message, message_type FROM asg.asg_flash_messages WHERE active = 'Y';
• Audit recently modified messages: SELECT flash_id, last_updated_by, last_update_date FROM asg.asg_flash_messages ORDER BY last_update_date DESC;
• Join to recipients to see distribution: SELECT m.flash_id, m.message, r.* FROM asg.asg_flash_messages m, asg.asg_flash_recipients r WHERE m.flash_id = r.flash_id;
• Security group scoping: SELECT flash_id, message FROM asg.asg_flash_messages WHERE security_group_id = :sgid;

These queries support operational troubleshooting on the mobile gateway and reconciliation of user-facing notifications.

Related Objects

The table participates in a defined referential structure within the ASG schema and the wider EBS data model:

• ASG_FLASH_RECIPIENTS — References ASG_FLASH_MESSAGES via FLASH_ID, recording which recipients receive each message. This is the principal dependent object and the primary link for delivery reporting.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID, providing the standard EBS security group context that governs visibility of the message.
• ASG_FLASH_MESSAGES_PK / ASG_FLASH_MESSAGES_U1 — The primary key constraint and unique index that enforce uniqueness on FLASH_ID.
• ASG schema objects generally — Other CRM Gateway for Mobile Devices tables and setup objects that consume flash messages for device delivery.

In combination, ASG_FLASH_MESSAGES and ASG_FLASH_RECIPIENTS form the core message-and-distribution pair for the mobile gateway's flash messaging capability.