Search Results ap_invoices_interface_s




Overview
Explore in AI Chat

Overview

JAI_FBT_SETTLEMENT_P is an APPS-owned PL/SQL package body classified as OTHER within the Oracle E-Business Suite environment. Its name and dependency footprint associate it with the Fiscalized Billing Tax (FBT) Settlement feature delivered by Oracle's Financials for India (JAI) product family. In EBS 12.1.1 and 12.2.2, the localization modules prefixed JAI provide statutory compliance functionality for Indian tax regimes, including excise, VAT/CST, service tax, and the fiscalized settlement of vendor and customer transactions.

The package serves as the procedural engine that consumes staged invoice data, evaluates it against the FBT repository of rates and rules, and produces settlement records. It functions as an integration layer: it reads data written into the open interface tables by external sources, resolves accounting and currency context from standard EBS reference tables, and writes the resulting settlement lines into the FBT settlement tables. The package body carries a VALID status in the data dictionary, confirming that it compiled successfully against all referenced objects in the reported environment.

Key Procedures and Functions

The documented metadata exposes a single public program unit within this package body:

  • FBT_SETTLEMENT — The primary driver routine of the package. Its name and its dependencies indicate that it performs the end-to-end settlement calculation, reading staged invoice and invoice line data, applying repository definitions, and populating the FBT settlement and settlement serials tables. Because it is the sole documented program unit, it is the entry point through which all other internal (undocumented, private) logic is orchestrated and invoked.

The package body additionally references itself (JAI_FBT_SETTLEMENT_P) in the dependency listings, indicating private helper routines and nested calls within the body. No parameter lists are documented in the available metadata, and none are asserted here.

Tables Accessed

Usage Notes

The package is typically invoked from concurrent programs or India-localization processes that generate FBT settlement output, most often after invoice data has been loaded into the AP interface tables by external or upstream systems. It is not referenced by any other database object, so invocation occurs through direct calls from application logic, concurrent program definitions, or custom client code rather than through inter-package chaining. Callers must ensure that the FND_GLOBAL and FND_PROFILE session context (operating unit, ledger, user) is initialized before execution, since the package relies on these to resolve localization and reporting attributes. Standard FND_FILE and FND_LOG dependencies confirm that it writes log and output files suitable for concurrent manager review, making diagnostics available through the standard request log.