Search Results get_le_id

Overview

APPS.FUN_TCA_PKG is a VALID PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resolves TCA (Trading Community Architecture) party and party-site information within the Oracle Financials intercompany flow. Its name and callers position it as the shared lookup layer that other Financials utilities use to translate a transaction context — operating unit, legal entity, party, or system reference — into the party identifiers and intercompany organization attributes those callers require.

The package is classified as OTHER and references only SYS.STANDARD in addition to its TCA tables, confirming it is a self-contained utility package rather than an implementation of a public API contract. Thirteen packages depend on it, most of them core intercompany components: FUN_AP_TRANSFER, FUN_AR_BATCH_TRANSFER, FUN_INITIATOR_WF_PKG, FUN_OPEN_INTERFACE_PKG, FUN_PARTY_MERGE_PUB, FUN_PERIOD_STATUS_PKG, FUN_RECIPIENT_WF, FUN_SECURITY, FUN_TRX_ENTRY_UTIL, FUN_TRX_PUB, FUN_TRX_PVT, FUN_WEBADI_PKG, and JA_CN_CFS_DATA_CLT_PKG. Any change to its behavior can therefore propagate through the entire intercompany transaction lifecycle.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions. Their documented purposes are as follows:

• IS_PARTY_EXIST — Determines whether a party record exists for a given context, allowing callers to validate party presence before processing intercompany transactions.
• FIND_PARTY — Retrieves or resolves the party associated with a supplied identifier or transaction context.
• IS_INTERCOMPANY_ORG — Tests whether an organization qualifies as an intercompany organization.
• IS_INTERCOMPANY_ORG_VALID — Validates that an intercompany organization is valid for the transaction being processed.
• GET_IC_ORG_VALID_DATES — Returns the effective (valid-from / valid-to) dates governing an intercompany organization relationship.
• GET_LE_ID — Resolves the legal entity identifier for the supplied context.
• GET_OU_ID — Resolves the operating unit identifier for the supplied context.
• GET_SYSTEM_REFERENCE — Returns the system reference value associated with the party or organization being queried.
• CF_TRANSACTING_ENTITY_FLAG — Returns or evaluates the transacting-entity flag, used to distinguish the entity acting in a transaction from other related entities.

Together these members form a consistent access pattern: validate the party, resolve the legal entity and operating unit, confirm intercompany status and validity dates, then read the transacting-entity and system-reference attributes.

Tables Accessed

The package accesses three tables through APPS synonyms:

• HZ_PARTIES — The central TCA party registry; used by FIND_PARTY and IS_PARTY_EXIST to locate and confirm party records.
• HZ_PARTY_USG_ASSIGNMENTS — Party usage assignments; used to determine how a party is classified and whether it qualifies for intercompany processing.
• HZ_RELATIONSHIPS — Party relationships; used to resolve associations between parties, legal entities, and organizations needed by the intercompany validity and identifier functions.

Usage Notes

FUN_TCA_PKG is an internal utility, not a documented public API. It is invoked indirectly whenever intercompany transactions are transferred, validated, or processed — for example during AP and AR intercompany batch transfers, intercompany open-interface loads, period-status checks, transaction entry, and workflow-driven intercompany routing. It is typically executed from PL/SQL code within the FUN product family rather than from a form or concurrent program directly, and is not intended for direct customer extension.

Custom code should treat the package as a read-only dependency and avoid calling it where a supported TCA public API exists. Because thirteen dependent packages rely on its behavior, any modification or wrapping carries broad upgrade and regression risk; the package should be reviewed during patching and release testing whenever intercompany or TCA functionality is affected.