Search Results get_organization_name

Overview

PA_BL_UTILS is a utility package body in the Oracle E-Business Suite Projects (PA) application, owned by the APPS schema. It provides shared helper logic for resolving descriptive names associated with project expenditure transactions. The package exists to centralize the small but frequently repeated lookup operations that translate stored identifiers — vendor IDs, person IDs, and organization IDs — into human-readable names suitable for display in Oracle Forms, reports, and concurrent program output. In Oracle EBS 12.1.1 and 12.2.2, the package serves as an internal building block rather than a public API; the ETRM classification of OTHER reflects that it is not published for external integration use. Its two documented functions, GET_SUPPLIER_OR_EMP_NAME and GET_ORGANIZATION_NAME, correspond to two common display requirements on expenditure and cost distribution screens: identifying who incurred or supplied a cost, and identifying the organization to which a transaction or distribution belongs. The header comment shows the file originated in the late 1990s, and the underlying logic has remained stable across the 12.x releases.

Key Procedures and Functions

• GET_SUPPLIER_OR_EMP_NAME — Returns a display name for an expenditure item. When the expenditure item's system linkage function is of type 'VI' (vendor invoice), the function resolves the supplier name; for all other linkage types it returns the employee full name for the incurred-by person. It accepts the expenditure item identifier, the system linkage function, an expenditure item date, and an incurred-by person identifier, and returns a VARCHAR2. The documented source shows that vendor resolution reads the system reference from the first cost distribution line and then looks up the vendor name, while employee resolution queries the person record as of the expenditure date. Fallback constants such as 'NO SUPPLIER FOUND' and 'NO EMPLOYEE FOUND' are returned when no matching record exists.
• GET_ORGANIZATION_NAME — Returns the organization name associated with an organization identifier. This is the function most closely associated with the search term "get_organization_name" and is typically used to convert an internal organization ID into its translated display name for presentation on expenditure, distribution, and reporting output. The documentation confirms the function exists and that it draws on the organization units table, but does not expose its full parameter list.

Tables Accessed

• PA_EXPENDITURE_ITEMS_ALL — Supplies expenditure item attributes, including the system linkage function and expenditure item date used to drive the employee-versus-supplier decision.
• PA_EXPENDITURES_ALL — Source of the incurred-by person identifier for the expenditure.
• PA_COST_DISTRIBUTION_LINES_ALL — Read to obtain the system reference (vendor identifier) from the first distribution line when the linkage function is 'VI'.
• HR_ALL_ORGANIZATION_UNITS_TL — The translated organization units table, read by GET_ORGANIZATION_NAME to return the organization name in the appropriate language.

In addition, and as shown in the documented source, the supplier path performs a lookup against PO_VENDORS, and the employee path queries PER_PEOPLE_F for the full name effective as of the expenditure date.

Usage Notes

Because the package is classified as OTHER and is not referenced by any other documented package, it should be treated as an internal utility invoked directly by Oracle Projects forms, reports, and custom extensions rather than through a supported public API. Typical invocation points include expenditure inquiry and adjustment forms that need to display the supplier or employee name, and concurrent or report programs that render organization names on cost distribution output. The functions are deterministic, read-only helpers and are safe to call from custom PL/SQL provided the caller respects the date-effective and linkage-type semantics described above: pass the correct system linkage function and expenditure item date so that the correct branch and effective-dated person row are selected. Custom code should not assume stability of the fallback literal strings, and any direct dependency on this package body carries the usual risk associated with non-published Oracle EBS internals across patches and upgrades.