Search Results fun_period_statuses




Overview
Explore in AI Chat

Overview

FUN_PERIOD_STATUSES is a table owned by the FUN (Financials Common Modules) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Intercompany period statuses whenever an Intercompany calendar has been defined in system options. Unlike the General Ledger period statuses that apply across an entire ledger, the Intercompany period statuses in this table are maintained at the Intercompany Transaction Type level. This means that periods can be opened and closed independently for each Intercompany transaction type, giving organizations granular control over when intercompany transactions may be entered, processed, or posted for each specific flow between legal entities.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies FUN_PERIOD_STATUSES as a standalone object. It does not function as a classic hub, link, or satellite in a normalized integration model; instead it behaves as a reference or configuration table whose business key is captured by the unique index FUN_PERIOD_STATUSES_U1 across INTECO_CALENDAR, INTECO_PERIOD_TYPE, PERIOD_NAME, and TRX_TYPE_ID.

Key Information Stored

The table contains 37 documented columns in the 12.2.2 physical schema. The most significant columns fall into three groups:

  • Period identity: PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, START_DATE, END_DATE, YEAR_START_DATE, and QUARTER_START_DATE define the intercompany accounting period and its calendar boundaries.
  • Status control: STATUS holds the open, closed, or permanently closed indicator for the period at the transaction type level. INTECO_CALENDAR and INTECO_PERIOD_TYPE identify which Intercompany calendar and period type the record belongs to.
  • Transaction type scope: TRX_TYPE_ID links the period status to a specific Intercompany Transaction Type, referencing IGI_EXP_TRX_TYPE.TRX_TYPE_ID. This is the column that differentiates this table from standard GL period statuses.
  • Audit and descriptive flexfield columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CONTEXT, and ATTRIBUTE1 through ATTRIBUTE20 support standard EBS auditing and descriptive flexfield extensibility.

The surrogate primary key is not uniquely identified by a single column in the documented metadata; the business key candidate is the composite unique index FUN_PERIOD_STATUSES_U1 (INTECO_CALENDAR, INTECO_PERIOD_TYPE, PERIOD_NAME, TRX_TYPE_ID).

Common Use Cases and Queries

Typical use cases include reporting on which intercompany periods are open for a given transaction type, validating whether intercompany entries can be posted, and troubleshooting period-close or intercompany balancing errors. A representative query joining to the transaction type table is:

SELECT p.period_name, p.status, p.start_date, p.end_date, t.trx_type_name FROM fun_period_statuses p, igi_exp_trx_type t WHERE p.trx_type_id = t.trx_type_id AND p.inteco_calendar = :calendar AND p.status = 'O';

Reporting scenarios frequently filter by INTECO_PERIOD_TYPE to isolate a specific period frequency (for example, monthly versus quarterly) and by PERIOD_YEAR for annual trend analysis. Reconciliation reports compare FUN_PERIOD_STATUSES against GL period statuses to detect mismatches that block intercompany processing.

Related Objects

  • IGI_EXP_TRX_TYPE — referenced by FUN_PERIOD_STATUSES.TRX_TYPE_ID; the primary parent in the FK relationship and the source of transaction type names.
  • GL_PERIOD_STATUSES — provides the ledger-level period status for comparison and reconciliation of intercompany versus GL open periods.
  • FUN_SYSTEM_OPTIONS — defines whether an Intercompany calendar is enabled, which determines whether FUN_PERIOD_STATUSES is populated.
  • IGI_INTERCOMPANY_ACCOUNTS and IGI_TRANSACTIONS — rely on valid, open intercompany period statuses when intercompany transactions are created and posted.
  • FND_CALENDARS or the FUN intercompany calendar definition objects — supply the INTECO_CALENDAR and INTECO_PERIOD_TYPE values referenced here.