Results for “igi_mpp_setup”

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

Overview

The IGI_MPP_SETUP view is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite. It belongs to the IGI — Public Sector Financials International product family, a module that extends standard Oracle Financials functionality for public sector organizations. As its documented description states, the view "Contains setup information for Multi Period Posting." Multi Period Posting (MPP) is an IGI feature that allows transactions to be distributed across multiple accounting periods and ledgers according to defined rules, which is particularly relevant to government and public sector accounting where encumbrance, budgetary, and multi-period allocations are common requirements.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as the operational access point for Multi Period Posting setup data. Rather than exposing an underlying table directly, the view applies a secure organization-level filter, making it suitable for both reporting and integration use while respecting the multi-org access model. Because it exposes configuration such as the default accounting rule, journal category, and journal source, it is a foundational reference for any process that creates or validates Multi Period Posting journal entries.

Underlying Base Objects

The view is defined over a single documented base object: the synonym IGI_MPP_SETUP_ALL. The _ALL table stores Multi Period Posting setup rows for all organizations, keyed in part by ORG_ID. The IGI_MPP_SETUP view restricts these rows using the standard multi-org security predicate against the USERENV('CLIENT_INFO') session value:

• The view selects from IGI_MPP_SETUP_ALL and filters on ORG_ID.
• The filter compares NVL(ORG_ID, ...) against the operating unit derived from the session's CLIENT_INFO, defaulting unmatched cases to -99.
• Rows with a null ORG_ID (shared/global setup) are matched through the same NVL logic.

This design means the view returns only the setup rows visible to the current organization context, which is essential in a multi-org enabled environment.

Key Columns

• SET_OF_BOOKS_ID — Identifies the ledger (set of books) to which the Multi Period Posting setup applies.
• FUTURE_POSTING_CCID — The code combination ID of the account used for future-period posting entries.
• DEFAULT_ACCOUNTING_RULE_ID — Reference to the default accounting rule governing how amounts are spread across periods.
• JE_CATEGORY_NAME — The journal category assigned to MPP-generated journals.
• JE_SOURCE_NAME — The journal source used when MPP entries are created.
• ORG_ID — The operating unit that owns the setup row; drives the multi-org filter.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle who-columns providing audit lineage for the setup record.

Common Use Cases and Queries

Typical scenarios include verifying MPP configuration for a ledger, auditing which accounting rule and journal source are in effect, and joining setup data to accounting rule or code combination tables. A representative query follows:

• List all MPP setups for the current organization, ordered by ledger:
  SELECT set_of_books_id, default_accounting_rule_id, je_source_name, je_category_name FROM igi_mpp_setup;
• Join to the accounting rules to resolve the default rule name:
  SELECT m.set_of_books_id, r.name FROM igi_mpp_setup m, gl_accounting_rules r WHERE m.default_accounting_rule_id = r.accounting_rule_id;
• Confirm the future posting account combination via FUTURE_POSTING_CCID against GL_CODE_COMBINATIONS.

Because the view enforces organization security, it is safe to use in concurrent programs and integrations without additional ORG_ID predicates, provided the correct operating unit context is initialized.