Visual Builder Add-In vs. FBDI

When Voya Financial chose to use Visual Builder Add-in (VB) over FBDI, they had several reasons to do so. First, VB was faster than FBDI for multiple actions. Second, VB can be opened and used quickly once the format is created. Third, all actions are taken on a single screen. Finally, the error messages are presented directly at the time of load.

In contrast, FBDI is slower to accomplish tasks than VB. You must recreate each time from the standard template, and there are multiple steps required for creation and load. Furthermore, the error messages are often found only at the end of processing. These differences made the solution clear for Voya Financial.

Visual Builder Add-In was the way to go.

Processes Improved with Visual Builder Add-In

Since utilizing Visual Builder Add-In, Voya Financial has experienced improvements in the following processes:

• Supplier Update
• PO Cancellation
• PO Close
• PO Schedule Close
• Invoice Creation
• Retrieval of Supplier, PO, and Requisition details

Installing Visual Builder Add-in

To install Visual Builder, you’ll navigate to the Oracle Downloads page and download the installer. Then you’ll run the .exe. Restart your computer, open Excel, and you’ll see the Visual Builder Add-In on the ribbon.

Initial Configuration

For your initial configuration, you’ll launch Excel, navigate to the Oracle Visual Builder tab in the ribbon and select Designer to launch the layout wizard.

To create a layout in the workbook, the REST services that you use must provide a service description that complies with the OpenAPI specification. The service description can be a URL or a local file. For Oracle business object REST API services, the URL typically includes a describe path segment. An example is:

https://my-service-host/fscmRestApi/resources/latest/invoices/describe

The first part of the connection will be using the Voya Oracle Cloud URL:

https://ekmd-test.fa.us2.oraclecloud.com

Using REST API for Oracle Procurement Cloud – All REST Endpoints, find the desired API endpoint. This will be the second part of the connection. The example below is using the Get all purchase orders endpoint:

/fscmRestApi/resources/11.13.18.05/purchaseOrders

Combine the web address and the API endpoint. Select Next.

After completing the Single Sign-On form, select Finish, and then Done.

Next, select Designer from the ribbon. Select the newly created connection and click Next.

From this window, select the desired fields that need to be included or select the top level to include all fields.

Select either the Table Layout option or the Form-over-Table Layout.

Managing Visual Builder Add-In Layouts

Once the layout has been configured and populated with data, the sheet can be customized further using the Layout Designer.

General Tab – Used to edit the Origin Cell and Business Objects. Editing the BO allows for users to make modifications to fields, custom actions, filters, and attachments.

Query Tab – Used to filter on specific data. Users can use this to search for specific items in the data set or filter based on given criteria.

Columns Tab – Can be used to add or remove columns from the sheet.

Advanced Tab – Used to create Macros and modify table capabilities.

Closing a PO Use Case

Using the newly created Purchase Order sheet, POs can be updated directly from Excel using the Visual Builder Add-In. To accomplish this, locate the PO that needs to be closed using the Query tab on the Layout Designer. Add a Custom Action field using the Columns tab. Then, select Upload Changes from the ribbon.

Next, navigate to Columns and select the + symbol. This will bring up the Table Column Manager, where the custom action column titled Close Action can be added to the table.

To apply the filter to the table, select Download Data from the ribbon again. Now, this will only pull data with a status of Open and will include the new field.

To close a PO, locate the PO, add the word Close in the corresponding Close Action row or column, and select Upload Changes from the ribbon.

If the action was successful, the status column will display Succeeded: Close. The result can be validated by logging in to Oracle, searching the PO, and verifying that it was closed.

For a tutorial on using this add-in, please view the Using Visual Builder Demo in the Quest Learn Library.