Search Results validate_resource_info

Overview

PA_FP_WEBADI_UTILS is a utility package in the Oracle E-Business Suite Projects (PA) module that supports the WebADI-based upload and maintenance of financial plan data — budgets and forecasts. WebADI (Web Application Desktop Integrator) allows users to work with project financial plan information in a spreadsheet, validate and upload it back into EBS, and receive structured error feedback. This package supplies the shared validation, metadata retrieval, and data-cleanup logic that the WebADI financial plan upload flow depends on.

The package is owned by APPS and classified as an "OTHER" API rather than a public open interface. It is referenced by three other packages and operates primarily against financial plan tables such as PA_BUDGET_VERSIONS, PA_BUDGET_LINES, and the WebADI staging tables PA_FP_WEBADI_UPLOAD_INF and PA_FP_WEBADI_XFACE_TMP. The delete_interface_tbl_data entry point that users commonly search for corresponds to the DELETE_INTERFACE_TBL_DATA procedure, which purges stale rows from the WebADI interface (staging) tables between upload attempts.

Key Procedures and Functions

The package exposes 20 documented procedures and functions. Principal entries include:

• GET_METADATA_INFO — Returns the WebADI integrator configuration details for a budget version, including content, mapping, layout, and integrator codes, plus flags for rejected lines and budget/forecast submission and an error message code.
• VALIDATE_BEFORE_LAUNCH — Performs pre-launch checks on a budget version before the WebADI upload is initiated.
• CONVERT_TASK_NUM_TO_ID — Resolves a user-entered task number to its internal task identifier.
• VALIDATE_CURRENCY_CODE / VALIDATE_TXN_CURRENCY_CODE — Confirm that supplied currencies are valid for the budget version or transaction context.
• VALIDATE_RESOURCE_INFO — Validates resource group and alias information for uploaded lines.
• GET_RES_ASSIGNMENT_INFO — Retrieves resource assignment details for planning lines.
• VALIDATE_CHANGE_REASON_CODE — Checks change reason codes used in forecast/budget adjustments.
• GET_VERSION_PERIODS_INFO — Returns period-level information for a budget version.
• CHECK_OVERLAPPING_DATES — Detects overlapping date ranges in plan data.
• GET_MC_ERROR_LOOKUP_CODE / CONV_MC_ATTR_MEANING_TO_CODE — Translate descriptive attribute meanings to lookups/codes for multi-currency handling.
• GET_AMOUNT_TYPE_NAME, GET_LAYOUT_DETAILS — Retrieve descriptive metadata for amount types and WebADI layout definition.
• DELETE_INTERFACE_TBL_DATA — Deletes rows from the WebADI interface/staging tables, typically used to clear prior upload data.
• RESUBMIT_CONC_REQUEST — Re-submits a concurrent request associated with the upload.
• GET_CURRENT_AMOUNT, GET_ORIGINAL_AMOUNT, GET_PRIOR_FORECAST_AMOUNT, GET_PERIOD_AMOUNTS — Return budget/forecast amount values for the current, original, prior-forecast, and period-level views.

Tables Accessed

The package reads and writes against several core Projects and WebADI tables via APPS synonyms:

• PA_BUDGET_VERSIONS, PA_BUDGET_LINES, PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LIST_MEMBERS, PA_TASKS — financial plan definition, line, and resource assignment data.
• PA_FIN_PLAN_TYPES_B, PA_PROJ_FP_OPTIONS, PA_AMOUNT_TYPES_B — plan type, financial plan option, and amount type metadata.
• PA_FP_TXN_CURRENCIES — transactional currency definitions.
• PA_FP_WEBADI_UPLOAD_INF, PA_FP_WEBADI_XFACE_TMP — staging/interface tables for the WebADI upload; DELETE_INTERFACE_TBL_DATA operates here.
• BNE_INTEGRATORS_B, BNE_LAYOUTS_B, BNE_LAYOUTS_TL, FND_APPLICATION — WebADI integrator and layout definitions and application lookup.

Usage Notes

PA_FP_WEBADI_UTILS is not intended as a standalone public API. It is invoked by the WebADI financial plan upload flow — from the WebADI integrator/Java layer, its calling packages (three documented referrers), and the concurrent programs that process uploads. DELETE_INTERFACE_TBL_DATA is most commonly called to clear staging rows from PA_FP_WEBADI_UPLOAD_INF and PA_FP_WEBADI_XFACE_TMP prior to a fresh upload, preventing duplicate or stale lines. Custom code should treat this package as internal (limited support, "OTHER" classification); direct calls risk incompatibility across patches, so developers typically use supported financial plan APIs instead.