Results for “register_code”

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

Overview

JAI_OM_OE_BOND_REG_HDRS is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds the header-level details of bond register types for an organization and location. In the context of Oracle Order Management and the Asia/Pacific localization for bonded warehouse and excise operations, this table serves as the master definition of each bond register — the regulatory construct under which imported or excisable goods are tracked while held in a bonded facility. Each row defines a register, its owning organization and location, the associated bond number and expiry, the amount registered, and a Letter of Undertaking flag. Downstream transaction and detail tables reference this header by REGISTER_ID.

From a dimensional modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. REGISTER_ID is a surrogate-style unique identifier that does not change across source systems, and the table is referenced by multiple child tables, which is characteristic of a hub in a Data Vault model. This is a heuristic suggestion, not a documented Data Vault design.

Key Information Stored

• REGISTER_ID — surrogate primary key, enforced by unique index JAI_OM_OE_BOND_REG_HDRS_PK. This is the business-key candidate used for all downstream joins.
• REGISTER_CODE — the user-visible code or number identifying the bond register to users and reports.
• ORGANIZATION_ID — the inventory organization that owns the register; foreign key to JAI_CMN_INVENTORY_ORGS.
• LOCATION_ID — the physical location or warehouse associated with the register.
• AMOUNT — the monetary amount or bond value registered for this register.
• BOND_NUMBER — the external bond or license number issued by the customs/regulatory authority.
• BOND_EXPIRY_DATE — the date on which the bond registration expires.
• LOU_FLAG — indicates whether a Letter of Undertaking applies to this register.
• OBJECT_VERSION_NUMBER — optimistic-locking column used by the EBS framework for concurrent updates.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and update context.

The surrogate primary key (REGISTER_ID) is distinct from any business-key candidate; no additional unique index beyond the PK is documented in the ETRM metadata.

Common Use Cases and Queries

Typical use cases include reporting on active and expiring bonds, reconciling register balances against transactions, and validating that a register is valid for a given organization and location before recording a bonded transaction. A common query pattern joins the header to its detail and transaction children to summarize activity per register:

• Listing registers for an organization: SELECT register_id, register_code, bond_number, bond_expiry_date FROM jai_om_oe_bond_reg_hdrs WHERE organization_id = :org_id;
• Expiry monitoring: filter on BOND_EXPIRY_DATE within a reporting window to raise renewal alerts.
• Reconciliation: join to JAI_OM_OE_BOND_REG_DTLS on REGISTER_ID to compare registered AMOUNT against detail balances.
• Transaction audit: join to JAI_OM_OE_BOND_TRXS on REGISTER_ID to trace all movement activity against a register.

Report definitions, OAF/Forms pages for bond register maintenance, and localization compliance reports for countries such as India or China typically query this table as the header source.

Related Objects

• JAI_CMN_INVENTORY_ORGS — referenced by ORGANIZATION_ID; supplies organization context.
• JAI_OM_OE_BOND_REG_DTLS — child table; joins on REGISTER_ID to REGISTER_ID.
• JAI_OM_OE_BOND_TRXS — transaction table; joins on REGISTER_ID to REGISTER_ID.
• JAI_OM_OE_BOND_REG_HDRS_PK — the unique index enforcing the primary key.

Together these objects form the bond register register-to-transaction chain used by the JA localization for bonded warehouse compliance.