Search Results res_map

Overview

PA_RLMI_RBS_MAP_PUB is a public PL/SQL API in the Oracle E-Business Suite Projects (PA) module that resolves and maintains the relationship between resource list members, RBS (Resource Breakdown Structure) elements, and budget versions. Its core business function is to derive the correct Resource List Member Id (RLMI) and RBS element Id for a given resource list Id or RBS version Id, ensuring that planning and budgeting data remains consistent across the project structure. The package header carries the identifier PAFPUT3S.pls 120.1, indicating a long-standing API surface within the Projects foundation layer.

The package is classified as a PUB (public) API, meaning Oracle supports calling it from custom code under the documented interface. Its dual-purpose design is driven by the p_process_code parameter: a value of RES_MAP triggers resource mapping, while RBS_MAP triggers RBS element mapping. This makes the package the primary entry point for synchronizing resource and RBS assignments during budget generation, RBS refresh, and project copy operations.

Key Procedures and Functions

The documented API exposes seven procedures and functions:

• MAP_RLMI_RBS — the principal driver procedure, accepting budget version, project, resource list, and RBS version identifiers alongside calling context, mode, and message-list control flags. It dispatches to the appropriate mapping logic based on the process code.
• INIT_REQDVARIABLES — initialization routine that prepares the required internal variables and working state before mapping is performed. The search term "init_reqdvariables" corresponds directly to this procedure.
• POPULATE_RBSMAP_TMP — populates the temporary structures used for RBS mapping.
• POPULATE_RESMAP_TMP — populates the temporary structures used for resource mapping.
• POPULATE_RESRBSMAP_OUTTBLS — writes resolved mapping results into the output tables.
• PUSH_RBS_VERSION — propagates RBS version data as part of the mapping workflow.

Parameter lists are intentionally omitted here; the only signatures visible in the excerpt belong to MAP_RLMI_RBS and should be referenced directly from the package specification before implementing custom calls.

Tables Accessed

The package reads and writes a broad set of Projects and inventory tables through APPS synonyms. Core project and planning tables include PA_PROJECTS_ALL, PA_BUDGET_VERSIONS, PA_RESOURCE_ASSIGNMENTS, and PA_PROJ_ELEMENT_VERSIONS. Resource and RBS configuration is sourced from PA_NON_LABOR_RESOURCES, PA_RBS_VERSIONS_B, PA_PLAN_RES_DEFAULTS, and PA_PROJ_FP_OPTIONS. Temporary working tables PA_RBS_PLANS_IN_TMP and PA_RBS_PLANS_OUT_TMP hold intermediate results during mapping, while MTL_ITEM_CATEGORIES links inventory items to the resource structure. Expenditure classification draws on PA_EXPENDITURE_CATEGORIES and PA_EXPENDITURE_TYPES, and event logging uses PA_EVENT_TYPES in conjunction with the PA_DEBUG logging utilities referenced in the header notes.

Usage Notes

MAP_RLMI_RBS supports several calling processes (BUDGET_GENERATION, RBS_REFRESH, COPY_PROJECT), contexts (PLSQL, SELF_SERVICE), and modes (PLSQL_TABLE, BUDGET_VERSION). When the calling mode is BUDGET_VERSION, values passed through the PL/SQL and system table parameters are ignored. The p_txn_source_id_tab collection must be populated with unique values. Logging behavior depends on context: SELF_SERVICE routes messages to PA_DEBUG.WRITE_LOG(), while PLSQL uses PA_DEBUG.write_file(). The package is referenced by seventeen other packages, confirming its role as a shared dependency across Projects budgeting and resource planning flows.