Search Results tplo_city

Overview

APPS.POA_DNB_LTPRT is a small, single-purpose PL/SQL package body that belongs to the Oracle Advanced Procurement / Trading Partner integration area (the "POA" prefix denoting a procurement/partner application component, and the "DNB" reference linking it to Dun & Bradstreet trading partner data). Its documented purpose is to extract a formatted, flat-file listing of all trading partner locations that have been classified as vendor sites, and to write that listing to an output file named POALTPRT.out. In effect it acts as a data-export utility that surfaces address and postal information for downstream consumption by external partner-registration or data-synchronization processes.

The package is classified as OTHER in the ETRM catalogue rather than as a public API, which indicates it is an internal or administrative utility rather than a supported integration interface. The header comment dates the source file to 2005, meaning the logic predates and has been carried forward largely unchanged into the EBS 12.1.1 and 12.2.2 code lines. Notably for a user arriving via a search on the TPLO_POSTAL_CODE column, the package is precisely the code path that reads and emits that column.

Key Procedures and Functions

• POA_LIST_ALL_TPRT — The sole documented procedure, taking standard concurrent-program style arguments for error buffer and return code. It opens a cursor over the EDW_TRD_PARTNER_M table restricted to rows where the business type is "VENDOR SITE" and the level name is "LOCATION", then iterates the result set and emits one comma-separated, double-quoted output line per trading partner location.
• Each output line contains the trading partner location primary key, name, four address lines, county, city, state or province, country, and finally the postal code (TPLO_POSTAL_CODE). The state value is coalesced with province, so a single column carries whichever applies.
• Logging is delegated to the POA_LOG package, which records debug lines, writes the output, and marks the run as SUCCESS or ERROR. On an unhandled exception the procedure captures SQLERRM and SQLCODE into the error and return buffers, rolls back, logs the failure, and returns without raising.

Tables Accessed

The package reads a single documented table, EDW_TRD_PARTNER_M, accessed through an APPS synonym. This is an Enterprise Data Warehouse staging or reporting table holding trading partner master data, including the location-level attributes consumed here. The package performs no inserts, updates, or deletes against business tables; the only transactional statement is a ROLLBACK in the exception handler. The query filters on TPLO_BUSINESS_TYPE and TPLO_LEVEL_NAME and projects the TPLO_ prefixed location columns, with TPLO_POSTAL_CODE being the postal code attribute relevant to the user's search.

Usage Notes

Given its structure — error buffer and return code parameters, verbose logging, and flat-file output — the procedure is designed to be invoked as a concurrent program, most likely through a host or SQL*Plus submission that captures the POALTPRT.out file for external distribution. It may also be called from custom code or a wrapper script when a point-in-time extract of vendor-site addresses is required.

Because the package is not classified as a public API and is referenced by no other documented packages, direct calls should be treated as unsupported: Oracle may change or remove it without notice during patching or upgrade. Developers who need the same trading partner address data for 12.1.1 or 12.2.2 should prefer querying EDW_TRD_PARTNER_M directly or using officially supported partner APIs, treating POA_DNB_LTPRT as a reference implementation rather than a stable integration point.