Search Results pa_rbs_mapping_rule_s

Overview

PA_RBS_MAPPING is a PL/SQL package body in the APPS schema that supports Oracle E-Business Suite Project Billing and Project Costing functionality for Resource Breakdown Structure (RBS) mapping. It provides the runtime engine that transforms project transaction and planning data into the RBS-based summarization structures used by Project Intelligence (PJI) reporting and by the RBS mapping architecture in Oracle Projects. The package reads mapping rules defined in the PA_RBS_MAPPING_RULES and PA_RBS_MAPPING_RULE_S tables and applies them to actuals and plan data, producing the resource-type and resource-assignment mappings that drive aggregation, denormalization, and rollup.

The package is internally dependent on FND_API, FND_GLOBAL, FND_MSG_PUB, FND_PROFILE, and FND_STATS for standard API error handling, message publishing, profile retrieval, and statistics gathering, as well as on numerous PA_RBS_* and PJI_* packages and tables. The metadata classifies the object as an OTHER API, indicating it is not a published public API but an internal engine invoked by Project Billing, Project Costing, and Project Intelligence processing. The presence of temporary tables such as PA_RBS_MAP_T1 through PA_RBS_MAP_TMP13 confirms that the package stages intermediate mapping data before final persistence.

Key Procedures and Functions

The documented API surface comprises nine procedures and functions:

• MAP_RBS_ACTUALS_NEW — The primary mapping routine for actual cost and billing transactions, mapping RBS elements to resource types and resource assignments using current rule definitions.
• MAP_RBS_ACTUALS — The legacy or alternate mapping routine for actuals, retained for backward compatibility with prior processing paths.
• MAP_RBS_PLANS — Maps planning and budget version data to the RBS structure for plan-side aggregation.
• CREATE_RES_TYPE_NUMERIC_ID — Creates a numeric identifier for a resource type when one does not already exist, ensuring consistent keying across the mapping tables.
• GET_RES_TOKEN — Retrieves a resource token used as a unique textual identifier during mapping.
• GET_RES_TYPE_NUMERIC_ID — Returns the numeric identifier associated with a given resource type.
• CREATE_MAPPING_RULES — Generates mapping rule rows from RBS element definitions and rule templates.
• GET_RESOURCE_TYPE_COLS — Returns the set of resource-type column definitions used when building dynamic mapping SQL.
• GET_RES_TYPE_ID — Returns the resource type identifier for a given mapping context.

Tables Accessed

Documented base tables include PA_RBS_ELEMENTS and PA_RBS_ELEMENTS_S (RBS element definitions), PA_RBS_ELEMENT_MAP and PA_RBS_ELEMENT_MAP_S (element-level mapping), PA_RBS_MAPPING_RULES and PA_RBS_MAPPING_RULE_S (the rule sets the user searched for), PA_RBS_HEADERS_B, PA_RBS_VERSIONS_B, PA_RBS_PRJ_ASSIGNMENTS, PA_RBS_ELEM_IN_TEMP, PA_RBS_PLANS_IN_TMP, PA_RBS_PLANS_OUT_TMP, and PA_RBS_TXN_ACCUM_MAP. Transaction-side access covers PA_EXPENDITURE_CATEGORIES, PA_EXPENDITURE_TYPES, PA_EVENT_TYPES, PA_PJT_EVENTS, PA_PJI_PROJ_EVENTS_LOG, PA_BUDGET_VERSIONS, PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_CLASSES_B, and PA_RES_TYPES_B. The PJI_* tables support aggregation and denormalization into the Project Intelligence summary structures.

Usage Notes

PA_RBS_MAPPING is invoked from Project Billing and Project Costing concurrent programs that process RBS mapping, and from Project Intelligence extraction and summarization jobs. The package is not referenced by any other database object, and it is a leaf dependency, meaning it is called directly by form logic and concurrent program execution rather than through a wrapper. Its functions may be leveraged in custom PL/SQL where resource-type resolution is required, but because it is classified as an internal engine, direct calls should be treated as unsupported and validated against patch levels in 12.1.1 and 12.2.2.