Search Results g_miss_value

Overview

APPS.PA_PLAN_RES_LIST_PUB is a public PL/SQL package in the Oracle E-Business Suite Projects (PA) module that governs the definition of planning resource lists and planning resource formats used in project planning and resource assignment. In Oracle EBS 12.1.1 and 12.2.2, planning resource lists represent reusable groupings of resource classes, resource types, and resource members that are applied to a project or project template for planning purposes. The package exposes a business-facing API — as opposed to a purely data-level interface — and provides the entry points that other applications, forms, and concurrent programs call to create, modify, copy, and delete these planning constructs.

The singleton source excerpt preserved in ETRM (PARESLPB.pls, version 120.3, dated 2006) reveals the internal design convention used throughout the package. The private procedure Convert_Missing_List_In_Rec documents the treatment of the G_MISS_VALUE sentinel referenced in the user query. In Oracle EBS APIs, an uninitialized or omitted input attribute frequently carries the value G_MISS_VALUE (or a related FND constant) rather than NULL. The procedure converts such input attributes to NULL, and, in update mode, substitutes the current database value for any attribute supplied as NULL so that omitted fields are not inadvertently overwritten. This protective conversion is applied to the Plan_Res_List_IN_Rec record, which carries the resource list header attributes, and the result is returned through the corresponding OUT record. The procedure operates under a mode flag — 1 for update and 0 for create — and in update mode resolves the resource list ID from the resource list name where the ID is not supplied.

Key Procedures and Functions

The package exposes fifteen documented public procedures and functions, which fall into distinct groups.

• CREATE_RESOURCE_LIST / UPDATE_RESOURCE_LIST / DELETE_RESOURCE_LIST — the primary transactional entry points for defining, maintaining, and removing a planning resource list.
• INIT_CREATE_RESOURCE_LIST / INIT_UPDATE_RESOURCE_LIST — initialization routines that prepare a resource list input record with default attributes or with existing database values before a create or update call. These are the routines most directly associated with the G_MISS_VALUE handling described above.
• EXEC_CREATE_RESOURCE_LIST / EXEC_UPDATE_RESOURCE_LIST — execution-level procedures that perform the actual persistence work behind the create and update APIs.
• LOAD_RESOURCE_LIST / LOAD_RESOURCE_FORMAT — load the definition of a resource list or a resource format into a working record for subsequent operations.
• LOAD_PLANNING_RESOURCE — loads an individual planning resource, including its resource class or resource type context.
• FETCH_RESOURCE_LIST / FETCH_PLAN_FORMAT / FETCH_RESOURCE_LIST_MEMBER — retrieval routines that return the header of a resource list, the detail of a planning format, or a specific resource list member row.
• DELETE_PLAN_RL_FORMAT / DELETE_PLANNING_RESOURCE — deletion routines that remove a planning resource-list format association or an individual planning resource.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PA_RESOURCE_LISTS_ALL_BG — the base table that stores planning resource list headers.
• PA_RESOURCE_LIST_MEMBERS — the member lines belonging to a resource list.
• PA_RESOURCE_CLASSES_B / PA_RES_TYPES_B — validation of resource class and resource type definitions.
• PA_RES_FORMATS_B / PA_PLAN_RL_FORMATS — definition and format association of planning resource formats.
• PA_IMPLEMENTATIONS / PA_PROJECTS_ALL — installation and project context used for validation and defaulting.
• DUAL / PLITBLM — scalar selection and the standard PL/SQL index-by table utility used in record handling.

Usage Notes

The package is characteristically invoked from the Projects forms (planning resource list maintenance windows), from concurrent programs that copy or load planning resource definitions, and from custom PL/SQL that must create or retrieve planning resource data programmatically. Callers should always initialize input records with the INIT_* procedures before issuing CREATE or UPDATE, because the G_MISS_VALUE conversion performed internally depends on that convention. No other package in the documented sample references this package, but this reflects the limited metadata extract rather than an absence of callers in a production instance.