Search Results cp_customer_name

Overview

AR_RAXMRP_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Receivables XML Publisher report commonly known as the Customer Report (internal short name RAXMRP). The package follows the standard Oracle Reports to XML Publisher migration pattern used throughout Release 12: the report definition, its data model, and its layout template are registered as a concurrent program, and the PL/SQL package supplies the formula columns, report-level triggers, and global bind variables that the report engine evaluates at runtime.

The package is declared AUTHID CURRENT_USER and its header carries the source identifier "$Header: RAXMRPS.pls 120.0 2007/12/27", placing it within the Receivables reporting family introduced during the 11i-to-R12 transition and carried forward unchanged into 12.1.1 and 12.2.2. Its responsibility is narrow: it does not perform transactional processing, validation, or accounting. Instead, it orchestrates report execution and supplies presentation-level derived values.

Key Procedures and Functions

The package exposes eight documented program units. Four are report event handlers and four are formula or accessor functions.

• BEFOREREPORT — Report trigger executed before the report data model begins processing. It initializes the package globals and prepares the session context required by the concurrent request.
• AFTERREPORT — Report trigger executed after the last data group is fetched. It is used for post-processing and cleanup of report-level state.
• AFTERPFORM — Trigger fired after the parameter form (or, in the concurrent manager case, after the concurrent program parameters) has been accepted. It resolves the customer name and character-count parameters into their working global counterparts.
• REPORT_NAMEFORMULA — Formula column that returns the displayable report name, derived from the company name supplied by the report environment.
• C_DATA_NOT_FOUNDFORMULA — Formula column, and the object the user searched for. It returns a numeric indicator expressing whether the report located data for the requested customer. It drives conditional layout behavior in the RTF template so that the "no records found" banner is rendered when the query returns no rows.
• RP_COMPANY_NAME_P — Accessor function returning the current value of the RP_COMPANY_NAME global, used by the template to print the legal entity or organization name.
• RP_REPORT_NAME_P — Accessor function returning the current value of the RP_REPORT_NAME global.
• RP_DATA_FOUND_P — Accessor function returning the current value of the RP_DATA_FOUND global, which carries the human-readable data-not-found message text.

The package also declares public globals including P_CONC_REQUEST_ID, P_CUSTOMER_NAME, CP_CUSTOMER_NAME, P_NUMBER_OF_CHAR, PH_CUST_NAME, RP_COMPANY_NAME, RP_REPORT_NAME, and RP_DATA_FOUND.

Tables Accessed

The only table documented as referenced through APPS synonyms is FND_CONCURRENT_REQUESTS. The package reads this table to resolve the concurrent request identifier passed in as P_CONC_REQUEST_ID, allowing the report to determine its submission context, including the requestor, the responsibility, and the request parameters. This is the standard mechanism by which Oracle Reports and XML Publisher concurrent programs obtain runtime metadata and by which they can print request-identifying information on the output. No Receivables transaction tables are accessed directly by this package; the customer data set itself is produced by the report's own SQL query, not by PL/SQL inside the package.

Usage Notes

AR_RAXMRP_XMLP_PKG is not intended for direct invocation from custom code. It is invoked implicitly by the Oracle Reports runtime and by the XML Publisher engine when the associated Receivables concurrent program is submitted. The report and its template are registered in the Concurrent Programs and Concurrent Program Executables forms; the template is attached through the XML Publisher Administrator responsibility, where the data definition and the RTF template are linked to the concurrent program.

Customizations should be limited to the RTF template. Extending the package body is unsupported because it is a seeded, non-shippable object whose header ships "noship." Because the c_data_not_foundformula logic drives conditional sections in the layout, changes to its return semantics can suppress or duplicate the "no data found" message; any template modification must preserve the numeric contract expected by the existing formula. The package is referenced by zero other packages, confirming that it is a terminal, report-specific unit with no downstream PL/SQL dependencies.