The Suppliers Integrator is a solution for uploading Supplier master data via the supported Oracle ERP Cloud REST Web Services.
The Supplier REST Web Service that exists today, as at version 23C, is an inbound web service that allows both the creation and update of supplier data in Oracle Fusion Suppliers.
If you would like us to investigate the potential provision of update functionality which we do not currently offer, please register your suggestion and interest with More4apps.
Ensure you are familiar with the More4apps Finance Module prerequisites before attempting to use this Integrator.
Tip: There are many fields available in each section of this Integrator so, for performance reasons, we highly recommend using tailored worksheet layouts for specific processes.
Important to Note: As with Oracle’s FBDI products, all approval configuration in Oracle’s ‘Setup and Maintenance’ > ‘Configure Supplier Registration and Profile Change Request’ form will be bypassed by the Supplier Integrator. Therefore, care must be taken to ensure that all data being uploaded via the Integrator has already been approved in line with your company’s policies.
Sections:
The following sections and functionality are available in the Supplier Integrator.
Also note which Sections can have ‘Child’ records as this will determine how data must be entered in those sections: see below for further details.
Section Name
|
Create New Records
|
Update Existing Records
|
Has Child Records?
|
Suppliers
|
Yes
|
Yes
|
Yes
|
Addresses
|
Yes
|
Yes
|
No
|
Sites
|
Yes
|
Yes
|
Yes
|
Site Assignments
|
Yes
|
No*
|
No
|
Supplier Contacts
|
Yes
|
Yes
|
Yes
|
Supplier Contact Addresses
|
Yes
|
No**
|
No
|
Business Classifications
|
Yes
|
No
|
No
|
Products & Services
|
Yes
|
No**
|
No
|
Supplier Attachments
|
Yes
|
No
|
No
|
Site Attachments
|
Yes
|
No
|
No
|
Submitting Spend Authorization
|
Yes
|
Yes
|
No
|
*Except for the ‘Site Assignment Inactive Date’ which can be updated.
**This functionality is available in the Oracle UI but, as at the current Fusion Release 23C, no REST web services exist to enable the updating of these records.
Processing of Child Records
The column ‘Has Child Records?’ in the above table indicates whether the section has hierarchical child records or not. If they don’t, there should be no blank rows between the data, or the upload will determine the rows have been orphaned.
Parent Section
|
Child Section
|
Blank Rows Between Allowed
|
Suppliers
|
Addresses
Supplier Sites
Supplier Contacts
Business Classifications
Products & Services
Supplier Attachments
|
No
Yes (as a parent itself)
Yes (as a parent itself)
No
No
No
|
Supplier Sites
|
Site Assignments
Site Attachments
|
No
No
|
Supplier Contacts
|
Contacts Addresses
|
No
|
The following diagram shows the relationships between the different sections of the Suppliers Integrator:
The above is an example of a typical layout of basic data in the Suppliers Integrator for one Supplier record:
The Supplier’s Address Name details are listed without any blank rows between them. If a row were left blank, the Integrator would assume that the last record before the blank was the end of that particular Supplier’s Address Name records and would then try to start creating a new Supplier record.
When Contact Names are entered they are associated with one or more Address Names. Where there are multiple associated Address Names, there will be blank rows in the Contacts section. These are expected by the Integrator and will not cause any issues.
The Site Names can be listed in any order, i.e. they don’t need to be on the same line as a specific Address, as there is a separate ‘Site Address Name’ column which links the Site Name to an Address. As a Site Name can be assigned multiple Client Business Units in the Site Assignments section, there may be blank rows between the Site Name records. Also, if the Site Assignment has not yet been defined against a Site, there will obviously be blank rows in the Site Assignments section.
The above is an example of a typical layout of sections of additional data relating to one Supplier record:
The Supplier Attachments, Business Classifications and Products and Services are associated only to the Supplier so they should be listed without any blank rows in between.
Attachments at Site level may cause there to be blank rows in the Site section if there are multiple Site Attachments associated with one Site. This is permitted by the Integrator.
Record Batching in the Supplier Integrator
More4apps takes advantage of REST web service payload batching in order to improve upload performance times. However, as of release 23C, only the following sections can batch records into larger payloads:
● Suppliers 50 records per batch
● Addresses 50 records per batch
● Supplier Contacts 50 records per batch
● Supplier Attachments 5 records per batch
● Site Attachments 5 records per batch
All other sections can only load 1 record at a time.
We hope Oracle will release more batching capability in the future to allow us to further improve the Integrator’s upload performance.
Products and Services – Category Type
Two values only are available for this field, BROWSING and PURCHASING. The image below displays the use of the PURCHASING category type:
BROWSING Category Types: these Categories, used in Oracle to identify classes of products, are assigned to Catalog Category hierarchies, e.g. ‘Office Supplies & Paper Products’ (parent Browsing Category) > ‘Mailing Supplies’ (child Browsing Category).
The BROWSING Categories do not have any Items directly assigned to them.
PURCHASING Category Types: these are also known as Item Categories. Within a Catalog, every Item belongs to a Purchasing Category and each Purchasing Category is associated with a Browsing Category. An example of a Purchasing Category associated with the Browsing Category ‘Mailing Supplies’ could be ‘Code: AA-BB-123 A4 Envelopes’.
This relationship is shown in the diagram below which is taken from the Oracle website:
Sections: