Search Results agent_code




Overview
Explore in AI Chat

Overview

The table JA.JAI_CMN_BOE_AGENTS is a master data repository within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is part of the JA (Oracle Financials for India) schema, which houses localization components for the Indian market. The table's primary function is to store definitive information about agents. As per the ETRM documentation, this agent information is specifically utilized during the creation of a BOE (Bill of Entry) invoice. This indicates its critical role in supporting localized Indian trade and customs invoicing processes integrated within the broader Oracle Financials and Payables modules.

Key Information Stored

The table is structured to capture the unique identifier, code, name, and complete postal address for each agent. The key mandatory columns are AGENT_ID, AGENT_CODE, AGENT_NAME, ADDRESS1, CITY, and STATE. The AGENT_ID is a system-generated unique numeric identifier, while the AGENT_CODE is a user-defined mandatory identifier. The address is split across three lines (ADDRESS1, ADDRESS2, ADDRESS3) and includes CITY, STATE, and an optional numeric PIN code. The table also includes standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and an OBJECT_VERSION_NUMBER for managing concurrent access and data versioning.

Common Use Cases and Queries

The primary use case is the population and validation of agent details on BOE-related transactional documents. For reporting and data verification, common queries include fetching a complete list of agents or looking up a specific agent by code or name. A typical query to retrieve all agent information is provided in the ETRM metadata:

SELECT AGENT_ID, AGENT_CODE, AGENT_NAME, ADDRESS1, ADDRESS2, ADDRESS3, CITY, STATE, PIN
FROM JA.JAI_CMN_BOE_AGENTS
ORDER BY AGENT_CODE;

Another frequent pattern is joining this table to transactional BOE invoice tables (not explicitly listed in the provided dependencies but implied by the table's purpose) to generate detailed invoices or compliance reports that include full agent addresses. Data maintenance operations, such as identifying agents missing state or city information, are also common administrative queries.

Related Objects

Based on the provided dependency information, JA.JAI_CMN_BOE_AGENTS is a standalone master table referenced by other objects. The ETRM explicitly states that "JA.JAI_CMN_BOE_AGENTS is referenced by following: JA JAI_CMN_BOE_AGENTS#". This suggests the existence of a database trigger (denoted by the '#') on the table, likely named JAI_CMN_BOE_AGENTS#, which may enforce business rules or propagate changes. The table's structure, with a primary key (JAI_CMN_BOE_AGENTS_PK on AGENT_ID) and a unique key (JAI_CMN_BOE_AGENTS_UK1 on AGENT_CODE), is designed to be referenced by foreign keys in transactional tables, such as those storing BOE invoice headers, although those specific referencing tables are not named in the excerpt provided.