Results for “pay_jp_effective_months_v”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_JP_EFFECTIVE_MONTHS_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product family. It is documented in ETRM as VALID and is restricted in scope to the Japanese localization, meaning it is not part of the global payroll data model and is not referenced by core, non-localized payroll flows. Its stated purpose is to supply a value set (lookup) that is attached to a parameter of the concurrent program definition "Geppen," which is the Japanese term commonly applied to monthly payroll processing runs. The view therefore serves a narrow but essential role: it constrains the list of allowable values presented to the user when a reporting or processing parameter must be expressed as an accounting or payroll period.
Architecturally the view behaves as a session-scoped calendar generator rather than a persistent data store. It returns a rolling thirteen-month window of dates derived at runtime from the effective date recorded for the user's current Oracle Forms or OAF session. Because the value list is computed per session, different users running the same concurrent request can legitimately see different sets of candidate months, since each session may carry its own effective date. This design keeps the view free of maintenance and independent of any period or calendar setup table.
Underlying Base Objects
The view is defined over a single referenced object: FND_SESSIONS, accessed through a synonym in the APPS schema. FND_SESSIONS is a standard Applications Technology foundation table that stores one row per active application session, including the SESSION_ID and the EFFECTIVE_DATE associated with that session. The view joins to this table implicitly through the SQL built-in USERENV('SESSIONID'), which supplies the SESSION_ID of the caller's own session and thereby restricts each of the view's constituent queries to a single row.
No payroll, period, or calendar table participates in the definition. All date arithmetic is performed with the standard ADD_MONTHS function, so the view has no dependency on PAY period definitions, GL calendars, or HR date-track configurations. The only environmental input is the session identifier, and the only data dependency is the effective date value held in FND_SESSIONS for that session.
Key Columns
The view exposes exactly one column, EFFECTIVE_DATE, which is documented in ETRM. Although the underlying base column and the projected column share the same name, they are semantically distinct: the base column in FND_SESSIONS stores the session's effective date, whereas the projection in the view carries thirteen derived values.
- The first branch returns the session effective date unmodified.
- Six branches return the effective date advanced by one through six months using ADD_MONTHS.
- Six branches return the effective date reduced by one through six months.
- The thirteen results are combined with UNION, which both concatenates the rows and eliminates duplicates; identical dates arising from different offsets are collapsed, so the row count can fall below thirteen in edge cases involving month-end normalization.
The column is untyped beyond the implicit DATE semantics of the source and the ADD_MONTHS return type. No label, description, or identifier column is provided, so consuming reports must format or label the value themselves.
Common Use Cases and Queries
The primary use case is the Geppen concurrent program parameter value set, where the user selects a pay month from the thirteen available choices. Beyond that, the view can be queried directly for diagnostics or lightweight date selection. A simple retrieval of all candidate months is:
SELECT EFFECTIVE_DATE FROM APPS.PAY_JP_EFFECTIVE_MONTHS_V ORDER BY EFFECTIVE_DATE;
Because the result is session-dependent, the following query is only meaningful when executed in the same session context as the target application session:
SELECT EFFECTIVE_DATE FROM APPS.PAY_JP_EFFECTIVE_MONTHS_V WHERE EFFECTIVE_DATE = TRUNC(SYSDATE, 'MM');
Typical scenarios include validating that a Japanese payroll run's period parameter falls within the permitted window, confirming the effective date recorded for a session, and reproducing the value list seen by a user when diagnosing a concurrent request submission. Note that results depend on FND_SESSIONS being populated for the invoking session; in a direct SQL*Plus connection without an initialized session, USERENV('SESSIONID') may not resolve to a valid FND_SESSIONS row and the view can return no rows.
-
This view is used in a lookup called from SRS definition "Geppen". This view is used for Japanese localization only.
APPS.PAY_JP_EFFECTIVE_MONTHS_V·↳ FND_SESSIONS·Explore PAY module →
-
This view is used in a lookup called from SRS definition "Geppen". This view is used for Japanese localization only.
APPS.PAY_JP_EFFECTIVE_MONTHS_V·↳ FND_SESSIONS·Explore PAY module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.