Search Results cancel_project_request




Overview
Explore in AI Chat

Overview

PA_PROJECT_REQUEST_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It exposes the business logic that governs the lifecycle of project requests within Oracle Projects. A project request is the pre-approval artifact used to capture proposed project information — such as customer, project template, and organizational context — before a project is formally created and funded. The package acts as the supported programmatic entry point for creating and cancelling these requests, shielding external callers from the underlying private package PA_PROJECT_REQUEST_PVT, which contains the bulk of the implementation.

Because it is classified as a PUB (public) API rather than a PVT package, PA_PROJECT_REQUEST_PUB is the layer intended for direct invocation by Oracle forms, concurrent programs, and customer-written extensions. The package is VALID in the ETRM data dictionary and carries a dependency on the Oracle Projects request tables as well as the Oracle Trading Community Architecture (TCA) registry. Its documented surface consists of three callable programs, reflecting a deliberately narrow, stable interface atop a much more complex private implementation.

Key Procedures and Functions

The ETRM documentation for 12.2.2 lists three documented programs in this package:

  • CREATE_PROJECT_REQUEST — Creates a new project request record. This is the primary entry point for initiating a project request from an external caller. It inserts the request into PA_PROJECT_REQUESTS, establishes the linkage between the request and the associated customer or party records in TCA, and assigns an initial status from PA_PROJECT_STATUSES. It also writes the corresponding relationship rows that tie the request to its related entities.
  • CANCEL_PROJECT_REQUEST — Cancels an existing project request. This routine transitions the request to a cancelled state and updates the associated status and relationship information so that the request is no longer treated as active.
  • PARTY_MERGE — Handles the impact of a TCA party merge on existing project requests. When two parties (customers) are merged in Oracle Trading Community Architecture, this routine reconciles the party references held by project requests so that the surviving party is correctly reflected and orphaned references are avoided.

Parameter lists are intentionally omitted here; the documentation excerpt names these programs but does not publish their signatures. Callers should consult the package specification in the database or the Oracle Projects API documentation for argument definitions.

Tables Accessed

The package reads and writes the following objects, which are referenced through APPS synonyms:

  • PA_PROJECT_REQUESTS — The core transactional table storing project request header information. It is the primary target of CREATE_PROJECT_REQUEST and the record updated by CANCEL_PROJECT_REQUEST.
  • PA_PROJECT_STATUSES — Provides the valid status codes applied to a project request, including the cancelled status used during cancellation.
  • PA_OBJECT_RELATIONSHIPS — Stores the generic relationships between the project request and related business objects, maintained as requests are created or cancelled.
  • HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES — The TCA registry tables that identify the customer or party associated with a request. These are read during creation and revised during a party merge.
  • AS_LEADS_ALL — The Oracle Sales leads table, reflecting the integration between project requests and the lead/sales pipeline.
  • FND_NEW_MESSAGES — The Oracle Application Object Library message repository, used to emit user-facing error or informational messages through standard EBS message handling.

Usage Notes

PA_PROJECT_REQUEST_PUB is typically invoked in three contexts. First, Oracle Projects forms that capture or cancel project requests call the public API rather than manipulating the base tables directly, preserving business rule enforcement. Second, custom PL/SQL extensions and integrations that need to create project requests programmatically should call CREATE_PROJECT_REQUEST and CANCEL_PROJECT_REQUEST instead of performing DML on PA_PROJECT_REQUESTS. Third, PARTY_MERGE is invoked as part of the TCA party merge process to keep project request data synchronized when customer records are consolidated.

The package is referenced by PA_PROJECT_REQUEST_PUB itself (recursive reference) and by PA_PROJECT_REQUEST_PVT, consistent with the PUB/PVT layering convention. The PVT package holds the detailed logic, while the PUB package provides the supported interface. Callers should not modify PA_PROJECT_REQUESTS directly, because doing so bypasses the relationship maintenance, status validation, and messaging performed by this API. Message text should be retrieved through the standard FND message mechanisms, since the package relies on FND_NEW_MESSAGES. Developers should review the specification in the target environment, as the ETRM excerpt documents only the object and its dependencies, not the full argument signatures.