Search Results doc_generation_method

Overview

PO_AUTOSOURCE_DOCUMENTS_V is an APPS-owned, VALID database view in the Oracle E-Business Suite Purchasing (PO) module. It is documented in ETRM for both 12.1.1 and 12.2.2 and carries the description "Retrofitted," indicating it was rebuilt or reconciled against the current release rather than being newly authored. The view presents the sourcing documents — quotations and blanket purchase agreements — that are associated with an Approved Supplier List (ASL) entry, together with the attributes needed to determine how those documents may be used as autosource candidates during requisition, purchasing, and sourcing flows. It consolidates header-, line-, and shipment-level agreement data into a single flattened row, which makes it suitable for reporting on approved supplier sourcing hierarchies without repeatedly joining the PO agreement stack. A notable attribute is the computed release generation method, derived from PO_ASL_ATTRIBUTES (aliased PAA.RELEASE_GENERATION_METHOD), which is the field most frequently referenced when users search on the term "doc_generation_method" and expect document or release generation behavior to be surfaced from the ASL configuration.

Underlying Base Objects

The documented ETRM metadata lists the referenced base objects. Core sourcing objects include PO_ASL_DOCUMENTS, PO_ASL_ATTRIBUTES, PO_APPROVED_SUPPLIER_LIS_VAL_V, and PO_AUTOSOURCE_DOCUMENTS_ALL. Agreement data is drawn from PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_LINE_TYPES. Supplier master data comes from PO_VENDORS, PO_VENDOR_SITES_ALL, and AP_SUPPLIER_CONTACTS. Organization and operating-unit context is supplied by PO_GA_ORG_ASSIGNMENTS, HR_ALL_ORGANIZATION_UNITS_TL, MTL_PARAMETERS, and GL_SETS_OF_BOOKS, while FND_GLOBAL provides session context (org_id, user_id). PER_ALL_PEOPLE_F and FINANCIALS_SYSTEM_PARAMETERS support buyer and currency lookup attributes. The view text confirms these relationships: PASL (PO_ASL_DOCUMENTS) is the driving table, joined to PAD (PO_ASL_ATTRIBUTES), PH, PL, and PLL for header, line, and shipment detail, and to vendor and site objects for sourcing party information.

Key Columns

• ASL_ID, VENDOR_ID, VENDOR_NAME — identify the approved supplier list entry and the sourcing supplier.
• DOCUMENT_TYPE_CODE, TYPE_NAME — distinguishes QUOTATION from BLANKET agreement documents.
• DOCUMENT_HEADER_ID, DOCUMENT_LINE_ID, SEQUENCE_NUM — link the row back to the specific agreement document, line, and ASL sequence.
• RELEASE_GENERATION_METHOD — the ASL attribute governing whether releases are generated automatically or manually; this is the effective "doc generation method" column.
• SEGMENT1, LINE_NUM, SHIPMENT_NUM, LINE_LOCATION_ID — human-readable document number, line, and shipment identifiers.
• STATUS_LOOKUP_CODE / AUTHORIZATION_STATUS — the decoded document status, selected conditionally by document type.
• AGENT_ID, FULL_NAME, VENDOR_CONTACT_ID — buyer and supplier contact information.
• CURRENCY_CODE, TERMS_ID, SHIP_VIA_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE, FOB_LOOKUP_CODE — header and shipment commercial terms.
• QUANTITY, UNIT_PRICE, PRICE_OVERRIDE, START_DATE, END_DATE — pricing and validity attributes for the agreement line/shipment.
• ORG_ID, PURCHASING_ORG_ID — multi-org security and procurement business unit context.

Common Use Cases and Queries

Typical usage centers on sourcing analysis for a given supplier or item: identifying which quotations and blankets are registered against an ASL entry, and how releases will be generated. A representative query returning the sourcing documents and their generation method is:

• SELECT vendor_name, document_type_code, segment1, line_num, release_generation_method FROM po_autosource_documents_v WHERE vendor_id = :p_vendor_id;
• SELECT asl_id, document_header_id, sequence_num, authorization_status FROM po_autosource_documents_v WHERE org_id = :p_org_id AND document_type_code = 'BLANKET' ORDER BY sequence_num;
• SELECT segment1, line_num, unit_price, currency_code, start_date, end_date FROM po_autosource_documents_v WHERE asl_id = :p_asl_id AND SYSDATE BETWEEN start_date AND end_date;

The view is also used to validate that an approved supplier has at least one active sourcing document, to troubleshoot autosource failures when no release generation method is configured on the ASL attribute, and to feed downstream extracts for supplier agreement reporting. Because it joins multi-org and session-dependent objects, queries should always constrain ORG_ID and run in a responsibility with appropriate procurement operating unit access.