Search Results ship_info_xd

Overview

APPS.PO_FED_FIELD_FUNCTIONS is a PL/SQL package in the Oracle E-Business Suite Purchasing (PO) module that serves the federal government extension of Oracle Procurement. Its principal business role is to populate and default the various federal-specific fields mandated by the Federal Acquisition Regulation (FAR) and related acquisition reporting requirements, covering information such as contracting office addresses, buyer and priority program designations, competitive sourcing data, item classification details, shipping information, and vendor customer designations. Rather than exposing these attributes through a single monolithic routine, the package is organized into a large set of narrowly scoped functions and procedures that the Purchasing user interface and business logic layers invoke independently. The object is registered in the APPS schema and confirmed with a VALID status, and it is documented in the ETRM as an API classified as OTHER. The package is referenced by five other packages, including PO_UDA_DEFAULTING_PKG, PO_AUTO_HEADER_PROCESS_PVT, PO_MULTI_MOD_PVT, PO_MULTI_MOD_VALIDATIONS, and PON_UDA_PKG, which indicates that it is deeply embedded in document defaulting, validation, and multi-organization modification flows rather than being an isolated utility.

Key Procedures and Functions

The documented interface exposes thirty-two procedures and functions. These are logically grouped as follows:

• Address routines: PR_ADDRESSDEF, PO_ADDRESSDEF, ADDRESS_XD, PO_ADDRESSES_XSC, PR_ADDRESSES_XSC, PR_ADDRESSES_XPD, PO_ADDRESSES_XPD, and ADDRESSES_XLE handle supplier and requisition address defaulting and derivation, supporting federal contracting office and delivery address requirements.
• Priority program and business unit information: BU_PRI_PRJ_INF_XLE, PR_BU_PRI_PRJ_INF_XPD, and PO_BU_PRI_PRJ_INF_XPD manage priority project or priority program indicators associated with requisition and purchase order business units.
• Federal customer designation: FED_CUST_DESG_XLE and PO_FED_CUST_DESG_XPD default and derive the federal customer designation attributes on purchasing documents.
• Item information: ADD_ITEM_INFO_XLE and ADD_ITEM_INFO_XD support additional item attribute capture.
• Shipping information: SHIP_INFO_XD and SHIP_INFO_XLE derive shipping-specific federal data.
• Sourcing and competitive information: PR_SOURCING_INFO_REQ_XPD, COMPETITIVE_INFO_XD, and COMPETITIVE_INFO_XV handle requisition sourcing data and competitive acquisition information used for federal reporting.

Parameter lists are not reproduced here; each routine is named according to the federal attribute block it services.

Tables Accessed

The package reads from a broad set of APPS synonyms reflecting the entities needed for federal defaulting and validation:

• Supplier and vendor data: AP_SUPPLIER_SITES_ALL, FV_CCR_VENDORS, and HZ_PARTIES provide supplier site, Central Contractor Registration, and party information.
• Location and party data: HR_LOCATIONS_ALL, HR_LOCATION_EXTRA_INFO, FND_TERRITORIES_TL, and HZ_PARTIES supply address and territory validation.
• Personnel and user data: PER_ALL_PEOPLE_F, PER_PEOPLE_EXTRA_INFO, and FND_USER identify buyers, requesters, and federal personnel assignments.
• Reference and lookup data: FND_LOOKUP_VALUES supplies federal code list values.
• Item and financial data: MTL_SYSTEM_ITEMS_TL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_PAYMENTS_ALL, and AP_CHECKS_ALL are referenced for item descriptions and for matching payments, invoices, and invoice distributions associated with federal acquisition reporting.

Usage Notes

PO_FED_FIELD_FUNCTIONS is invoked implicitly rather than directly by end users. It is called when the Purchasing forms or the AutoCreate process default federal fields onto requisitions, purchase orders, and purchase order releases; when multi-organization modifications and their validations run; and when User Defined Attribute defaulting logic executes through PO_UDA_DEFAULTING_PKG, PON_UDA_PKG, and PO_MULTI_MOD_PVT. Because the ETRM classifies it as OTHER rather than as a public API, custom code should treat it as an internal dependency and prefer supported extension points. Sites implementing federal acquisition reporting or the federal procurement extensions will see this package exercised routinely during document entry, document validation, and concurrent document processing.