Results for “agent_name”

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

Overview

The JAI_CMN_BOE_APPLIED_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Asia/Pacific Localizations (product code JA) module. Its status in ETRM is documented as VALID, and it is available in both EBS 12.1.1 and 12.2.2. The view consolidates Bill of Exchange (BOE) application data by joining BOE matching lines with their corresponding BOE header records and the associated agent definitions. Bills of Exchange are a commonly used trade finance instrument in the Asia/Pacific region, and this view supplies a flattened, query-friendly representation of the association between a shipment or transaction line, its vendor and vendor site, the originating BOE, and the agent responsible for the instrument.

Because it is a view rather than a table, JAI_CMN_BOE_APPLIED_V does not store data of its own; it derives its rows at runtime from three BOE-related base objects. This makes it suitable for ad-hoc reporting, custom concurrent programs, Oracle Reports/BI Publisher data sources, and inbound/outbound integration extracts where a single denormalized row per BOE application line is required.

Underlying Base Objects

The documented view text defines the object over three base objects, each referenced through a synonym in the APPS schema:

• JAI_CMN_BOE_HDRS (aliased JBH) — the BOE header table holding vendor and vendor site information plus the agent identifier.
• JAI_CMN_BOE_AGENTS (aliased JBA) — the agent master for BOEs, keyed by AGENT_ID and carrying the AGENT_NAME.
• JAI_CMN_BOE_MATCHINGS (aliased JRB) — the BOE matching/allocation table linking a BOE to a transaction and shipment line with an applied amount.

The join conditions are: JRB.BOE_ID = JBH.BOE_ID and JBH.AGENT_ID = JBA.AGENT_ID. In practice this means a row is produced for every BOE matching record that has a valid header and a valid agent. If a matching line references a BOE with no agent, or an agent that does not exist in the agent master, that row will be excluded by the inner joins.

Key Columns

• TRANSACTION_ID — sourced from JRB.TRANSACTION_ID; identifies the transaction to which the BOE amount has been applied (typically corresponding to an AP invoice or related transaction).
• SHIPMENT_LINE_ID — sourced from JRB.SHIPMENT_LINE_ID; identifies the specific shipment line matched to the BOE.
• VENDOR_ID and VENDOR_SITE_ID — sourced from JBH; the supplier and supplier site tied to the BOE header.
• AGENT_NAME — sourced from JBA.AGENT_NAME; the descriptive name of the BOE agent. This is the column most commonly searched for when users look up "agent_name" against this object.
• BOE_ID — sourced from JRB.BOE_ID; the unique identifier of the Bill of Exchange.
• AMOUNT — sourced from JRB.AMOUNT; the amount of the BOE applied to the transaction/shipment line.

Common Use Cases and Queries

Typical uses include reporting applied BOE amounts by supplier or agent, reconciling BOE matchings to AP transactions, and extracting agent-level BOE data for trade finance reporting. A representative query listing applied BOE lines for a given agent is:

SELECT v.boe_id,
       v.transaction_id,
       v.shipment_line_id,
       v.vendor_id,
       v.vendor_site_id,
       v.agent_name,
       v.amount
FROM   apps.jai_cmn_boe_applied_v v
WHERE  v.agent_name = :agent_name
ORDER BY v.boe_id, v.transaction_id;

To summarize applied amounts per agent:

SELECT agent_name, COUNT(*) boe_lines, SUM(amount) total_applied
FROM   apps.jai_cmn_boe_applied_v
GROUP BY agent_name;

Because the view joins three base tables with inner joins, custom queries should account for the possibility that unmatched BOE header or agent records are absent. For completeness in reconciliation reports, consider outer-joining to JAI_CMN_BOE_MATCHINGS directly.