Results for “agent_code”

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

Overview

JA.JAI_CMN_BOE_AGENTS is a setup (master) table in the Oracle E-Business Suite Asia/Pacific Localizations module. It stores the registry of agents associated with Bill of Exchange (BOE) invoices — that is, the banks, financial institutions, or authorized intermediaries that handle BOE transactions for a legal entity. The table is owned by the JA schema and is validated at status VALID in both release 12.1.1 and 12.2.2.

The object is the primary source of agent definitions consumed by the BOE header table JAI_CMN_BOE_HDRS, which is the transaction-level entity that records each BOE drawn, accepted, or settled. Because agent identity is captured centrally here and referenced from transactional headers, the table behaves as a reference or master entity rather than a transactional fact.

Under the heuristic Data Vault classification mined from its foreign-key structure, JAI_CMN_BOE_AGENTS is hub-leaning: it carries a surrogate primary key, a natural business key (AGENT_CODE), and descriptive attributes, and it is referenced by other tables rather than referencing them. In a Data Vault model this would typically be implemented as a hub for the agent business key, with a satellite holding the name and address attributes.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• AGENT_ID — surrogate primary key, enforced by JAI_CMN_BOE_AGENTS_PK. It is the column propagated to transactional tables and should never be exposed as a business identifier.
• AGENT_CODE — the business-key candidate, enforced by unique index JAI_CMN_BOE_AGENTS_UK1. This is the user-facing identifier used in setup forms, reports, and the "agent_code" search term.
• AGENT_NAME — the descriptive name of the agent or bank.
• ADDRESS1, ADDRESS2, ADDRESS3 — free-form address lines for the agent.
• CITY, STATE, PIN — locality, region, and postal code components of the agent address.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns providing audit lineage.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework to detect concurrent updates.

The distinction between AGENT_ID and AGENT_CODE is important: joins between the header and setup tables use the surrogate key, while end-user queries and interfaces normally resolve the code.

Common Use Cases and Queries

Typical usage centers on validating BOE agents, driving invoice and remittance reports, and integrating agent data with external banking interfaces. A common pattern resolves the agent name onto BOE header detail:

• Join JAI_CMN_BOE_HDRS to JAI_CMN_BOE_AGENTS on AGENT_ID to report invoices by agent.
• Look up an agent by business key: SELECT agent_id, agent_name FROM ja.jai_cmn_boe_agents WHERE agent_code = :code.
• List active agents and their addresses for regulatory or audit reporting.
• Detect orphaned references by finding distinct AGENT_ID values in JAI_CMN_BOE_HDRS that have no matching row in the setup table.

Related Objects

• JAI_CMN_BOE_HDRS — the principal dependent table; JAI_CMN_BOE_HDRS.AGENT_ID references JAI_CMN_BOE_AGENTS, making this the primary transactional consumer of agent definitions.
• JAI_CMN_BOE_AGENTS_PK — primary-key constraint and unique index on AGENT_ID.
• JAI_CMN_BOE_AGENTS_UK1 — unique constraint and index on AGENT_CODE, protecting the business key.

Because the documented relationship set is limited to the BOE header, broader integration points — such as BOE lines, payment, or agent setup forms — should be confirmed against the specific 12.1.1 or 12.2.2 instance before being relied upon in custom extensions.