Search Results ra_cust

Overview

ZX_JE_EXTRACT_PKG is the Oracle E-Business Tax (EBTax) package body responsible for extracting tax line detail from EBTax into the journal entry interface consumed by Oracle General Ledger. The package assembles the reporting metadata, tax amounts, and associated source-document context required to produce subledger journal entries for tax distributions arising from Receivables, Payables, and General Ledger transactions. Its public methods are compartmentalized by source application — POPULATE_JE_AR for Receivables, POPULATE_JE_AP for Payables, and POPULATE_JE_GL for General Ledger — so that the same extraction logic can be reused across mixed transaction populations without duplicating code.

The package is classified as "OTHER" in the ETRM metadata, indicating it is an internal EBTax utility rather than a documented public API. It is invoked by one other package in the applications schema, reflecting its position as a supporting component of the tax journal entry extraction flow rather than a standalone entry point.

Key Procedures and Functions

• POPULATE_JE_AR — Extracts tax lines originating from Oracle Receivables transactions and populates the tax journal entry reporting structure. This procedure drives the Receivables side of the extraction, resolving customer transaction invoices and their associated tax lines.
• POPULATE_JE_AP — Performs the equivalent extraction for Oracle Payables invoices, gathering tax line information from supplier invoices and mapping it into the reporting structures used for journal entry creation.
• POPULATE_JE_GL — Handles tax lines that must be reported through General Ledger sources, completing the third leg of the extraction. This covers scenarios where tax is journaled directly in GL rather than through a subledger.

In addition to the three documented procedures, the package contains private helper logic, notably a procedure that populates reporting code and reporting code name values for a given tax line (referenced in the header comments as get_emea_rep_code_name), which is called from both POPULATE_JE_AR and POPULATE_JE_AP to prevent duplication of reporting code lookups.

Tables Accessed

• ZX_LINES — The primary EBTax tax line table, providing the tax line identifiers and amounts being extracted.
• ZX_REP_TRX_DETAIL_T, ZX_REP_TRX_JX_EXT_T, ZX_REP_TRX_JX_EXT_T_S — The reporting transaction detail and its journal extension tables, into which extracted reporting rows are written.
• RA_CUSTOMER_TRX_ALL — Supplies Receivables transaction context for the AR extraction path. This is the object most directly associated with the user search term "ra_cust".
• AP_INVOICES_ALL — Supplies Payables invoice context for the AP extraction path.
• GL_JE_LINES — Provides General Ledger journal line detail for the GL extraction path.
• ZX_REPORTING_CODES_B, ZX_REPORTING_CODES_TL, ZX_REPORTING_TYPES_B, ZX_REPORT_CODES_ASSOC — Configuration tables that resolve reporting code values, translated names, reporting type definitions, and the association between codes and reporting types.
• FINANCIALS_SYSTEM_PARAMS_ALL — Supplies ledger and system parameter defaults required to build the journal entries.
• HR_LOCATIONS_ALL — Provides location information, typically for reporting or address derivation.
• PLITBLM — The standard PL/SQL integer table type used internally for array processing.

Usage Notes

ZX_JE_EXTRACT_PKG is not intended to be called directly by end users or typical customizations. It is invoked in the context of EBTax journal entry extraction, generally driven by concurrent processing that creates tax journal entries for subledger and GL transactions. The procedure selection is determined by the source application of the transaction being processed, so a Receivables distribution invokes POPULATE_JE_AR, a Payables invoice invokes POPULATE_JE_AP, and GL-sourced tax invokes POPULATE_JE_GL.

Because the package writes into the ZX reporting journal extension tables and reads key configuration tables such as ZX_REPORTING_CODES_B and ZX_REPORT_CODES_ASSOC, changes to reporting code setup can affect its output. Customizations should avoid modifying the package body directly; instead, extensions should operate on the reporting tables or use supported EBTax APIs. The package is listed as referenced by one other package, confirming it is a dependent component in the tax to GL extraction chain rather than a top-level API.