Results for “application_code”

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

Overview

ASG_APPLICATIONS_B is a core configuration table within the ASG product family — CRM Gateway for Mobile Devices — as delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the master definition of every mobile application that the CRM Gateway can serve to handheld and wireless devices. Each row represents one supported mobile application, combining device targeting attributes, versioning information, delivery-channel flags, and security-group scoping. Because the CRM Gateway for Mobile Devices relies on this registry to decide what content is pushed to a given device, ASG_APPLICATIONS_B functions as authoritative reference data rather than transactional data.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies ASG_APPLICATIONS_B as hub-leaning. Its single-column primary key, plus a persisted SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS, supports treating MOBILE_APPLICATION_ID as a durable business key around which satellites (versioning, status, delivery-channel attributes) and links (to device users) would be modeled. This classification is a modeling suggestion, not a physical constraint.

Key Information Stored

The physical schema documents 14 columns under the ASG schema. The most significant are:

• MOBILE_APPLICATION_ID — surrogate primary key (ASG_APPLICATIONS_B_PK) and the single column of unique index ASG_APPLICATIONS_B_U1, making it the de facto business-key candidate. It is the value propagated to dependent tables.
• APPLICATION_CODE — the short identifier used to resolve the application at runtime.
• DEVICE_TYPE — restricts the application to a class of mobile device.
• APP_VERSION — the deployed version of the mobile application, used for compatibility and upgrade decisions.
• STATUS — active/inactive indicator controlling whether the application is offered.
• SYNCHRONIZATION_FLAG — governs whether the application participates in synchronization.
• SMS and EMAIL — delivery-channel indicators.
• FLASH_MESSAGE_LENGTH — size constraint applied to flash messaging.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-org/security scoping.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include auditing the mobile application catalog, verifying which applications a device user may access, and diagnosing synchronization or delivery problems.

• List all active applications for a device class:

  SELECT mobile_application_id, application_code, app_version, status
  FROM   asg.asg_applications_b
  WHERE  device_type = :device_type
  AND    status = 'Y';

• Trace all device users attached to a given application:

  SELECT d.user_id, d.mobile_application_id
  FROM   asg.asg_device_users d, asg.asg_applications_b a
  WHERE  d.mobile_application_id = a.mobile_application_id
  AND    a.application_code = :code;

• Report delivery-channel coverage (SMS versus EMAIL) per security group:

  SELECT security_group_id, SUM(DECODE(sms,'Y',1,0)) sms_cnt,
         SUM(DECODE(email,'Y',1,0)) email_cnt
  FROM   asg.asg_applications_b
  GROUP  BY security_group_id;

Related Objects

• ASG_DEVICE_USERS — references ASG_APPLICATIONS_B via MOBILE_APPLICATION_ID; the principal child/consumer table.
• FND_SECURITY_GROUPS — referenced by ASG_APPLICATIONS_B.SECURITY_GROUP_ID, supplying security scoping.
• ASG_APPLICATIONS_TL — the translatable companion table holding language-specific application names and descriptions.
• FND_APPLICATION / FND_USER — contextual dependencies for audit columns and application registration.
• CRM Gateway mobile APIs that read the registry when provisioning devices and synchronizing content.