Search Results get_attribute_status

Overview

APPS.PN_INDEX_RENT_PVT is a private (PVT) PL/SQL package body belonging to the Oracle Property Manager (PN) module. It supports the Index Rent feature, which calculates rent adjustments on lease agreements based on an external index such as CPI. The "PVT" classification indicates this is an internal implementation package rather than a public API; callers should not depend on its signature remaining stable across patches. In Oracle EBS 12.1.1 and 12.2.2, the package exposes only three documented entry points (DEBUG, CREATE_INDEX_RENT, UPDATE_INDEX_RENT) while internally providing helper routines that validate descriptive flexfield (DFF) attributes and constraint-level DFF usage before rent records are persisted. The header comment (version 120.1, dated 2010/12/15) shows the file is shipped NOSHIP, meaning it is delivered but not customer-modifiable.

Key Procedures and Functions

• DEBUG — Diagnostic utility. It writes a log message to the PN debug facility, controlled by the profile option PN_DEBUG_MODE and a log-level argument. Debug output is emitted only when PN_DEBUG_MODE is set to 'Y'; otherwise the routine is a no-op.
• CREATE_INDEX_RENT — Creates index rent records for a lease. It is the primary insertion point for index-based rent adjustments, driving validation logic and the DFF checks used during creation.
• UPDATE_INDEX_RENT — Modifies existing index rent records, applying the same validation and DFF constraint checks as creation.

Beyond the documented entries, the package body includes the function of direct interest to the "get_attribute_status" search: get_attribute_status. This function accepts a descriptive flexfield name and returns a NUMBER. It queries FND_DESCR_FLEX_COL_USAGE_VL, counting columns where the descriptive flexfield name matches (uppercased and trimmed), ENABLED_FLAG = 'Y', and DISPLAY_FLAG = 'Y'. The returned count represents the number of active, displayable DFF attributes. Its exception handler traps WHEN OTHERS and returns 0, so callers receive a safe default rather than a propagated error. A related procedure, validate_constraints_desc_flex, consumes this count when validating index constraint DFF attributes, returning a status of 'S' (success) or 'E' (error) along with message count and message data.

Tables Accessed

• PN_INDEX_LEASES_ALL — Stores lease-level index rent definitions; read and written by the create/update routines.
• PN_INDEX_LEASE_CONSTRAINTS_ALL — Holds constraint records applied to index leases; used when validating constraint DFF attributes.
• PLITBLM — The generic EBS message/table used by the message-handling framework to build return status and message data.
• FND_DESCR_FLEX_COL_USAGE_VL — Queried by get_attribute_status to determine the enabled and displayable DFF columns.

Usage Notes

Because PN_INDEX_RENT_PVT is a PVT package, it is normally invoked indirectly through the public Property Manager APIs and the Index Rent maintenance forms rather than called directly. The debug flag is governed by the PN_DEBUG_MODE profile option, which should only be enabled during troubleshooting since it produces verbose logging. Two other packages reference this package, confirming it is a shared internal dependency. The get_attribute_status function is most useful to developers investigating why constraint attributes are excluded from validation: a return of 0 typically indicates the descriptive flexfield name is misspelled, the attribute is not enabled, or the display flag is unset. Custom code should call the public PN APIs instead of this private package.