Search Results create_translations




Overview
Explore in AI Chat

Overview

PO_ATTRIBUTE_VALUES_PVT is a private (PVT) PL/SQL package in the Oracle Purchasing application schema (APPS) that manages descriptive and functional attribute values associated with purchasing documents. Its scope spans blanket agreements, quotations, requisition templates, and standard purchase order lines. In Oracle EBS 12.1.1 and 12.2.2, extensible attributes are stored separately from the core document lines so that category-level, item-level, and manually entered attribute metadata can be captured without altering the PO_LINES structure. This package encapsulates the logic required to create, copy, translate, retrieve, update, and delete those attribute value records, and to move attribute data from the Purchasing interface tables into the base transaction tables during import.

The package is classified as private, meaning it is intended to be called by other Purchasing APIs and concurrent programs rather than directly by end users. The presence of the 120.12.12010000.3 version header indicates the file was last shipped under the 12.1 code line, and the same interface remains in use through 12.2.2.

Key Procedures and Functions

The documented API exposes seventeen procedures. The central entry point is HANDLE_ATTRIBUTES, which processes attribute values for an interface header and optionally links them to an existing PO header, with an optional language argument. TRANSFER_INTF_ITEM_ATTRIBS moves item-level attribute rows from the interface into the transactional tables. CREATE_DEFAULT_ATTRIBUTES generates default attribute value records for a given document type (BLANKET, QUOTATION, or REQ_TEMPLATE), keyed by PO line, requisition template name and line number, item category, inventory item, organization, and description. CREATE_DEFAULT_ATTRIBUTES_MI provides a multi-language (MLS/translation) variant of the same defaulting logic, while CREATE_ATTRIBUTES_TLP_MI and CREATE_TRANSLATIONS build the translation rows held in PO_ATTRIBUTE_VALUES_TLP.

UPDATE_ATTRIBUTES and UPDATE_ATTRIBUTES_MI maintain existing attribute values and their translated equivalents. COPY_ATTRIBUTES replicates attribute values, typically when a line is duplicated or a document is copied. DELETE_ATTRIBUTES removes attribute values at the line level, and DELETE_ATTRIBUTES_FOR_HEADER removes all attribute values belonging to a document header. GEN_DRAFT_LINE_TRANSLATIONS produces draft translation rows for lines. The query functions GET_IP_CATEGORY_ID, GET_ITEM_ATTRIBUTES_VALUES, GET_ITEM_ATTRIBUTES_TLP_VALUES, and GET_BASE_LANG resolve category identifiers, item attribute values, translated attribute values, and the base language, respectively. Collectively these procedures support the full attribute lifecycle during document entry, import, translation, and maintenance.

Tables Accessed

The package reads and writes PO_ATTRIBUTE_VALUES and PO_ATTRIBUTE_VALUES_TLP, its principal storage tables for base and translated attribute values. It references PO_LINES and PO_LINES_ALL for line and organization context, and PO_REQEXPRESS_LINES_ALL and PO_REQUISITION_LINES_ALL for requisition template and requisition line data. Item and category information is drawn from MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_TL, and MTL_PARAMETERS. Language handling relies on FND_LANGUAGES, while system defaults come from FINANCIALS_SYSTEM_PARAMETERS and FINANCIALS_SYSTEM_PARAMS_ALL and FND_PROFILE_OPTION_VALUES. Interface processing uses PON_ATTRIBUTES_INTERFACE, and auction pricing data is drawn from PON_AUCTION_ITEM_PRICES_ALL. These access points confirm the package sits at the intersection of document entry, item master, and multi-language infrastructure.

Usage Notes

PO_ATTRIBUTE_VALUES_PVT is referenced by fifteen other packages, indicating it is a shared internal utility within Purchasing rather than a standalone public API. It is typically invoked indirectly through the Purchasing forms (for example, when attribute flexfields are entered or defaulted on a PO line, blanket, quotation, or requisition template), through the PO document import concurrent programs during interface processing, and by other Purchasing private packages that require attribute defaulting or translation. Custom code should generally call the supported public APIs rather than this PVT package, because its signature and behavior are not part of the committed external interface and may change between releases. Where attribute defaulting is required programmatically, CREATE_DEFAULT_ATTRIBUTES or its multi-language counterpart is the appropriate internal entry point.