Thursday, September 19, 2019

Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 (Doc ID 1916149.1)

https://community.oracle.com/community/support/oracle_e-business_suite/e-business_customizations

 Migrating and Managing Customizations for Oracle E-Business Suite 12.2

https://learn.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=904&get_params=cloudId:243,objectId:15787


Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)

Oracle E-Business Suite Release 12.2 includes significant database and file system architecture changes designed to support the new Online Patching feature.
Consequently, integrations with Oracle E-Business Suite may need to be modified to comply with new deployment and development standards in order to work correctly with Oracle E-Business Suite Release 12.2. Examples include custom and third-party integrations, as well as integrations with other Oracle products such as Oracle Application Express.
Note: This document supplements the main Online Patching documentation, which is covered in books including Oracle E-Business Suite Concepts and Oracle E-Business Suite Developer's Guide. See References section at the end of this document.

In This Document

Section 1: Integration Types and Compliance Requirements

The Oracle E-Business Suite Release 12.2 database architecture introduces a new Logical Schema layer that maps to the base product tables, which are now considered a private Physical Schema.
Key points about the Logical Schema include:
  • The Logical Schema is the public interface of the Oracle E-Business Suite database schema, and is the layer through which applications (including integrations) may access Oracle E-Business Suite tables.
  • The Logical Schema is implemented via APPS table synonyms and Editioning Views, and accessed from the Oracle E-Business Suite APPS schema.
  • The table and column definitions of the Logical Schema are mapped to physical table columns in the product schemas.
  • The logical-to-physical mapping may change without warning during online patching cycles, so it is no longer safe to reference the physical tables and columns in the product schemas directly.
The Oracle E-Business Suite Release 12.2 file system architecture contains two complete copies of the application tier code, called the dual file system. One of the file systems in the dual file system is used by the running application, and the other is used for patching. The run and patch file system designations switch with each patching cycle. Data files are stored on a third file system, called the non-editioned file system (fs_ne).
Modifications may need to be made to an integration for it to comply with Oracle E-Business Suite Release 12.2 development and deployment standards.
There are two types of compliance, minimal compliance and full compliance.
  • Minimal compliance is required for an application to function correctly at runtime.
  • Full compliance is required for your integration be patched online.
The table below lists the type of compliance, the rules that your integration must adhere to to achieve that compliance, and the tools that you can use to test that adherence.
Type of ComplianceRuleTools
MinimalNon-editioned objects cannot depend on editioned objects.Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations
MinimalReferences to the data model must go through a synonym in the apps schema.Run gscc.pl and fix all violations. Run ADZDDBCC.sql and fix all violatons tagged as minimal.
FullFollows rules for minimal compliance plus additonal development standards laid out in the Developer's Guide.Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations. Run gscc.pl and fix all violations. Run ADZDDBCC.sql and fix all violations, including those tagged as minimal and those tagged as full.

Note: For instructions on using the scripts referred to in this document – such as ADZDDBCC.sql – you may refer to My Oracle Support Knowledge Document 1531121.1, Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2.
The rest of this section describes the five principal integration categories, and how to determine whether any modifications are required for them to be compliant with the Oracle E-Business Suite Release 12.2 architecture.

1.1 Integration via application tier web services or other interfaces

Integration characteristics

This category of integration:
  • Works with Oracle E-Business Suite exclusively through web services, or other application tier interfaces such as file import or application tier APIs.
  • Does not have a database schema that must be installed on the Oracle E-Business Suite database.
  • Only interacts with Oracle E-Business Suite via application tier web services or other application tier public interfaces (that is, it does not make a direct connection to the Oracle E-Business Suite database).

Release 12.2 compliance requirements

For minimal compliance:
  • No changes are required for products in this category to achieve minimal Oracle E-Business Suite online patching compliance.
For full compliance:
  • Because the code for this integration category does not reside within the Oracle E-Business Suite file system, it cannot be patched using Oracle E-Business Suite Release 12.2 online patching.
Note: When your code interacts with Oracle E-Business Suite Release 12.2 data files, remember that they will be located on the non-editioned file system.

1.2 Integration via database connection or independent database schema

Integration characteristics

This category of integration:
  • Makes a direct connection to the Oracle E-Business Suite database.
  • May install custom database objects that do not have direct dependencies on Oracle E-Business Suite objects.
  • May reference Oracle E-Business Suite objects such as APPS synonyms, views and PL/SQL packages from outside the Oracle E-Business Sute database.
  • Does not make any changes to the Oracle E-Business Suite schema (via DDL) during installation or runtime operation.

Release 12.2 compliance requirements

For minimal compliance:
  • Direct references to Oracle E-Business Suite objects must be through the APPS (logical) Schema.
    • Direct references to objects in the Oracle E-Business Suite APPS (logical) schema (synonyms, views, or PL/SQL packages) are permitted.
    • Direct references to objects in the Oracle E-Business Suite product (physical) schemas are prohibited.
  • You must run the Global Standards Compliance Checker (gscc.pl) against code that has references to Oracle E-Business Suite code and fix any violations.
For full compliance:
  • Because the code for this integration category does not reside within the Oracle E-Business Suite file system, it cannot be patched using Oracle E-Business Suite Release 12.2 online patching.

1.3 Integration via custom schema with dependent database objects

Integration characteristics

This category of integration:
  • Installs a custom schema into the Oracle E-Business Suite database, which includes objects that depend on Oracle E-Business Suite objects.
  • Does not make any changes to the Oracle E-Business Suite schema (DDL) during installation or runtime operation.

Release 12.2 compliance requirements

For minimal compliance:
  • The custom schema may only directly reference objects in the Oracle E-Business Suite APPS (Logical) schema.
  • The custom schema must be enabled for editioning.
    • If the custom schema exists during the Oracle E-Business Suite Release 12.2 upgrade, it must be registered with Oracle E-Business Suite and will be upgraded for editioning automatically.
    • If the custom schema is installed after the Oracle E-Business Suite Release 12.2 upgrade, the custom schema must be registered with Oracle E-Business Suite and enabled for editioning.
  • You must run the Global Standards Compliance Checker (gscc.pl) and fix any violations.
  • You must run the Online Patching Readiness Reports:
    • Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations.
    • Run ADZDDBCC.sql and fix any violations tagged as "[minimal]".
For full compliance:
  • If you want to be able to patch your application online, you must:
    • Meet the above requirements for minimal compliance.
    • Fix any violations listed in the output of ADZDDBCC.sql (this includes sections marked both [full] and [minimal]).

1.4 Integration via extension or customization of Oracle E-Business Suite schema

Integration characteristics

This category of integration:
  • Extends or customizes the Oracle E-Business Suite Logical or physical schema via any of the following methods:
    • Installing a custom Oracle E-Business Suite product schema and registering a custom Oracle E-Business Suite product.
    • Installing objects into an existing Oracle E-Business Suite APPS or product schema.
    • Installing triggers on existing Oracle E-Business Suite tables.
    • Installing any other code that will be invoked by Oracle E-Business Suite runtime operations such as alerts, workflow activities, and business event subscriptions.

Release 12.2 compliance requirements

Integrations in this category are essentially additional Oracle E-Business Suite product functionality, and must conform to the full requirements of the Oracle E-Business Suite Release 12.2 Development Standards.
Be aware that:
  • Release 12.2 Object definition standards and usage standards and Dynamic DDL standards apply to all code running as part of Oracle E-Business Suite.
  • Release 12.2 Object patching standards apply to all objects that will be patched using online patching.
For minimal compliance:
  • You must run the Global Standards Compliance Checker (gscc.pl) and fix any violations.
  • You must run the Online Patching Readiness Reports:
    • Run ADZDPSUM.sql, ADZDPAUT.sql, and ADZDPMAN.sql and fix any violations.
    • Run ADZDDBCC.sql and fix violations tagged as "[minimal]".
For full compliance:
To achieve full Release 12.2 compliance, so you can patch your application online:
  • Meet the above requirements for minimal compliance.
  • Fix any violations listed in the output of ADZDDBCC.sql (this includes sections marked both [full] and [minimal]).

1.5 Integration via table replication

Integration characteristics

This category of integration:
  • Replicates data from Oracle E-Business Suite product tables using either:
    • ETL Replication via Oracle Data Integrator or similar mechanism.
    • Stream Replication via Oracle Streams or Oracle Golden Gate.

Release 12.2 compliance requirements

For minimal compliance:
  • ETL Replication must access Oracle E-Business Suite tables via the APPS (Logical) Schema.
    • To achieve minimal online patching compliance, you must run the Global Standards Compliance Checker (gscc.pl) against the metadata definition that drives the ETL replication, and fix any violations reported.
  • Stream Replication of tables from Oracle E-Business Suite Release 12.2 is not currently supported.
For full compliance:
  • The code for this integration category cannot be patched using Oracle E-Business Suite Release 12.2 online patching.

Section 2: Additional Guidance for Meeting Integration Compliance Requirements

This section provides additional information on how to implement Oracle E-Business Suite Release 12.2 integration compliance requirements.

2.1 Access Oracle E-Business Suite tables via the APPS (Logical) Schema

Oracle E-Business Suite Release 12.2 implements a Logical Schema in the APPS user. The APPS table synonyms point to editioning views instead of the original product tables. The APPS synonyms and editioning views serve to map logical table and column names to the physical tables and columns that provide the actual data storage.
The Oracle E-Business Suite Logical Schema can differ from the Oracle E-Business Suite Physical schema in the following ways:
  • The Logical Table Name is the name of the APPS table synonym. The Physical Table Name is normally identical to the Logical Table Name, but can be different if the storage table is replaced with a revised table in an online patch.
  • The APPS table synonym normally points to the Editioning View of the storage table, rather than the table itself. The Editioning View name is automatically generated from the storage table name by appending a '#' character, thus:
    editioning_view_name := substr(storage_table_name, 1, 29)||'#';
  • The Logical Column Names for a table are defined by the editioning view. The editioning view maps the Logical Column Names to the Physical Columns Names of the storage table. Logical column names start off identical to physical column names, but over time the original physical columns may be replaced with revised columns that have different names: for example, 'AMOUNT', 'AMOUNT#1', 'AMOUNT#2'...
  • The physical table may provide storage for multiple editions (copies) of data. In this case, rows stored in the physical table are filtered by a VPD policy so that only the appropriate edition of data is visible in the logical schema. When accessing the table through the logical schema, this filtering policy is applied automatically: however, access to the physical table would see all copies of the data and lead to incorrect results.
The details of the Oracle E-Business Suite Logical-to-Physical schema mapping are normally hidden from application code by the simple practice of accessing Oracle E-Business Suite tables via the APPS table synonyms. However, some products may attempt to introspect the Oracle E-Business Suite schema definition by querying the Oracle Data Dictionary views. Any such products will need to be enhanced to understand the difference between the Oracle E-Business Suite Logical and Physical schema, and how to query the applicable information from the data dictionary views.
The Oracle E-Business Suite Online Patching Development Standards contains supplemental information about how data dictionary view queries used in Oracle E-Business Suite Release 12.1 can be modified to produce the corresponding query of either logical or physical structure in Oracle E-Business Suite Release 12.2. If your integration contains a repository of metadata about Oracle E-Business Suite table and column structure, you will also need to consider whether the repository information is meant to represent logical or physical schema information, and be ready to modify the repository data accordingly.

2.2 Enable editions for integrated schemas referencing Oracle E-Business Suite objects

If your integration uses a database schema that has hard-coded dependencies on Oracle E-Business Suite objects, that schema must enable editions in the Oracle database. Although the act of enabling editions is a simple DDL command, there are requirements that must be satisfied before the enablement will succeed. When a schema is enabled for editions in Oracle Database 11.2, all code objects owned by that schema become editioned, which means that the objects can have different definitions in each database edition.
The key requirement is that there can be no non-editioned objects (in any schema) with a hard dependency on an editioned object (in the integrated schema).
Examples of problematic dependencies include:
  • Table columns that depend on a TYPE (user defined type) in the integrated schema.
  • PUBLIC synonyms or synonyms in non-editioned users that reference code objects in the integrated schema.
  • In Oracle Database 11g, materialized view queries that reference code objects in the integrated schema.
    • In Oracle Database 12g, the "evaluate using current edition clause" can be employed to create a materialized view that depends on editioned code objects.
  • XML SCHEMA objects owned by integrated schema.
Oracle E-Business Suite Release 12.2 includes a schema upgrade procedure that can automatically fix the above issues and enable editions on a specified user. But your custom product will also need to be able to install correctly into an Oracle E-Business Suite Release 12.2 database where editioning is already enabled. To accomplish this, your install process will need to enable editions on a schema immediately after creating the schema, before creating any objects in that schema.

References

The following links provide additional information on the Oracle E-Business Suite Release 12.2 architecture, development standards, and the Online Patching feature.

7. Change Log

DateDescription
2016-07-14
  • Under Section 1 compliance table, added notebox with reference to Doc 1531121.1.
2016-07-11
  • In Sections 1.1 to 1.5, created and populated subsections for minimal compliance and full compliance.
2016-03-31
  • Made various updates throughout document.
2014-08-15
  • Initial publication.
My Oracle Support Knowledge Document 1916149.1 by Oracle E-Business Suite Development.

 

at No comments:

Tuesday, September 17, 2019

How To Audit An Oracle Applications' User? in R12

How To Audit An Oracle Applications' User? in R12

How To Audit An Oracle Applications' User?

Sign-On:Audit Level allows you to select a level at which to audit users who sign on to Oracle Applications.
 Four audit levels increase in functionality: None, User, Responsibility, and Form.
 None is the default value, and means do not audit any users who sign on to Oracle Applications.

Auditing at the User level tracks:
Who signs on to the system
The times users log on and off
Auditing at the Responsibility level performs the User level audit functions and tracks:
- The responsibilities users choose
- How much time users spend using each responsibility

Auditing at the Form level performs the Responsibility level audit functions and tracks:
The forms users choose
How long users spend using each form
System Administrator visible, revisable at all levels.
One can monitor users in the System Administrator responsibility by navigating to:
Security -> User-> Monitor form.  This is the Monitor Users Window. Use this window to monitor what the application users are currently doing.
 As well as seeing which users are signed on, one can see:
Which responsibilities, forms (windows), and terminals they are using
How long they have been logged in;
What Oracle database processes they are using.

In addition there are 5 reports that one can run that will provide user audited information:

Signon Audit Concurrent Requests - Use this report to view information about who is requesting what concurrent requests and from which responsibilities and forms.
Signon Audit Forms - Use this report to view who is navigating to what form and when they do it.
Signon Audit Responsibilities - Use this report to view who is selecting what responsibility and when they do it.
Signon Audit Unsuccessful Logins - Use this report to view who unsuccessfully attempted to sign on to Oracle Applications as another user. An unsuccessful login occurs when a user enters a correct username but an incorrect password. You can generate Signon Audit Unsuccessful Logins Reports for any users, regardless of whom one is auditing.
Signon Audit Users - Use this report to view who signs on and for how long.

With System Administrator responsibility navigate to:
Profile => System
Query for profile: "Sign-On:Audit Level"
Set the site level value to "FORM" // if User Lever "USER"
     Sign-On:Audit Level = FORM   // USER
Save the record.
Logout and login again.
Retest the issue.

Note: The concurrent program "Purge Signon Audit Data" should be used regularly to purge old sign on data.

395849.1,1359749.1,104282.1
+++++++++++++++++++++++++
For user sessions since auditing was enabled, run the "Signon Audit Users" concurrent request.
 The following query should help in finding out previous login times:

1. Log into sqlplus as the apps user.

2. Perform the following select:

SQL> select to_char(creation_date,'DD-MON-YY HH:MI:SS'), disabled_flag
from icx_sessions
where user_id=(select user_id from fnd_user where user_name = 'OPERATIONS');
/
Notes:
1. The disabled_flag = N means the session is still active.
2. The sessions shown are from the time the icx_sessions table was last purged.
3. This query gives all the login times, not just logins that happened prior to enabling sign-on audit. Add a date filter to the where clause if you only want sessions prior to the date when sign-on audit was enabled.

1364259.1
++++++++++++++++++++=
Note:
First of all, auditing at the responsibility level is enabled as a system profile option called Sign-On:Audit Level. Sign-On:Audit Level can be done for the site, responsibility and user and can be done at the form, responsibility and the user level. In other words, it works like a matrix. If you decide to audit a responsibility, then you need to decide at what level: form, responsibility or user. If you audit the responsibility at the form level, then you will get the most details about who used the responsibility, what forms they accessed using this responsibility, when they accessed the responsibility and when they left the responsibility. If auditing the responsibility is done at the responsibility level, you will not get the forms that the responsibility accessed but you will get everything else. If you audit the responsibility at the user level, you will get the user that accessed the responsibility, when they started and when they stopped. Very limited data.

The second level of auditing is for the data itself. This auditing is called AuditTrail and is more involved in setup. You need to identify the data that you want to audit and then translate that to the specific table and column that you want tracked. Audit groups are then created from the identified columns and tables (note that you can audit different tables and different columns within those tables). It is not common place to audit all of the columns for all of the HR or Payroll tables given the amount of resource that will be required to create and store information in the shadow tables that are created specifically for auditing.
The reports for the Sign-On:Audit Level can be found using the System Administrator responsibility and they are:

Signon Audit Concurrent Requests
Signon Audit Forms
Signon Audit Responsibilities
Signon Audit Unsuccessful Logins
Signon Audit Users

=====================================
What Tables Are Involved In Using The System Profile 'Sign-On:Audit Level'? [ID 368260.1]
Sign-On: Audit Level can be set at 4 different levels.  The level you specify will determine which Change Tracking  information Integra Apps will capture.  
The four levels (from lowest to highest level of audit) and the information that they capture are:

1. None
Tracks no additional info.

2. User
Tracks:
    who signs on to Oracle Apps
    the time users log on and off
    the terminals in use

3. Responsibility
Tracks:
    User Info
    the responsibilities user choose
    how much time users spend using each responsibility

4. Form
Tracks:
    User Info
    Responsibility Info
    the forms users choose
    how long users spend using each form

Based on the level chosen, the information captured gets stored in the following tables:

    FND_LOGINS
    FND_LOGIN_RESPONSIBILITIES
    FND_LOGIN_RESP_FORMS

1. Least detailed level: User.
When the profile is set to User, the only table that gets updated is the table FND_LOGINS and only one record per user session.

2. Next level: Responsibility.
When the profile is set to Responsbility both FND_LOGINS and FND_LOGIN_RESPONSIBILITIES will be updated.
FND_LOGINS gets only one record per user session.
FND_LOGIN_RESPONSIBILITIES will be updated with one record for each
responsibility selected during the session.

3. Most detailed level: Form.
When the profile is set to Form all three tables are involved.
FND_LOGINS gets only one record per user session.
FND_LOGIN_RESPONSIBILITIES will be updated with one record for each
responsibility selected during the session.

FND_LOGIN_RESP_FORMS will be updated with one record for each form selected during the session.
+++++++++++++++++++++++++++++++++

To BottomTo Bottom
In this Document
Goal
Solution
References

APPLIES TO:

Oracle Application Object Library - Version 11.5.9 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
***Checked for relevance on 24-Nov-2012***
Reviewed for Relevance 29 Jul 18.

GOAL

Step-by-step action for setting up an audit on an EBS Applications user.

SOLUTION

Sign-On:Audit Level allows you to select a level at which to audit users who sign on to Oracle Applications. Four audit levels increase in functionality: None, User, Responsibility, and Form.  None is the default value, and means do not audit any users who sign on to Oracle Applications.

Auditing at the User level tracks:
  • Who signs on to the system
  • The times users log on and off
  • Auditing at the Responsibility level performs the User level audit functions and tracks:
    - The responsibilities users choose
    - How much time users spend using each responsibility
Auditing at the Form level performs the Responsibility level audit functions and tracks:
  • The forms users choose
  • How long users spend using each form
  • System Administrator visible, revisable at all levels.
One can monitor users in the System Administrator responsibility by navigating to:
Security -> User-> Monitor form.  This is the Monitor Users Window. Use this window to monitor what the application users are currently doing. As well as seeing which users are signed on, one can see:
  • Which responsibilities, forms (windows), and terminals they are using
  • How long they have been logged in;
  • What Oracle database processes they are using. 
In addition there are 5 reports that one can run that will provide user audited information:
  • Signon Audit Concurrent Requests - Use this report to view information about who is requesting what concurrent requests and from which responsibilities and forms.
  • Signon Audit Forms - Use this report to view who is navigating to what form and when they do it.
  • Signon Audit Responsibilities - Use this report to view who is selecting what responsibility and when they do it.
  • Signon Audit Unsuccessful Logins - Use this report to view who unsuccessfully attempted to sign on to Oracle Applications as another user. An unsuccessful login occurs when a user enters a correct username but an incorrect password. You can generate Signon Audit Unsuccessful Logins Reports for any users, regardless of whom one is auditing.
  • Signon Audit Users - Use this report to view who signs on and for how long. 
For further detailed information please read "Oracle Applications System Administrator's Guide - Security Release 11i"; Chapter 5 'User and Data Auditing'
Still Have Questions?
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Utilities Community.

To provide feedback on this note, click on the Rate this document link.

REFERENCES

NOTE:1359749.1 - AP: How to Enable Auditing on a Table With No Primary Ke?
at No comments:

Oracle Web Applications Desktop Integrator (Web ADI) Tips for Troubleshooting (Doc ID 390476.1)


Click to remove from FavoritesTo BottomTo Bottom
In this Document
Purpose
Troubleshooting Steps
References

APPLIES TO:

Oracle Web Applications Desktop Integrator - Version 11.5.10.0 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

PURPOSE

This document is to help better understand Web ADI setup and configuration with Oracle Applications, and touch on the key issues seen within ATG Web ADI Support.
Section 1: Overview
Section 2: Trouble Shooting
Section 3: Web ADI Patches
Section 4 Client PC Configuration
Section 5 Work Around
Section 6 Web ADI Debug
Section 7 When to Create New Templates
Section 8 Further BNE Resources

TROUBLESHOOTING STEPS

Section 1 Web ADI Overview:
Web Applications Desktop(Web ADI) is a tool for Users which allows the upload and export of data to and from Oracle Applications using standard desktop office products.

This is done though the standard desktop products, such as Microsoft Word and Excel

Web ADI is becoming a more popular product for the Users as they become more experienced with the standard Word and Excel functionality, and the ease of using Cut and Paste or Dragging information directly to Excel and hitting the upload function.

Web ADI is integrated into almost every functional product, and overlaps with the standard Export functionality seen in Core Forms.


Release 12 Desktop Integrator Responsibility
Official script for BNE responsibilities is: $BNE_TOP/patch/115/import/US/bneresp.ldt
For Release 12.x, this ldt does just have 'Desktop Integration' responsibility, and it has had just that one in all versions for 120.x and 120.x.1200000.x

Integrators:
-An Integrator is a Web ADI term used to encapsulate all of the information required to move data to/from a desktop application into Oracle Applications. An Integrator definition may include information about open interface tables, validation, business rules, and data that can be downloaded.

-System Administrator > Application > Function > create a new function
          similar to the Web ADI Create Document function, but change the bne:page=BneCreateDoc

-URL Call
BneApplicationService?bne:page=BneCreateDoc

-A list of currently installed integrators can be seen with the following SQL query :
select user_name from bne_integrators_tl order by 1;

-This query lists the integrator name and product and can be used to just see what integrators are available for a particular Product

SELECT biv.integrator_code,
biv.user_name,
fa.application_id,
fa.application_short_name
FROM bne_integrators_vl biv,
fnd_application fa,
fnd_application_tl fat
WHERE biv.application_id = fa.application_id
AND fa.application_id = fat.application_id
/* The next line can be commented out to return all products */
AND fa.application_short_name = '&ApplicationShortNameApplicationShortName'
AND fat.language = 'US'
ORDER BY fa.application_short_name,
biv.user_name;

-To allow a Integrator to be removed from the list or enabled, update the enabled_flag on the bne_integrators_b table to "Y" or "N" for the desired :
integrator_code/application_id combination.
UPDATE bne_integrators_b
SET enabled_flag='N' 
WHERE integrator_name='<Integrator name>';

Viewers:
-A Viewer is a Web ADI term for the desktop application in which a document will be generated.

-A customer can select Excel 97 from the list and still generate a spreadsheet
successfully on Excel 2007.

The BNE .ldt file which creates the Viewer List is the bnevw.ldt. For example, the Version 115.59.1013.4 Will deliver the Excel 2007 for 11i Applications.

$BNE_TOP/patch/import/US/bnevw.ldt

FNDLOAD APPS/APPS 0 Y UPLOAD $BNE_TOP/admin/import/bnevw.lct $BNE_TOP/patch/115/import/US/bnevw.ldt

Layouts:
-A Layout tells Web ADI which columns will be displayed in the Desktop Application document and how those columns will be displayed, including formatting. Web ADI provides a set of screens that users and Integrator Developers can use to create their own Layouts. Integrator Developers are able to provide Layouts as seed data.

FNDLOAD APPS/APPS 0 Y UPLOAD $BNE_TOP/admin/import/bnelay.lct $BNE_TOP/patch/115/import/US/bnelay.ldt

Tables related to Layout definition:
-select count(1) from BNE.BNE_LAYOUTS_B;
-select count(1) from BNE.BNE_LAYOUTS_TL;
-select count(1) from BNE.BNE_LAYOUT_BLOCKS_B;
-select count(1) from BNE.BNE_LAYOUT_COLS;
-select count(1) from BNE.BNE_LAYOUT_LOBS;

select lt.user_name, lc.layout_code, lc.block_id, lc.interface_seq_num
from bne_layout_cols lc, bne_layouts_b lb, bne_layouts_tl lt
where lb.application_id = lt.application_id
and lb.layout_code = lt.layout_code
and lb.integrator_app_id = 231
and lb.integrator_code = 'JOURNALS_115'
and lc.application_id = lt.application_id
and lc.layout_code = lt.layout_code
and lt.language = 'US'
and lc.application_id = 231
and lc.interface_app_id = 231
and lc.interface_code = 'GL_INTERFACE_115'
order by lc.layout_code, lc.block_id, lc.interface_seq_num;


Content:
-This is the information that will be downloaded into the Viewer. Content definitions is to identify the data to be downloaded, and any required parameters. The Content that is passed to or selected in the Create Document page flow determines the Content that will be used to derive the Content data.

Can be a Text File or Java Class for Content.


-Tables related:
BNE_CONTENTS_TL
BNE_CONTENTS_B
BNE_CONTENT_COLS_TL


The Login URL for the BNE when attempting to Upload.
oracle.apps.bne.webui.pageflow.BneOALoginPage.class calls the cancelUrl and successUrl


How BNE pulls the Responsibilities:

Bne Responsibilities web page is
oracle.apps.bne.webui.pageflow.BneOALoginPage2.java

Which, gets the resp list from
oracle.apps.bne.utilities.oa.BneOASessionUtils.java

Which uses these queries:

sqlQuery = "SELECT RT.RESPONSIBILITY_NAME, UR.RESPONSIBILITY_APPLICATION_ID, UR.RESPONSIBILITY_ID " +
"FROM FND_RESPONSIBILITY_TL RT, FND_RESPONSIBILITY R, FND_USER_RESP_GROUPS UR " +
"WHERE UR.USER_ID = :1 " +
"AND SYSDATE BETWEEN UR.START_DATE AND NVL(UR.END_DATE, SYSDATE) " +
"AND R.APPLICATION_ID = UR.RESPONSIBILITY_APPLICATION_ID " +
"AND R.RESPONSIBILITY_ID = UR.RESPONSIBILITY_ID " +
"AND SYSDATE BETWEEN R.START_DATE AND NVL(R.END_DATE, SYSDATE) " +
"AND R.APPLICATION_ID = RT.APPLICATION_ID " +
"AND R.RESPONSIBILITY_ID = RT.RESPONSIBILITY_ID " +
"AND RT.LANGUAGE = :2 ";
if ( version != null )
{
sqlQuery += "AND NVL(R.VERSION, '0') = :3 ";
}
sqlQuery += "ORDER BY 1 ";

OR

String sqlQuery = "SELECT RT.RESPONSIBILITY_NAME, UR.RESPONSIBILITY_APPLICATION_ID, UR.RESPONSIBILITY_ID, S.SECURITY_GROUP_NAME, S.SECURITY_GROUP_ID " +
"FROM FND_RESPONSIBILITY_TL RT, FND_RESPONSIBILITY R, FND_USER_RESP_GROUPS UR, FND_SECURITY_GROUPS_VL S " +
"WHERE UR.USER_ID = :1 " +
"AND SYSDATE BETWEEN UR.START_DATE AND NVL(UR.END_DATE, SYSDATE) " +
"AND R.APPLICATION_ID = UR.RESPONSIBILITY_APPLICATION_ID " +
"AND R.RESPONSIBILITY_ID = UR.RESPONSIBILITY_ID " +
"AND SYSDATE BETWEEN R.START_DATE AND NVL(R.END_DATE, SYSDATE) " +
"AND R.APPLICATION_ID = RT.APPLICATION_ID " +
"AND R.RESPONSIBILITY_ID = RT.RESPONSIBILITY_ID " +
"AND UR.SECURITY_GROUP_ID = S.SECURITY_GROUP_ID " +
"AND RT.LANGUAGE = :2 ";

if ( version != null )
{
sqlQuery += "AND NVL(R.VERSION, '0') = :3 ";



BNE Servlets:

The Release 12 BNE Servlets can be found under following location:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

Note: Don't confuse '$IAS_ORACLE_HOME' with '$ORA_CONFIG_HOME' as the $IAS_ORACLE_HOME will point you to the wrong
orion-web.xml.


<!-- WEBADI Servlets -->

<servlet>
<servlet-name>BneApplicationService</servlet-name>
<servlet-class>oracle.apps.bne.webui.BneApplicationService</servlet-class>
</servlet>

Description:
Application Service is a re-implementation of a simple UIX ( CABO ) Page Broker. Its
primary purpose is to deliver UIX ( CABO ) pages and flows ( including menus ) via
a BneBasePage Controller and BneBasePage which retains UIX ( MARILN ) nodes and
event handling.

<servlet>
<servlet-name>BneComponentServiceBneComponentService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.component.BneComponentService</servlet-class>
</servlet>

Description:
BneComponentServiceBneComponentService - Calls Component Classes passing all parameters.
This is one of the three Web ADI servlets. It is concerned with the
running of Web ADI components - most typically LOVs.
It runs in secure (non GUEST) authentication mode. If a user is not logged
in with a non GUEST account, it will force them to log in.


<servlet>
<servlet-name>BneDocumentServiceBneDocumentService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.document.BneDocumentService</servlet-class>
</servlet>

Description:
BneDocumentServiceBneDocumentService - servlet used for launching Bne Viewers.
This servlet is deprecated in favor of using the Create Document page flow which will use
the BneTemplateService to stream viewers. This will give transparent cross browser support
on the windows platform, whereas this service relies on Internet Explorer functionality.

As of R12, this servlet has been changed to take advantage of Document Parameters stored in
the database. The core viewer parameters are now sourced from here and not the servlet
request/parameter list in the servlet session.

<servlet>
<servlet-name>BneViewerXMLServiceBneViewerXMLService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.document.BneViewerXMLService</servlet-class>
</servlet>

Description:
BneViewerXMLServiceBneViewerXMLService extends BneAbstractXMLServletBneAbstractXMLServlet. Its main steps are to Perform Validation,
Load Viewer Class, Run Viewer Creation and Stream XML.

<servlet>
<servlet-name>BneDownloadServiceBneDownloadService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.download.BneDownloadService</servlet-class>
</servlet>

Description:
BneDownloadServiceBneDownloadService extends BneAbstractXMLServletBneAbstractXMLServlet.

<servlet>
<servlet-name>BneOfflineLOVServiceBneOfflineLOVService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.download.BneOfflineLOVService</servlet-class>
</servlet>

Description:
BneOfflineLOVServiceBneOfflineLOVService extends BneAbstractXMLServletBneAbstractXMLServlet.

<servlet>
<servlet-name>BneUploaderService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.upload.BneUploaderService</servlet-class>
</servlet>

Description:
Web Interface for Web ADI Uploads. An upload is the process of receiving
an xml file of data from the viewer (excel, word, project, etc), parsing the
xml, validating the data and either loading it into database tables or passing
the data values to an API, either pl/sql (currently) or java (in the future)

Upload functionality is accomplished at a high level by three classes.

BneUploaderService (which takes the handleRequest (from BneAbstractXMLServletBneAbstractXMLServlet,
which is a wrapper over the doGet/doPost from HttpServlet) into a call to....)
BneUploader (which handles calling the main upload functionality via SAX)
BneSAXUploader</li>


BneUploaderService is the web interface to the BneUploader class. All of the significant
functionality of the upload is accomplished by the BneUploader class, refer to the javadoc
for BneUploader for details about the upload functionality.

Effectively this makes BneUploaderService a web wrapper for the BneUploader class.
As such, there are four main functions carried out by BneUploaderService.
1st, obtain the upload file (and any http request parameters) from the servlet request
2nd, ensure that the request is made within a self service applications session
3rd, call the processUpload method of the BneUploader class
4th, return any messages to the calling environment, in xml format

<servlet>
<servlet-name>BneTemplateRedirectServiceBneTemplateRedirectService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.document.template.BneTemplateRedirectService</servlet-class>
</servlet>

Description:
BneTemplateRedirectServiceBneTemplateRedirectService extends BneHTMLServletBneHTMLServlet.

<servlet>
<servlet-name>BneTemplateService</servlet-name>
<servlet-class>oracle.apps.bne.integrator.document.template.BneTemplateService</servlet-class>
</servlet>

Description:
This class is a part of the Web ADI framework used to stream Template
(or Bootstrap) viewers to the client. It requires only the bne:documentId
parameter sent on the http request.

<servlet>
<servlet-name>BneAdminServletBneAdminServlet</servlet-name>
<servlet-class>oracle.apps.bne.framework.BneAdminServlet</servlet-class>
</servlet>

Description:
This servlet is a facility to help administer Web ADI.
It acts as a service to:
-get log file information
-change your log level
-various middle tier information
-reset internal caches

<servlet>
<servlet-name>BneCaboTestServletBneCaboTestServlet</servlet-name>
<servlet-class>oracle.apps.bne.framework.BneCaboTestServlet</servlet-class>
</servlet>

Description:
This servlet is for testing Web ADI UIX configuration settings. It creates four pages,
the first is a default form which is used to call 2 explanation pages and 2 test pages:UIXsimple
or UIXcomplex. The form parameter "showpage" determines which of these pages is shown,
if there is no value for showpage, a form is displayed giving the user various choices.
Otherwise the appropriate html or UIX page is shown.

<servlet>
<servlet-name>BneSnoopServletBneSnoopServlet</servlet-name>
<servlet-class>oracle.apps.bne.framework.BneSnoopServlet</servlet-class>
</servlet>

Description:
This servlet is used to test the configuration of a Bne Servlet,
shows the java properties and servlet properties.


Release 11.5.10 BNE Servlets can be found under following location:
$IAS_ORACLE_HOME/Apache/Jserv/etc/zone.properties

# ----- WEBADI Servlet -----
#
servlet.BneSnoopServlet.code=oracle.apps.bne.framework.BneSnoopServlet
servlet.BneProxy.code=oracle.apps.bne.share.BneProxy
servlet.BneComponentService.code=oracle.apps.bne.integrator.component.BneComponentService
servlet.BneDocumentService.code=oracle.apps.bne.integrator.document.BneDocumentService
servlet.BneApplicationService.code=oracle.apps.bne.webui.BneApplicationService
servlet.BneCaboTestServlet.code=oracle.apps.bne.framework.BneCaboTestServlet
servlet.BneUploaderService.code=oracle.apps.bne.integrator.upload.BneUploaderService


You may see references to BNE in the jserv.properties, however this parameter is no longer used as of 11.5.9 and higher.
wrapper.classpath=/u02/oracle/visappl/bne/11.5.0/conf

This relates to $BNE_TOP/conf/webadi.properties. This file is also no longer used but still exists on the 11.5.10 file system.
This properties file was replaced by the Profiles and zone.properties file.

The main tables in ADI are as follows:

BNE_CONTENTS_TL
BNE_INTEGRATORS_TL
BNE_INTERFACES_TL
BNE_INTERFACE_COLS_TL
BNE_LAYOUTS_TL
BNE_LAYOUT_COLS
BNE_MAPPINGS_TL


Section 2 Trouble Shooting:

1. Functional Setup Test through BNE Admin Servlet:

BNE Admin Servlet.

http://<server_name>:<server_port>/oa_servlets/oracle.apps.bne.framework.BneAdminServlet

Please note down the BNE Code Level, Java Version and Log Information sections. Provide this information to Support.

At this point Clear the BNE Cache, by clicking on the Link. At the bottom of the page you should see 'Cache Cleared'

2. Upload the Journal Import Request 'View Output' to the SR, if the issue reported is related to the Upload functionality.

3. To enable Debug, set the BNE Profiles:
BNE Server Log Filename = <provide name>
BNE Server Log Level = TRACE
BNE Server Log Path = <set to the value of the $APPLTMP> OR <match the value given in the webadi.properties for 11i.


4. Log in to the Applications as the System Administrator and navigate to Applications - Function.

Query the %BNE%

Check the Function BNE_CREATE_DOCUMENT and make sure the correct Web HTML call is to the Servlet BneApplicationService and that the Web Host is set to the correct host.

5. Check if BNE is Installed:

select application_short_name, application_name, product_version,status
from FND_PRODUCT_INSTALLATIONS , fnd_application,fnd_application_tl
where fnd_product_installations.application_id = fnd_application.application_id
and fnd_product_installations.application_id = fnd_application_tl.application_id
and language = 'US'
and application_short_name = 'BNE';

COL app_s_name FORMAT a16
COL inst_status FORMAT a15
COL product_version FORMAT a12
COL patchset FORMAT a15
COL appl_id FORMAT 99999

select fav.application_id APPL_ID,
fav.application_short_name app_s_name,
decode(fpi.status,'I','Installed','S','Shared','N','No', fpi.status) inst_status,
fpi.product_version,
nvl(fpi.patch_level, 'Not Available') patchset
from fnd_application_vl fav, fnd_product_installations fpi
where fav.application_id = fpi.application_id
and fav.application_short_name = 'BNE';

For a more comprehensive picture, run the AD Configuration Report ($AD_TOP/sql/adutconf.sql) to document the status of an Oracle E-Business Suite system, and provide information about all installed products (including shared and dependent products).

If a shared product is present in the shared products list of any installed products (you can verify this from the $APPL_TOP/admin/applprod.txt file)

6. What patchset level do you have for Web ADI?
select substr(aa.application_short_name,1,20) "Product", a.patch_level "Patch Level"
from fnd_product_installations a, fnd_application aa
where a.application_id = aa.application_id
and aa.application_short_name = 'BNE';



Section 3 Web ADI Patches:
NOTE: Many Web ADI code fixes are delivered within ATG Rup patches.  Please ensure to apply the more recent ATG Rup patch to obtain the latest ADI code fixes.
Please review Note 726989.1 List of Patches in Web Applications Desktop Integrator (Web ADI) for Releases 11i and 12, for all the latest BNE Patchs.

Note that there are a number of Patches labeled as BNE A and each BNE A Patch(set) is different. Pay attention to the release date and patch number. The same for BNE B Patch(set). For Release 12, BNE A typically go with the R12.0.x and the BNE B typically go with 12.1.x version.


Section 4 Client PC Configuration:

The main issues are related to the Microsoft Office or the Browsers not configured correctly to meet the Web ADI requirements.

For the Browsers, to create an excel spreadsheet on your desktop through Web ADI, the 'Initialize and script Active X controls not marked as safe' setting must be set to 'Prompt'. This is only defaulted to this value on a 'Low' security setting', therefore you will probably need to alter this setting through Internet Explorers Custom Settings option as follows; Select Tools -> Internet Options -> Security tab from the Internet Explorer Menu Bar. Select the zone that you are running Oracle E-Business Suite through and click the 'Custom Level' button. You can then set the value as recommended above.

Changing Macro Security Settings for Excel XP/2003
For Web ADI to work with Microsoft Excel 2002/2003, you must change the macro
settings for Excel 2002/2003. To do so:
1. In Excel, from the Tools menu, select Macro, then Security, then Security Level.
2. Select the "Medium" option.
3. Select the Trusted Sources tab.
4. Select the "Trust access to Visual Basic Project" option.

Changing Macro Security Settings for Excel 2007
For Web ADI to work with Microsoft Excel 2007, you must change the macro
settings for Excel 2007. To do so:
1. Click the Office Button (top-left button in the window)
2. Click the 'Excel Options' button.
3. Click 'Trust Center' link from the menu on the left.
4. Click 'Trust Center Settings...' button.
5. In the 'Trust Center' window click 'Macro Settings' link from the menu on the left.
6. Under 'Macro Settings' check 'Disable all macros with notification'.
7. Under 'Developer Macro Settings' check 'Trust Access to the VBA project object model'.
8. Click 'OK' button to close the 'Trust Center' window.
9. Click 'OK' button to return to the spreadsheet.

Changing Macro Security Settings for Excel 2010
1. Click File -> Options
2. Click 'Trust Center' link in the 'Excel Options' window.
3. Click 'Trust Center Settings...' button.
4. In the 'Trust Center' window click 'Macro Settings' link from the menu on the left.
5. Under 'Macro Settings' check 'Disable all macros with notification'.
6. Under 'Developer Macro Settings' check 'Trust Access to the VBA project object model'.
7. Click 'OK' button to close the 'Trust Center' window.
8. Click 'OK' button to return to the spreadsheet.

Make sure the Browsers are configured per the following documents in order for the Web ADI to function correctly.
Note 285218.1 Recommended Browsers for Oracle E-Business Suite 11i

Note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
Is Safari for Mac supported for WebADI on EBS R12?
As documented in the known issues section of Note 864552.1,
the following Oracle E-Business Suite Release 12 products are not certified for Mac OS X:
    * Oracle E-Business Suite Release 12 ADI and Web ADI.
Section 5 Work Around:
Web ADI is a Reporting Tool, that has all the product specific reports under a central location. Each Product will still have there own reports located somewhere within that products functionality, so its just a matter of locating the equivalent report. Each product offers Export functionality for another method of manipulating the Data with Microsoft Office products.
Note:
Web ADI support issues cannot be Severity 1 or Severity 2P1. The highest any ADI issue can be is Severity 2. Web ADI is a tool that replicates functions that can be performed under each Product within the Oracle Applications. There is always a work around to the Web ADI though product specific Reports and Export functionality.



Section 6 Web ADI Debug:

Gathering BNE RDA for 11i and R12 will provide all the BNE Class files and there versions, Profiles, BNE Tables along with other Key Information.

Since the old BNETEST is no longer supported or used, the RDA has basically become the replacement.

1. Login to E-Business Suite using your username/password
2. Select the "Application Diagnostics" or the "Oracle Diagnostics Tool" responsibility
3. Click on the Registered Test linked to Web Applications Desktop Integrator.
4. Enter:
Responsibility ID = 24076
Application Shortname = BNE
Your apps username and password.
Click on the Run Test button.
5. Upload results to SR
OR
Basic Test Quick Test
Run this basic WebADI test to see if WebADI is functioning:
1. Make sure that to have  the Oracle Web ADI Responsibility added to the sysadmin user.
Security > User > Define
Query up the Sysadmin user.
Add the Oracle Web ADI Responsibility
Save Changes.

2. Verify the Menu associated with the Oracle Web ADI responsibility is "Web ADI Menu (1)"
Security > Responsibility
Query up the Oracle Web ADI responsibility and verify that the menu associted with this responsibility is "Web ADI Menu (1)".

3. Add the function "Daily Rates Web-ADI Spreadsheet" to the "Web ADI Menu (1)" menu.
Application > Function
Give it a name/prompt and add the function "Daily Rates Web-ADI Spreadsheet".
Save the changes.
Check the concurrent request and verify that the menus recompiled successfully.

4. Logout and back in, then run this WebADI Test:
Responsibility = Oracle Web ADI
 > Create Document >
Viewer = Excel 2000
Next
Integrator = General Ledger - Daily Rates
Next
Continue to accept the defaults and click on Next until the document is created.

Does this complete successfully?

To enable Debug, set the profiles under System Administrator - System Profiles
Example:
BNE Server Log Filename : <create name> (make sure name doesn't exist already and if it does, delete it)
BNE Server Log Level : TRACE
BNE Server Log Path : (free to choose, eg. in the $LOG_HOME/bne.log) (use the full path to the $LOG_HOME)
BNE profile options are only valid at the Site Level.
If you make changes to any of the profile options, you will need to bounce the web services before the changes will take effect.
If this is a Multi-Node environment, make sure the BNE Log is being created on the Middle tier that the BNE is running on.

Reproduce the issue.

Once the issue was reproduced, turn off Trace by setting BNE Server Log Level back to Detail.

Upload the Trace to Support


Section 7 When to Create New Templates:
Their will be some cases that Customers Pre-Saved Web ADI Templates no longer work or fail to upload. The major reason for this is due to Architectural changes with the environment using the Web ADI.
In some cases Web ADI is on an environment that goes though Architectural changes, such as moving to SSL, SSO or Load Balancer Configurations, the Web ADI Pre-Saved Integrators will need to be recreated due to Server URL and and other various information being Hard Coded in the Excel Macro's. For SSO, Load Balancer the Issue will be related to the Arcitecural change with the Login URL being incorrect. For SSL, it will be a combination for Server URL along with SSL Certificate Keys. Web ADI is a Web Server based application that uses Apache Servlets. If you look into the Functions under Sysadmin Responsibility -> Responsibility and lookup Web ADI you will see all the Functions set up are calling Servlets to luanch the particular Menu call. This will be set under the HTTP Tab. If the URL Call set in this Function changes, the Pre-Saved Templates will fail due to the Macro passing a invalid or particular authentication to the Oracle Applications. Due to this, the Templates will no longer work and will need to be re-created.
Other reasons to create New Templates:
- Upgrade of Applications. Example: Customer has upgraded from R11.5.10 to R12.1.3 or even 12.1.2 to 12.1.3
- Upgrade of Database. Example: Upgraded from RDBMS version 11.1.0.4 to 12.1.0.1
- Upgrade of Excel. Example: Upgraded from Excel 2007 to Excel 2013
- Upgrade of Apps Server.
- In addition, old workbooks/templates tend to get corrupted over a period of time and could cause errors.
You will need to Recreate the Template using the Web ADI Create Document flow. Select the Cells you want to copy from the Old Template and click Copy. Select the Cell in the Upper left and copy the data to the new Template created using the Edit Menu, click Paste Special to paste to the cells. Click Values. This copies the values to the new Template.

Section 8 Further BNE Resources:

Oracle® Web Applications Desktop Integrator Implementation and Administration Guide
Release 12 Part No. B31411-01
http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120bneig.pdf

Oracle® Web ADI Implementation and Administration Guide
Release 11i Part No. B15518-01
http://download.oracle.com/docs/cd/B25516_18/current/acrobat/115bneig.pdf

Note 726989.1 List of Patches in Web Applications Desktop Integrator(Web ADI) for Releases 11i and 12

Note 285218.1 Recommended Browsers for Oracle E-Business Suite 11i

Note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12

Note 106528.1 Application Desktop Integrator - Product Documentation

Note 1077728.1 Using Microsoft Office 2007 and 2010 with Oracle E-Business Suite 11i and R12

Note 1251224.1 FAQ: Certification Information For Client ADI And Webadi

REFERENCES

NOTE:285218.1 - Recommended Browsers for Oracle E-Business Suite 11i
NOTE:106528.1 - Application Desktop Integrator - Product Documentation
NOTE:389422.1 - R12: Recommended Browsers for Oracle E-Business Suite
NOTE:726989.1 - Web Applications Desktop Integrator (Web ADI) List of Patches
NOTE:1077728.1 - Microsoft Office Integration with Oracle E-Business Suite 11i and R12
NOTE:1251224.1 - FAQ: Certification Information For Client ADI And Webadi
at 3 comments:
Subscribe to: Posts (Atom)

Oracle E-Business Suite Release 12.2 System Schema Migration

In This Document Section 1: Overview of the EBS System Schema Section 2: Requirements for Using the EBS System Schema Section 3: Migrating t...