Search Results val_attachments_interface




Overview
Explore in AI Chat

Overview

PON_SOURCING_OPENAPI_GRP is a public API group package in the Oracle E-Business Suite Sourcing (formerly Oracle Sourcing / Negotiations) module, owned by the APPS schema. It provides the programmatic entry point for creating and validating draft negotiation records through the Sourcing open interface tables, and for managing related setup and integration data. The package is classified as a GRP (group) object in ETRM, which indicates that it is intended primarily as an umbrella or dispatcher package whose member procedures are invoked by external callers, concurrent programs, or workflow components rather than being a single-purpose utility.

Its central business role is to accept staging data loaded into the PON interface tables (headers, items, shipments, attachments, and attributes) and to move that data into the live sourcing/negotiation schema, while performing the validations required before the records are accepted. The package also exposes helper routines for trading partner resolution and cleanup of stale interface rows.

Key Procedures and Functions

  • CREATE_DRAFT_NEG_INTERFACE — Overloaded procedure (two signatures) that creates a draft negotiation from an interface identifier. Depending on the signature used, it returns the generated document number and document URL, or additionally reports whether a concurrent program was started along with the associated request identifier. Both signatures return a result indicator plus error code and error message.
  • VAL_AUC_HEADERS_INTERFACE — Validates the negotiation header rows staged for a given interface identifier, returning error code and error message.
  • VAL_AUC_ITEMS_INTERFACE — Validates the line/item rows associated with the interface identifier and reports validation errors through the same output parameters.
  • VAL_AUC_SHIPMENTS_INTERFACE — Validates the shipment-level rows for the interface identifier. This is the routine most commonly referenced when diagnosing shipment interface errors during negotiation import.
  • VAL_ATTACHMENTS_INTERFACE — Validates attachment rows staged for the interface identifier, ensuring referenced documents and categories are valid before the draft negotiation is created.
  • GET_TRADING_PARTNER_INFO — Resolves trading partner information (identifier, name, and contact identifier/name) from a supplied vendor identifier, supporting supplier-facing negotiation creation.
  • PURGE_INTERFACE_TABLE — Removes processed or obsolete interface rows for a given interface identifier, returning a result indicator with error code and message.
  • IS_CPA_INTEGRATION_ENABLED, GET_DISPLAY_LINE_NUMBER, PON_RENEG_SUPER_LARGE_NEG, and MAINTAIN_CLM_RELATIONS — Additional documented members supporting CPA (contract purchase agreement) integration checks, display line numbering, handling of very large negotiations, and maintenance of CLM (contract lifecycle management) relations.

Tables Accessed

The interface validation and creation routines operate primarily on PON_AUC_HEADERS_INTERFACE, PON_ATTACHMENTS_INTERFACE, and PON_ATTRIBUTES_INTERFACE, with shipment and item data staged in the corresponding PON interface structures. Lookup and setup data are drawn from FND_LOOKUP_VALUES, FND_CURRENCIES, FND_DOCUMENT_CATEGORIES, FND_PRODUCT_GROUPS, FINANCIALS_SYSTEM_PARAMS_ALL, and FND_USER. Attachment validation and resolution rely on FND_ATTACHED_DOCUMENTS and FND_ATTACHED_DOCUMENTS_S. Trading partner resolution reads HZ_PARTIES and HZ_RELATIONSHIPS. Item-related validations consult MTL_CATEGORIES_KFV and MTL_UNITS_OF_MEASURE. All access is performed through APPS synonyms.

Usage Notes

The package is typically invoked from the Sourcing negotiation import flow: interface rows are populated by external sources or concurrent programs, the VAL_AUC_* routines are called to surface header, item, and shipment errors to the user, and CREATE_DRAFT_NEG_INTERFACE is then called to generate the draft negotiation and its document URL. PURGE_INTERFACE_TABLE is used in cleanup cycles after successful import. Because the procedures return error code and error message out parameters rather than raising standard exceptions, callers must inspect x_result and x_error_code explicitly. The package is referenced by one other package in ETRM, so customizations should preserve its documented signatures.