Results for “application_type”

50+ results




Overview
Explore in AI Chat

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

Overview

ASG_SNAPSHOT_LOGS is a table owned by the ASG schema within the Oracle E-Business Suite CRM Gateway for Mobile Devices product (ASG). It serves as the central tracking and metadata repository for snapshot executions performed by the mobile device synchronization infrastructure. Each record captures the definition, configuration, and status of a snapshot operation — a logical grouping of data published to mobile clients — including which base table is snapshotted, how primary and filter keys are derived, and the publication context under which the snapshot was released.

From a Data Vault modeling perspective, the mined foreign key structure classifies this table as hub-leaning. This is a modeling suggestion rather than a mandated design: the surrogate primary key SNAPSHOT_LOG_ID behaves as a hub key, while dependent child tables attach descriptive attributes against it. Because the table also carries descriptive configuration attributes (filtering, refresh grouping, application type), it functions simultaneously as a hub with an attached effectivity/configuration satellite. Its granularity is one row per snapshot definition per release, anchored by the primary key constraint SNAPSHOT_LOG_ID_PK.

Key Information Stored

The documented physical schema contains twenty columns. The most significant for functional and diagnostic purposes are:

  • SNAPSHOT_LOG_ID — the surrogate primary key, uniquely identifying each snapshot log record and acting as the hub key referenced by dependent tables.
  • TABLE_NAME — the base application table whose data is captured by the snapshot.
  • OWNER — the schema owning the snapshotted base table.
  • PRIMARY_KEY_FLAG — indicates whether primary key handling is enabled for the snapshot.
  • PRIMARY_KEY_COLUMNS — the column list constituting the snapshot's primary key definition.
  • FILTER_KEY_COLUMNS — columns used to filter which base table rows are included in the snapshot.
  • CREATE_PRIMARY_FLAG — controls whether a primary key constraint is generated on the target structure.
  • REFRESH_GROUP — the synchronization grouping to which the snapshot belongs, governing refresh cadence.
  • APPLICATION_TYPE — categorizes the snapshot by the owning application context.
  • STATUS — the lifecycle state of the snapshot log record.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing Oracle EBS multi-tenant data access partitioning.
  • RELEASE_VERSION, PUBLICATION_ID, BASE_PUB_ID — publication lineage attributes linking the snapshot to a specific mobile publication and its base publication.
  • PCT_FREE, PCT_USED — storage parameters applied to the snapshot's physical structures.
  • Standard WHO audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

No unique business-key index is documented beyond the surrogate primary key; the natural business identity is effectively the combination of TABLE_NAME, OWNER, REFRESH_GROUP, and publication context.

Common Use Cases and Queries

Typical usage centers on diagnosing mobile synchronization failures, auditing snapshot publication lineage, and reporting which base tables are exposed to field devices. A representative query joins the log to its resolution children:

  • Identify active snapshots for a given base table: SELECT snapshot_log_id, table_name, owner, status FROM asg_snapshot_logs WHERE table_name = :table_name AND status = :status;
  • Trace publication lineage: filter on PUBLICATION_ID or BASE_PUB_ID alongside RELEASE_VERSION to confirm which snapshots belong to a shipped mobile release.
  • Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the caller's operating unit or security group.
  • Configuration audit: inspect PRIMARY_KEY_COLUMNS and FILTER_KEY_COLUMNS to verify filter logic applied to a sincronization batch.

Related Objects

The following objects are structurally bound to ASG_SNAPSHOT_LOGS through documented foreign key relationships:

  • ASG_CONF_RESOLUTION — references ASG_SNAPSHOT_LOGS via ASG_CONF_RESOLUTION.SNAPSHOT_LOG_ID; holds conflict-resolution rules applied per snapshot.
  • ASG_COLUMN_GROUPS — references ASG_SNAPSHOT_LOGS via ASG_COLUMN_GROUPS.SNAPSHOT_LOG_ID; defines column groupings projected for each snapshot.
  • FND_SECURITY_GROUPS — parent of ASG_SNAPSHOT_LOGS.SECURITY_GROUP_ID; governs multi-tenant access partitioning across the EBS instance.

These three relationships form the documented dependency envelope. ASG_CONF_RESOLUTION and ASG_COLUMN_GROUPS function as degenerate dependents (link/satellite candidates) keyed off the hub's surrogate identifier, while FND_SECURITY_GROUPS supplies the mandatory Oracle EBS security context for every snapshot log row.