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

What Is Extensible Attribute Architecture?

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

Extensibility framework and features basically comes from Oracle Product Lifecycle Management (PLM).

Extensible Attributes are similar to DFF’s in the sense that Extensible Attributes feature provides out-of-the box capability to store additional information associated with certain EBS modules entities.In the past, Oracle Descriptive FlexFields (DFF) had a limitation of 15 or 22 data fields per record. There is no limit for Extensible attributes.

The functionality allows you to view and maintain these additional attributes without having to create custom screens. It also allow you to group related attributes and display attributes on specific UI pages.

dgreybarrow R12 Extensible Attributes –What are they?

  • Extensible attributes add additional rows or records into the database structure and therefore are limitless.
  • Extensible attributes can contain one single record (of numerous extended. data fields) or multiple record
  • The extended database fields have four data types to choose from and can contain list of value (LOV) definitions for data consistency (entry and reporting) and can control record inserts to be based upon uniqueness (no duplicates)

dgreybarrow In Comparison to Descriptive FlexFields (DFF)

Here are the quick comparision with DFF.

Extensible Attribute

dgreybarrow Some of the features are

  • Limited to certain EBS modules entities.
  • Attributes can be displayed as text, check box or radio group.
  • Database view is created for each attribute group.
  • Uses Value Set for attribute validation.
  • Extensible Attributes store unlimited number of repeating attributes (multiple rows of similar data), unlike Descriptive Flexfields.

dgreybarrowComponents of an extension:

  • Attribute Group
  • Attributes
  • Associations
  • Pages
  • Functions
  • Actions
  • Value Sets (Recommend creating before attribute groups)

Extensible entities have corresponding tables to store additional attributes.

For example, in the case of Teleservice some of the tables are CS_INCIDENTS_EXT_B, CS_INCIDENTS_EXT_AUDIT, etc.

If customer wants to use Extensible Attributes in Oracle Loans then you need to check with Loans Development to see if they implemented or not Extensibility framework.

Will see more details for TCA Extensible Attributes, in next post.

Posted in AOL, Oracle TCA | No Comments »

EBS Online Documentation Library

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

Oracle E-Business Suite is a comprehensive suite of integrated, global business applications which provides a customer focused strategy.You can access Online Documentation via

Use this web site to search the various documentation types for Oracle EBS Applications. This web page provides access to documentation available in PDF and HTML formats. Use the tabs to locate and view Oracle EBS documentation.

What’s New with in online Library?

  • You can get a master list of all books (Apps and ATG) from main page via “Index” link
  • This will have a enhanced search capability
  • Ability to create your ‘Favorite List’ of books, Click this link .
  • You can also have direct access to HTML version of documentation

EBS Online Library

dgreybarrow Similar Post

Posted in Misc | 1 Comment »

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 »