Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Oracle Desktop Integration Framework

Posted on June 5th, 2011 by Sanjit Anand ||Email This Post Email This Post

Oracle E-Business Suite Desktop Integration Framework or DIF in short bring you the design time framework to develop desktop integration solutions for Oracle E-Business Suite applications.This is important enhancement for Oracle 12.1.2.

If we look at high level architecture of Desktop Integration Framework, we see that it’s a design time framework, that lets you define integrator, interface, content, components and business rules for EBS applications across product families. And it leverages, Oracle Web ADI’s integrator services and metadata repository for its execution.
Architecture Desktop Integration Framework

On a very high level, you can say Desktop Integration Framework features are:

  • A wizard based UI used tocreate and manage desktop integrators.
  • It has ability to define integrator that can upload data through PL/SQL API or directly to database table.
  • It has ability to define integrator that can download data from text file or based on a SQL query.
  • It has ability to define data validation rules that ensure data integrity
  • It has ability to define UI components, so that you can embed EBS UI widgets such as LOVs, pop-lists, date pickers and flex fields in Excel.
  • You can leverage EBS security model – SSO integration compliant solution.
  • It has ability to consume integrator definition and create document within business flow.
  • It has ability to define layouts, mappings for custom integrators.

dgreybarrow What are the key components

Important one is Integrator

Integrator is metadata that encapsulates all information required to move data to and from desktop application into Oracle E-Business Suite. An Integrator definition may include information about open interface tables, validation, business rules, and data that can be downloaded.

In order to enable Developers to create and manage integrators, there is new responsibility called Desktop Integration Manager. So, user (say an Integration Developer) can create, update and delete custom integrators from EBS UI.

From Manage Integrators screen, you can search and view list of integrators. You can select an integrator and define layout and mappings for it.

Lets look at the screenshots below:

DIF menu

So, here we have new responsibility – Desktop Integration Manager

It has 4 functions – Manage Integrators, Create Integrator, Manage Components and Define Parameter.

When you clicks on Manage Integrator, Integrators page is displayed.


Now you can search integrator by name, internal name or code, application to which it belongs to, on its status – whether it is enabled or not. on UI Source is a column that indicates whether its Oracle seeded or custom created integrator.

As you can see in the above screenshot, search results for integrators belonging to Application Object Library is displayed. The Update and Delete icons for Custom integrator is enabled, whereas its disabled for Source ‘Oracle’ integrators.

Now, next question you have how user can create integrator.

Its very simple. As mention earlier, Desktop Integration Framework provides wizard based UI to create integrator.

you can access this wizard either by clicking ‘Create Integrator’ function from Desktop Integration Manager responsibility or by clicking Create Integrator button in Integrators list page.

Integrator 1

The first step in the wizard is to define integrator related properties – such as its name, internal name, to which application the integrator belongs to, whether its used for reporting only, its status – whether it is enabled or not. Then, there is a check box to indicate whether Integrator should be listed in Create Document page flow of Desktop Integration responsibility. Its very simple.

If this option is left unchecked, the integrator will not be available from Create Document function in Desktop Integration responsibility. However, the user can integrate the generate spreadsheet functionality within application functional page flow. Web ADI is used in the background to generate the spreadsheet or desktop document.

Then, you can select and expand Integrator Parameters section, which holds a list of parameters.

Integrator 2

Then, you can define function based security rules. You have LOV to help user search and select a function. Also, please note, Integrators with Enabled status as Yes are available for end-user in their business flow.

Now lets understand , the Integrator Parameters(look at the expanded view in above figure)..typically these are set of parameters that are defined by Integration Developer depending upon business requirement. These parameters are used by Integrator and Web ADI at run-time.

At the run-time, when end-user is done with data-entry and wants to upload the data to Oracle E-Business Suite. End-user clicks on Upload sub-menu under Oracle menu in Excel, then Upload Page is displayed. It has various options like which rows to upload (All or flagged), whether to validate data while uploading, whether to initiate import program to move uploaded data from interface tables to base tables.

  • Importer Parameters are used to define rules for importing data.
  • Upload & Server Parameters are used to define Upload Page that is displayed to end-user, and for back-end upload service.
  • Document Parameters are set of parameters required for creating document. It could be used to prompt end-user at run-time or programmatically pass them at run-time.
  • Session Parameters are used to define values that are to be stored with the document for the lifecycle of document, that is, for document’s session

Next Security Rules:

As mentioned earlier , user can define function based security rules for an integrator. It ensures that end-users who have access to assigned function can only, create document of integrator.

dgreybarrow Process Flow of Desktop Integration Framework:

In order to define custom desktop integrators the process remain same as earlier in WebADI. the steps are :

  1. Define Integrator properties,
  2. Create Interface
  3. Create Content
  4. Define Layout
  5. Define Mappings
  6. Create Document

Next few slides you can see the navigation steps with screen snapshots:


Integrator 11


If required, Create Content for integrator. There may be scenarios wherein you may want to define integrator for only data entry purpose that is only for uploading data to E-Business Suite, then you may not need to create content.

Next is Interface


As fourth step, create layout for the integrator. Then create mapping for the integrator. Finally, create document using the integrator definition.


next is query




Posted in Web ADI | No Comments »

Oracle Web ADI Information Query

Posted on December 14th, 2008 by Sanjit Anand ||Email This Post Email This Post

Often at the time of working with Oracle Web ADIs, we want to know what all components are associated with it like Integrator, Layout, Mapping, Underlying PL/SQL procedure etc.

Also while migrating Web ADIs from one instance to another (in case of Installation upgrades, or from Development Instance to Production Instance), using FNDLOAD, we need to know each associated component of a Web ADI to migrate it completely.

<pre lang=”plsql”>

bit.application_id APP_ID,
bit.user_name INTEGRATOR_NAME,
bit.integrator_code INTEGRATOR_CODE,
blcv.layout_code INTEGRATOR_LAYOUT,
bm.mapping_code INTEGRATOR_MAPPING,
biv.interface_name API,
biv.upload_type TYPE,
bne_integrators_tl bit,
bne_layout_cols_v blcv,
bne_layouts_b bl,
bne_interfaces_vl biv,
bne_contents_vl BC,
bne_mappings_vl BM
AND biv.interface_code = blcv.INTERFACE_CODE
AND bit.integrator_code=bl.integrator_code
AND bit.integrator_code=bc.integrator_code
AND bit.integrator_code=bm.integrator_code
AND UPPER(bit.user_name) LIKE UPPER(‘<integrator USER name>’)
</pre >

The query enables a you to reduce his time spent on analysis of a Web ADI. All that one should know is the name of the Integrator of the Web ADI. Even the end user (Business User) would know the name of the Integrator that they are using.

Posted in Web ADI | No Comments »

How to know Web ADI Version ?

Posted on July 18th, 2008 by Sanjit Anand ||Email This Post Email This Post

How to know ‘Web ADI’ Version in EBS?

You have two options to find the version of WebADI , if you do not want to get any help from DBA.

dgreybarrow-2Option 1(a) Release 12

  1. You need to logon in EBS
  2. Once you get the Homepage, you need to paste the url in the same browser window.
  3. You replace the hostname,domain and port number
  4. Once you enter these details, An html/xml return page list out the ‘Web ADI’ versions.
  5. Look for the attribute named “Bne Release Label”.

Read the rest of this entry »

Posted in Web ADI | 3 Comments »

Extending and managing Web ADI (Integrator Layout) – Part II

Posted on May 9th, 2008 by Sanjit Anand ||Email This Post Email This Post

This is yet another extension of previous post, will discuss how to manage and define layout of the WebADI integrator.

dgreybarrow-2 Managing/Defining Layout

You can also manage /Define layouts, means you can build the spreadsheet by modifying the Layouts.

You must be in responsibility with access to the integrator to define the layout.

  • Responsibility: Desk Integration
  • Menu Options : Define Layout

Read the rest of this entry »

Posted in Web ADI | No Comments »

Extending and managing Web ADI (Integrator) – Part I

Posted on May 9th, 2008 by Sanjit Anand ||Email This Post Email This Post

As mention in earlier post (#1,#2,#3 ) , WebAdi is tool that can be used to load many different types of data from spreadsheet based excel application into various application of Oracle APPS. There are number of Seeded Integrator comes with Oracle, but still Oracle provides the capability to its expandability. Various Integrators to load different types of information. However, you can do setups new, custom spreadsheet can be created to load different types of information into Oracle.

dgreybarrow-2 Basic User Procedure we have seen for a webADI is


  1. Use the webADI page Consist of creating spreadsheet by
    1. Specific to data type which we called as integrator
    2. Specific to Layout which is for controlling purpose of the spreadsheet.
  2. Adding Data to the excel Spreadsheet.
  3. In spreadsheet, you need to select the Oracle/Upload menu option.This is menu option that you can use from WebAdi added from Excel menu.
  4. Than the data get uploaded to Oracle target table, which might be custom, or base. Any error will be flagged and the error reason will be placed on corresponding row in the spreadsheet.

Read the rest of this entry »

Posted in Oracle General Ledger, Web ADI | 14 Comments »

R12 : Uploading a Journal using Web ADI : Step by Step

Posted on May 7th, 2008 by Sanjit Anand ||Email This Post Email This Post

In last two post we have seen , Web ADI is a Browser based application, which enables users to log into the Oracle database and upload ADI spreadsheets, without having the ADI application installed onto the users machine.We have already seen step by step setup in 11i , now this post is extension of previous post with a case of R12.

1. Responsibility: As mention earlier WebADI User linked to the correct Set of Books for your business. In R12 , the starting point would be responsibility called Desktop Integration


Read the rest of this entry »

Posted in Oracle General Ledger, Web ADI | 2 Comments »

WebAdi : Desktop Integration makes life easier

Posted on May 2nd, 2008 by Sanjit Anand ||Email This Post Email This Post

Lets take about one of the great office productive tool based application which is called “Web ADI” that being used within the E-Business Suite to provide end-users with a familiar user interface.Key end users are highly accepted this productive tool , because of there own advantages and great office capability.

greyBarrow ADI & Web ADI…

ADI stands for Applications Desktop Integrator, and is an Excel based interface through which users can upload and view data in the Oracle system.To access the database, users must use their standard Oracle User name, and password.

Web ADI is a Browser based application, which enables users to log in to the Oracle Database, and upload ADI spreadsheets, without having to have the ADI application loaded locally on the users machine, or having it set up on a central server and users accessing it through Citrix.

For Web ADI to work, interfaces are set up. These interfaces are Macro driven spreadsheets, in which specific cells are linked to database table columns, and match to fields in the Standard Oracle Forms. Through them data is fed into the database, which can subsequently be viewed in the Core Oracle Forms.

  • The leveraging of Desktop Application functionality for performing E-business Suite tasks.
  • Web ADI is a java based tool used to load many different types of data from Excel into varied application modules.
  • This tool resembles the client-server ADI in name only. It has no concurrent manager or publication functionality. It also requires no client code to be loaded on the PC.

adi evalaution

greyBarrowThe difference between ADI and WebADI

The main big between ADI and Web ADI, is that Web ADI is now based out of framework for building Desktop Integration applications in the EBS.That means we can designed and extend with a combination of meta-data and java. There is no requirement for these teams to know Visual Basic for Applications or the techstack requirements to get Office to interact with the Oracle Middle Tier or any of a hundred different nuances in the desktop environment.

Read the rest of this entry »

Posted in Oracle General Ledger, Web ADI | 16 Comments »