Search Results validate_source_system




Overview
Explore in AI Chat

Overview

APPS.FTP_PAYMENT_SCHEDULE_PKG is a PL/SQL package that belongs to the Funds Transfer Pricing (FTP) module of Oracle E-Business Suite. Its documented role is to manage the staging and validation lifecycle of payment schedule data used by the FTP engine. The FTP module computes internal cost-of-funds and transfer pricing for financial instruments; payment schedules describe the timing and amount of expected cash flows that feed those computations. This package supports that flow by transferring source data into the staging table FTP_PAYMENT_SCHEDULE, validating reference values against the source system and instrument type definitions, and removing staged data when it is no longer required.

The package carries the standard APPS schema ownership and is classified under the ETRM documentation as OTHER, meaning it is not a published public API but an internal utility used by the FTP data-loading process. The header indicates it has been in place since well before Release 12 (script revision 120.4, dated 2006) and remains valid in both 12.1.1 and 12.2.2.

Key Procedures and Functions

  • TransferData — Performs the main data movement operation for payment schedules. It accepts an input flag controlling truncation (isTruncate) and returns the standard concurrent-program style errbuf and retcode OUT parameters, indicating that it is designed to be invoked from a concurrent program or a PL/SQL caller that expects the EBS concurrent manager calling convention. Its purpose is to load staging rows into FTP_PAYMENT_SCHEDULE, optionally clearing existing data first.
  • DeleteData — Removes staged payment schedule records without executing a transfer. This is typically used for cleanup or to reset the staging area before a fresh load.
  • Validate_Source_System — Validates a supplied source system code and returns a resolved numeric source_system_code along with a return status. This is the procedure most commonly associated with the search term "validate_source_system." It ensures that the source system reference used by the incoming payment schedule data exists and is valid before the data is processed.
  • Validate_Inst_Type_Code — Validates an instrument type code supplied as a numeric value and returns a status indicator. This check confirms that the instrument type associated with the payment schedule is a recognized value before the record is accepted.

Tables Accessed

  • FEM_SOURCE_SYSTEMS_B — The base table holding source system definitions; read by Validate_Source_System to confirm the supplied source system code is valid.
  • FTP_PAYMENT_SCHEDULE — The principal staging/target table for payment schedule data, populated by TransferData and cleared by DeleteData.
  • FTP_PAYMENT_SCHEDULE_T — Likely the translation table associated with the payment schedule entity, used to resolve descriptive or language-dependent values during validation and loading.
  • FND_LOG_MESSAGES — The standard EBS logging table, written to record diagnostic and error messages generated during transfer and validation execution.
  • PLITBLM — The generic EBS PL/SQL table-of-strings utility table, typically used for bulk message handling or temporary storage of row identifiers during processing.

Usage Notes

The package is not documented as being referenced by any other package, which suggests it sits at the top of its own call chain and is invoked directly rather than being consumed as a sub-API. In practice, TransferData, with its errbuf/retcode signature, is almost certainly registered as a concurrent program so that payment schedule data can be loaded on demand or on a schedule through the standard EBS concurrent manager. DeleteData and the two Validate procedures are more likely to be called from custom code or from a pre-processing step within the same concurrent request, allowing a caller to check source system and instrument type codes and to clean staging data before a transfer run.

For 12.1.1 and 12.2.2, the package behaves identically; there is no evidence of form-level invocation, and the procedures should be treated as internal FTP utilities. Customizations should not modify the package but should wrap or replicate its validation logic where independent validation is required, since the procedures are proprietary and subject to change without notice.