Search Results update_eff_report_details




Overview
Explore in AI Chat

Overview

PSP_EFF_REPORT_DETAILS_API is a public PL/SQL package body in the APPS schema that belongs to the Oracle E-Business Suite HRMS family of modules related to the Public Sector/Federal HR reporting framework (Efficient Reporting). The Effective Report Details API encapsulates the business logic required to create, maintain, and update the detail lines associated with Effort or Effective Reports administered within the enterprise. Its primary role is to enforce business rules and data integrity before information is written to the underlying report detail tables, while exposing a controlled, version-aware programmatic interface to callers.

The package is classified as an API in the ETRM metadata and is a VALID object. It extends the standard Oracle EBS API pattern by depending on FND_API for the common API return-status conventions and error-handling structures, and on HR_API and HR_UTILITY for Human Resources security and utility routines. In Oracle EBS 12.1.1 and 12.2.2, the package body is normally invoked rather than called directly by end users; application logic from Oracle Forms, concurrent programs, or custom extensions calls it to abstract the insert/update complexity of report details.

Key Procedures and Functions

The documented interface exposes a single procedure:

  • UPDATE_EFF_REPORT_DETAILS — the maintenance routine that updates an existing Effort Report Detail record. It encapsulates the validation and persistence logic required to modify report detail information, ensuring that changes conform to the rules of the parent Effective Report. This procedure is the supported public entry point; callers should use it rather than issuing direct DML against the detail tables.

Internally, the body also relies on the PSP_EFF_REPORT_DETAILS_BK1 and PSP_ERD_UPD packaged routines, which carry out the bulk of the row-level insert and update processing. These are treated as private implementation helpers and should not be invoked directly by customer code.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • PSP_EFF_REPORT_DETAILS — the primary detail table where individual line-level report data is stored; the API reads and writes here.
  • PSP_EFF_REPORTS — the report header table, consulted to validate the parent report context for each detail record.
  • PSP_REPORT_TEMPLATES_H — the report template definition table, used to confirm that detail entries conform to the template structure configured for the report.
  • PLITBLM — the PL/SQL integer table type used internally for bulk operations and collection handling.

Usage Notes

Because the package body is not referenced by any other database object, it functions solely as a callable API surface rather than as a shared dependency within the schema. It can be invoked from Oracle Forms personalizations or custom PL/SQL that needs to update report details, from concurrent programs performing batch maintenance, or from integration code. Per the ETRM metadata, the package is referenced by two other packages, indicating reuse within the broader Effective Reporting feature set.

When calling UPDATE_EFF_REPORT_DETAILS, callers should follow the standard Oracle API conventions: initialize the FND_API global, pass the appropriate identifiers for the report and detail rows, handle the returned status, and commit explicitly. Direct DML against PSP_EFF_REPORT_DETAILS should be avoided to preserve validation and template integrity enforced by the API. Testing in a non-production environment is recommended before deployment, since the procedure performs validation that may reject records not conforming to the associated report template.