Results for “form_number”

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

Overview

JAI_CMN_ST_FORMS is a table owned by the JA schema within the Asia/Pacific Localizations product (JA) of Oracle E-Business Suite. Its documented purpose is to store information pertaining to Service Tax (ST) forms, which are statutory documents that businesses operating in Asia/Pacific jurisdictions must generate for indirect tax reporting and compliance. In EBS 12.1.1 and 12.2.2 alike, this table is a transactional component of the localization infrastructure that supports the printing, tracking, and reconciliation of tax forms issued against a registered entity's tax reporting obligations.

The table is defined with 13 physical columns and is uniquely identified by the primary key constraint JAI_CMN_ST_FORMS_PK, defined on the FORM_ID column. This is the constraint that users and developers frequently reference when searching for "jai_cmn_st_forms_pk." JAI_CMN_ST_FORMS references JAI_CMN_STFORM_HDRS_ALL via the ST_HDR_ID foreign key column, establishing a master-detail relationship. The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. From a modeling perspective, this suggests the table behaves primarily as a descriptive satellite capturing attributes attached to a parent ST form header entity, rather than as an independent hub of business keys or a link between two hubs.

Key Information Stored

The table stores both the technical identity of each ST form record and the business attributes that describe the form itself.

• FORM_ID — Surrogate primary key enforced by JAI_CMN_ST_FORMS_PK. Values are generated internally and carry no business meaning.
• ST_HDR_ID — Foreign key to JAI_CMN_STFORM_HDRS_ALL. This is the join column that links an individual form line to its parent form header record.
• FORM_NUMBER — The statutory or system-assigned number of the ST form. This is the strongest business-key candidate for external lookup.
• FIN_YEAR — The financial year to which the form relates, used for period-based tax reporting.
• FORM_DATE — The date on which the form was prepared or issued.
• TRANSACTION_DATE — The date of the underlying transaction the form documents.
• FORM_AMOUNT — The monetary amount represented on the form, typically the taxable or tax value.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column, used to detect concurrent updates.

The remaining documented columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — are the standard Oracle Application Object Library audit columns present on virtually every transactional EBS table. Their presence confirms the table is written through the normal EBS DML path and is subject to standard WHO-column auditing.

Common Use Cases and Queries

Typical usage centers on retrieving forms for a financial year, reconciling form amounts against underlying transactions, and reporting form activity by header.

• Listing forms for a parent header: SELECT f.form_id, f.form_number, f.form_date, f.form_amount FROM ja.jai_cmn_st_forms f WHERE f.st_hdr_id = :p_hdr_id;
• Financial year reporting: SELECT fin_year, COUNT(*), SUM(form_amount) FROM ja.jai_cmn_st_forms GROUP BY fin_year ORDER BY fin_year;
• Joining to the header for descriptive context: SELECT h.*, f.form_number, f.form_amount FROM ja.jai_cmn_st_forms f, ja.jai_cmn_stform_hdrs_all h WHERE f.st_hdr_id = h.st_hdr_id;
• Locating a specific form by its statutory number: SELECT * FROM ja.jai_cmn_st_forms WHERE form_number = :p_form_number;

Because FORM_NUMBER is the natural business identifier, reports and reconciliation extracts should join to the header and filter by FIN_YEAR and FORM_DATE rather than by surrogate FORM_ID.

Related Objects

• JAI_CMN_STFORM_HDRS_ALL — Parent/master table. Joined on JAI_CMN_ST_FORMS.ST_HDR_ID = JAI_CMN_STFORM_HDRS_ALL.ST_HDR_ID. This is the only documented foreign key relationship for this table.
• JAI_CMN_ST_FORMS_PK — The primary key constraint on FORM_ID, used by the optimizer for unique lookups and by application code for row identification.
• The ST form header and detail APIs, concurrent programs, and report templates within the JA localization module typically read this table through its parent header, so dependent logic generally reaches JAI_CMN_ST_FORMS via JAI_CMN_STFORM_HDRS_ALL rather than through direct table access.