Search Results update_structures_setup_attr




Overview
Explore in AI Chat

Overview

PA_PROJECT_STRUCTURE_PUB1 is a public PL/SQL package in the Oracle EBS Projects (PA) module that exposes the programmatic interface for managing project work structures and project structure versions. In Oracle Projects, a project structure represents the hierarchical work breakdown — workplans, task structures, and financial structures — against which budgets, expenditures, and commitments are planned and collected. This package provides the application programming interface (API) layer that forms, self-service pages, and concurrent programs call to create, copy, version, publish, delete, and financially enable or disable those structures without writing directly to the underlying PA tables.

Because structure maintenance is tightly coupled to project setup and to the financial roll-up of costs, the package centralizes validation, version control, and attribute handling. Its header indicates an internal global variable for the current user id and a check routine that gates whether a given action is permitted against a version id and status code, reflecting the workflow-driven lifecycle of structure versions.

Key Procedures and Functions

The documented interface contains twenty-four procedures and functions. The following groupings reflect their documented purpose:

  • CHECK_ACTION_ALLOWED — function that evaluates whether an action is permitted for a given structure version and status code, enforcing the structural workflow rules.
  • SetGlobalUserId / GetGlobalUserId — maintenance routines for the package-level global that stores the current user id, ensuring audit columns and security context are populated during API calls.
  • Create_Structure — creates a new project structure, accepting structure name, number, description, calling flag, and ten descriptive flexfield attribute columns.
  • Create_Structure_Version / Create_Structure_Version_Attr — create a new version of an existing structure, with a variant that populates version-level attributes.
  • Update_Structure / Update_Structure_Version_Attr — modify structure headers and version attribute values.
  • Update_Structures_Setup_Attr — the routine directly associated with the user's search; it updates structure setup attributes, typically the configuration options governing how a structure behaves during setup and financial processing.
  • Delete_Structure_Version / Delete_Working_Struc_Ver — remove versions, including deletion of a working (unpublished) version.
  • Publish_Structure — promotes a structure version to published status so it can be used in planning and execution.
  • Copy_Structure / Copy_Structure_Version — copy an existing structure or a specific version as the basis for a new one.
  • Submit_Workplan / Rework_Workplan / Update_Workplan_Versioning — orchestrate the workplan lifecycle, including submission and rework, and control versioning behavior for workplans.
  • Enable_Financial_Structure / Disable_Financial_Structure / Clear_Financial_Flag — control whether a structure is used to collect and roll up financial transactions, and clear the associated indicator.

Tables Accessed

The package operates primarily on the Projects structure tables: PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_SCHEDULE store the structure elements, their versions, and scheduling data; PA_PROJECTS_ALL provides the parent project context; PA_OBJECT_RELATIONSHIPS links structures to related objects. Financial and planning behavior draws on PA_PROJECT_TYPES_ALL, PA_BUDGET_VERSIONS, PA_COMMITMENT_TXNS, PA_EXPENDITURE_ITEMS_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_EXP_REPORT_DISTS_ALL to validate and consolidate costs and commitments against the structure. Supporting lookups include PA_PROJECT_CUSTOMERS, FND_USER for the global user context, and MTL_MATERIAL_TRANSACTIONS where project-related material activity is referenced.

Usage Notes

PA_PROJECT_STRUCTURE_PUB1 is normally invoked from Oracle Projects forms and self-service pages (the Workplan and project setup flows), from concurrent programs performing structure copy or versioning, and from custom extensions that need to create or maintain structures programmatically. Callers should set the global user id before invoking transactional routines and should honor the standard API conventions — API version, initialization of the message list, commit control, and validation-only mode — as reflected in the documented parameter comments. Because the package is referenced by ten other packages, changes to its behavior can cascade through integration points, so custom code should call the published procedures rather than manipulating PA structure tables directly.