Search Results should_req_be_autocreated

Overview

PO_AUTOCREATE_DOC is an Oracle EBS PL/SQL package owned by the APPS schema that supports the Oracle Purchasing AutoCreate workflow. Its primary business function is to drive the automatic creation of purchase order and blanket agreement documents from approved requisition lines, enforcing the sourcing rules, buyer defaults, and release generation rules configured for the operating unit. The package is classified as a general-purpose (OTHER) API and is not a public, supported interface, so it is typically invoked by Oracle's own requisition processing, workflow, and document action logic rather than by customer code. It is validated in both 12.1.1 and 12.2.2 and references standard SYS objects as well as various APPS synonyms.

Key Procedures and Functions

The ETRM metadata documents 47 procedures and functions. The following representative entries illustrate the package's responsibilities:

• SHOULD_REQ_BE_AUTOCREATED — Evaluates whether a given requisition line qualifies for automatic document creation based on sourcing and profile criteria.
• GET_REQ_INFO — Retrieves requisition line attributes needed for downstream autocreation processing.
• IS_SOURCE_DOC_INFO_OK — Validates that source document information (contract, agreement, or blanket) is complete and usable.
• DOES_CONTRACT_EXIST and GET_SOURCE_DOC_TYPE — Determine whether an existing contract or source document applies and identify its type.
• RFQ_REQUIRED_CHECK and ONE_TIME_ITEM_CHECK — Apply business rules for whether an RFQ is required and whether the requisition line references a one-time item.
• GET_BUYER_FROM_REQ_LINE, GET_BUYER_FROM_ITEM, GET_BUYER_FROM_CATEGORY, GET_BUYER_FROM_SOURCE_DOC, GET_BUYER_FROM_CONTRACT — Resolve the appropriate buyer using the requisition line, item, category, source document, or contract.
• GET_SUPP_INFO_FOR_ACRT, GET_REL_GEN_METHOD, IS_REQ_PCARD_LINE — Retrieve supplier information, determine the release generation method, and identify procurement card lines.
• START_WF_PROCESS, START_WF_LINE_PROCESS, LAUNCH_REQ_LINE_PROCESSING, CONT_WF_AUTOCREATE_REL_GEN — Manage the workflow processes that drive autocreation and release generation.
• INSERT_CAND_REQ_LINES_INTO_TBL — Populates the candidate requisition line table used for subsequent autocreation runs.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

• PO_DRAFTS — Stores the draft purchase order or blanket agreement created during autocreation.
• PO_DOCUMENT_TYPES, PO_DOCUMENT_TYPES_ALL_B, PO_DOC_STYLE_HEADERS — Provide document type and style configuration.
• PO_AGENTS, PO_GA_ORG_ASSIGNMENTS, PO_ASL_ATTRIBUTES — Supply buyer, organization assignment, and approved supplier list data.
• MTL_SYSTEM_ITEMS, HR_LOCATIONS_ALL, PER_ALL_PEOPLE_F, FND_USER — Provide item, location, person, and user reference data.
• ECE_TP_DETAILS — Stores trading partner details used in supplier resolution.
• FINANCIALS_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMS_ALL — Supply operating unit and system-level profile values.
• FND_NEW_MESSAGES — Supports message and notification handling.

Usage Notes

PO_AUTOCREATE_DOC is invoked indirectly through Oracle Purchasing's requisition autocreation and workflow processes rather than being called from EBS forms directly. It is referenced by PO_DOCUMENT_ACTIONS_SV and PO_REQAPPROVAL_LAUNCH, and it is referenced by two other packages, indicating it is a dependency of the autocreate and document action flows. Because it is classified as OTHER, it is not part of the supported public API surface; customizations should avoid calling its procedures directly, as signatures and behavior may change between releases. Administrators typically interact with this functionality through the AutoCreate concurrent program and the Purchasing responsibility, where the package's buyer-resolution, sourcing, and workflow logic executes behind the scenes.