Search Results jai_om_lc_hdrs_pk

Overview

JA.JAI_OM_LC_HDRS is a transactional header table within the Asia/Pacific Localizations (JA) product family in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores Letter of Credit (LC) header information captured against customer orders, including the identifying LC number, the customer, issuing and negotiating bank details, validity dates, monetary amounts, and the outstanding balance. The table functions as the master record for each customer LC, from which downstream order, shipment, and payment activities draw their LC references.

Under a heuristic Data Vault classification derived from its foreign key structure, this table is satellite-leaning. It records descriptive and mutable attributes (balances, dates, bank data, remarks) rather than defining many-to-many relationships, and its single foreign key toward the customer entity (HZ_PARTIES) supports that characterization. The classification is a modeling suggestion only; in native EBS it functions as a standard transactional entity table owned by the JA schema.

Key Information Stored

The table is documented with 42 columns. The surrogate/primary key is defined by the unique index JAI_OM_LC_HDRS_PK, built on LC_NUMBER, which also serves as the business-key candidate for this entity. The most significant columns are:

• LC_NUMBER — primary key and business identifier for the Letter of Credit.
• REFERENCE_NUMBER — customer or internal cross-reference to the LC.
• CUSTOMER_ID — foreign key to HZ_PARTIES; identifies the customer holding the LC.
• START_DATE / END_DATE — validity window of the LC.
• LC_TYPE — classification of the LC (for example, sight versus usance).
• LC_ORIGINAL_AMOUNT / LC_BALANCE_AMOUNT — the issued value and the remaining available balance.
• NEGOTIATION_DAYS, LAST_NEGOTIATION_DATE, LAST_SHIP_DATE, CREDIT_PERIOD — payment and shipment timing controls.
• ISS_BANK_NAME, ISS_BRANCH_NAME, ISS_BANK_ADDRESS — issuing bank details.
• NEG_BANK_NAME, NEG_BRANCH_NAME, NEG_BANK_ADDRESS — negotiating bank details.
• DESCRIPTION and REMARKS — free-text annotations.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include LC register reporting, balance/utilization tracking, and order-to-shipment validation against open LCs. A common pattern joins the LC header to the customer:

SELECT lc.lc_number, lc.reference_number, lc.lc_type,
       lc.lc_original_amount, lc.lc_balance_amount,
       lc.start_date, lc.end_date,
       hp.party_name
FROM   ja.jai_om_lc_hdrs lc,
       hz_parties       hp
WHERE  lc.customer_id = hp.party_id
AND    lc.end_date >= :p_as_of_date
ORDER BY lc.start_date;

A utilization report compares original against remaining balance by customer and LC type, while an expiry watchlist filters on END_DATE within the current period. Because the flexfield columns reside on this header, reporting that segments LC data by ATTRIBUTE_CATEGORY is also practical without joining additional tables.

Related Objects

• HZ_PARTIES — referenced by JAI_OM_LC_HDRS.CUSTOMER_ID; the customer master providing party identity and names.
• JA.JAI_OM_LC_HDRS_PK — the unique index enforcing the LC_NUMBER primary key.
• Other JA localization objects in the JAI_OM_LC_* family (such as LC associational or assignment tables) that link LC headers to orders and shipments.
• Order Management (ONT) order and line tables, which reference LC information for sales order processing.
• Receivables (AR) objects where LC-controlled collections affect customer balances.

As with all JA localization objects, direct DML should be avoided in favor of the supported concurrent programs and forms that maintain LC integrity.