Search Results itg_synccoainbound_pvt




Overview
Explore in AI Chat

Overview

ITG_SYNCCOAINBOUND_PVT is a private PL/SQL package in the APPS schema that supports the synchronization of Chart of Accounts (COA) key flexfield values between Oracle EBS and an external or inbound data source. The package is part of the ITG (Integrated Technology Group) product family and is classified as a PVT API, meaning it is intended for internal use by other ITG packages and wrappers rather than for direct customer invocation. Its central responsibility is to keep the FND_FLEX_VALUES and related key flexfield definition tables aligned with inbound COA data, adding new flexfield values, updating existing ones, and reconciling the value set and segment attribute information that governs chart of accounts behavior. Because COA structures underpin nearly all financial transactions, accurate synchronisation is essential for journal entry validation, account combination generation, and reporting integrity.

Key Procedures and Functions

The package exposes three documented procedures:

  • ADD_FLEXVALUE — Creates a new flexfield value in the target value set. It typically applies the inbound COA definition to the underlying FND_FLEX_VALUES and translation tables and establishes the associated segment attribute values that determine how the value behaves in each key flexfield segment.
  • CHANGE_FLEXVALUE — Modifies an existing flexfield value, updating descriptive, translation, and attribute information for a value already present in the value set, while preserving referential integrity with existing account combinations.
  • SYNC_FLEXVALUE — Orchestrates the synchronization flow, evaluating inbound records against current flexfield definitions and routing each record to the appropriate add or change operation. This is the primary entry point for the inbound COA synchronization process.

All three procedures operate within the transaction context of the calling program and are not documented as autonomous; control over commit and rollback therefore rests with the invoker.

Tables Accessed

The package reads and writes the following key flexfield tables through APPS synonyms:

  • FND_FLEX_VALUES, FND_FLEX_VALUES_S, and FND_FLEX_VALUES_TL — store the base flexfield value definitions, their translated descriptions, and multilingual content.
  • FND_FLEX_VALUE_SETS — identifies the value set that owns each value and defines its validation characteristics.
  • FND_ID_FLEX_SEGMENTS — maps values to the key flexfield segments in which they are permitted.
  • FND_SEGMENT_ATTRIBUTE_TYPES and FND_SEGMENT_ATTRIBUTE_VALUES — hold the attribute type definitions and per-value attribute assignments that control posting, budgeting, and other segment-level behavior.
  • DUAL and PLITBLM — used for scalar evaluation and PL/SQL table lookups within the package body.

Usage Notes

ITG_SYNCCOAINBOUND_PVT is referenced by the package ITG_BOAPI_WRAPPERS, which acts as the public-facing layer for the ITG business object API. Customizations and integrations requiring inbound COA synchronization should therefore call ITG_BOAPI_WRAPPERS rather than this private package. The synchronization logic is typically invoked from concurrent programs, interface tables, or inbound web service calls that stage COA data for validation and merge into the key flexfield tables. It should also be noted that the package is tightly coupled to Oracle's key flexfield validation rules; any direct invocation must respect value set security, cross-validation rules, and segment qualifier configuration. The package does not appear to commit work, so callers must manage transaction boundaries explicitly. Testing of inbound COA loads should be performed in a non-production environment because changes to flexfield values affect all downstream account combinations.