Search Results copy_references

Overview

JAI_AR_TCS_REP_PKG is an Oracle E-Business Suite PL/SQL package owned by APPS that implements Tax Collection at Source (TCS) reporting logic for the Oracle Receivables (AR) and Order Management (OM) flows within the India Localization (JAI) product family. The package was introduced to support the statutory requirement that sellers collect tax at source on specified categories of sales, and it is responsible for validating transactions, deriving accounting, and generating the tax repository records that underpin the TCS return. The current file version (120.3, dated 2011/08/18) reflects change history entries for bug#5631784 (forward porting of 11i bug#4742259, "Tax Collection at Source in Receivables") and bug#6109941 (correction to retrieval of the TCS financial year via the get_tcs_fin_year cursor). The package is declared AUTHID CURRENT_USER and is tightly integrated with the JAI Registration (JAI_RGM) tables that hold party, tax, and reference definitions, as well as with standard AR and OM transaction tables. It exposes a broad API surface (19 documented procedures and functions) and is referenced by 13 other packages, indicating that it functions as a shared repository of TCS processing logic rather than a single-purpose utility.

Key Procedures and Functions

The procedural interface spans four logical areas:

• Validation: VALIDATE_SALES_ORDER, VALIDATE_INVOICE, VALIDATE_APP_UNAPP and VALIDATE_RECEIPTS evaluate whether a given order, invoice, application, or receipt qualifies for TCS treatment and return the document type alongside process status and message outputs.
• Accounting: AR_ACCOUNTING, WSH_INTERIM_ACCOUNTING and RECEIPT_INTERIM_ACCOUNTING compute and post the accounting entries associated with TCS, including interim accounts for delivery and receipt events.
• Repository maintenance: INSERT_REPOSITORY_REFERENCES, INSERT_REPOSITORY_TAXES, COPY_TAXES_FROM_SOURCE, COPY_REFERENCES and INSERT_REPOSITORY_REFERENCES (invoked from the JAI_RGM_REFS_ALL context) populate and clone the registration/reference data used by the tax return.
• Processing and document generation: PROCESS_INVOICES, PROCESS_RECEIPTS, PROCESS_APPLICATIONS, PROCESS_UNAPP_RCPT_REV and PROCESS_TRANSACTIONS drive the end-to-end TCS processing of AR documents; UPDATE_ITEM_GEN_DOCS and GENERATE_DOCUMENT handle the generation and update of the TCS documents; UPDATE_PAN_FOR_TCS maintains the permanent account number (PAN) detail required on the TCS return.

Tables Accessed

Access is through APPS synonyms. Standard Receivables tables include RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL (invoice header and line validation and accounting), AR_RECEIVABLE_APPLICATIONS_ALL (application/unapplication checks for PROCESS_APPLICATIONS), AR_CASH_RECEIPTS_ALL (receipt validation and reversal logic) and AR_PAYMENT_SCHEDULES_ALL (installment and due-date context). Order Management and shipping data come from OE_ORDER_HEADERS_ALL and JAI_OM_WSH_LINES_ALL, used by the sales-order and interim-accounting routines. The localization repository is represented by JAI_RGM_DEFINITIONS, JAI_RGM_PARTIES, JAI_RGM_REFS_ALL, JAI_RGM_REGISTRATIONS and JAI_RGM_TAXES, which supply party classification, item classification and tax setup. JAI_AP_TDS_YEARS and JAI_CMN_CUS_ADDRESSES provide financial-year and customer-address parameters, and FND_LOGINS is used for session/user context.

Usage Notes

The package is normally invoked indirectly. In a 12.1.1 or 12.2.2 environment it is called from the India Localization Receivables forms and from concurrent programs that build the TCS return, and it is also consumed by the 13 dependent packages that reference it. Custom code should follow the same pattern: call the validation procedures first (for example VALIDATE_INVOICE or VALIDATE_APP_UNAPP) to obtain the document type and process flag, then invoke the corresponding PROCESS_* routine, and finally the accounting and document-generation procedures. Because output parameters such as p_process_flag and p_process_message are declared NOCOPY, callers must declare matching OUT variables and inspect them before committing. Cross-reference to the standard AR and OM APIs should be preserved, since the package assumes the base transactions already exist and are valid.