Search Results po_autocreate_postproc_pvt




Overview
Explore in AI Chat

Overview

PO_AUTOCREATE_TYPES is a declarative PL/SQL specification package in the Oracle E-Business Suite Purchasing module. It does not expose callable business logic in the conventional sense; instead it publishes a library of PL/SQL record TYPE definitions used by the Automatic Creation (AutoCreate) processing framework to move requisition, RFQ, and quoted data into purchase order and release documents. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve against the schema of the calling session, which allows AutoCreate workers to operate without hard-coded schema qualification of the underlying tables.

The record types defined here act as strongly typed, in-memory staging structures that mirror the column layout of the AutoCreate interface tables and the target PO_HEADERS_ALL columns. Centralizing these definitions ensures that the header-level, line-level, and distribution-level constructs processed by the AutoCreate engine remain consistent across the many programs that consume them.

Key Procedures and Functions

The ETRM metadata documents no callable procedures or functions for this package. It is a types-only specification: its public surface consists of record and collection type declarations rather than executable subprograms. The primary documented type is headers_rec_type, a record describing a single header (or release) record processed during AutoCreate. The fields visible in the specification fall into several functional groupings:

  • Interface and key identifiers — intf_header_id, draft_id, po_header_id, and from_header_id tie the in-memory record back to the AutoCreate interface and to the PO header or source document.
  • Document classification — action, document_num, doc_type, doc_subtype, from_type_lookup_code, and revision_num define what kind of document is being created or updated.
  • Supplier data — vendor_name, vendor_num, vendor_id, vendor_site_code, vendor_site_id, vendor_contact, vendor_contact_id, and vendor_doc_num.
  • Terms, currency, and shipping — payment_terms, terms_id, currency_code, fob, freight_carrier, freight_term, pay_on_code, shipping_control, ship_to_loc_id, and bill_to_loc_id.
  • Pricing and rate information — rate_type, rate_type_code, rate_date, rate, quote_warning_delay, amount_agreed, and amount_limit.
  • Lifecycle and control flags — approval_required_flag, approval_status, approved_date, confirming_order_flag, acceptance_required_flag, acceptance_due_date, frozen_flag, encumbrance_required_flag, closed_code, and the associated date fields (effective_date, expiration_date, release_date, revised_date, printed_date, closed_date).
  • Release-specific attributes — po_release_id, release_num, release_date, min_release_amount, and amount_to_encumber.
  • Multi-org context — org_id.

Tables Accessed

The documented table references are PO_HEADERS_ALL and DBMS_SQL (the latter being the Oracle-supplied dynamic SQL package rather than an application table). PO_HEADERS_ALL is the base table for purchasing document headers and releases; the attribute set captured by headers_rec_type corresponds closely to its columns, confirming that the record type is used to populate or select from PO_HEADERS_ALL during AutoCreate. DBMS_SQL indicates that at least one consumer of these types builds and executes dynamic SQL, which is consistent with the generic, caller-schema design of the package.

Usage Notes

PO_AUTOCREATE_TYPES is not invoked directly by end users. It is referenced by other PL/SQL units—the metadata notes six dependent packages—within the Automatic Creation concurrent program flows and related forms and APIs. Customizations that need to manipulate AutoCreate staging data should declare variables of the published record types (for example, a headers_rec_type variable) so that their code remains aligned with the engine's expectations, particularly regarding the org_id and interface key fields. Note also the query string that led to this object: po_tbl_varchar1 is a descriptive-flexfield attribute column on PO_HEADERS_ALL and on the AutoCreate interface tables. It is not a field of headers_rec_type in the documented excerpt, so solutions that need to read or default DFF context values during AutoCreate must address those columns separately from this record structure.