Search Results manage_processes

Overview

AMW_SCOPE_PVT_W is a private PL/SQL package in the APPS schema that underpins the scope-management engine used by Oracle E-Business Suite's Asset Management and related resource-scheduling modules. It is part of the AMW ("Asset Management Workbench") family of packages, whose responsibility is to determine and persist the operational scope — the set of subsidiary organizations, lines of business (LOBs), organizations, and business processes — that a given user, responsibility, or scheduling activity is permitted to work with. The package therefore acts as the runtime engine behind the "scope" concept that restricts and de-normalizes the organizational hierarchy used elsewhere in the Asset Management flow.

The "_W" suffix identifies this as a wrapping package, meaning its procedures are designed to expose PL/SQL table types to callers — typically Oracle Forms or OAF-based pages — across the client/server boundary. The pairing of rosetta_table_copy_in_* and rosetta_table_copy_out_* procedures is characteristic of EBS's "Rosetta" marshalling convention, where collections are copied between JDBC-style typed tables and the internal PL/SQL table types defined in the companion AMW_SCOPE_PVT package.

Key Procedures and Functions

The package exposes 22 documented procedures, which fall into three functional groups.

• Rosetta table copy procedures — ROSETTA_TABLE_COPY_IN_P1/OUT_P1 through ROSETTA_TABLE_COPY_IN_P13/OUT_P13 marshal collection data across the deployment boundary. Each numbered pair corresponds to one of the collection types declared in AMW_SCOPE_PVT (subsidiary, LOB, organization, process, and process-hierarchy tables). The "_IN_" variants copy an external varchar or number table into the package's internal table type; the "_OUT_" variants perform the reverse operation. The P13 pair is notable for handling a four-column process-hierarchy structure.
• Scope population procedures — POPULATE_CUSTOM_HIERARCHY, GENERATE_ORGANIZATION_LIST, GENERATE_SUBSIDIARY_LIST, and GENERATE_LOB_LIST build the specific scope lists required by a caller. These are the "populate_denormalized_tables" style routines that flatten hierarchical relationships into denormalized, read-optimized lists enabling fast filtering and display.
• POPULATE_PROCESS_HIERARCHY — constructs the multi-level process hierarchy used by process-driven scope filters, resolving parent/child relationships into a navigable structure.
• ADD_SCOPE — the primary entry point for committing a newly defined scope. It carries the standard EBS API signature, including API version number, message list initialization, commit flag, and validation level, and is designed to be called from concurrent or UI code that needs to persist a scope definition atomically.

Tables Accessed

The only table directly referenced in the documented metadata is PLITBLM (via its APPS synonym). PLITBLM is one of the standard EBS "PL/SQL table" shadow tables used to persist PL/SQL index-by tables across session boundaries and to support the Rosetta marshalling of collections. Its role here is to hold the intermediate scope collections (subsidiaries, LOBs, organizations, processes) while GENERATE_* procedures populate them. Other tables referenced indirectly through AMW_SCOPE_PVT are not documented in the excerpt.

Usage Notes

AMW_SCOPE_PVT_W is not a public API and is not directly referenced by any other documented package (0 referencing packages). It is invoked indirectly by the presentation layer — typically EBS Forms or OAF pages in the Asset Management scope-setup UI — as well as by concurrent programs that regenerate scope caches after organizational changes. Because it is a wrapper, custom code should call the underlying AMW_SCOPE_PVT procedures rather than this wrapper directly; direct calls risk Rosetta table-type mismatches across EBS patch levels. The package's API version and validation-level parameters should always be supplied when invoking ADD_SCOPE from custom extensions.