Search Results igi_itr_charge_setup




Overview
Explore in AI Chat

Overview

The IGI.IGI_ITR_CHARGE_SETUP table is a configuration table within the Oracle E-Business Suite module IGI – Public Sector Financials International. Its documented purpose is to maintain Internal Trading System (ITR) options that define how charges are used by a given user or operating context. In practice, it functions as a setup and control table rather than a transactional table: rows represent the specific options an implementation has enabled for internal trading charge processing, including encumbrance handling, approver determination, and workflow behavior. Because it drives configuration rather than recording daily financial events, it is consulted at runtime by internal trading processes rather than being posted to directly. The table is owned by the IGI schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone, which suggests it is best treated as a hub or a configuration satellite rather than a link table. It has no reverse dependencies documented and only one outbound foreign key, so it does not participate in a complex relationship web. The single FK to GL_ENCUMBRANCE_TYPES reflects the fact that encumbrance setup is an external reference rather than an internal hierarchical dependency.

Key Information Stored

The table contains 15 documented columns in the ETRM 12.2.2 physical schema. The most significant are described below.

  • SET_OF_BOOKS_ID — Identifies the set of books (ledger) to which the internal trading charge setup applies. This is the principal business-context discriminator.
  • USE_ENCUMBRANCE_FLAG — Controls whether encumbrance accounting is enabled for internal trading charges.
  • ENCUMBRANCE_TYPE_ID — Foreign key to GL_ENCUMBRANCE_TYPES; names the specific encumbrance type used when encumbrances are enabled.
  • ORIGINATOR_APPROVE_FLAG — Determines whether the originator of an internal trading transaction may also act as approver.
  • SEGMENT_NAME and SEGMENT_PROMPT — Define the accounting segment used for charge allocation and the prompt shown to users when entering charges.
  • FIND_APPROVER_METHOD — Specifies the method or hierarchy used to locate the approver for a charge.
  • USE_WORKFLOW_FLAG — Indicates whether Oracle Workflow approval routing is applied to internal trading charges.
  • AUTO_APPROVE_EXCEED_DAYS — Sets a time threshold after which charges are automatically approved if no action is taken.
  • USE_DOUBLE_TIMEOUT_FLAG — Controls whether a second-timeout approval escalation is applied.
  • Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard WHO columns that record who created and last modified each setup row, supporting audit and concurrency control.

No surrogate single-column primary key is documented as such; SET_OF_BOOKS_ID serves as the practical business-key candidate, since setup options are keyed by ledger context. Where a unique index exists, it is likely to include SET_OF_BOOKS_ID alone or in combination with another configuration discriminator.

Common Use Cases and Queries

Administrators and developers query this table to verify internal trading charge configuration, to drive conditional logic in charge-processing code, and to report on approval and encumbrance policies across ledgers. A typical lookup returns the active options for a ledger:

SELECT set_of_books_id,
       use_encumbrance_flag,
       encumbrance_type_id,
       originator_approve_flag,
       find_approver_method,
       use_workflow_flag,
       auto_approve_exceed_days,
       use_double_timeout_flag
FROM   igi.igi_itr_charge_setup
WHERE  set_of_books_id = :p_set_of_books_id;

Other practical reporting scenarios include identifying ledgers that have encumbrance accounting disabled for internal trading, auditing which ledgers use workflow-based approval versus automatic approval, and confirming the configured approval escalation thresholds before period-close activities. Integration and extension developers reference the flags here when building custom internal trading charge validation logic.

Related Objects

The documented foreign-key relationship points to the following reference table, which is the primary join target:

  • GL_ENCUMBRANCE_TYPES — joined via IGI_ITR_CHARGE_SETUP.ENCUMBRANCE_TYPE_ID = GL_ENCUMBRANCE_TYPES.ENCUMBRANCE_TYPE_ID, providing the encumbrance type name and description.

Because the Data Vault classification is standalone with no reverse dependencies in the metadata, other significant related objects are best identified from the broader internal trading subsystem rather than from hard FK constraints. These typically include the internal trading charge definition and transaction tables within the IGI schema (for example, objects that store ITR charge lines and approver assignments), Oracle Workflow routing tables used when USE_WORKFLOW_FLAG is enabled, and the GL ledger and accounting setup tables that supply SET_OF_BOOKS_ID context. When building queries, the reliable join is to GL_ENCUMBRANCE_TYPES; other relationships should be confirmed against the live schema, as they are not documented as physical foreign keys here.