Results for “flash_message_length”

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

Overview

ASG_APPLICATION_VL is a multilingual (translated) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the ASG product family, "CRM Gateway for Mobile Devices," which governs the registration, configuration, and synchronization of mobile applications that connect to the EBS instance. The view presents a single, language-aware record for each registered mobile application, resolving the application's descriptive name into the session's current language while exposing the operational attributes stored at the base-table level.

Because it is a _VL view, it collides the "_B" (base) and "_TL" (translation) tables through the standard EBS multi-language pattern. Reporting and integration layers query it instead of joining the base and translation tables directly, ensuring that multilingual deployments return the correct localized application name without custom join logic. The view is documented as VALID and exposes a stable column list that includes the APPLICATION_CODE attribute frequently used to identify a mobile application programmatically.

Underlying Base Objects

ASG_APPLICATION_VL is defined over two documented base objects, both accessed through APPS-owned synonyms:

• ASG_APPLICATIONS_B — the base table holding the operational and non-translated columns of each mobile application.
• ASG_APPLICATIONS_TL — the translation table holding the language-specific MOBILE_APPLICATION_NAME.

The view text joins the two on MOBILE_APPLICATION_ID and filters the translation row with the condition TL.LANGUAGE = USERENV('LANG'), so only the row matching the caller's session language is returned. This is the conventional EBS _VL construct and means the view is effectively a one-to-one projection of ASG_APPLICATIONS_B (all base columns are passed through unchanged) plus a single localized name column.

Key Columns

• MOBILE_APPLICATION_ID — primary identifier for the mobile application; the join key between base and translation tables.
• APPLICATION_CODE — the application's short code, the attribute most frequently used to look up a specific mobile application in integrations and setup queries.
• MOBILE_APPLICATION_NAME — the localized descriptive name, sourced from ASG_APPLICATIONS_TL.
• DEVICE_TYPE — the target device class for which the application is configured.
• APP_VERSION — the released version of the mobile application.
• STATUS — the current lifecycle/enabled state of the application record.
• SYNCHRONIZATION_FLAG, SMS, EMAIL — control flags indicating whether synchronization, SMS, and email channels are enabled for the application.
• FLASH_MESSAGE_LENGTH — the configured maximum length for flash messages.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, inherited from the base table.

Common Use Cases and Queries

Typical uses include validating mobile application setup, driving synchronization logic, and producing multilingual configuration reports. Because APPLICATION_CODE is the natural business key, it is the usual filter in support and diagnostic queries.

List all mobile applications in the session language:

SELECT mobile_application_id, application_code, mobile_application_name,
       device_type, app_version, status
FROM   apps.asg_application_vl
ORDER BY application_code;

Look up a specific application by code:

SELECT application_code, mobile_application_name, device_type,
       app_version, status, synchronization_flag, sms, email
FROM   apps.asg_application_vl
WHERE  application_code = :p_application_code;

Identify active applications with synchronization enabled:

SELECT application_code, mobile_application_name, app_version
FROM   apps.asg_application_vl
WHERE  status = 'Y'
AND    synchronization_flag = 'Y';

The view is read-only; all maintenance is performed against the underlying ASG_APPLICATIONS_B and ASG_APPLICATIONS_TL tables. When querying, always reference the APPS schema (or a synonym) so the USERENV('LANG') filter resolves to the correct localization.