Search Results program_application_name

Overview

The APPS.FND_PORTLET_DEPENDENCY_PKG package body is a low-level Oracle E-Business Suite utility that maintains the FND_PORTLET_DEPENDENCY table, which records the refresh relationships between portlets and the concurrent programs or functions on which they depend. Portlets displayed on the EBS Home page and other dashboard regions frequently derive their content from concurrent requests (for example, a request set or single program). When such a portlet is refreshed, the framework must know which concurrent program result to re-query so that the displayed data reflects the latest output. This package provides the insert, delete, and refresh-triggering interfaces used to register, remove, and act upon those dependency definitions.

The package is classified as an OTHER API, meaning it is not part of the officially supported public API surface but is instead an internal implementation detail of the portlet refresh infrastructure. It is owned by APPS and is referenced by no other documented packages, confirming its role as a leaf-level helper rather than a general-purpose repository component. The header comment indicates the current version dates to 2005, and the code base is stable across 12.1.1 and 12.2.2.

Key Procedures and Functions

• INSERT_CONCURRENT_ROW — A convenience wrapper that registers a dependency between a concurrent program and a portlet function. It identifies the concurrent program by name and application code, and the target by function name, then delegates to INSERT_ROW with system-derived audit columns.
• DELETE_CONCURRENT_ROW — The logical counterpart to the insert routine. It removes a previously registered concurrent-program dependency, keyed by concurrent program name, application code, and function name.
• INSERT_ROW — The core insert routine. It accepts the refresh dependency, its context, the function name, and the standard WHO audit columns. Before inserting, it checks for an existing matching row using a cursor on FND_PORTLET_DEPENDENCY and guards the insert with a NOT EXISTS clause, making the operation idempotent.
• DELETE_ROW — The core delete routine. It removes the row matching the supplied refresh dependency, context, and function name.
• PP_ACTION — An action dispatcher that performs a specific operation against the dependency records. In the ETRM metadata it is documented without a parameter list; its name suggests it handles a post-processing or portlet-processing action against the stored dependency definitions.

Tables Accessed

• FND_PORTLET_DEPENDENCY — The primary table maintained by this package. It stores one row per portlet-to-concurrent-program dependency, keyed by refresh dependency, refresh dependency context, and function name. All insert, delete, and existence checks operate on this table.
• FND_CONCURRENT_PROGRAMS — Consulted to resolve the concurrent program identified by the program name and application code passed to INSERT_CONCURRENT_ROW.
• FND_APPLICATION — Used to resolve the application code supplied with the concurrent program reference.
• DUAL — The single-row source in the INSERT_ROW SELECT ... FROM DUAL statement, which enforces the conditional insert pattern.

Usage Notes

Because this package is an internal OTHER-classified component with no documented callers, it is not intended for direct invocation by customer code. It is exercised by the EBS portlet and Home page framework when portlet definitions are created, modified, or refreshed, and indirectly whenever a concurrent program is associated with a portlet function. The program_application_name search term returns this object because the X_CONCURRENT_APPLICATION_CODE parameter of INSERT_CONCURRENT_ROW and DELETE_CONCURRENT_ROW is the application short name that, together with the concurrent program name, uniquely identifies the program being registered as a portlet dependency. The NOT EXISTS guard in INSERT_ROW means repeated registration attempts are safe and produce no duplicate rows, which is important because portlet setup may be re-run during cloning or patching. Administrators troubleshooting missing or stale portlet data should inspect FND_PORTLET_DEPENDENCY content rather than call the package directly, and should treat any custom dependency on this package as unsupported.