PO Approved Supplier List Upload – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
This upload supports the creation and update of Approved Supplier Lists (ASL) in Oracle Purchasing.
The upload supports creation/update/deletion of the following Approved Supplier List entities:
- Approved Supplier Lists (Global and Local)
- Approved Supplier List Attributes. Including Local (Using Organization specific) attributes against a global ASL.
- Source Documents
- Authorizations
- Supplier Capacities
- Supplier Tolerances
Notes:
-
You cannot delete Manufacturer ASLs using this upload. There is a restriction in the standard Oracle API used by this upload that prevents this.
-
When the ASL attributes for the same Item/Commodity, Supplier, Supplier Site, and Using Organization are repeated in the upload excel, then first row flagged for upload will be used to apply the attribute updates. The attributes on subsequent rows are ignored.
-
The following points are only significant if you define Local Attributes for a Using Organization against a Global ASL: Source Documents are associated with the Using Organization of the ASL Attributes Authorizations, Supplier Capacities and Supplier Tolerances are always associated with the Using Organization of the ASL
If you delete a Local ASL defined for a specific using organization against a Global ASL, only the local using organization attributes will be deleted. The Global ASL will not be deleted.
-
When downloading existing ASL data into the upload excel, Source Documents, Authorizations, Capacities, and Tolerances are downloaded into separate rows in the excel. This is to minimize the duplication of data in the excel. However, when entering data for upload Source Documents, Authorizations, Capacities, and Tolerances can be added in the same excel row. i.e. You can upload an excel row containing a Source Document, Authorization, Capacity, and Tolerance.
-
Capacity Entries with a capacity from/to date in the past cannot be updated by this upload due to validations applied in the standard Oracle API used by the upload. It is possible to delete a capacity entry with a capacity from date in the past, but only if the capacity to date is either null or later than the current date.
-
By default, Authorizations, Supplier Capacities, and Supplier Tolerances are not included in the downloaded data. The following report parameters may be Yes in order to include these in the download: Download Authorizations Download Capacities Download Tolerances
Report Parameters
Upload Mode, Owning Organization Code, Type, Item, Item From, Item To, Commodity, Commodity From, Commodity To, Global ASL, Using Organization Code, Missing Release Method, Business Type, Operating Unit, Supplier, Supplier Number, Supplier Site, Manufacturer, ASL Status, ASL Disabled, Source Document, Download Authorizations, Download Capacities, Download Tolerances
Oracle EBS Tables Used
mtl_categories_tl, po_approved_supplier_list, mtl_manufacturers, po_asl_statuses, per_people_x, chv_bucket_patterns, mtl_system_items_vl, mtl_categories_b_kfv, ap_suppliers, ap_supplier_sites, mtl_parameters, hr_all_organization_units_tl, po_asl_attributes, po_asl_documents, po_headers_all, po_lines_all, org_access_view
Report Categories
Running This SQL Without Blitz Report
Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | None |
| Blitz Report™ XML Import | PO_Approved_Supplier_List_Upload.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/po-approved-supplier-list-upload/ |
Case Study & Technical Analysis: PO Approved Supplier List Upload Report
Executive Summary
The PO Approved Supplier List (ASL) Upload is a powerful data management tool designed to streamline the creation, update, and deletion of Approved Supplier List entries within Oracle Purchasing. It offers comprehensive functionality to manage not only the core ASL records but also associated attributes like source documents, authorizations, supplier capacities, and tolerances, for both global and local ASLs. This Excel-based utility is essential for procurement organizations to efficiently maintain master sourcing data, enforce purchasing policies, optimize supplier relationships, and ensure the accuracy and integrity of their supply chain information.
Business Challenge
Maintaining an accurate and up-to-date Approved Supplier List is a cornerstone of effective procurement, but it can be a highly complex and resource-intensive task in Oracle EBS:
- High Volume Data Entry: For organizations with numerous items, suppliers, and sourcing rules, manually creating or updating ASL entries and their many associated attributes (e.g., lead times, quality certifications, capacity details) is a slow, repetitive, and error-prone process.
- Ensuring Data Consistency: Inconsistent ASL data can lead to buyers using unauthorized suppliers, incorrect sourcing rules being applied, or inaccurate supplier performance metrics, all of which negatively impact procurement efficiency and compliance.
- Managing Complex Attributes: The ASL can hold a wealth of information, including source documents (like Blanket Purchase Agreements), quality authorizations, supplier capacity constraints, and delivery tolerances. Managing these granular attributes through standard forms is cumbersome.
- Impact on Planning and Sourcing: Outdated or inaccurate ASL data directly affects supply chain planning (e.g., material planning based on incorrect lead times) and strategic sourcing decisions.
The Solution
This comprehensive Excel-based upload tool transforms the management of the Approved Supplier List, making it efficient, accurate, and scalable.
- Bulk Creation, Update, and Deletion: It enables the mass creation of new ASL entries, efficient updates to existing records, and targeted deletions (with specific limitations) for various ASL components in a single operation from a spreadsheet.
- Integrated Attribute Management: The upload supports all key ASL entities: core entries, attributes, source documents, authorizations, supplier capacities, and tolerances, providing a holistic management solution.
- Supports Global and Local ASLs: The tool differentiates between global ASLs and local (Using Organization-specific) attributes, providing flexibility for centralized sourcing strategies and decentralized operational needs.
- Improved Data Accuracy and Efficiency: By allowing data preparation in Excel, users can leverage spreadsheet validation features before uploading, drastically reducing data entry errors and accelerating ASL maintenance processes.
Technical Architecture (High Level)
The upload process leverages Oracle Purchasing’s standard APIs for ASL management, ensuring robust data validation and integrity.
- Primary Tables Involved:
po_approved_supplier_list(the central table for ASL entries).po_asl_attributes(stores item/category-specific attributes for ASL entries).po_asl_documents(links ASL entries to source documents like BPAs).chv_authorizations(for supplier authorizations).po_supplier_item_capacityandpo_supplier_item_tolerance(for supplier-item specific capacity and tolerance details).mtl_system_items_vl,mtl_categories_b_kfv,ap_suppliers,ap_supplier_sites(for validating master data).
- Logical Relationships: The tool takes an Excel file, validates the data against relevant master data tables, and then utilizes Oracle APIs to perform the requested operations (insert, update, delete) on the
po_approved_supplier_listand its child tables. The complex logic for handling global vs. local ASL attributes and the specific update/deletion rules (e.g., for capacities) are handled by the underlying Oracle APIs.
Parameters & Filtering
The upload report offers extensive parameters for precise control over the data operation:
- Upload Mode: The key parameter determining the action: ‘Create’, ‘Update’, or ‘Delete’ (implicitly via ‘Create, Update’ mode for lines).
- ASL Identification:
Owning Organization Code,Type(Item/Category),Item,Commodity,Supplier,Supplier Number,Supplier Site,Manufacturerallow for precise targeting of ASL entries. - Global/Local Control:
Global ASLandUsing Organization Codemanage the scope of the ASL. - Download Options:
Download Authorizations,Download Capacities,Download Tolerancesare crucial for populating the Excel template with existing data before making updates.
Performance & Optimization
Using an API-based upload for complex ASL data is significantly more efficient than manual entry.
- Bulk Processing via APIs: The tool processes ASL entries and their attributes in batches, leveraging Oracle’s standard integration mechanisms (APIs) which are designed for high-volume, efficient data loading, particularly for master data.
- Error Reporting and Specific Limitations: The tool provides detailed error messages for invalid records. The
README.mdexplicitly calls out specific API limitations (e.g., cannot delete Manufacturer ASLs, restrictions on updating past capacity entries), which are important for users to understand to ensure successful uploads. - Efficient Download for Update: The ability to download existing ASL data with specific attributes (authorizations, capacities, tolerances) into separate rows simplifies the update process by providing a clear starting point for modifications.
FAQ
1. What is the main benefit of using this upload tool over manual ASL entry? The primary benefit is efficiency and accuracy. For high volumes of ASL data, manual entry is time-consuming and error-prone. This tool automates the process, reduces errors, and ensures consistency, freeing up procurement staff for more strategic tasks.
2. Can I use this tool to remove a supplier from the Approved Supplier List? Yes, the tool supports deleting ASL entries (with the noted exception of Manufacturer ASLs). You would typically download the existing ASL data, mark the line(s) for deletion, and then re-upload. For a local ASL against a Global ASL, only the local attributes will be deleted, leaving the global ASL intact.
3. How does the system handle the update of supplier capacity entries for past dates?
As per the README.md, capacity entries with a capacity from/to date in the past cannot be updated by this upload due to standard Oracle API validations. However, it is possible to delete a past capacity entry if its capacity to date is null or in the future. This highlights the importance of real-time data maintenance.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics