Search Results rosetta_table_copy_in_p0

Overview

APPS.EAM_OBJECTINSTANTIATION_PUB_W is a thin wrapper package body belonging to the Enterprise Asset Management (EAM) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its dedicated purpose is to bridge the strongly typed PL/SQL collection used by the published EAM object instantiation API and the generic, weakly typed JTF_NUMBER_TABLE structure consumed by Oracle's integration and RosettaNet-style messaging layer. The package name and the "Rosetta" procedure naming convention identify it as generated adapter code produced by the EBS integration framework, which automatically emits complementary *_PUB_W wrappers for every public API that participates in message-based outbound and inbound flows.

The $Header line, EAMWOBIB.pls 115.0 2003/09/08, indicates that the file was created for the EAM work-order BIB (Business Integration Broker) interface and has remained stable since that release. It is not a business-logic package; it performs no validation, no DML, and no EAM processing of its own. All substantive behavior resides in the parent specification package, EAM_OBJECTINSTANTIATION_PUB.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P0 — Converts an inbound JTF_NUMBER_TABLE into the EAM-specific association_id_tbl_type collection expected by the public API. It iterates the source table from FIRST to LAST using NEXT, assigning each element to a dense target index starting at 1. A guard skips processing when the source is null or empty, so the target remains unpopulated in that case.
• ROSETTA_TABLE_COPY_OUT_P0 — Performs the inverse conversion, populating an outbound JTF_NUMBER_TABLE from an EAM association_id_tbl_type instance. The target is first initialized to an empty JTF_NUMBER_TABLE, then extended by t.COUNT and filled positionally. Sparse source collections are handled correctly because the loop walks the source using t.FIRST and t.NEXT while writing densely to the target.

Both procedures are declared as PUBLIC in the wrapper and exist solely as plumbing for the integration layer. No default values, business rules, or error handling beyond null checks are present.

Tables Accessed

The ETRM metadata records a single referenced object via an APPS synonym: PLITBLM. PLITBLM is the standard EBS PL/SQL table-of-number storage used by the Forms and integration infrastructure to marshal numeric collections across program units. In this package it is relevant only insofar as JTF_NUMBER_TABLE shares the same underlying numeric-table representation; the package itself issues no SQL against database tables and performs no inserts, updates, or deletes. No EAM transactional tables (for example, work orders, asset associations, or instantiation staging tables) are touched by these procedures.

Usage Notes

EAM_OBJECTINSTANTIATION_PUB_W is invoked exclusively by generated integration code, not by end users. Typical call paths include Business Integration Broker message processing, XML Gateway inbound/outbound maps, and any custom concurrent program or form that has been built against the EAM object instantiation public API and needs to pass or receive association identifiers as a generic numeric table.

• Called during outbound message construction, where an EAM collection must be flattened into JTF_NUMBER_TABLE before serialization.
• Called during inbound message consumption, where a JTF_NUMBER_TABLE arriving from the messaging layer must be converted into the typed EAM collection.
• Referenced by one other package in the ETRM dependency map, confirming its role as a leaf-level adapter rather than a service entry point.

Because the wrapper is versioned at 115.0 and marked noship, it should be treated as internal infrastructure. Customizations should call EAM_OBJECTINSTANTIATION_PUB directly and rely on the wrapper only through the standard integration stack, particularly since the procedures are positional, do not preserve source index values, and assume contiguous dense assignment in the target collection.