MICHIGAN ORACLE USERS SUMMIT
DEPLOYING CUSTOM WEBADI
INTEGRATORS IN R12.XPRESENTER NAME: JOHN J. GOMEZ
PRESENTER TITLE: ORACLE EBS PROJECT MANAGER
COMPANY : SYNTAX
WEDNESDAY, OCTOBER 30, 2019 / 7:30AM – 5:30PM
SCHOOLCRAFT COLLEGE –VISTATECH CENTER
18600 HAGGERTY ROAD, LIVONIA, MI 48152
OBJECTIVES
Show users how to batch load information into their Oracle EBS environment by using seeded data.
Eliminate blot-on applications which streamlines your configurations AND reduces total cost of ownership.
Demonstrate flexibility for development based on different programming disciplines.
Showcase flexibility to interact with different Oracle Modules to batch load data.
CONTENT OVERVIEW
Web Application Data Integrator (WebADI) Overview Pre-requisites Designing your Integrator Building your integrator Demo Q&A
WEB APPLICATION DATA INTEGRATOR (WEBADI) OVERVIEW
Oracle provides tools to enable uploads of large quantities of data into via Spread Sheet Uploads.
This established functionality, however the ability to create custom, non-Oracle provided integrators, is now more user friendly.
The first versions of this tool required the installation of a Microsoft Windows program as well as Microsoft Excel. Many long-time EBS users will remember it as Desktop ADI and Request
Center. For additional information please reference My Oracle Support Note
726727.1
PRE-REQUISITES/ASSUMPTIONS Your environment is at the most current patch level for your version of
EBS R12. The seeded WebADI Integrators are working correctly. This activity requires development resources. Your user configuring the custom integrator has experience with the
seeded WebADI Integrators. Ability to read/write basic SQL also needed.
Implementation experience with the target module requiring the integrator is needed.
Microsoft Office is properly configured to use WebADI. Custom integrator will only import data.
DESIGNING YOUR INTEGRATOR
Obtain detailed requirements regarding before beginning. Treat integrators with the same level of attention you’d give to interfaces or SQL
Loaders. Custom integrators can use API’s for loading data into seeded or custom tables. Custom programs that facilitate loading of data into seeded tables, interfaces or
custom tables exist. Most business users are accustomed to Excel This frees development and speeds up adoption of your solution.
Your custom integrator will function and look the same as the Oracle provided ones. This reduces the need to train users.
DESIGNING YOUR INTEGRATOR – CONT’D
You can only tie one custom integrator to one module/application each. For example, a custom Accounts Payable loader will only be tied to AP. It cannot also load data to Accounts Receivable at the same time.
Will you use an API or custom program to load your data? Here we use a concurrent program for loading of data. Both methods require you to create a staging table to house imported data
prior to loading to your destination. Using a custom schema to house your staging table is HIGHLY
recommended.
DESIGNING YOUR INTEGRATOR – CONT’D
Will data require validation prior to entry into the Excel Spread Sheet or as part of entry….? If some of your data consists of lookups, then this should be identified as part of your design.
This allows you to design an upload Spread Sheet that validates data as the information is being entered.
This alleviates the amount of programming required when building the integrator. Oracle provides the ability within custom integrators to design pop up windows as well as
drop-down lists as a method of data entry to assure that only valid data is allowed as part of your upload. System populated look-ups allow you to control datasets.
BUILDING YOUR INTEGRATOR
Creating a new integrator can be done through configuration wizards. They guide you through the process and help to make sure you don’t miss anything.
To begin you will need the following responsibilities: Desktop Integration Manager Functional Administrator
BUILDING YOUR INTEGRATOR – CONT’D
Desktop Integration Manager R12.2.7Managing your integrators
This responsibility allows you to view the existing integrators that are a part of your system.
For Oracle provided integrators, you will only be able to view the configurations.
The responsibility also allows you the ability to launch your integrator from this screen.
BUILDING YOUR INTEGRATOR – CONT’D
Functional Administrator WebADI & OAF
WebADI relies heavily on the Oracle Application Framework for its look and feel.
As with any other webpage-intensive application many of the changes that are made to your configurator will rely on your ability to clear the server cache for them to display.
The navigation to this screen is: Functional Administrator →Core Services →Caching Framework .
BUILDING YOUR INTEGRATOR – CONT’D
Prior to starting the wizard to define your integrator, you should: Ensure your upload table has been
defined. A developer must do this. Confirm the configuration of your table
using Application Developer Navigate to Application →Database →Table.
You can then query for your import table.
Note: You can not register your table through this form.
BUILDING YOUR INTEGRATOR – CONT’D
There are 5 steps that the wizard will guide you through when defining a new integrator. 1. Integrator Name 2. Interface to be used 3. Contents to be used (if applicable) 4. Uploader (Seeded or custom) 5. Importer (API, Custom program)
BUILDING YOUR INTEGRATOR – CONT’D
Defining your import destination This step is critical for how your
integrator will receive data as well as what the user interface will look like. As you can see, once you
select a destination in this case a table, you are able to look attributes of how that information will be used as well as presented.
BUILDING YOUR INTEGRATOR – CONT’D
Content Sets
Content Sets are utilized within Integrators as a means of loading specific information as a part of your upload. They are also useful when creating a reporting – only integrator.
In this example we will not be using any Content Sets.
BUILDING YOUR INTEGRATOR – CONT’D
The Uploader
The uploader is the window that will be presented to users when they are ready to import their data through the integrator. Users new to the integrators should use
Template be utilized. The uploader is also the location that
allows you to prompt the user for specific parameters that may be required by your concurrent program or API.
Parameters defined within the uploader can be passed and utilized by your concurrent program at a later step.
BUILDING YOUR INTEGRATOR – CONT’D
The last step in building your integrator is defining the importer. This tells the system which method you will use
to load your data from the staging destination you’ve created to its final destination within EBS. In this case AP Invoices.
This is where you tie in any specific parameters that you prompted the user for during the upload into your concurrent program or API call.
For this example we have defined an asynchronous concurrent request. This means that the concurrent program will generate any specific error messages through it’s output. No messages will be returned through the spreadsheet to the user.
The Importer
BUILDING YOUR INTEGRATOR – CONT’DLists of Values
An excellent way of assuring that only valid data is loaded into your system is to use Lists of Values. To accomplish this you will need to define a custom component. This example show the definition of a vendor name LOV.
Once you have defined your custom component you will need to link it to the field in your staging table that it applies to. As shown here.
This is the alias for the table column you are using for your data.
Tells the system to sort order for your data.
This is the column in your source table where your data is coming from. It must match identically.
This is the name of the table column in your staging table.
This is the name of the table your source data is coming from.
This will be the name of the LOV the user is presented in the spread sheet.
Once defined your component is available within the Component Name LOV.
There are two types of LOV available. One is “Pop List”, this creates a pop-up window within your spread sheet. The other is “Standard”,
this generates a drop-down list within your spread sheet.
Demo R12.2.7 Vision Environment
Q&A
SAVE THE DATE
WWW.MOUS.US
THANK YOU
• COLLABORATE 20April 19-23, 2020
Mandalay Bay Resort & Casino
Las Vegas, NV
• MOUS 2020October 28, 2020
Schoolcraft College -VisTaTech Center,
18600 Haggerty Rd, Livonia, MI
SURVEYS
WWW.MOUS.US
THANK YOU• Session Surveys
Please complete the session survey for this
session using Guidebook.
https://guidebook.com/g/mous2019
• Conference SurveyPlease complete the hard copy conference
survey at the end of the conference and
turn it in at the MOUS registration desk.
