Results for “rotation_no”

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

Overview

JAI_CMN_BOE_HDRS is the header table for the Bill of Entry (BOE) functionality delivered within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). It resides in the JA schema and stores the top-level information for a BOE when a BOE Invoice is created through the Invoice Linking (IL) process. The table functions as the authoritative parent record for each BOE transaction, holding customs, shipment, vendor, and financial summary data that downstream BOE detail, matching, and write-off processes reference by the BOE_ID surrogate key.

From a Data Vault modeling perspective, JAI_CMN_BOE_HDRS is classified heuristically as satellite-leaning. The BOE_ID primary key acts as the hub-like identifier for a business event (a customs BOE), while the descriptive attributes — vessel, port, dates, amounts, and consignee details — behave as satellite attributes. This classification is a modeling suggestion based on the FK topology, not an implemented Data Vault design.

Key Information Stored

The table contains 28 documented columns. Its surrogate primary key is BOE_ID, enforced by the unique index JAI_CMN_BOE_HDRS_PK. There are no other documented unique indexes, so BOE_ID is the sole business-key candidate recorded in the metadata.

• BOE_ID — surrogate primary key identifying each BOE header record.
• ORGANIZATION_ID — operating unit or organization that owns the BOE; FK to HR_ALL_ORGANIZATION_UNITS.
• VENDOR_ID and VENDOR_SITE_ID — supplier and supplier site on the BOE; FKs to HZ_PARTIES and HZ_PARTY_SITES.
• AGENT_ID — customs clearing agent; FK to JAI_CMN_BOE_AGENTS.
• LEGAL_ENTITY_ID — legal entity associated with the BOE; FK to FV_LEGAL_ENTITIES.
• LOCATION_ID — port or customs location; FK to HR_LOCATIONS_ALL.
• BOE_TYPE, PORT_CODE, PORT_NAME — classify the BOE and identify the port of entry.
• BOL_DATE, IMPORT_DATE, ROTATION_DATE — key customs and shipment dates.
• VESSEL_NAME, ROTATION_NO, IMPORT_SR_NUM — shipping and import reference identifiers.
• COUNTRY_ORIGIN, COUNTRY_CONSIGNMNT — origin and consignment countries.
• BOE_AMOUNT, AMOUNT_APPLIED, AMOUNT_WRITTEN_OFF — financial totals tracking BOE value, matched amount, and written-off amount.
• CONSOLIDATED_FLAG — indicates whether the BOE is part of a consolidated shipment.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) support concurrency control and auditing.

Common Use Cases and Queries

Typical reporting scenarios include BOE register extracts, customs reconciliation, agent performance, and applied-versus-written-off amount analysis. A common query joins the BOE header to its detail and matching lines:

• Retrieve all BOEs for a given organization and date range: SELECT boe_id, boe_type, port_code, bol_date, boe_amount FROM jai_cmn_boe_hdrs WHERE organization_id = :org AND bol_date BETWEEN :from_date AND :to_date;
• Outstanding balance analysis: SELECT boe_id, boe_amount, amount_applied, amount_written_off, (boe_amount - amount_applied - amount_written_off) outstanding FROM jai_cmn_boe_hdrs WHERE organization_id = :org;
• Agent and vendor summary: SELECT h.agent_id, h.vendor_id, COUNT(*) boe_count, SUM(h.boe_amount) total_amount FROM jai_cmn_boe_hdrs h GROUP BY h.agent_id, h.vendor_id;

These patterns support customs compliance audits and month-end reconciliation of import charges against matched invoices.

Related Objects

JAI_CMN_BOE_HDRS participates in a well-defined parent-child structure documented through foreign key relationships.

• JAI_CMN_BOE_DTLS — child BOE line details joined on BOE_ID.
• JAI_CMN_BOE_MATCHINGS — invoice matching records joined on BOE_ID.
• JAI_CMN_BOE_WRITEOFFS and JAI_CMN_WRITEOFFS_T — write-off records referencing the BOE header via BOE_ID.
• JAI_CMN_BOE_AGENTS — agent master referenced through AGENT_ID.
• HZ_PARTIES and HZ_PARTY_SITES — supplier and site references via VENDOR_ID and VENDOR_SITE_ID.
• HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS_ALL, and FV_LEGAL_ENTITIES — organizational, location, and legal entity references via ORGANIZATION_ID, LOCATION_ID, and LEGAL_ENTITY_ID.