Results for “ar_late_charge_doc_gt”

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

Overview

AR_LATE_CHARGE_DOC_GT is an Oracle Receivables (AR) schema table that functions as a global temporary table (indicated by the _GT suffix) used during the late charge and interest calculation and document generation process. It stores the intermediate and staged results of late charge (interest) computations before those charges are converted into Receivables transactions and accounting entries. In Oracle EBS 12.1.1 and 12.2.2, this table supports the Create Late Charge documents workflow, where outstanding balances on overdue transactions are evaluated against late charge terms and an interest amount is calculated, validated, and ultimately posted.

From a heuristic Data Vault modeling perspective, the mined FK structure places this object as a standalone construct — it is a staging/working table rather than a durable hub, link, or satellite. Its transient nature reflects its purpose: it holds document-level rows keyed by INTEREST_HEADER_ID, INTEREST_LINE_ID, and INTEREST_BATCH_ID while the late charge batch is being processed.

Key Information Stored

The table contains 38 documented columns. The most significant include:

• INTEREST_HEADER_ID — foreign key to AR_INTEREST_HEADERS_ALL; identifies the late charge interest header record being processed. Acts as the primary business identifier for the working row set.
• INTEREST_LINE_ID — FK to AR_INTEREST_LINES_ALL; the line-level identifier associating the charge with a specific interest line.
• INTEREST_BATCH_ID — FK to AR_INTEREST_BATCHES_ALL; groups rows into the batch run that generated them.
• CUST_TRX_TYPE_ID — FK to RA_CUST_TRX_TYPES_ALL; determines the transaction type used to create the late charge document.
• LEGAL_ENTITY_ID — FK to FV_LEGAL_ENTITIES; the legal entity owning the transaction for accounting and tax purposes.
• RECEIVABLES_TRX_ID — FK to AR_RECEIVABLES_TRX_ALL; maps the charge to a receivables activity.
• CUSTOMER_ID / CUSTOMER_SITE_USE_ID — the customer and site receiving the late charge.
• ORIGINAL_TRX_ID / ORIGINAL_TRX_CLASS — identifies the source overdue transaction and its class.
• INTEREST_CHARGED / DAILY_INTEREST_CHARGE / INTEREST_RATE — the computed charge amounts and rate applied.
• EXECUTION_STATUS / HDR_ERR_MSG / LINE_ERR_MSG — processing outcome and error diagnostics.
• ORG_ID — operating unit identifier supporting multi-org security.

Foreign keys to the interest, transaction type, legal entity, and receivables activity tables serve as the principal business-key candidates; INTEREST_HEADER_ID combined with INTEREST_LINE_ID typically distinguishes each working row.

Common Use Cases and Queries

Principal use cases include diagnosing failed late charge generation, auditing calculated interest, and reporting on late charges by customer or legal entity. A representative query retrieves processing errors for a batch:

• SELECT interest_header_id, customer_id, execution_status, hdr_err_msg, line_err_msg FROM ar_late_charge_doc_gt WHERE execution_status = 'ERROR';
• Join to AR_INTEREST_HEADERS_ALL and AR_INTEREST_LINES_ALL on the matching IDs to reconcile computed interest against source interest lines.
• Aggregate INTEREST_CHARGED by ORG_ID or LEGAL_ENTITY_ID for late charge reporting.
• Join to RA_CUST_TRX_TYPES_ALL and AR_RECEIVABLES_TRX_ALL to validate the document type and receivables activity assigned before posting.

Because this is a global temporary table, rows are session-scoped and generally purged after the concurrent program completes, so queries are intended for real-time monitoring and troubleshooting rather than historical reporting.

Related Objects

• AR_INTEREST_HEADERS_ALL — joined on INTEREST_HEADER_ID; parent interest header.
• AR_INTEREST_LINES_ALL — joined on INTEREST_LINE_ID; interest line details.
• AR_INTEREST_BATCHES_ALL — joined on INTEREST_BATCH_ID; batch definition.
• RA_CUST_TRX_TYPES_ALL — joined on CUST_TRX_TYPE_ID; transaction type for the charge document.
• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID; legal entity and accounting context.
• AR_RECEIVABLES_TRX_ALL — joined on RECEIVABLES_TRX_ID; receivables activity mapping.

These relationships support the Create Late Charge concurrent program and the AutoInvoice import of generated documents into RA_CUSTOMER_TRX_ALL.