Search Results rosetta_table_copy_in_p7

Overview

APPS.EAM_WORKORDER_UTIL_PKG_W is a wrapper package in Oracle Enterprise Asset Management (eAM) that provides the public, interface-facing surface for work order utility logic. The trailing "_W" convention indicates a wrapper layer: the substantive business logic resides in EAM_WORKORDER_UTIL_PKG, while this package exposes a set of conversion and helper routines that are safe to invoke from outside the eAM schema, including from Java, OAF, or other PL/SQL consumers. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the defining schema, which requires invoking sessions to hold the necessary privileges on the underlying objects. Its header revision ($Header: EAMVWUPS.pls 120.0.12020000.2 2012/11/07) places the current artifacts within the 12.1.1 and 12.2.x release lineage. The bulk of the package body consists of generated "Rosetta" array marshalling routines used to translate between Oracle EBS collection types and the nested table types defined in EAM_WORKORDER_UTIL_PKG.

Key Procedures and Functions

The 16 documented routines fall into three functional groups.

• ROSETTA_TABLE_COPY_IN_P4 / _OUT_P4 — Convert between ten parallel scalar collection parameters and the eAM BOM table type (t_bom_table). The IN variant loads a nested table from the JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE collections; the OUT variant reverses the direction for results returned to the caller.
• ROSETTA_TABLE_COPY_IN_P5 / _OUT_P5 — The same conversion pattern for the eAM component table type (t_component_table), comprising nine parameters including a JTF_DATE_TABLE element.
• ROSETTA_TABLE_COPY_IN_P6 / _OUT_P6, _P7 / _OUT_P7, and _P30 / _OUT_P30 — Additional Rosetta conversion pairs for the operation time table (t_optime_table) and other internal eAM collection types referenced by the utility package. The numeric suffixes correspond to the ordinal of each type in the generated conversion set rather than to any business meaning. ROSETTA_TABLE_COPY_OUT_P30, the routine matching the user's search, is therefore the outbound marshalling routine for the thirtieth collection signature in this wrapper.
• RETRIEVE_ASSET_BOM — Returns the asset bill of materials applicable to a given asset or work order context.
• COPY_TO_BOM — Persists work order material requirements into the BOM structures used by eAM.
• ADJUST_OPERATIONS — Reconciles or adjusts work order operations records.
• DEPENDENCY_VIOLATED — Evaluates whether a proposed change violates an operation dependency rule.
• GET_WORKFLOW_DETAILS — Retrieves workflow metadata associated with an eAM work order.
• GET_REPLACED_REBUILDS — Identifies rebuildable items that have been replaced, supporting repair-versus-replace decisions.

Tables Accessed

The documented synonym reference is PLITBLM, the standard EBS table used by the Rosetta conversion infrastructure to buffer PL/SQL index-by and nested table transfers. The remaining tables touched by the package are reached indirectly through EAM_WORKORDER_UTIL_PKG's BOM, component, and operation interfaces and are not enumerated in the wrapper metadata. Because the package is AUTHID CURRENT_USER, grants on these underlying objects must be present for the calling schema.

Usage Notes

This package is not an end-user API and carries an API classification of OTHER, indicating no formal public API guarantee. It is invoked indirectly: eAM work order forms, the eAM concurrent programs that process bills of material and operations, and any custom OAF or Java integration that must pass collection data across the JDBC boundary rely on the Rosetta IN/OUT pairs for type conversion. The package is referenced by zero other packages, confirming it sits at the outer edge of the dependency graph. Customizations should not call the Rosetta routines directly unless the calling code already works with the JTF collection types; application logic should instead target EAM_WORKORDER_UTIL_PKG. Because the header dates to 2012 and the specification is generated, the wrapper is stable across 12.1.1 and 12.2.2, but the same is not guaranteed for the underlying utility package.