This upload can be used to create and/or update Suppliers, Supplier Sites, Supplier Bank Accounts, and Supplier Contacts
Upload Mode, Operating Unit, Supplier Type, Exclude Employee Suppliers, Supplier Name, Supplier Name From, Supplier Name To, Supplier Number, Supplier Number From, Supplier Number To, Payment Method, Tax Registration Number, Supplier Site, Supplier/Site Status, Bank Account Status, Contact Status, Update Supplier Bank Accounts, Update Supplier Sites, Update Site Bank Accounts, Update Site Contacts, Default Site Bank Acct Assign Lvl, Default Tax Rounding Rule, Default Inclusive Tax, Default Allow Offset Taxes, Default Pay Each Document Alone
per_employees_x, per_business_groups_perf, fnd_territories_vl, rcv_routing_headers, ap_terms_vl, ap_awt_groups, iby_ext_party_pmt_mthds, iby_payment_methods_vl, iby_payment_reasons_vl, iby_formats_vl, iby_delivery_channels_vl, iby_bank_instructions_vl
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
www.enginatics.com/reports/ap-supplier-upload/
Blitz Report™ import options
The AP Supplier Upload is a powerful data management utility designed to streamline the maintenance of the Supplier Master in Oracle Payables. It facilitates the bulk creation and update of Suppliers, Supplier Sites, Contacts, and Bank Accounts. By automating these tasks, organizations can significantly reduce the administrative burden of vendor management, ensure data consistency across operating units, and accelerate supplier onboarding processes.
Managing a large vendor base presents several operational hurdles:
- Manual Data Entry: Creating suppliers one by one is slow and prone to typographical errors (e.g., wrong tax IDs, misspelled names).
- Mass Updates: Updating payment terms or bank accounts for thousands of suppliers due to a policy change or bank merger is manually infeasible.
- Data Integrity: Inconsistent data entry standards across different users can lead to duplicate suppliers and reporting errors.
- Migration & Integration: Loading legacy supplier data during system implementations or acquisitions requires a robust, repeatable tool.
The AP Supplier Upload serves as a bridge between external data sources (like Excel spreadsheets) and the Oracle EBS Supplier Master.
- Bulk Processing: Enables the upload of thousands of supplier records in a single run, saving days of manual work.
- Comprehensive Scope: Handles the full hierarchy of supplier data: Header (Supplier), Sites (Address & Operating Unit specific), Contacts, and Banking details.
- Validation: Ensures that uploaded data adheres to Oracle's strict validation rules (e.g., unique Tax Registration Numbers, valid Payment Methods) before committing changes.
- Update Capability: Unlike standard interface programs that often only support creation, this tool allows for the update of existing records, making it ideal for data cleansing initiatives.
The solution utilizes Oracle's public APIs and interface tables to ensure data integrity and validation.
-
Primary Tables:
AP_SUPPLIERS(formerlyPO_VENDORS): Stores the supplier header information.AP_SUPPLIER_SITES_ALL(formerlyPO_VENDOR_SITES_ALL): Stores address and operating unit-specific site details.IBY_EXT_BANK_ACCOUNTS: Stores external bank account information (R12 Payments model).IBY_PMT_INSTR_USES_ALL: Links bank accounts to suppliers or sites.AP_SUPPLIER_CONTACTS: Stores contact information.
-
Logical Relationships:
- The tool typically accepts a flat file or Excel input which maps to the supplier hierarchy.
- It first checks for the existence of the Supplier. If not found, it creates it.
- It then processes Supplier Sites, linking them to the parent Supplier and the specified Operating Unit.
- Bank Accounts are created in the Payments (IBY) module and assigned to the Supplier or Site level based on the parameters.
- Contacts are linked to the specific Supplier Site.
The tool offers flexible parameters to control the scope of the upload and update:
- Upload Mode: Determines if the run is for creating new records, updating existing ones, or both.
- Operating Unit: Specifies the target OU for Supplier Sites.
- Update Flags (Update Supplier Bank Accounts, Update Supplier Sites, etc.): Boolean flags that give granular control over which parts of the supplier record should be modified, preventing unintended overwrites.
- Supplier Name/Number From/To: Allows for processing a specific subset of suppliers if running an update on existing data.
- Default Values: Parameters like "Default Tax Rounding Rule" or "Default Payment Method" allow for setting standard values for new records without populating every field in the source file.
- API-Based Processing: Uses Oracle's standard APIs (e.g.,
AP_VENDOR_PUB_PKG,IBY_DISBURSEMENT_SETUP_PUB) to ensure all business logic and validations are triggered, preventing data corruption. - Batch Processing: Can handle large datasets by processing records in loops, often with commit intervals to manage rollback segments.
- Error Handling: Provides detailed error messages for rejected records, allowing users to correct and re-upload only the failed lines.
Q: Can I use this tool to update the Tax Registration Number for existing suppliers? A: Yes, by using the "Update" mode and mapping the new Tax Registration Number in the upload file, the tool can update this field for existing suppliers identified by their Supplier Number or Name.
Q: Does this tool support creating bank accounts for multiple operating units? A: Yes, bank accounts in R12 are defined at a central level (Trading Community Architecture). This tool can assign a bank account to a Supplier Site, which is specific to an Operating Unit. You can assign the same bank account to multiple sites if needed.
Q: What happens if a supplier in the upload file already exists? A: If the tool is in "Create" mode, it may error out or skip the record depending on the configuration. If in "Update" or "Merge" mode, it will attempt to update the existing supplier with the new details provided in the file.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.
The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.
You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics