Search Results itg_boapi_wrappers




Overview
Explore in AI Chat

Overview

ITG_BOAPI_WRAPPERS is an APPS-owned PL/SQL package that provides a consolidated wrapper interface for Oracle E-Business Suite integration points involving the ITG (Integration) product family. The package bundles together a set of low-level business object API calls, primarily drawn from the ITG_Sync*_PVT family of packages, and exposes them through a single, stable entry point. The "BOAPI" naming reflects its role as a Business Object API wrapper: rather than invoking each underlying synchronization or validation package directly, callers route through ITG_BOAPI_WRAPPERS, which standardizes the calling convention and manages transactional context.

The package also provides a bracketing mechanism for inbound processing. Procedures such as Begin_Wrapper and End_Wrapper establish and close a working context around a batch of related messages, while Reap_Messages handles cleanup of residual message records. Collectively, the package supports inbound synchronization of chart of accounts flex values, exchange rates, purchasing lines, vendors, items, UOM definitions, and PO numbers.

Key Procedures and Functions

  • BEGIN_WRAPPER — Opens a processing wrapper for a referenced document, capturing reference identifier, organization, document type, client type, and creation date, and marks the package as active.
  • END_WRAPPER — Closes the wrapper opened by BEGIN_WRAPPER. This is the procedure most commonly associated with the search term "end_wrapper." It finalizes the current document context, returns a client identifier plus standard return status and message outputs, and resets the active flag.
  • REAP_MESSAGES — Cleans up or harvests message records associated with a given reference, document, or creation date.
  • SYNC_FLEXVALUE — Wraps ITG_SyncCOAInbound_PVT to synchronize a chart-of-accounts flex value, including value set, description, effective/expiration dates, account type, and enabled flag.
  • PROCESS_EXCHANGERATE — Wraps ITG_SyncExchInbound_PVT to synchronize currency exchange rate definitions, including currencies, rate type, conversion factor, and effective date.
  • UPDATE_POLINE — Invokes the purchasing line update business object API with standard version, initialization, commit, and validation-level parameters, targeting a specific PO code, organization, release, line, document type, quantity, and amount.
  • SYNC_VENDOR, SYNC_VENDORSITE, SYNC_VENDORCONTACT — Synchronize supplier header, supplier site, and supplier contact records through the corresponding inbound business object APIs.
  • SYNC_ITEM — Synchronizes item master definitions.
  • PROCESS_PONUMBER — Processes purchase order number allocation or synchronization.
  • SYNC_UOM_ALL — Synchronizes the complete unit-of-measure definition set.

Tables Accessed

The ETRM metadata records no directly referenced tables for this package through APPS synonyms. This is expected, since ITG_BOAPI_WRAPPERS is a thin delegating layer: the substantive insert, update, and query activity against integration staging and interface tables occurs inside the ITG_Sync*_PVT packages and the purchasing business object APIs it calls. Message-related persistence is likewise managed through the underlying inbound processing packages rather than by ITG_BOAPI_WRAPPERS itself.

Usage Notes

The package is not intended for direct end-user invocation. It is typically called from inbound integration programs that parse external payloads, then invoke Begin_Wrapper, dispatch one or more SYNC or PROCESS procedures, and complete processing with End_Wrapper and Reap_Messages. Because it is a wrapper and not a seeded public API, no other documented packages reference it, indicating that callers are custom or legacy integration code rather than standard EBS product modules.

The default parameters on End_Wrapper — NULL reference and document values with a SYSDATE creation date — allow callers to close the currently active wrapper context without re-supplying identifying information. The NOCOPY output parameters reflect a performance-oriented signature intended for high-volume inbound synchronization runs. Because the source header comment dates to 2006 and carries a "noship" designation, the package should be treated as a custom or non-shipped artifact that is specific to the ITG integration implementation; any use in a 12.1.1 or 12.2.2 environment should be validated against the actual deployed package body, since ETRM documents classification only as OTHER.