Search Results create_map

Overview

PJI_MAP_ROWSET_MEASURE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Projects Intelligence (PJI) product family, which supplies the extract, transformation, and reporting infrastructure used by Oracle Project Management, Oracle Project Resource Management, and Oracle Project Portfolio Analysis. Within that infrastructure, the package is responsible for maintaining the persistent definition of a "rowset" and the measures associated with that rowset. A rowset is a logical grouping of fact rows drawn from the project management tables; a measure is a numeric or descriptive quantity computed across that rowset. Administrators define these groupings when configuring project management reports, scorecards, and dashboards, and the package performs the DML that materializes those definitions in the repository tables. Its API classification is OTHER, indicating that it is an internal support package rather than a public, supported integration API exposed in the Oracle Projects documentation set.

Key Procedures and Functions

The package exposes four documented program units. Their parameter lists are not published in the ETRM metadata and must not be assumed; only their functional intent is described here.

• INSERT_ROW — Inserts a new row into the rowset repository, establishing a rowset definition or a single measure entry within an existing rowset definition.
• CREATE_MAP — Builds the mapping between the logical rowset definition and the underlying physical fact tables. This is the step that translates a user-defined rowset into the join and selection logic that the reporting engine later applies.
• UPDATE_ROW — Modifies an existing rowset or measure record, supporting maintenance of definitions after initial creation.
• DELETE_ROW — Removes a rowset or measure record, typically invoked when a report definition is retired or reconfigured.

The presence of a symmetric insert, update, and delete triad alongside CREATE_MAP indicates that the package implements a complete lifecycle for rowset-measure definitions rather than a read-only query interface.

Tables Accessed

The package works against the following objects, reached through APPS synonyms:

• PJI_MT_ROWSET_B — The base table holding rowset header-level definition records. The _B suffix denotes a base table, implying a corresponding _TL translation table exists for multilingual display names. INSERT_ROW, UPDATE_ROW, and DELETE_ROW operate here.
• PJI_MT_ROWSET_DET — The detail table storing individual measure rows that belong to a rowset. It is the child of the base table and carries the per-measure attributes consumed by the mapping logic in CREATE_MAP.
• PLITBLM — A general-purpose PL/SQL table indexed by VARCHAR2 that Oracle Projects uses as an in-memory or staging structure, commonly to pass collections of keys or codes between procedural layers without a round trip to the database.

Dependency metadata additionally records a reference to PA_VARCHAR2_30_TBL_TYPE, a PL/SQL collection type based on VARCHAR2(30), consistent with the package's use of array-based parameter passing.

Usage Notes

PJI_MAP_ROWSET_MEASURE is not designed for direct invocation by end users. It is called by the Project Management rowset configuration forms and by the concurrent programs that build and refresh project management report definitions. In 12.1.1 and 12.2.2 the surrounding technology stack is essentially identical, so behavior is consistent across both releases; the documented dependency list references only SYS.STANDARD, the PA collection type, and the three APPS tables, and no other APPS package references this unit, confirming that it sits at the bottom of the dependency chain.

Because no other package invokes it, customization or extension should be confined to the supported configuration forms. Direct calls from custom PL/SQL are possible but unsupported, and any such code must supply the collection types the package expects and respect rowset integrity rules enforced by the base and detail table relationship. Always test rowset changes in a non-production environment before regenerating published project management reporting structures.