Search Results get_drafts_addressxml

Overview

PO_XML_FPDSNG_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the generation of XML payloads for federal procurement reporting, specifically the FPDS-NG (Federal Procurement Data System – Next Generation) extract. The package name reflects its role in producing FPDS-oriented XML fragments from Purchasing document data. It is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the calling user rather than the definer, and it is classified under the ETRM API classification of OTHER.

The package assembles address, contact, and descriptor-flexfield (DFF) information for purchasing documents and their associated draft records. This is a common requirement when purchasing transactions must be transmitted or archived in a structured XML format that conforms to external reporting schemas, where organization addresses, vendor contacts, and user-defined attribute groups must be assembled into discrete XML fragments. The header comment references PODTFPDS.pls, confirming the package belongs to the Purchasing FPDS code family.

Key Procedures and Functions

The documented interface consists of fourteen functions, organized around several functional groupings:

• Location resolution: GET_LOCATION_ID and GET_LOCATION_NAME resolve the inventory organization location identifier and its descriptive name from an organization identifier.
• Header UDA XML: GET_UDA_HEADER_XML returns an XMLTYPE containing user-defined attribute header data, while GET_UDA_HEADER_DRAFTS_XML returns the equivalent payload for a specified draft header.
• Contacts XML: GET_CONTACTSXML and GET_DRAFTS_CONTACTSXML return CLOB contact fragments for a purchasing document and for a draft header respectively.
• Address XML: GET_ADDRESSXML and GET_DRAFTS_ADDRESSXML return CLOB address fragments. GET_DRAFTS_ADDRESSXML is the function matching the search term "get_drafts_addressxml": it produces the address XML specifically for a draft purchasing document identified by header identifier.
• Amount aggregations: GET_HEADER_AMOUNT_ORDERED, GET_LINE_AMOUNT_ORDERED, and GET_WITHOUT_OPT_AMOUNT_ORDERED compute ordered amounts at header, line, and option-excluded levels.
• Vendor detail XML: GET_VENDOR_ADDRESS_DETAILS and GET_VENDOR_CONTACT_DETAILS return CLOB fragments for vendor address and contact details based on a UDA template, header, and draft identifier.
• Issuing office: GET_ISSUING_OFF_LOC_CODE returns the issuing office location code for a header and draft combination.

The package also declares several package-level variables, including P_ATTR_GROUP_COL_LIST, HEADERID, p_draft_id, carId, include_sgd, and is_doc_mod, used as internal state or parameter defaults.

Tables Accessed

The package references the following documented objects through APPS synonyms:

• PO_HEADERS_ALL and PO_HEADERS_ALL_EXT_B — the core purchasing document header and its extension table, supplying document identification and header-level attributes.
• PO_UDA_AG_TEMPLATES and PO_UDA_AG_TEMPLATE_USAGES — user-defined attribute group templates and their usages, driving selection of UDA-based address, contact, and attribute group content.
• FND_DESCR_FLEX_COLUMN_USAGES, EGO_FND_DF_COL_USGS_EXT, and EGO_FND_DSC_FLX_CTX_EXT — descriptor flexfield column usage and context extension metadata used to resolve attribute group columns and contexts.
• XMLTYPE and DBMS_LOB — Oracle data types and the LOB PL/SQL package used to construct and manipulate XML and CLOB output.
• DUAL — used for singleton expression evaluation.

Usage Notes

PO_XML_FPDSNG_PKG is not invoked by any other documented package (referenced by 0 packages), indicating it is a top-level utility called directly rather than a nested dependency. In practice, the functions are invoked by the FPDS extraction program or by custom XML generation code that assembles the complete reporting document from the individual address, contact, UDA, and amount fragments this package returns. Because outputs are CLOB or XMLTYPE, callers typically concatenate the fragments into a larger XML envelope before transmission or archival.

Consumers should note the distinction between live document and draft variants: functions prefixed with GET_DRAFTS_ accept a header identifier and target in-progress draft documents, whereas their unprefixed counterparts operate on committed purchasing documents. Customizations that extend FPDS output should reuse these functions rather than reimplementing address and contact assembly, since they encapsulate the required flexfield context and template resolution logic.