Search Results ftp_tp_pkg




Overview
Explore in AI Chat

Overview

FTP_TP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It belongs to the Oracle Financial Services Transfer Pricing (FTP) subsystem, a component of the Enterprise Performance Foundation / Financial Services data model that supports rule-based transfer pricing, profitability analysis, and management ledger processing. The package is classified as OTHER in the ETRM repository, meaning Oracle does not publish it as a supported public API; it is an internal utility package invoked by the transfer pricing engine rather than by external callers.

The package concentrates two related responsibilities: metadata introspection over the FEM (Financial Services Data Model) object catalog, and control of transfer pricing process execution. The name itself — TP for transfer pricing — confirms its functional scope. It validates node mappings, resolves column and value set metadata, registers and locks process runs, and identifies chaining relationships between pricing steps. Oracle reports zero packages referencing FTP_TP_PKG, and its only declared dependency is on SYS.STANDARD, indicating that it relies on dynamic SQL and FEM metadata rather than on hard-coded compile-time references to other PL/SQL units.

Key Procedures and Functions

  • VALIDATE_NODE_MAP — Confirms that a node mapping defined for a transfer pricing process step is structurally valid against FEM metadata before execution.
  • GET_TP_OUT_COLS — Returns the output column definitions produced by a transfer pricing process, used when building runtime result sets.
  • REGISTER_TP_PROCESS — Registers a transfer pricing process instance, establishing the run record consumed by downstream processing and locking logic.
  • ACCT_TYPE_JOIN_INFO — Supplies join information for account types, allowing the engine to correlate extended account type definitions with transaction data.
  • CHG_CRDT_ACC_BASIS_JOIN — Provides join metadata for the charge/credit accounting basis, used when assembling adjustment and basis lookups.
  • GET_VALUESETS_INFO — Retrieves value set definitions associated with transfer pricing parameters, supporting validation of user-supplied values.
  • START_PROCESS_LOCKS — Acquires the locks required before a transfer pricing process may begin, preventing concurrent conflicting runs.
  • STOP_PROCESS_LOCKS — Releases those locks on completion or failure, restoring the process to an available state.
  • LEDGER_PROCESSING — Drives ledger-level processing for the transfer pricing run, the principal execution entry point within the package.
  • CHAINING_EXISTS — Determines whether a chaining relationship exists between process steps, governing sequencing across FEM_PL_CHAINS definitions.
  • GET_VALID_TABLE_LIST — Returns the list of tables eligible for a given transfer pricing operation.
  • VERIFY_VALID_COLUMN — Confirms that a column referenced by a process definition exists and is permitted for use.

Tables Accessed

All table access occurs through APPS synonyms. The dominant group is the FEM metadata catalog: FEM_DIMENSIONS_B, FEM_DIM_ATTRIBUTES_B, and FEM_XDIM_DIMENSIONS hold dimension definitions; FEM_OBJECT_CATALOG_B, FEM_OBJECT_DEFINITION_B, and FEM_OBJECT_DEPENDENCIES describe registered objects and their interrelationships; FEM_DS_INPUT_LISTS and FEM_DS_INPUT_OUTPUT_DEFS define data source inputs and outputs; FEM_TABLE_CLASS_ASSIGNMT maps tables to classification groups; FEM_GLOBAL_VS_COMBO_DEFS stores global value set combinations; FEM_LN_ITEMS_HIER supports line item hierarchies. Account type handling draws on FEM_EXT_ACCOUNT_TYPES_B and FEM_EXT_ACCT_TYPES_ATTR. FEM_PL_CHAINS provides the process chaining definitions tested by CHAINING_EXISTS. Finally, FTP_ADJUSTMENT_RULE stores user-defined adjustment rules that the engine evaluates during ledger processing.

Usage Notes

FTP_TP_PKG is invoked internally by the transfer pricing engine during process execution, typically triggered from the Transfer Pricing setup and run pages in the Financial Services application or from the associated concurrent program that initiates ledger processing. Because the package manages process locks, it should not be called concurrently against the same process definition without allowing START_PROCESS_LOCKS and STOP_PROCESS_LOCKS to complete in pairs. Custom code should treat the package as unsupported: Oracle lists no public API classification, no external referencing packages, and no published parameter documentation. Any direct invocation is at the customer's own risk and must be re-verified after patching, since the FEM metadata structures it depends on are subject to change across 12.1.1 and 12.2.2 maintenance levels.