Search Results p_sort_by_phonetics

Overview

AR_CUST_BAL_RPT_PKG is an Oracle Receivables (AR) report-support package owned by APPS and classified as OTHER within ETRM. Its business purpose is to supply report-level logic to the AR Customer Balance Statement Letter Report, the concurrent output that communicates a customer's outstanding receivable balance and aging detail in statement-letter format. The package body is created by the installation script AR_CBSLRPTB.pls (source control header 120.0.12000000.1, dated 23-Oct-2007) and was first drafted under version Draft1A on 02-Feb-2007 by Sajana Doma.

Because the letter report is generated through the Oracle Reports runtime, the package provides the report's BeforeReport and AfterReport trigger entry points. These trigger functions execute at defined points in the report execution lifecycle, allowing the report to initialize session-level values before the main query runs and to perform any concluding actions afterward. The package therefore does not itself produce output; it configures the data retrieval context that the report query depends upon.

Key Procedures and Functions

Two functions are documented in the ETRM metadata:

• BEFOREREPORT — Invoked as the report's BeforeReport trigger. It retrieves the current concurrent request identifier and stores it for later use, then reads the value of the RA_CUSTOMERS_SORT_BY_PHONETICS profile option through FND_PROFILE.VALUE. Based on that profile setting, it determines the sort expression used by the report. When the profile evaluates to 'Y', the sort is set to the phonetic organization name column (HZP.ORGANIZATION_NAME_PHONETIC); otherwise the sort defaults to the party name column (HZP.PARTY_NAME). The function returns TRUE on success. An exception handler traps any error, forcing the sort profile to 'N' and the sort expression to HZP.PARTY_NAME, guaranteeing that the report can proceed even if profile or session retrieval fails.
• AFTERREPORT — Invoked as the report's AfterReport trigger. In the documented implementation it performs no substantive processing and simply returns TRUE, serving as the formal completion hook for the report lifecycle.

This design directly addresses the search term ra_customers_sort_by_phonetics: the profile option controls whether customer names are ordered phonetically or alphabetically in the generated balance statement letter.

Tables Accessed

ETRM documents one table reference via APPS synonyms: FND_CONCURRENT_REQUESTS. The package does not query this table directly in the visible source; rather, the concurrent request identifier is obtained through FND_GLOBAL.CONC_REQUEST_ID, and the concurrent requests table underlies that session context. The request ID is retained so that the report can associate its output and logging with the correct concurrent request. Customer name and organization name data, referenced through the HZP alias (Oracle Trading Community / HZ party tables), are consumed by the report query itself rather than by the package functions.

Usage Notes

The package is invoked automatically by the Statement Generation Program when the Customer Balance Statement Letter Report is run as a concurrent program. It is not intended for direct invocation by users or custom code. Administrators influence its behavior by setting the RA_CUSTOMERS_SORT_BY_PHONETICS profile option at the site, application, responsibility, or user level; a value of 'Y' enables phonetic ordering, while any other value yields standard party-name ordering. Because the BeforeReport handler fails safe to alphabetical sorting, misconfiguration or missing profile data will not prevent report completion. The package is referenced by no other packages, confirming its role as a leaf-level report support component, and is compatible with both EBS 12.1.1 and 12.2.2 in the APPS schema.