Search Results rcv_project_grp




Overview
Explore in AI Chat

Overview

RCV_PROJECT_GRP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM repository as a "GRP" (group) package. Its documented purpose is to expose project and task reference information associated with receiving transactions. In an Oracle EBS environment where Receiving (RCV) transactions are linked to Oracle Projects, each receiving line can carry a project number and a task number that identify the Projects context for the goods receipt. RCV_PROJECT_GRP provides a narrow, read-oriented programming interface that returns those values given a receiving transaction identifier.

The package header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the defining user. The header carries the revision marker $Header: RCVGPRJS.pls 115.1 2004/02/10, indicating the file has been stable since early 2004 and that the public interface is effectively frozen. The package defines only two functions and no procedures, which is consistent with the GRP classification: it is a lightweight accessor group rather than a transaction-processing or validation API. Both documented functions follow the standard EBS API signature convention, accepting p_api_version and p_init_msg_list before the operational parameter, which allows callers to use the same call pattern applied to other EBS public APIs.

Key Procedures and Functions

  • GET_PROJECT_NUMBER — Returns a VARCHAR2 containing the project number associated with a receiving transaction. The caller supplies the API version, the initialization flag for the message list, and the receiving transaction identifier. The function is intended to translate the internal transaction key into the externally recognizable project number.
  • GET_TASK_NUMBER — Returns a VARCHAR2 containing the task number associated with the same receiving transaction identifier. It mirrors GET_PROJECT_NUMBER in its signature and behavior, supplying the task-level detail that complements the project number.

The presence of p_init_msg_list on both functions indicates that the implementation is expected to honor the standard EBS message-stack contract, so callers should inspect the FND message stack after invocation when the return value is null.

Tables Accessed

The ETRM metadata for RCV_PROJECT_GRP does not enumerate the base tables accessed through APPS synonyms. Based on its documented function, the package logically resolves the receiving transaction identifier against the receiving transaction and distribution tables (RCV_TRANSACTIONS and RCV_SHIPMENT_LINES, and the associated project/task reference columns) to derive the project and task numbers. Because no table references are documented, implementers should treat the underlying data access as an internal implementation detail and rely solely on the returned project and task numbers rather than joining directly to those sources.

Usage Notes

RCV_PROJECT_GRP is referenced by one other package in the ETRM metadata, confirming it is a shared utility within the Receiving module rather than a standalone entry point. It is typically invoked when a form or concurrent program needs to display or print the project and task context of a receipt without querying the underlying receiving tables directly. Typical callers include Receiving forms, receiving-related reports, and custom extensions that must present project and task references alongside receipt details. Because the interface is a pair of simple scalar-returning functions with a stable signature unchanged since 2004, custom code may call the package safely in Oracle EBS 12.1.1 and 12.2.2, subject to standard support policy regarding direct calls to non-public APIs. Callers should pass a valid API version and handle the null return case by checking the message stack.