Search Results bill_addr_id

Overview

The IGS_FI_BILL_ADDR table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Oracle Grants Accounting) product family. It functions as a child table to the bill header (IGS_FI_BILL_ALL) and is responsible for storing the physical address details associated with a financial bill. Its primary role is to manage the two distinct categories of addresses required for billing operations: the 'Bill To' address, where the invoice is sent, and the 'Remittance' address, where payment should be directed. While a bill is limited to a single remittance address, it can have multiple 'Bill To' addresses, enabling complex billing distribution scenarios. This table is essential for ensuring accurate invoicing and payment processing within the grants management lifecycle.

Key Information Stored

The table's structure is designed to capture comprehensive address information and its context. The critical columns include:

• BILL_ADDR_ID: The primary key, a unique system-generated identifier for each address record.
• BILL_ID: The foreign key linking the address to its parent bill in the IGS_FI_BILL_ALL table.
• ADDR_TYPE: A flag indicating the address category, restricted to 'R' for Remittance or 'B' for Bill To.
• ADDR_LINE_[1-4], CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE: Standard address components to fully define a postal location.
• DELIVERY_POINT_CODE: An optional field for specialized delivery or internal routing codes.
• Standard WHO and Concurrent Request Columns (CREATED_BY, LAST_UPDATE_DATE, REQUEST_ID, etc.): Audit columns tracking the record's creation and modification history.

Common Use Cases and Queries

This table is central to generating accurate invoice documents and payment instructions. A common reporting requirement is to retrieve all billing addresses for a specific bill or a set of bills, often joined with the header information. For instance, to list all 'Bill To' addresses for a particular bill, one would execute:

SELECT addr_line_1, city, state, postal_code, country
FROM igs.igs_fi_bill_addr
WHERE bill_id = :p_bill_id
AND addr_type = 'B';

Another critical use case is data validation, ensuring that bills have the required address types. A query to identify bills missing a remittance address would be:

SELECT b.bill_number
FROM igs.igs_fi_bill_all b
WHERE NOT EXISTS (
  SELECT 1
  FROM igs.igs_fi_bill_addr a
  WHERE a.bill_id = b.bill_id
  AND a.addr_type = 'R'
);

Integration with external systems for electronic funds transfer (EFT) or print formatting also heavily relies on the data stored in this table.

Related Objects

The IGS_FI_BILL_ADDR table maintains a strict hierarchical relationship within the IGS billing schema. Its primary dependencies are:

• Parent Table (Foreign Key Reference): IGS_FI_BILL_ALL. The BILL_ID column in IGS_FI_BILL_ADDR references the BILL_ID in IGS_FI_BILL_ALL. This enforces that every address record must be associated with a valid, existing bill header.
• Primary Key Constraint: IGS_FI_BILL_ADDR_PK on the BILL_ADDR_ID column. This unique identifier is the target for any potential foreign key relationships from other child objects, though none are detailed in the provided metadata.
• Unique Index: IGS_FI_BILL_ADDR_U1 on BILL_ADDR_ID, created in the APPS_TS_TX_IDX tablespace to enforce primary key uniqueness and improve query performance.

The table is stored in the APPS_TS_TX_DATA tablespace with standard Oracle EBS configuration parameters, indicating its role in holding transactional business data.