Search Results po_autocreate_pvt




Overview
Explore in AI Chat

Overview

PO_AUTOCREATE_PVT is a private PL/SQL package in the APPS schema that forms the core engine of the Oracle Purchasing AutoCreate feature in Oracle E-Business Suite 12.1.1 and 12.2.2. AutoCreate enables buyers to generate purchase orders, release orders, and blanket agreements automatically from approved requisition lines, either through the AutoCreate form or through a concurrent program. PO_AUTOCREATE_PVT encapsulates the reusable business logic that drives requisition-to-order conversion: creating draft purchasing documents, copying requisition attributes onto their destination document types, computing local pricing, populating descriptive flexfield (UDA) data, performing complex pricing validation, applying post-processing logic for Procurement Agent Reporting (PAR), and handling supplier and buyer attachments. Its classification as a PVT package indicates that it is an internal, supporting implementation package and not a public API intended for direct customer invocation.

The package is validated and documented in ETRM 12.2.2, and it references only standard Oracle infrastructure objects such as PO_TBL_NUMBER, PO_TBL_VARCHAR100, and PO_TBL_VARCHAR2000 collections, alongside SYS.STANDARD. It sits within a tightly coupled family of AutoCreate packages, and nine other packages depend on it, confirming its central role in the AutoCreate pipeline.

Key Procedures and Functions

The documented interface exposes fifteen procedures and functions. Their purposes are summarized below.

  • WRAPUP — Performs the final consolidation and cleanup steps at the end of an AutoCreate run.
  • CREATE_PO — Creates the purchasing document (or draft) that results from the auto-created requisition lines.
  • CALCULATE_LOCAL — Computes local-currency values for the developing purchasing document.
  • REPORT_ERROR — Records or raises an error encountered during auto-create processing.
  • GET_REQUISITION_LINE_NUM — Retrieves the requisition line number associated with the current processing context.
  • GET_ERROR_CODE_TBL — Returns the in-memory table of accumulated error codes for the run.
  • INITIALIZE_ERROR_CODE_TBL — Initializes that error-code collection prior to processing.
  • FORM_ATTR_DISPLAY_NAME — Derives the display name for a descriptive flexfield attribute in the form context.
  • INSERT_ROW_IN_UDA_INTERFACE — Inserts a row into the UDA (descriptive flexfield) interface for later application to purchasing documents.
  • POPULATE_UDA_DATA_IN_INTERFACE — Populates UDA (descriptive flexfield) data into the relevant interface tables.
  • DO_POST_PROCESSING_FOR_PAR — Executes post-processing steps required for Procurement Agent Reporting.
  • COMPLEX_PRICING_VALIDATION — Validates pricing for documents involving complex pricing schemes.
  • UPDATE_MOD_LINE_ID — Updates the modified line identifier on the developing document line.
  • COPY_PAR_ATTACHMENTS — Copies attachments associated with the PAR (Procurement Agent Reporting) context.
  • GET_ATTACHMENT_COUNT — Returns the count of attachments for a given document or entity.

Tables Accessed

The package operates largely through the interface and draft tables that underpin AutoCreate. It writes to PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, PO_LINE_LOCATIONS_INTERFACE, PO_DISTRIBUTIONS_INTERFACE, and PO_PRICE_DIFF_INTERFACE, which stage the developing purchasing document. It then works with the draft tables PO_DRAFTS, PO_HEADERS_DRAFT_ALL, PO_LINES_DRAFT_ALL, PO_LINE_LOCATIONS_DRAFT_ALL, and PO_DISTRIBUTIONS_DRAFT_ALL, which hold the in-progress document before it is committed. Requisition source data is read from PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL. Supporting tables include FND_ATTACHED_DOCUMENTS (attachment copy and count logic), PO_ENTITY_DIFFERENCES and PO_ENTITY_LOCKS (change detection and concurrency control during drafting).

Usage Notes

PO_AUTOCREATE_PVT is invoked from within AutoCreate processing rather than from custom code. Its primary callers are the sibling packages PO_AUTOCREATE_PREPROC_PVT, PO_AUTOCREATE_MAINPROC_PVT, and PO_AUTOCREATE_POSTPROC_PVT, which structure the pre-processing, main, and post-processing phases of a run. It is also called by PO_AUTO_DIST_PROCESS_PVT, PO_AUTO_HEADER_PROCESS_PVT, PO_AUTO_LINE_PROCESS_PVT, PO_AUTO_LINE_LOC_PROCESS_PVT, PO_AUTO_IMPLEMENT_PVT, PO_INTERFACE_S, and recursively by PO_AUTOCREATE_PVT itself. In practice these calls are triggered by the AutoCreate form (POXPOACR) and related concurrent processes when a buyer selects requisition lines and issues the create action. Because it is a private package, customizations should extend or wrap the public AutoCreate entry points rather than calling PO_AUTOCREATE_PVT directly, as its signatures and internal behavior are not guaranteed across patches or releases.