Search Results insert_gl_entry




Overview
Explore in AI Chat

Overview

JAI_PA_BILLING_PKG is an Oracle EBS packaged PL/SQL unit owned by APPS that supports the Oracle Projects billing flow for Indian localizations (the JAI prefix denotes the India localization module set). It was originally created for Projects Billing implementation and forward-ported to Release 12 from Release 11i, as recorded in the header change history (Bug#6012570). The package addresses the intersection of Project Draft Invoice processing and Indian tax legislation — specifically excise duty and VAT — by generating the corresponding accounting entries and by mapping draft invoice tax lines into Oracle Payables and Oracle General Ledger. In this sense the package acts as a bridge between Oracle Projects (PA) billing data and the India tax and subledger accounting structures.

The user query referencing "gipsa package bill format for hospital" appears to be a search for a billing format specific to a hospital or a "GIPSA" context; no such format is defined in the documented metadata. The package does not render bill formats or layouts. Its actual scope is tax computation and accounting integration for project draft invoices. Any expectation of a printed or formatted hospital bill should be directed to the Projects billing report or XML Publisher template layer, not to this package.

Key Procedures and Functions

The package exposes eight documented program units:

  • GET_SPEC_VERSION — returns the package specification version string (declared constant gv_package_spec_version = '120.0').
  • GET_BODY_VERSION — returns the package body version, allowing callers to verify the deployed code level.
  • PROCESS_DRAFT_INVOICE_RELEASE — the principal entry point, handling the release of a project draft invoice and driving the downstream tax and accounting processing.
  • PROCESS_EXCISE — computes and posts excise duty amounts associated with the draft invoice transactions, using the RG 23AC-II register structures.
  • PROCESS_VAT — computes and posts VAT amounts for the same invoice context.
  • CHECK_EXCISE_BALANCE — validates the available excise balance, typically before excise is applied or reversed.
  • INSERT_GL_ENTRY — inserts journal line records into the GL interface structures using the package's gl_entry record type (debit/credit amount, debit/credit code combination, regime code, tax type, JE source and category, set of books, currency).
  • IMPORT_TAXES_TO_PAYABLES — transfers calculated tax lines from the Projects draft invoice into Oracle Payables invoice distributions and payment schedules.

Tables Accessed

The package reads and writes Project, Payables, and General Ledger data through APPS synonyms. Project billing data is held in PA_DRAFT_INVOICES_ALL, with the India localization staging table JAI_PA_DRAFT_INVOICES (referenced by the constant gv_draft_invoice_table) recording the draft invoice transactions to be processed. Payables integration touches AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_PAYMENT_SCHEDULES_ALL. General Ledger interaction uses GL_INTERFACE (journal import), GL_JE_HEADERS, GL_CURRENCIES, and GL_SETS_OF_BOOKS. India tax setup and transactional data are drawn from JAI_RGM_DEFINITIONS (regime codes and IDs), JAI_CMN_DOCUMENT_TAXES, JAI_CMN_JOURNAL_ENTRIES, JAI_CMN_JOURNAL_ENTRIES_S, JAI_CMN_RG_23AC_II_TRXS, JAI_CMN_FIN_YEARS, and JAI_CMN_INVENTORY_ORGS. FND_CURRENCIES supplies currency definitions.

Usage Notes

JAI_PA_BILLING_PKG is classified as OTHER and is invoked programmatically rather than through a dedicated concurrent program or form. It is referenced by five other packages, indicating that it is called from the Projects billing integration layer when a draft invoice is released and when taxes must be posted to Payables or General Ledger. Typical invocation occurs during release of project draft invoices, at which point PROCESS_DRAFT_INVOICE_RELEASE orchestrates excise and VAT calculation, balance checking, GL entry creation, and tax import to Payables. Customizations should call the public functions and procedures only, and should verify the deployed version by calling GET_SPEC_VERSION and GET_BODY_VERSION before relying on behaviour. The debug flag gv_debug is fixed as false and the log file constant is set to jai_pa_billing.log, so diagnostics are not enabled by default.