Results for “psp_report_period_frequency_b”

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

Overview

The PSP_REPORT_PERIOD_FREQUENCY_B table resides in the PSP schema and belongs to the Oracle EBS Labor Distribution module. It stores the base-table definitions of period frequencies — either seeded by Oracle or defined by the user — that drive the time-based logic of effort report templates. Each row defines a discrete frequency such as weekly, monthly, or quarterly, together with the duration and unit of measure needed to compute the reporting interval. Effort reporting depends on these frequency definitions to determine the span of each reporting period and to align effort certification with the correct cycle.

In Data Vault modeling terms, the mined foreign-key structure suggests a hub-leaning classification. The table serves as a stable reference point identified by a single surrogate key, with descriptive and language-specific attributes distributed elsewhere. This classification is a modeling suggestion drawn from the relationship structure rather than a mandated design.

Key Information Stored

The table is defined with twelve documented columns. The most significant are summarized below.

• PERIOD_FREQUENCY_ID — The surrogate primary key, enforced by PSP_REPORT_PERIOD_FREQ_B_PK. It uniquely identifies each frequency definition and is the column referenced by all dependent objects.
• PERIOD_DURATION — The numeric length of the frequency interval, interpreted together with the unit of measure.
• UNIT_OF_MEASURE — The unit in which the duration is expressed, such as days, weeks, or months.
• START_DATE — The effective start date governing when the frequency definition becomes active.
• REPORT_TYPE — Classifies the report context in which the frequency is applied.
• ZD_EDITION_NAME — The editioning column used in the E-Business Suite edition-based redefinition model.
• OBJECT_VERSION_NUMBER — Supports optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns recording who created and last modified each row and when.

The unique index PSP_REPORT_PERIOD_FREQ_B_U1 spans (PERIOD_FREQUENCY_ID, ZD_EDITION_NAME), reflecting the editioning-aware business-key candidate. The language-specific business columns are held in the companion translation table rather than here.

Common Use Cases and Queries

Typical usage centers on resolving the frequency assigned to a report template and translating it into an interval for period generation. A common reporting pattern joins the base table to its translation table and to the template records that consume it.

• Listing available frequencies with their translated names:

SELECT b.period_frequency_id, t.name, b.period_duration, b.unit_of_measure
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');

• Identifying the frequency applied to each effort report template:

SELECT r.template_id, r.period_frequency_id, b.period_duration, b.unit_of_measure
FROM   psp_report_templates r,
       psp_report_period_frequency_b b
WHERE  r.period_frequency_id = b.period_frequency_id;

• Auditing user-defined frequencies by creation and update metadata for governance reviews.
• Validating that active frequency definitions carry a populated start date and duration before period generation runs.

Related Objects

The following objects are the most significant references or dependents of this table, based on the documented key relationships.

• PSP_REPORT_PERIOD_FREQUENCY_TL — The translation table. Join on PSP_REPORT_PERIOD_FREQUENCY_TL.PERIOD_FREQUENCY_ID = PSP_REPORT_PERIOD_FREQUENCY_B.PERIOD_FREQUENCY_ID to retrieve language-specific names and descriptions.
• PSP_REPORT_TEMPLATES — Stores the current effort report templates. Join on PSP_REPORT_TEMPLATES.PERIOD_FREQUENCY_ID = PSP_REPORT_PERIOD_FREQUENCY_B.PERIOD_FREQUENCY_ID to determine the frequency each template uses.
• PSP_REPORT_TEMPLATES_H — The history table for report templates. The same PERIOD_FREQUENCY_ID join preserves frequency context across template version history.

These relationships establish the table as a reference hub consumed by both transactional template records and their historical counterparts, with descriptive text supplied by the translation table.