Search Results submit_pay_instr_ts_report




Overview
Explore in AI Chat

Overview

The APPS.FV_FEDERAL_PAYMENT_FIELDS_PKG package is a PL/SQL server-side package in Oracle EBS that supplies Federal-specific payment attributes required by the Federal payment formats used in Oracle Payables and Payments. It is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner, which is consistent with the APPS-tier security model for shared, cross-schema utility packages. The package header identifies two logical tiers of functionality: payment instruction (header) level functions that accept a payment instruction ID and return Federal attributes, and payment level functions that accept a payment ID and return attributes needed at the individual payment line. This separation mirrors the structure of Federal payment files, where agency-level identifiers and summary control values are emitted once per payment instruction while payment-specific values are emitted per disbursement. The package is referenced by four other packages, indicating it functions as a shared utility layer rather than a standalone entry point.

Key Procedures and Functions

  • GET_FEIN — Returns the Federal Employee Identification Number from FV_OPERATING_UNITS, taken from the payment instruction context.
  • GET_ABBREVIATED_AGENCY_CODE — Returns the Abbreviated Agency Code, sourced from the profile option FV_AGENCY_ID_ABBREVIATION. This is the object most commonly searched by developers and administrators validating Federal agency identifiers on payment output.
  • GET_ALLOTMENT_CODE — Returns the Federal allotment code applicable to the payment instruction.
  • TOP_OFFSET_ELIGIBILITY_FLAG — Evaluates whether the payment qualifies for Treasury Offset Program (TOP) offsetting, based on configured exclusion criteria.
  • GET_PAY_INSTR_SEQ_NUM — Returns the payment instruction sequence number, used for control totals and sequencing in Federal formatted output.
  • SUMMARY_FORMAT_PROG_COMPLETED — Flags or updates completion state for the summary format program that consolidates payment data.
  • SUBMIT_PAY_INSTR_TS_REPORT — Submits the payment instruction Treasury Schedule report.
  • SUBMIT_CASH_POS_REPORT — Submits the cash position report used for Federal cash management reporting.
  • LOG_ERROR_MESSAGES — Records error messages generated during package processing, supporting diagnostics and audit.

Tables Accessed

The package reads and writes a documented set of tables through APPS synonyms. Payment and disbursement data come from IBY_PAY_INSTRUCTIONS_ALL, IBY_PAYMENTS_ALL, and IBY_DOCS_PAYABLE_ALL. Invoice and supplier detail derive from AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS, and AP_SUPPLIERS. Federal operating unit attributes, including the FEIN, come from FV_OPERATING_UNITS_ALL. Allotment and sequencing use FV_PB_SEQ_ASSIGNMENTS_ALL. Summary consolidation and Treasury Offset Program logic use FV_SUMMARY_CONSOLIDATE_ALL, FV_TOP_EXCLUSION_CRITERIA, and FV_TOP_EXCLUSION_CRITERIA_ALL. Ledger context is obtained from GL_LEDGERS, and PLITBLM is used for PL/SQL error message retrieval by LOG_ERROR_MESSAGES.

Usage Notes

This package is not typically called directly by end users. It is invoked by Federal payment format programs and by the four dependent packages that generate Federal disbursement files. Developers extending or debugging Federal payment output can call GET_ABBREVIATED_AGENCY_CODE and the other getter functions from custom PL/SQL to retrieve the same values the seeded formats use, ensuring consistency with profile-driven configuration such as FV_AGENCY_ID_ABBREVIATION. Concurrent program requests for the Treasury Schedule and cash position reports should be routed through SUBMIT_PAY_INSTR_TS_REPORT and SUBMIT_CASH_POS_REPORT rather than submitted independently, so that the package maintains control over parameters and sequencing. Because the package relies on profile option and operating unit setup, correct configuration of Federal agency identifiers and operating unit FEIN values is a prerequisite for accurate output. Behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, with the online patching model in 12.2.2 applying to the APPS edition rather than to the package logic itself.