Results for “use_gl_calendar”

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

Overview

PN_VAR_RENT_DATES_ALL is a Property Manager (PN) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the GL calendar assignment and date-frequency configuration that governs how variable rent agreements are reported, invoiced, audited, and reconciled. In practical terms, the table answers operational questions such as which accounting calendar applies to a variable rent arrangement, how often reporting and invoicing cycles recur, and which day-of-month or offset conventions drive those cycles.

The entity is owned by the PN schema and is documented as VALID, containing 46 columns. It carries the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus 15 descriptive ATTRIBUTE flex columns and an ORG_ID for multi-org partitioning. The documented primary key is PN_VAR_RENT_DATES_PK, defined on VAR_RENT_DATE_ID.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. The table's grain is one row per variable rent date configuration, and its foreign key points upward to a parent agreement record, which is characteristic of a satellite attached to a business key hub/link rather than of an independent hub. This classification is a modeling suggestion derived from the FK structure, not a physical implementation.

Key Information Stored

The most significant columns fall into three groups: identity, calendar context, and frequency configuration.

• VAR_RENT_DATE_ID — surrogate primary key (PN_VAR_RENT_DATES_PK). Unique index PN_VAR_RENT_DATES_U1 also covers this column.
• VAR_RENT_ID — foreign key to PN_VAR_RENTS_ALL; identifies the variable rent agreement this date configuration belongs to. Unique index PN_VAR_RENT_DATES_U2 documents it as a business-key candidate, implying a one-to-one or tightly constrained relationship between agreement and date setup.
• GL_PERIOD_SET_NAME and USE_GL_CALENDAR — the General Ledger period set and a flag determining whether GL calendar periods drive the schedule.
• PERIOD_TYPE, YEAR_START_DATE, and EFFECTIVE_DATE — period granularity, fiscal year anchor, and the date from which the configuration is effective.
• PERIOD_FREQ_CODE and REPTG_FREQ_CODE, REPTG_DAY_OF_MONTH, REPTG_DAYS_AFTER, VRG_REPTG_FREQ_CODE — reporting cycle frequency and the day/offset rules that determine when reporting obligations fall.
• INVG_FREQ_CODE, INVG_DAY_OF_MONTH, INVG_DAYS_AFTER, INVG_SPREAD_CODE, INVG_TERM — invoicing frequency, day/offset, spread method, and term length.
• AUDIT_FREQ_CODE, AUDIT_DAY_OF_MONTH, AUDIT_DAYS_AFTER — audit cycle configuration.
• RECON_FREQ_CODE, RECON_DAY_OF_MONTH, RECON_DAYS_AFTER — reconciliation cycle configuration.
• ORG_ID — operating unit identifier supporting multi-org access control.
• COMMENTS and ATTRIBUTE_CATEGORY/ATTRIBUTE1–15 — free-text notes and descriptive flexfield storage.

The repeated FR EQ_CODE / DAY_OF_MONTH / DAYS_AFTER triad across reporting, invoicing, audit, and reconciliation shows that the table is a consolidated scheduling record rather than a single-purpose configuration row.

Common Use Cases and Queries

Typical usage centers on schedule validation and exception reporting. A frequent query retrieves the complete frequency setup for a given agreement:

• Join PN_VAR_RENT_DATES_ALL to PN_VAR_RENTS_ALL on VAR_RENT_ID to return agreement identifiers alongside calendar and frequency columns.
• Filter by ORG_ID and EFFECTIVE_DATE to audit which configurations are active for an operating unit at a point in time.
• Detect anomalies where INVG_DAY_OF_MONTH exceeds 28, which can misalign invoicing in short months.
• Reconcile USE_GL_CALENDAR against GL_PERIOD_SET_NAME to confirm that agreements expected to follow the GL calendar are correctly flagged.
• Report on configurations missing a reconciliation or audit frequency, indicating incomplete setup.

Reporting extracts commonly project VAR_RENT_ID, GL_PERIOD_SET_NAME, all four frequency codes, and EFFECTIVE_DATE. Integrations and interfaces referencing this table should always filter on ORG_ID to respect multi-org security, and should account for the ATTRIBUTE flex columns when downstream systems consume descriptive flexfield data.

Related Objects

• PN_VAR_RENTS_ALL — parent table; joined via PN_VAR_RENT_DATES_ALL.VAR_RENT_ID = PN_VAR_RENTS_ALL.VAR_RENT_ID. This is the dominant relationship and the basis for the satellite classification.
• PN_VAR_RENT_DATES_PK — primary key constraint on VAR_RENT_DATE_ID.
• PN_VAR_RENT_DATES_U1 — unique index on VAR_RENT_DATE_ID.
• PN_VAR_RENT_DATES_U2 — unique index on VAR_RENT_ID, enforcing the one-to-one business constraint.
• GL period and calendar objects — GL_PERIOD_SET_NAME resolves against GL period set definitions (for example FND calendars and GL_PERIOD_SETS), which provide the period names referenced by USE_GL_CALENDAR.
• Multi-org entities — ORG_ID resolves to the operating unit definition in HR_ALL_ORGANIZATION_UNITS and its associated MO operating unit views.
• Property Manager variable rent APIs — the PL/SQL packages that maintain PN_VAR_RENTS_ALL and its date configuration rows, which perform the inserts and updates against this table.

Because the table sits downstream of the variable rent agreement and upstream of scheduling logic, changes to it propagate directly into reporting, invoicing, audit, and reconciliation behavior. Treat it as reference-grade configuration data when designing extracts, and preserve its effective-dating semantics in any historical reporting model.