Results for “xnp_sync_registration”

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

Overview

XNP.XNP_SYNC_REGISTRATION is a table within the Oracle E-Business Suite Number Portability module (product code XNP). Its documented purpose is to maintain the state of synchronized workflows associated with number portability order processing. In practical terms, each row represents the synchronization context for a porting order, tracking whether the participants involved in that order have reached a consistent state.

The table resides in the XNP schema and is marked VALID in the ETRM 12.2.2 metadata. Under the heuristic Data Vault classification applied to its foreign-key structure, XNP_SYNC_REGISTRATION is characterized as satellite-leaning. This should be treated as a modeling suggestion rather than a definitional statement: the table behaves more like a descriptive satellite that records state and status attributes concerning a parent business entity, rather than a pure hub of identifiers or a link resolving many-to-many relationships. The parent entity it describes is the order referenced through ORDER_ID.

Because number porting in Oracle EBS depends on coordinated interactions between carriers, the synchronization registration record provides the metadata that orchestration logic uses to determine whether all required parties remain aligned.

Key Information Stored

The documented physical schema contains 12 columns. Among the most important:

• SYNC_REGISTRATION_ID — the surrogate primary key, enforced through XNP_SYNC_REGISTRATION_PK and also carried by unique index XNP_SYNC_REGISTRATION_U1.
• ORDER_ID — the foreign key to XDP_ORDER_HEADERS, tying the synchronization record to the porting order it governs. This column participates in the composite unique index XNP_SYNC_REGISTRATION_U2.
• SYNC_LABEL — a label that distinguishes synchronization registrations; together with ORDER_ID it forms the business-key candidate XNP_SYNC_REGISTRATION_U2 (SYNC_LABEL, ORDER_ID). This implies an order may hold more than one labeled synchronization context.
• STATUS — the current synchronization status of the workflow.
• MAX_PARTICIPANTS — the number of participants expected in the synchronization group.
• PARTIES_NOT_IN_SYNC — identifies which participants have not yet reached a synchronized state.
• SECURITY_GROUP_ID — the multi-org/security-group discriminator, foreign-keyed to FND_SECURITY_GROUPS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each registration row.

Common Use Cases and Queries

The most frequent operational need is resolving synchronization state against the parent order, which is the documented join to XDP_ORDER_HEADERS. A representative query:

• SELECT sr.SYNC_REGISTRATION_ID, sr.SYNC_LABEL, sr.STATUS, sr.MAX_PARTICIPANTS, sr.PARTIES_NOT_IN_SYNC FROM XNP.XNP_SYNC_REGISTRATION sr WHERE sr.ORDER_ID = :order_id;
• Identifying stalled synchronizations by filtering on STATUS or on rows where PARTIES_NOT_IN_SYNC is populated, useful for exception dashboards.
• Reporting all synchronization contexts for a porting order joined to XDP_ORDER_HEADERS via ORDER_ID to correlate order attributes with synchronization outcomes.
• Security-scoped queries constraining SECURITY_GROUP_ID to enforce row-level access consistent with EBS security-group conventions.

Because the unique key is (SYNC_LABEL, ORDER_ID), queries that resolve a specific synchronization context should generally filter on both columns rather than on ORDER_ID alone.

Related Objects

• XDP_ORDER_HEADERS — referenced by XNP_SYNC_REGISTRATION.ORDER_ID; the primary parent object for the synchronization record.
• FND_SECURITY_GROUPS — referenced by XNP_SYNC_REGISTRATION.SECURITY_GROUP_ID; governs row-level security.
• XNP_SYNC_REGISTRATION_PK — primary key constraint/index on SYNC_REGISTRATION_ID.
• XNP_SYNC_REGISTRATION_UK1 / XNP_SYNC_REGISTRATION_U2 — unique constraint on (SYNC_LABEL, ORDER_ID).
• XNP_SYNC_REGISTRATION_U1 — unique index on SYNC_REGISTRATION_ID.

All facts above derive from the documented XNP schema metadata; additional child synchronization tables are not confirmed in the provided excerpt.