Search Results pn_loc_acc_map




Overview
Explore in AI Chat

Overview

PN_REC_EXP_EXTR_FROM_GL_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It belongs to the Property Manager (PN) module and supports the recovery and expense extraction process used by telecommunications and property management customers. Its core business function is to read expense and budget balances from Oracle General Ledger and stage that data into the recovery expense interface for subsequent processing. The package effectively bridges General Ledger account balances to the property recovery engine, enabling organizations to recover operating expenses from tenants based on lease terms.

In the context of Oracle EBS 12.1.1 and 12.2.2, this package operates as a background utility rather than a user-facing API. It is classified as OTHER within the ETRM documentation, indicating it is an internal technical package invoked by the recovery extraction framework rather than a published integration interface. The presence of the pn_loc_acc_map search term in the user query reflects the package's reliance on location-to-account mapping to associate GL balances with specific properties and locations.

Key Procedures and Functions

The package body exposes three documented procedures and functions. Their purpose is summarized below; parameter lists are not documented and are therefore not reproduced here.

  • EXTRACT_EXPENSE_FROM_GL — The primary driver procedure. It queries GL balances and budget information, applies location account mapping, and writes the extracted expense records into the PN_REC_EXP_ITF interface table for downstream recovery processing.
  • PUT_LOG — A logging utility used to record processing messages, errors, and status information during extraction. It supports diagnostic tracing of the extraction run.
  • PUT_LINE — A lower-level output routine used to write formatted lines to the log or output file, complementing PUT_LOG for detailed trace output.

Tables Accessed

The package references both GL and PN tables through APPS synonyms. Its GL dependencies include GL_BALANCES (source of actual account balances), GL_BUDGETS and GL_BUDGET_VERSIONS (budget comparison data), GL_PERIOD_STATUSES (to restrict extraction to open or valid accounting periods), and GL_SETS_OF_BOOKS (to resolve the ledger context). GL_LOOKUPS is also referenced, likely for decoding lookup values.

On the Property Manager side, the package reads PN_LOCATIONS_ALL to identify valid locations, and critically reads PN_LOC_ACC_MAP and PN_LOC_ACC_MAP_ALL, which provide the mapping between locations and GL accounts. This mapping is the mechanism by which GL expense balances are attributed to the correct location for recovery. PN_PROPERTIES_ALL supplies property-level context, and PN_REC_EXP_ITF is the interface table into which extracted expense records are inserted. The package also depends on PN_MO_CACHE_UTILS and PN_RECOVERY_EXTRACT_PKG for shared cache and recovery extraction logic. Utility dependencies include FND_DATE, FND_FILE, FND_MESSAGE, FND_PROFILE, DBMS_SQL, PLITBLM, and STANDARD.

Usage Notes

PN_REC_EXP_EXTR_FROM_GL_PKG is not referenced by any other database object, confirming that it sits at the top of its call hierarchy and is invoked directly. In practice it is called by the recovery expense extraction concurrent program within the Property Manager responsibility. Administrators submit the extraction program to populate PN_REC_EXP_ITF before running the recovery expense generation process. The package uses FND_FILE for output, so results and logs are visible through the concurrent request log and output files. Because the package depends on PN_LOC_ACC_MAP for location-to-account mapping, customers must maintain accurate location account mappings before extraction, otherwise GL balances will not be attributed correctly to properties. Custom code may invoke EXTRACT_EXPENSE_FROM_GL directly, but this should be done with care given the package's internal nature and lack of a documented public interface.