Search Results create_object

Overview

APPS.RCV_SHIPMENT_OBJECT_SV is a server-side PL/SQL specification (package header) that defines the high-level record types, cursor declarations, and package-level variables used by the Receiving Open Interface (ROI) processing infrastructure in Oracle E-Business Suite. The package is declared with AUTHID CURRENT_USER and, as stated in its header comments, "contains the server side APIs: high-level record types, cursors and record type variables." It does not itself perform the receipt-creation transaction logic; rather it serves as the shared declaration layer consumed by the body and by sibling packages in the receiving stack.

The package sits within the RCV module and underpins the inbound ASN, ASBN, and standard receipt flows that feed RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE. Its cached g_is_edi_installed flag, introduced to address a performance issue, reflects the package's role in optimizing repeated validation calls during high-volume receipt processing.

Key Procedures and Functions

The documented procedure/function list for this package contains a single named entry, NAME, and the ETRM record identifies no additional public API members. The substantive content of the package specification is declarative rather than procedural:

• ErrorRecType — a record type capturing error_status and error_message, used to return standardized error information to callers.
• c1 — a cursor over RCV_HEADERS_INTERFACE implemented to support parallel processing of the RVCTP concurrent program. It selects header rows by request ID and group ID, restricted to ASN, ASBN, and STD transaction types, and locks rows FOR UPDATE OF processing_status_code NOWAIT.
• c2 — a cursor over RCV_TRANSACTIONS_INTERFACE that returns transaction rows for a given header interface ID, projecting unit of measure class, ship-to organization, receipt exception code, and error code into a normalized shape.
• cascaded_trans_rec_type — a record type supporting the cascading transaction structures used during receipt propagation.

Package-level variables including uom_class, ship_to_org_id, receipt_code, error_code, and error_text are anchored to PO_LINE_LOCATIONS columns via %TYPE, ensuring the receiving logic remains aligned with purchasing data structures.

Tables Accessed

The package specification references the following objects through APPS synonyms:

• RCV_HEADERS_INTERFACE — the receipt header staging table, read and row-locked by cursor c1 during concurrent ROI processing.
• RCV_TRANSACTIONS_INTERFACE — the transaction staging table, read by cursor c2 to supply validated receipt lines.
• PO_LINE_LOCATIONS — read for unit of measure class, ship-to organization, and receipt exception code, and used as the anchor for %TYPE declarations.
• RCV_SHIPMENT_HEADERS — the destination shipment header table consulted in the receiving flow.
• PLITBLM — a PL/SQL index-by table type typically used for bulk collections.

Usage Notes

RCV_SHIPMENT_OBJECT_SV is not an application-facing API and is not invoked directly from Oracle Forms. It is consumed internally by the Receiving Open Interface (ROI) receive transaction processor (RVCTP) and by packages that build and validate receipt records prior to insert into the interface tables. The parallel-processing cursor c1 allows multiple RVCTP workers to divide interface header rows by request ID and group ID safely, using NOWAIT locking to prevent contention.

Custom code should generally not call this specification directly. Developers extending receipt processing should target the documented receiving APIs and rely on this package only as the shared type and cursor library that the standard ROI flow depends upon. Because the specification is compiled with AUTHID CURRENT_USER, privilege resolution follows the invoker, which is significant when custom wrappers invoke dependent receiving packages. The package is referenced by a substantial number of other packages, so any modification to its declarations carries broad recompilation impact.