Search Results create_plan_rl_format




Overview
Explore in AI Chat

Overview

PA_PLAN_RL_FORMATS_PUB is a public PL/SQL package in the APPS schema that supports reporting layout (RL) format definitions used by Oracle Project Management and the Project Resource Management planning functionality within Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, the Project Management module allows project managers to define and reuse reporting layouts that determine how project plan and resource data is displayed, structured, and reported. The PA_PLAN_RL_FORMATS_PUB package exposes the public API layer for creating and removing these plan reporting layout format definitions.

The package carries the PUB suffix, which in Oracle EBS naming convention identifies it as a public, externally callable API. It is documented under the PA (Projects) product family and is classified as a valid, compiled package object in the ETRM repository. The package depends on the standard Oracle Application Object Library API library, FND_API, which provides the common error-handling, message-stacking, and return-status conventions (such as FND_API.G_RET_STS_SUCCESS) used across EBS public APIs. It also references the PL/SQL system package STANDARD and the database type PA_NUM_TBL_TYPE, a Projects multi-number table type commonly used to pass collections of identifiers or values into project APIs.

Key Procedures and Functions

The ETRM metadata documents two public procedures within the package. Descriptions follow the documented procedure names; parameter lists are not documented and are therefore not reproduced here.

  • CREATE_PLAN_RL_FORMAT — Creates a new plan reporting layout format definition. This procedure is the entry point for programmatically defining a reporting format that can later be assigned to project plan reporting and layout configurations. Consistent with EBS public API standards, it is expected to validate input, perform inserts or updates against the underlying reporting layout tables, and communicate success or failure through the FND_API message and return-status mechanism.
  • DELETE_PLAN_RL_FORMAT — Removes an existing plan reporting layout format definition. It handles the deletion of a previously created format, again using FND_API conventions to report validation errors and processing results back to the calling program.

Both procedures are part of the public interface exposed to forms, concurrent programs, and custom extensions. Any write operations they perform are subject to the standard Projects validation and security model.

Tables Accessed

The documented table reference for this package is provided through APPS synonyms and includes PLITBLM. This table is associated with Projects planning and reporting layout data storage. The package reads and writes the records that represent reporting layout format definitions, ensuring that created formats are persisted and that deleted formats are removed. Because PLITBLM is accessed via the APPS synonym, the package respects the standard EBS schema synonym convention and runs with the privileges of the APPS schema. The metadata also references the PL/SQL table type PA_NUM_TBL_TYPE, indicating that procedures may accept or process collections of numeric identifiers as part of their internal processing and validation.

Usage Notes

PA_PLAN_RL_FORMATS_PUB is typically invoked indirectly by the Oracle Projects forms and concurrent programs that manage plan reporting layouts, rather than being called manually by end users. The Project Management responsibility forms that maintain reporting layout formats rely on this package to execute the create and delete operations behind the user interface. Custom developers extending Oracle Projects should invoke the public procedures of this package rather than performing direct inserts or deletes against the underlying tables, since the API enforces validation and records error messages through FND_API.

The ETRM metadata indicates that this package is not referenced by any other documented package, meaning it sits at the outer edge of the dependency chain within the documented set. It depends on FND_API and STANDARD, and its own package body. When troubleshooting reporting layout issues in EBS 12.1.1 or 12.2.2, administrators should verify the validity and compilation status of this package, confirm that the PLITBLM data is accessible through the APPS synonym, and review FND_API message stack output returned to the calling form or program. Because only the package specification, package body, and dependency listings are documented, any signature details, error codes, or additional helper procedures beyond the two public procedures named above should be confirmed against the deployed source in the specific environment.