Results for “sequence_name”

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

Overview

ASG_SEQUENCES is a table in the ASG schema (CRM Gateway for Mobile Devices) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores sequence definitions that govern how numeric or code values are generated and synchronized on mobile devices connected through the CRM Gateway. Sequences of this type are typically used to allocate identifiers for mobile-side transactions and records that must reconcile with server-side numbering when devices operate in a disconnected or intermittently connected mode. The table is owned by ASG and holds 13 documented columns in the 12.2.2 physical schema.

Under a heuristic Data Vault classification derived from its foreign key structure, ASG_SEQUENCES is satellite-leaning. It carries descriptive attributes (sequence name, schema, table, column, and mobile value) that qualify a parent entity rather than acting as a pure hub or a pure link. Modelers should treat this as a suggestion only; the table's actual role is operational metadata for sequence allocation in the mobile gateway.

Key Information Stored

The primary key is defined by the constraint ASG_SEQUENCES_PK on SEQUENCE_ID, and a unique index ASG_SEQUENCES_U1 also exists on SEQUENCE_ID. SEQUENCE_ID is therefore the surrogate identifier and the de facto business-key candidate for this object.

• SEQUENCE_ID — Surrogate primary key uniquely identifying each sequence record.
• SEQUENCE_NAME — The logical name by which the sequence is referenced by the mobile application or gateway process.
• PUBLICATION_ID — Foreign key to ASG_PUBLICATIONS, tying the sequence to a specific publication or mobile application distribution.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multitenant or organizational data segregation consistent with EBS security conventions.
• B_SCHEMA, B_TABLE, B_COLUMN — Identify the backend schema, table, and column against which the sequence value is applied or validated.
• MOBILE_VALUE — The current or last-used sequence value as known to the mobile device, supporting reconciliation on synchronization.
• RELEASE_VERSION — Version marker for the publication release associated with the sequence.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns recording creation and change history.

Common Use Cases and Queries

Typical usage centers on sequence inspection, publication-scoped reporting, and reconciliation between mobile and server values. Administrators query this table to determine which sequences belong to a publication before deploying or refreshing a mobile application.

• List sequences for a publication: SELECT SEQUENCE_ID, SEQUENCE_NAME, MOBILE_VALUE FROM ASG.ASG_SEQUENCES WHERE PUBLICATION_ID = :pub_id ORDER BY SEQUENCE_NAME;
• Locate the backend target of a sequence: SELECT SEQUENCE_NAME, B_SCHEMA, B_TABLE, B_COLUMN FROM ASG.ASG_SEQUENCES WHERE SEQUENCE_ID = :id;
• Audit recent changes: SELECT SEQUENCE_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM ASG.ASG_SEQUENCES WHERE LAST_UPDATE_DATE > SYSDATE - 30;
• Security-group filtered reporting joined to publications to confirm assignment scope.
• Reconciliation scripts comparing MOBILE_VALUE against server-generated identifiers to detect gaps or duplicates after device synchronization.

Related Objects

• ASG_PUBLICATIONS — Parent object referenced by ASG_SEQUENCES.PUBLICATION_ID; defines the mobile publication to which each sequence belongs.
• FND_SECURITY_GROUPS — Referenced by ASG_SEQUENCES.SECURITY_GROUP_ID; governs row-level access and organizational partitioning.
• ASG_SEQUENCES_PK / ASG_SEQUENCES_U1 — Primary key constraint and unique index on SEQUENCE_ID, used by all direct lookups.
• Other ASG schema tables in the CRM Gateway for Mobile Devices product that consume sequence values during device synchronization.
• Standard EBS audit and concurrent program infrastructure that references CREATED_BY, LAST_UPDATED_BY, and RELEASE_VERSION.

Because the table is defined as VALID in ASG, joins should be qualified with the ASG schema prefix, and access should respect the SECURITY_GROUP_ID filter expected by the CRM Gateway for Mobile Devices product.