Results for “period_frequency_id”

50+ results




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

Overview

The PSP.PSP_REPORT_PERIOD_FREQUENCY_TL table is the translation table for PSP_REPORT_PERIOD_FREQUENCY within the Oracle EBS Labor Distribution (PSP) module. It stores language-specific, user-facing translations of the report period frequency values that drive Labor Distribution reporting cycles—such as weekly, biweekly, semimonthly, and monthly frequencies. In a multilingual EBS deployment, this table enables the same underlying frequency definition to be presented in each installed language without duplicating the base business record.

The object resides in the PSP schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its role is purely descriptive: it carries translated display text keyed to a parent frequency row. A heuristic Data Vault classification mined from the foreign key structure suggests a satellite-leaning model, since the table depends on PSP_REPORT_PERIOD_FREQUENCY_B through its PERIOD_FREQUENCY_ID foreign key and holds descriptive, keyed attributes rather than independent business entities or pure relationships.

Key Information Stored

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

  • PERIOD_FREQUENCY_ID — the foreign key to PSP_REPORT_PERIOD_FREQUENCY_B and part of the composite unique key. It identifies the base frequency record being translated.
  • LANGUAGE — the language code for the translation row; part of the unique key and the primary determinant of which translated string is returned.
  • PERIOD_FREQUENCY — the translated, user-facing name of the period frequency, such as the localized equivalent of "Weekly" or "Monthly".
  • SOURCE_LANGUAGE — the language of the source text from which the translation was derived.
  • ZD_EDITION_NAME — the edition identifier supporting Oracle's edition-based redefinition and associated with the unique index PSP_REP_PERIOD_FREQ_TL_U1.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — which record who created and last modified each translation row.

The surrogate key relationship is defined by the foreign key to the base table, while the business-key candidate is the composite unique index PSP_REP_PERIOD_FREQ_TL_U1 over PERIOD_FREQUENCY_ID, LANGUAGE, and ZD_EDITION_NAME. This composite ensures a single translation per frequency per language per edition.

Common Use Cases and Queries

Reporters and developers query this table whenever a human-readable, language-specific frequency label is required. Common scenarios include Labor Distribution reporting, concurrent program parameters, and lookup-driven pages that must display frequency names in the user's session language.

A typical join resolves the translated label for the current language:

  • SELECT b.period_frequency_id, t.period_frequency
  • FROM psp_report_period_frequency_b b, psp_report_period_frequency_tl t
  • WHERE b.period_frequency_id = t.period_frequency_id
  • AND t.language = USERENV('LANG');

Other uses include translation completeness audits (comparing available languages against expected ones) and edition-aware queries that filter on ZD_EDITION_NAME to respect edition-based redefinition boundaries.

Related Objects

The most significant dependency is the base table that this translation table serves:

  • PSP_REPORT_PERIOD_FREQUENCY_B — the base ("B") table holding the language-independent frequency definition; joined via PERIOD_FREQUENCY_ID.
  • PSP_REPORT_PERIOD_FREQUENCY — the logical entity for which _B and _TL are the physical implementation.
  • PSP_REPORT_PERIOD_FREQUENCY_TL (self) — related through shared PERIOD_FREQUENCY_ID and language context when building multi-language views.
  • PSP reporting and Labor Distribution reporting engine objects that consume period frequency identifiers to schedule or label reports.

Because translations are always resolved through the foreign key to PSP_REPORT_PERIOD_FREQUENCY_B, any query or report requiring frequency labels should join these two tables on PERIOD_FREQUENCY_ID and constrain or order by LANGUAGE.