Results for “source_document_type”

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

Overview

JAI_RGM_ITEM_GEN_DOCS is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about documents generated during TCS (Tax Collected at Source) processing, a statutory requirement for certain Asia/Pacific country localizations. Each row links an originating transaction — typically a cash receipt or an invoice — to the document that was generated as a result of TCS processing, capturing the classification of the item, the type and amount of the generated document, and the identity of the generated transaction within Oracle Receivables.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this table behaves as a satellite-leaning entity. Records are strongly keyed by a transaction identifier and carry descriptive attributes and references to other hubs (receipts, transactions), which is characteristic of satellite or link-satellite constructs rather than a pure hub. This is a heuristic classification offered as a modeling suggestion only; the operational role of the table in EBS is transactional detail for TCS document generation.

Key Information Stored

The table defines 14 documented columns. The most significant for functional and reporting purposes are:

• TRANSACTION_ID — the primary key column and the column behind both the primary key constraint JAI_RGM_ITEM_GEN_DOCS_PK and the unique index JAI_RGM_ITEM_GEN_DOCS_U1. It serves as the surrogate identifier for each generated-document record and is the business-key candidate documented via the unique index.
• SOURCE_DOCUMENT_ID — foreign key to AR_CASH_RECEIPTS_ALL; identifies the cash receipt that triggered TCS processing.
• SOURCE_DOCUMENT_TYPE — indicates the category of the source document (for example, receipt versus invoice) so the originating transaction can be interpreted correctly.
• GENERATED_DOC_ID — foreign key to RA_CUSTOMER_TRX_ALL; points to the Receivables transaction created as the TCS output document.
• GENERATED_DOC_TRX_NUMBER — the human-readable transaction number of the generated document, useful in reports and reconciliation.
• GENERATED_DOC_TYPE — the classification of the generated document (for example, credit memo or invoice).
• GENERATED_DOC_AMT — the monetary amount of the generated document, central to TCS tax reporting.
• ITEM_CLASSIFICATION — the item classification used to determine the applicable TCS treatment.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording creation and modification metadata.

Common Use Cases and Queries

Typical use cases include reconciling TCS-generated documents against their source receipts, reporting TCS document amounts by source document type or item classification, and auditing the chain from receipt to generated Receivables transaction. A representative join pattern follows:

• Joining to AR_CASH_RECEIPTS_ALL on SOURCE_DOCUMENT_ID = CASH_RECEIPT_ID to retrieve the originating receipt details.
• Joining to RA_CUSTOMER_TRX_ALL on GENERATED_DOC_ID = CUSTOMER_TRX_ID to retrieve the generated invoice or credit memo.
• Aggregating GENERATED_DOC_AMT grouped by GENERATED_DOC_TYPE or ITEM_CLASSIFICATION for statutory TCS reporting.
• Filtering by CREATION_DATE or LAST_UPDATE_DATE to extract documents generated within a reporting period.

Because the table carries standard audit columns and an OBJECT_VERSION_NUMBER, it is safe to query concurrently with application activity provided bind variables or appropriate read consistency are used.

Related Objects

The FK metadata identifies the following significant related objects and join columns:

• AR_CASH_RECEIPTS_ALL — the cash receipts table; joined via JAI_RGM_ITEM_GEN_DOCS.SOURCE_DOCUMENT_ID = AR_CASH_RECEIPTS_ALL.CASH_RECEIPT_ID.
• RA_CUSTOMER_TRX_ALL — the Receivables transactions table; joined via JAI_RGM_ITEM_GEN_DOCS.GENERATED_DOC_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID.
• JAI_RGM_REFS_ALL — references this table through two columns, PARENT_TRANSACTION_ID and TRANSACTION_ID, forming a hierarchical relationship where generated documents can be chained to parent transactions.

Together these objects provide the transactional context required to trace TCS document generation from source receipt through to the resulting Receivables transaction.