Search Results add_flexvalue

Overview

ITG_SYNCCOAINBOUND_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It provides the inbound synchronization logic used to reconcile Chart of Accounts (COA) key flexfield values between an external or legacy source system and the Oracle General Ledger key flexfield structures stored in the FND_FLEX tables. The package is associated with the "ARCS" (Accounts Receivable / financial consolidation style) customization and is identified by the header revision itgvscib.pls, version 120.3, dated 2006/09/15. The package is classified as a PVT (private) API, meaning it is intended for internal use by the owning product rather than as a public, externally supported interface.

The core business purpose is to validate and maintain flexfield value definitions, ensuring that inbound COA data respects the value set assignments and validation rules defined in the Oracle Flexfields setup. In particular, it guards against pushing flex values that violate the maximum size constraint imposed by the value set, a safeguard introduced to address Bug 5533589. Because the user search term is "sync_flexvalue," the most relevant documented routine is SYNC_FLEXVALUE, which encapsulates this synchronization behaviour.

Key Procedures and Functions

The package exposes three documented routines:

• ADD_FLEXVALUE — Creates a new flexfield value definition in the target value set. It is invoked when an inbound COA value does not already exist and must be inserted so that subsequent transactions can reference it.
• CHANGE_FLEXVALUE — Modifies an existing flexfield value, including attributes such as the enabled flag, to align the local definition with the inbound source.
• SYNC_FLEXVALUE — The principal synchronization entry point. It compares the inbound flex value against existing records and determines whether an add, change, or no-op is required, applying the value-set validation logic before committing the operation.

Supporting private logic inside the body includes the function get_flex_data, which queries FND_FLEX_VALUES for a given flex value and value set; vset_is_not_valid, which confirms that a value set is enabled and attached to the GL# key flexfield; and flex_value_is_not_valid, which enforces the maximum value size defined in the Flexfields Validation Sets setup form.

Tables Accessed

The package reads and writes the central Flexfields repository tables:

• FND_FLEX_VALUES, FND_FLEX_VALUES_S, and FND_FLEX_VALUES_TL — the base, translated, and secure views of flexfield values; used to look up existing values and to insert or update value definitions.
• FND_FLEX_VALUE_SETS — defines the value set and its validation characteristics, including maximum size, used by the validation functions.
• FND_ID_FLEX_SEGMENTS — maps value sets to the GL# key flexfield segments, ensuring only valid GL segments are synchronized.
• FND_SEGMENT_ATTRIBUTE_TYPES and FND_SEGMENT_ATTRIBUTE_VALUES — provide segment-level attribute configuration applied during validation.
• DUAL and PLITBLM — used for scalar selects and PL/SQL table handling respectively.

Usage Notes

ITG_SYNCCOAINBOUND_PVT is a private package and is not a supported public API. It is typically invoked from inbound COA integration programs, custom concurrent programs, or form-driven synchronization logic that imports external account structures into Oracle GL. It is referenced by at least one other package within the same customization. Because SYNC_FLEXVALUE writes directly to FND_FLEX_VALUES and its related tables, callers should ensure the inbound data has been validated and that appropriate concurrency controls are applied. The CLN_DEBUG_LEVEL profile option controls diagnostic logging, with a default level of 5.