Results for “jai_cmn_om_ar_ar3_forms”

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

Overview

The JAI_CMN_OM_AR_AR3_FORMS table is a localization data object owned by the JA schema within the Asia/Pacific Localizations product family of Oracle E-Business Suite. It is documented as valid in both the 12.1.1 and 12.2.2 releases. The table stores AR3 forms and their associated details, and it is referenced by both the Receivables (AR) and Order Management (OM) modules. In practice, the AR3 form is a statutory excise and tax document used primarily for Indian and broader Asia/Pacific regulatory compliance, where shipment, excise exemption, and delivery information must be captured against a customer, site, and transaction.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link table. It records relationships or associations between multiple business entities — customers, sites, organizations, locations, transaction types, and deliveries — rather than serving as a pure descriptive satellite. Each row carries descriptive attributes (form numbers, dates, exemption data) that can be treated as link-level or link-satellite content.

Key Information Stored

The table contains 23 documented columns. The most significant are summarized below:

• FORM_ID — surrogate primary key, enforced by the unique index JAI_CMN_OM_AR_AR3_FORMS_PK. No alternate business-key unique index is documented, so FORM_ID is the sole documented candidate.
• CUSTOMER_ID — references HZ_PARTIES, identifying the party to whom the AR3 form relates.
• CUSTOMER_SITE_ID — references HZ_PARTY_SITES, identifying the specific customer site.
• ORGANIZATION_ID — references HR_ALL_ORGANIZATION_UNITS, identifying the operating unit or inventory organization.
• LOCATION_ID — references HR_LOCATIONS_ALL, capturing the location context.
• TRX_TYPE_ID — references RA_CUST_TRX_TYPES_ALL, defining the receivables transaction type.
• TRX_NUMBER and TRX_DATE — the transaction reference and date for the AR3 record.
• DELIVERY_ID and DELIVERY_DATE — references WSH_NEW_DELIVERIES and records the shipment delivery details.
• EXCISE_EXEMPT_TYPE, EXCISE_EXEMPT_REFNO, EXCISE_EXEMPT_DATE — statutory excise exemption data.
• AR3_FORM_NO and AR3_FORM_DATE — the AR3 form identity and issuance date.
• RECEIVED_DATE — date the form was received.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical use cases include AR3 form reconciliation for excise reporting, delivery-to-invoice traceability, and exemption certificate tracking. A common reporting pattern joins the form to its customer and transaction context:

• Reporting AR3 forms by customer and site for a given organization and date range.
• Reconciling AR3 form numbers against deliveries and AR transactions.
• Auditing excise exemption references and dates.
• Identifying forms by received date for compliance tracking.

A representative query joining the primary business entities:

SELECT f.AR3_FORM_NO, f.AR3_FORM_DATE, f.TRX_NUMBER, f.TRX_DATE, p.party_name
FROM JA.JAI_CMN_OM_AR_AR3_FORMS f, HZ_PARTIES p
WHERE f.CUSTOMER_ID = p.party_id
AND f.ORGANIZATION_ID = :org_id;

Related Objects

The documented foreign keys establish direct relationships with the following significant objects:

• HZ_PARTIES via CUSTOMER_ID — customer party master.
• HZ_PARTY_SITES via CUSTOMER_SITE_ID — customer site master.
• HR_ALL_ORGANIZATION_UNITS via ORGANIZATION_ID — organization definition.
• HR_LOCATIONS_ALL via LOCATION_ID — location master.
• RA_CUST_TRX_TYPES_ALL via TRX_TYPE_ID — receivables transaction types.
• WSH_NEW_DELIVERIES via DELIVERY_ID — shipping deliveries.

These relationships confirm the table's cross-module role bridging Order Management shipment data with Receivables transaction data for statutory AR3 compliance reporting in the Asia/Pacific localization.