Results for “batch_id_p”

18 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AR_RAXINVPR_XMLP_PKG is the report logic package body associated with the Oracle Receivables transaction printing concurrent program (commonly invoked as "Print Transactions" / RAXINVPR). The package encapsulates the PL/SQL processing that drives an Oracle Reports (XML Publisher) concurrent request, including parameter validation, dynamic WHERE clause construction, and report-level value formatting. Its source header ($Header: RAXINVPRB.pls 120.0 2007/12/27) confirms it is a seeded Oracle Applications object, shipped under the APPS schema and classified as OTHER in the ETRM repository.

The primary business purpose of this package is to assemble the selection criteria for transaction printing, then expose that criteria to the report data model. It supports multiple print modes — batch, open invoices, customer transactions, adjustments, and direct transaction identifiers — controlled by parameters such as p_choice, p_open_invoice, p_cust_trx_type_id, p_cust_trx_class, p_customer_id, p_batch_id, and associated date and number ranges. The print_option parameter, which the user searched against, is a report driver that determines how transactions are selected and formatted for output.

Key Procedures and Functions

The package exposes 17 documented program units. The report-timing functions include BEFORE_REPORT, AFTER_REPORT, and AFTER_PFORM, which follow the standard Oracle Reports PL/SQL trigger naming convention. BEFORE_REPORT builds the dynamic WHERE and table fragments by calling ARP_TRX_SELECT_CONTROL.BUILD_WHERE_CLAUSE with the incoming report parameters, then assigns the results to package-level globals (p_where1, p_where2, p_table1, p_table2). AFTER_PFORM performs the post-form trigger logic.

Parameter getter functions expose report parameters to the data model and layout: PRINT_OPTION_P (returns the print_option value), TYPE_ID_P, CUSTOMER_ID_P, BATCH_ID_P, OPEN_INVOICES_P, INVOICE_DATES_P, INVOICE_NUMBERS_P, and FUNCTIONAL_CURRENCY_P. Companion globals with a _T suffix (for example print_option_t, type_id_t, customer_id_t, batch_id_t) are declared in BEFORE_REPORT to hold the resolved filter values. Report-attribute getters include RP_DATA_FOUND_P, RP_COMPANY_NAME_P, and RP_REPORT_NAME_P.

Additional functions provide formatting and control logic: INSTALLMENT_PRINTING_PENDING_P and INSTALLMENT_LAST_PRINT_DATEFOR support installment-level printing, while D_AMOUNTFORMULA is the Oracle Reports formula function that formats the displayed amount column.

Tables Accessed

The package reads several base and setup tables through APPS synonyms:

  • AR_SYSTEM_PARAMETERS — retrieves tax registration number and other Receivables system options used in report headers.
  • RA_CUST_TRX_TYPES — resolves transaction type attributes for filtering and display.
  • RA_BATCHES — validates and selects batch information when the batch print option is chosen.
  • HZ_CUST_ACCOUNTS and HZ_PARTIES — supply customer name and party details for the printed output.
  • FND_CONCURRENT_REQUESTS — provides concurrent request context, including report name resolution.

Validation logic within BEFORE_REPORT raises an application error when p_choice = 'BATCH' and p_batch_id is null, using ARP_STANDARD.FND_MESSAGE to surface message 740. Note that several SRW.USER_EXIT and SRW.MESSAGE calls are commented out in the source excerpt, indicating the package was refactored away from direct SRW calls.

Usage Notes

AR_RAXINVPR_XMLP_PKG is not intended for direct invocation by custom code. It is executed by the Oracle Reports server when the associated concurrent program (RAXINVPR) is submitted from the Receivables Transactions form, the Standard Report Submission window, or a scheduled concurrent request. The report parameters map to the selection fields presented to the user, including the print_option that governs which transactions are gathered. Because the package reads from the concurrent requests table and depends on standard Receivables APIs (ARP_TRX_SELECT_CONTROL, ARP_STANDARD), it should be treated as a seeded, upgrade-managed object. Customizations should be limited to report template and XML Publisher layout changes rather than modifications to the package body itself.