Results for “doctype_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PON_OPEN_INTERFACE_PVT is a private PL/SQL package in the Oracle E-Business Suite sourcing module that supports the open interface for importing negotiation (auction) data into Oracle Sourcing. The package is part of the Oracle Purchasing and Sourcing family and operates under the APPS schema in release 12.1.1 and 12.2.2. Its core responsibility is to validate, transform, and stage data originating from external sources or feeder systems so that it can be loaded into the base negotiation tables PON_AUCTION_HEADERS_ALL and related child records.

The package implements a substantial amount of edit-checking logic against interface tables such as PON_AUCTION_HEADERS_INTERFACE, PON_AUC_ATTRIBUTES_INTERFACE, and PON_ATTRIBUTE_SCORES_INTERFACE. Header-level columns like CONTRACT_TYPE, SECURITY_LEVEL_CODE, BID_VISIBILITY_CODE, and numerous negotiation flags are validated against a predefined map of allowable values, ensuring that only compliant data is promoted to the production negotiation tables. In this way, PON_OPEN_INTERFACE_PVT serves as the validation and loading engine behind the Sourcing open interface, guarding data integrity before records become visible to buyers and suppliers.

Key Procedures and Functions

The package exposes 29 documented procedures, organized around distinct stages of negotiation import. Header processing centers on CREATE_NEGOTIATION_HEADER, PROCESS_NEGOTIATION_HEADER, CREATE_NEGOTIATION, and CREATE_NEGOTIATIONS, along with CREATE_HEADER_ATTR_INTER and VALIDATE_HEADER. These routines build the negotiation header, process its attributes, and validate the header against the allowed-value map.

Line and pricing routines include CREATE_LINES_WITH_CHILDREN, ADD_PRICE_BREAKS, and VAL_PRICE_BREAKS, which construct negotiation lines and their price break structures while validating tier and response data.

Team and supplier routines include CREATE_NEG_TEAM, CREATE_MEMBERS_IN_COLLTEAM, INSERT_COLLABTEAM_MEMBER, INVITE_SUPPLIER, and VALIDATE_INVITED_SUPPLIERS, which assemble the negotiation team and control supplier invitations.

Attribute and scoring routines include PROCESS_UDA_ATTRIBUTES and VAL_ATTR_SCORES, handling user-defined attributes and attribute scores. Supporting utilities include ACCEPTANCE_VALUES_INSERT, CHECK_RANGE_OVERLAP, CHECK_UNIQUENESS, PRINT_LOG, and the initialization routine populate_column_test_table, which builds the allowed-values map used throughout validation.

Tables Accessed

The package reads and writes the interface staging tables PON_AUCTION_HEADERS_INTERFACE, PON_AUC_ATTRIBUTES_INTERFACE, and PON_ATTRIBUTE_SCORES_INTERFACE, and loads validated records into PON_AUCTION_HEADERS_ALL. Supplier validation references AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and HZ_PARTIES. Organizational and location data come from HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, and HR_LOCATIONS_ALL.

Payment terms and system defaults are drawn from AP_TERMS and FINANCIALS_SYSTEM_PARAMS_ALL. Lookup values and user references are sourced from FND_LOOKUP_VALUES and FND_USER, while document style configuration is read from PO_DOC_STYLE_HEADERS. Notably, the metadata's reference to PO_DOC_STYLE_HEADERS relates directly to the user's search on "doctype_name," which denotes the document type/style column used to classify negotiation documents during import.

Usage Notes

PON_OPEN_INTERFACE_PVT is a private (PVT) package, meaning it is not intended for direct invocation by end users or external integrations. It is typically called by the Sourcing open interface concurrent programs and, per the metadata, is referenced by one other package that orchestrates the import flow. External systems should populate the PON_AUCTION_*_INTERFACE tables and then run the standard Sourcing import concurrent program, which internally invokes this package.

Custom code referencing this package directly is discouraged because the API is private and subject to change between patch levels. When troubleshooting import failures, check PRINT_LOG output for validation errors generated by VALIDATE_HEADER, VALIDATE_INVITED_SUPPLIERS, and VAL_PRICE_BREAKS.