PO Approved Supplier List Upload creates, updates and deletes Oracle Purchasing Approved Supplier List (ASL) entries – item or commodity to supplier or manufacturer assignments – together with their supplier attributes (purchasing, scheduling, planning, inventory, VMI, consigned), source documents, authorizations, capacities and tolerances, from Excel, via the standard Oracle public API.
When to use it
- Mass-create new ASL entries linking items or commodities to suppliers or manufacturers.
- Bulk-maintain ASL supplier attributes (purchasing UOM, release method, scheduling, VMI, consigned, inventory settings) across many ASLs.
- Define local (organization-specific) attributes against existing global ASLs.
- Attach or remove source documents (blankets/quotations/contracts) in bulk.
- Load or update supplier-scheduling authorizations, capacities and tolerances.
- Disable/enable ASLs or change ASL status en masse, or delete obsolete ASLs.
Before you start
- Blitz Report is installed and you are signed in to a responsibility with access to the owning/using organizations.
- The supplier (with a purchasing site) and/or manufacturer exists, and the item or purchasing commodity exists.
- ASL statuses, bucket patterns, schedulers and purchasing documents referenced are set up.
Step 1 – Choose a mode, set the parameters and download
In Blitz Report, open PO Approved Supplier List Upload, choose an Upload Mode (Create, Update – the default – downloads existing ASLs to edit; Create gives an empty template), and set the parameters:
| Parameter | Purpose |
|---|---|
| Upload Mode | Create or Create, Update. Default is Create, Update. |
| Owning Organization Code / Type / Item / Commodity / Supplier / Manufacturer / Status | Restrict which existing ASLs are downloaded. |
| Download Authorizations / Capacities / Tolerances | Include these child rows in the download (excluded by default). |
Run the upload to download and open the Excel file. Each ASL and child entity is automatically handled as a create or an update depending on whether it already exists.
Step 2 – Enter the ASL entries
On each row choose the Type (Item or Commodity) and the Item or Commodity, the Supplier Business Type (Direct / Manufacturer / Distributor) and the Supplier or Manufacturer, set Global ASL (Yes for all organizations) and the Status, and fill the supplier attributes, source document, authorization, capacity or tolerance columns as needed.
Step 3 – Delete entries (optional)
Set Delete this ASL to remove an ASL, or Delete this Document / Authorization / Capacity / Tolerance to remove an individual child entity. Manufacturer ASLs cannot be deleted (an Oracle API restriction).
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.
Step 5 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates, updates or deletes each ASL and child entity. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created, updated or deleted ASL entries with their attributes, source documents, authorizations, capacities and tolerances.
- A result report listing every row with a status (success or error) and a message.
Common questions
Do I set the Action column to choose create vs update?
No. The upload auto-detects create vs update from the ASL key (item/commodity, supplier, site, owning and using organization).
How do I add a local attribute set to a global ASL?
Mark Global ASL = Yes and populate the Using Organization; the upload adds local attributes without altering the global ASL.
Can I add a document, authorization, capacity and tolerance for the same ASL in one row?
Yes, on entry. On download they appear in separate rows to reduce duplication.
Why don’t Authorizations/Capacities/Tolerances appear in my download?
They are excluded by default – set Download Authorizations / Capacities / Tolerances to Yes.
Why can’t I delete a Manufacturer ASL?
The standard Oracle API does not support it; the upload blocks it with a clear message.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Manufacturer ASLs cannot be deleted using this upload | Delete this ASL = Yes on a Manufacturer business-type ASL. | Remove it through the Oracle form; this upload cannot delete Manufacturer ASLs. |
| Vendor / Manufacturer / Distributor Manufacturer is required | The Business Type doesn’t match the supplier fields. | Populate the supplier field that matches the chosen Business Type. |
| An ASL for this Manufacturer does not exist for this Item/Commodity | A Distributor ASL references a Manufacturer with no existing ASL. | Create the Manufacturer ASL first, then the Distributor ASL. |
| Document / Authorization / Capacity / Tolerance cannot be deleted – it does not exist | Delete = Yes for a child entity that isn’t there. | Verify the child entity exists before flagging it for deletion. |
| Multiple suppliers named X exist – populate the Supplier Number | Duplicate supplier/manufacturer names. | Populate the Supplier Number to disambiguate. |