Results for “base_date”

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

Overview

The JL_BR_AP_TAX_CALENDAR_HEADERS table, owned by the JL schema (Latin America Localizations product family), stores header-level definitions for Brazilian withholding tax calendars used by Oracle Payables. Each row establishes a named tax calendar that governs the due dates and scheduling behavior applied to Brazilian withholding tax obligations processed through Payables. This object is central to Brazil-specific statutory compliance, since withholding tax remittance in Brazil follows calendar-driven deadlines rather than simple invoice-date rules.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. Its single-column primary key, TAX_CALENDAR_NAME, functions as a natural business key rather than a generated surrogate, making the table suitable as a hub entity in a dimensional or Data Vault style model, with descriptive attributes (such as TAX_TYPE and BASE_DATE) behaving as satellite payload. Downstream calendar line detail is linked via the child table, forming the natural link relationship.

Key Information Stored

The table contains nine documented columns. The most significant are:

• TAX_CALENDAR_NAME — The primary key and business-key candidate (enforced by unique index JL_BR_AP_TAX_CALENDAR_HEAD_U1). This is the identifier users search for and reference throughout configuration and reporting.
• TAX_TYPE — Classifies the withholding tax category the calendar governs, determining which tax regime the schedule applies to.
• BASE_DATE — The anchor date from which calendar-driven due dates are calculated, driving the scheduling logic for withholding tax remittance.
• DESCRIPTION — Free-text description providing a human-readable label for the calendar definition.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each header row and when.

Because TAX_CALENDAR_NAME is both the primary key and the unique business identifier, it bridges header configuration to the detailed line schedules held in the child table.

Common Use Cases and Queries

Typical scenarios include validating withholding tax calendar setup, reporting on active tax calendars by type, and joining header definitions to line-level due dates for statutory reporting. Because it is a header table, most queries either look up a single calendar by name or join downward to lines.

Sample lookup by name:

• SELECT tax_calendar_name, tax_type, base_date, description FROM jl.jl_br_ap_tax_calendar_headers WHERE tax_calendar_name = :p_name;

Sample header-to-lines join for due-date reporting:

• SELECT h.tax_calendar_name, h.tax_type, l.* FROM jl.jl_br_ap_tax_calendar_headers h, jl.jl_br_ap_tax_calendar_lines l WHERE h.tax_calendar_name = l.tax_calendar_name AND h.tax_type = :p_tax_type;

Typical reporting uses include auditing which calendars exist per tax type, confirming the base date driving remittance schedules, and cross-checking that every configured withholding calendar has corresponding line detail.

Related Objects

• JL_BR_AP_TAX_CALENDAR_LINES — The principal dependent table. Its foreign key JL_BR_AP_TAX_CALENDAR_LINES.TAX_CALENDAR_NAME references JL_BR_AP_TAX_CALENDAR_HEADERS.TAX_CALENDAR_NAME, providing the detailed calendar schedule entries for each header.
• Primary key constraint JL_BR_AP_TAX_CALENDAR_HEAD_PK and unique index JL_BR_AP_TAX_CALENDAR_HEAD_U1 — Both defined on TAX_CALENDAR_NAME, enforcing uniqueness and supporting the hub-style identity of each calendar.
• Oracle Payables (AP) withholding tax flows — Application-level processes and concurrent programs that consume these calendar definitions when calculating Brazilian withholding tax due dates.
• JL schema localization objects — Related Brazilian localization tables that share tax type and calendar conventions referenced by TAX_TYPE.