Search Results document_sourcing_method

Overview

The POS_ASL_ORDER_MODIFIERS_V view is a reporting and integration artifact owned by the APPS schema within Oracle E-Business Suite. It belongs to the ICX product family (Oracle iProcurement) and is documented as VALID in ETRM 12.2.2. The view exposes Approved Supplier List (ASL) order modifier attributes that govern how purchasing documents are sourced and generated for a given supplier, supplier site, and item or category combination. More precisely, the view presents the subset of ASL attribute records defined at the global (organization-independent) level, because its defining predicate restricts output to a single sentinel value, USING_ORGANIZATION_ID = -1. In Oracle EBS sourcing terminology, a USING_ORGANIZATION_ID of -1 denotes ASL attributes that apply across all operating units rather than to a specific inventory organization. iProcurement and Purchasing logic therefore treat this view as the canonical presentation of global ASL order modifiers — pricing tolerances, processing lead time, minimum order quantity, fixed lot multiples, delivery calendars, and origination data — that drive sourcing decisions and requisition-to-order conversion defaults.

Underlying Base Objects

The view is defined over a single documented base object, the synonym PO_ASL_ATTRIBUTES (which resolves to the underlying Purchasing ASL attributes table). The view is a simple projection rather than a join: it selects a defined list of columns from PO_ASL_ATTRIBUTES and filters with WHERE USING_ORGANIZATION_ID = -1. No aggregation, union, or additional table join is present in the documented view text. This simplicity means the view carries no filtering beyond the organization scope, and its performance profile is essentially that of the base synonym. Because the same set of columns exists in the base object, this view should be regarded as a filtered presentation layer — useful for readability and for isolating global ASL modifiers — rather than as a transformation or denormalization of source data. Records updated in the base object propagate to the view immediately, so the view is always consistent with PO_ASL_ATTRIBUTES.

Key Columns

• ASL_ID — Primary key reference to the Approved Supplier List header record that these order modifiers qualify.
• USING_ORGANIZATION_ID — Organization scope; the view restricts this to -1, indicating global applicability.
• VENDOR_ID / VENDOR_SITE_ID / ITEM_ID / CATEGORY_ID — The supplier, supplier site, and item or category to which the modifiers apply.
• DOCUMENT_SOURCING_METHOD / RELEASE_GENERATION_METHOD — Sourcing and release-generation behavior flags.
• PRICE_UPDATE_TOLERANCE — Permitted variance before a price update is flagged.
• PROCESSING_LEAD_TIME / MIN_ORDER_QTY — Lead time and minimum order quantity used in supply planning.
• FIXED_LOT_MULTIPLE — The quantity increment to which order quantities are rounded, relevant to the user's search term.
• ENABLE_PLAN_SCHEDULE_FLAG / ENABLE_SHIP_SCHEDULE_FLAG / ENABLE_AUTOSCHEDULE_FLAG / ENABLE_AUTHORIZATIONS_FLAG — Scheduling and authorization controls.
• DELIVERY_CALENDAR / COUNTRY_OF_ORIGIN_CODE — Calendar assignment and origination information.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and the concurrent request columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Analysts and developers use this view to verify the fixed lot multiple and related order modifiers that iProcurement applies when building sourcing suggestions or auto-created orders for globally scoped ASLs. A common query lists all modifier records for a given supplier site or item:

SELECT asl_id, vendor_id, vendor_site_id, item_id,
       min_order_qty, fixed_lot_multiple,
       processing_lead_time, price_update_tolerance
FROM   apps.pos_asl_order_modifiers_v
WHERE  vendor_site_id = :site_id
AND    item_id = :item_id;

Because the view already constrains USING_ORGANIZATION_ID = -1, callers do not need to add that predicate; they should not attempt to override it. A second typical use is auditing round-quantity behavior, examining every ASL line where a fixed lot multiple is defined, and correlating that back to PO_ASL_ATTRIBUTES for organization-specific variants. The view is equally suitable for integration extracts that feed sourcing engines, provided consumers understand it returns only global-level modifier rows and not organization-overridden rows, which must be sourced directly from the underlying synonym.