Search Results get_cc_tasks




Overview

INV_UI_TASK_LOVS is an Oracle Inventory (INV) PL/SQL package owned by the APPS schema. It is a user-interface support package whose specific purpose is to supply the data behind List of Values (LOV) windows used by Oracle E-Business Suite forms that reference a "task" attribute. Rather than hard-coding LOV queries inside individual forms, the Inventory development team centralised the retrieval logic in this package so that any form exposing a task-number LOV — receiving, move orders, cycle counting, and physical inventory — calls the appropriate procedure and receives the qualifying rows as a strongly typed reference cursor.

All five documented procedures return rows through the declared t_genref REF CURSOR type, which is defined as a REF CURSOR at package level. The caller therefore opens the LOV block, invokes the procedure, and iterates the returned cursor to populate the LOV. The package contains no insert, update, or delete logic and is classified in ETRM as an OTHER API — it is a query-only utility, not a transaction-bearing API.

The user search term get_sub_lov_rcv corresponds to the naming convention used at the source-code level for the receiving sub-LOV. In the shipped header the receiving procedure is named GET_RCV_TASKS; the comment block above the declaration carries the legacy label "GET_SUB_LOV_RCV". This reflects the same functional area — the sub-LOV used on receiving forms — and explains why a search for the older internal name resolves to this package.

Key Procedures and Functions

Five procedures are documented. Each returns a reference cursor of type t_genref through an OUT NOCOPY parameter.

  • GET_TASKS — The generic task LOV. It optionally restricts the returned rows to a specified project. This is the baseline procedure that other, context-specific procedures extend.
  • GET_MO_TASKS — Supplies task numbers in the move-order context. It accepts restricting parameters for the project, organization, and move-order header so that only tasks valid for the move order being entered are presented.
  • GET_CC_TASKS — Supplies tasks for cycle counting. It is scoped by project, organization, cycle count, and an unscheduled flag, allowing the LOV to include or exclude tasks that have not been scheduled for the count.
  • GET_PHY_TASKS — Supplies tasks for physical inventory. It is scoped by project, organization, a dynamic-entry flag, and a physical inventory identifier.
  • GET_RCV_TASKS — The receiving task LOV, historically labelled GET_SUB_LOV_RCV. It carries the richest parameter set because receiving tasks are contextual on document type and document identifiers — purchase order header, PO line, order-entry header, requisition header, shipment, project, and task number — with additional optional parameters for item, LPN (ASN handling), PO release, and a deliver flag added under bug 6785303. The presence of several defaulted parameters indicates the procedure is called from multiple form entry points with differing levels of context.

Tables Accessed

The package reads the following base tables through APPS synonyms, joining them to validate and filter task rows against the calling context.

All are read-only; no DML is performed by this package.

Usage Notes

INV_UI_TASK_LOVS is invoked at runtime by Oracle Inventory and Purchasing/Receiving forms whenever a task-number LOV is opened. The form calls the appropriate procedure, passes the current block/record context as the restricting parameters, and renders the returned reference cursor as the LOV result set. Because the parameters map directly to form block items, the LOV narrows automatically as the user fills in a project or document.

The package is not referenced by any other package according to ETRM metadata, confirming it is an end-point utility for UI consumption rather than a shared service. Customisations should therefore avoid embedding business logic in it. Custom code may call these procedures where a task LOV is required, but must handle the OUT NOCOPY reference cursor and observe the documented parameters, since the cursor is consumed by the caller and not reusable across fetches. The last significant header revision dates to 2008 (version 120.2), so the behaviour is stable across the 12.1.1 and 12.2.2 releases. Standard practice is to reference the LOV from a form item's LOV property or from a record group with a query-based mechanism rather than invoking the procedures directly from SQL*Plus or reports.