Search Results print_line

Overview

GMF_SYNC_VENDOR is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM object register as an "OTHER" API type. Its purpose is to synchronize supplier (vendor) records held in the Process Manufacturing purchasing tables into the general ledger-relevant context defined by policy and organization data. The package is part of the GMF (Oracle Process Manufacturing) family of synchronization utilities that coordinate data between the Oracle Payables/Purchasing supplier model and the GL policy master used by Process Manufacturing. The header comment places the source at version 115.5, last shipped in December 2002, indicating the package has been stable across the 12.1.1 and 12.2.2 releases for which this documentation applies.

Key Procedures and Functions

The ETRM documentation records three procedures and functions within this package:

• GMF_SYNC_VENDOR — The principal entry point. It accepts an output error buffer, an output return code, and an input company/organization code (p_co_code), and drives the vendor synchronization loop. Internally it caches and resets the GL_LOG_TRIGGER_ERROR session variable, and processes vendor sites for the resolved organization. Bug 1677297 enhanced this procedure to track individual vendor_id, vendor_site_code, and segment1 values, and to accumulate counts of successfully synchronized and failed vendors.
• PRINT_LINE — A diagnostic output procedure used to write a single formatted line to the request or debug output log. Because this procedure is invoked by name and by convention in legacy GMF synchronization utilities, requesters searching for "print_line" are typically looking for this routine when tracing logged synchronization output.
• PRINT — The companion diagnostic output procedure that writes an unformatted message or buffer to the same output destination, generally used for banner or status messages surrounding the line-level output.

Parameter lists are not enumerated in the available metadata; only procedure and function names are documented, and no parameter details should be assumed beyond those appearing in the source excerpt.

Tables Accessed

The documented tables referenced through APPS synonyms are:

• FND_PRODUCT_GROUPS — Read by the cursor c_gl_plcy_mst to determine the multi-org flag, which governs whether the resolved organization identifier is applied to the synchronization scope.
• GL_PLCY_MST — The GL policy master, joined in the same cursor to resolve the organization (org_id) associated with the supplied company code.

In addition, the source excerpt references PO_VENDOR_SITES_ALL (cursor c_po_vendor_sites_all), PO_VENDORS (cursor c_po_vendors), and GMF_SESSION_VARS for the GL_LOG_TRIGGER_ERROR cache. These are visible in the code but are not part of the ETRM documented table list, and are noted here only as they appear in the excerpt.

Usage Notes

GMF_SYNC_VENDOR is typically invoked as a background synchronization step after supplier records are created or modified in the purchasing model, either from a concurrent program, from Process Manufacturing setup forms, or from custom code performing supplier maintenance for a specific company code. Because it operates with FOR UPDATE locking on PO_VENDOR_SITES_ALL and manipulates the GL_LOG_TRIGGER_ERROR session variable, it is intended for controlled batch execution rather than high-concurrency interactive use. The error_buf and retcode output parameters make it suitable for programmatic invocation where callers must capture success or failure. ETRM records no other packages referencing this unit, so callers are expected to be applications or concurrent programs rather than dependent PL/SQL packages.