EBS 12.2 represents our most-groundbreaking release in years (Press Release). It includes new product functionality, new Fusion Middleware and database components, and introduces new tools for installing, configuring, and maintaining E-Business Suite environments:
Hundreds of new featuresIncludes significant enhancements across the integrated suite of business applications spanning enterprise resource planning, human capital management, and supply chain management. You can find the complete list here:
Online PatchingApply EBS patches while users are still entering transactions and using the E-Business Suite. Online Patching uses the Oracle Database’s Edition-Based Redefinition feature and other new technologies to allow the E-Business Suite to be updated while the system is still running. You can learn more about Online Patching via our official documentation and this technical webcast.WebLogic ServerUses Oracle WebLogic Server, which replaces the Oracle Containers for Java (OC4J) application server used in EBS 12.0 and 12.1. You can learn more about how this improves the system administration experience via our official documentation and this technical webcast.
- E-Business Suite 12.2 Release Content Document (Note 1302189.1)
Upgrading to EBS 12.2Is there a direct upgrade path from EBS 11i to 12.2?Yes, there is a direct upgrade path from EBS 126.96.36.199 to EBS 12.2. EBS 188.8.131.52 customers do not have to install an intermediary EBS 12 release (such as 12.1.3) before upgrading to EBS 12.2. EBS 184.108.40.206 customers must have applied the minimum baseline patch requirements for Extended Support as described in Patch Requirements for Extended Support of Oracle E-Business Suite Release 11.5.10 (Document 883202.1). Customers on earlier EBS 11i releases (such as 11.5.7) need to be at the 220.127.116.11 level plus the minimum baseline patch requirements for Extended Support before they can upgrade to EBS 12.2.Is there a direct upgrade path from EBS 12.0 to 12.2?Yes, there is a direct upgrade path from EBS 12.0.4 and 12.0.6 to EBS 12.2. EBS 12.0.4 or 12.0.6 customers do not have to install an intermediary EBS 12 release (such as 12.1.3) before upgrading to EBS 12.2. Customers on earlier EBS 12.0 releases (such as 12.0.3) will need to be at the 12.0.4 or 12.0.6 level before they can upgrade to EBS 12.2.Is there a direct upgrade path from EBS 12.1 to 12.2?Yes, there is a direct upgrade path from EBS 12.1.1, 12.1.2, and 12.1.3 to EBS 12.2.How can I prepare for EBS 12.2?
- Option for installing EBS 12.2 on to existing database servers.
- Capability of installation into existing Real Application Clusters environments.
- Database deployment on Automatic Storage Management (ASM) and other file systems.
More technical references
- Read the Oracle E-Business Suite 12.2 Technical Planning Guide, First Edition (Note 1585857.1)
XML Publisher reports
Application File System
- Server with Responsibility
When needed one and the same profile option can be assigned to different levels. For example, when you implement Global Security Profiles to create access control on Operation Units – every responsibility for an Operating Unit may need a setting for profile options MO: Security Profile and HR: Security Profile. In the form which is used to set profile options all those different responsibilities can’t be seen at once.
In that case I use the SQL statement below to quickly provide me a list of the values of a profile option for all levels.
The profile option name (column profile_option_name from table applsys.fnd_profile_options) can be found within the definition of the profile itself through responsibility Application Developer – menu Profile.
Here’s the SQL to provide you the values on all levels of a specific profile.
10007,m.node_name||’ + ‘||b.responsibility_name,a.level_id) LEVEL_VALUE,
NVL(a.profile_option_value,’Is Null’) VALUE,
to_char(a.last_update_date, ‘DD-MON-YYYY HH24:MI’) LAST_UPDATE_DATE,
e.profile_option_name = ‘XLA_MO_SECURITY_PROFILE_LEVEL’ AND e.PROFILE_OPTION_NAME = pot.profile_option_name (+)
AND e.profile_option_id = a.profile_option_id (+)
AND a.level_value = b.responsibility_id (+)
AND a.level_value = c.application_id (+)
AND a.level_value = d.user_id (+)
AND a.level_value = n.node_id (+)
AND a.LEVEL_VALUE_APPLICATION_ID = x.responsibility_id (+)
AND a.level_value2 = m.node_id (+)
AND a.LAST_UPDATED_BY = dd.USER_ID (+)
AND pot.LANGUAGE = ‘US’
- Item1 —- Black
- Item2 —- Red
- Item3 —- Green
- Item4 —- Orange
- R12 – How to Delete Oracle AR TransactionsMarch 22, 2019 - 8:37 pm
- How to Define Custom Key Flexfield (KFF) in R12January 19, 2018 - 5:43 pm
- AutoLock Box Concepts In R12November 10, 2017 - 8:30 am
- R12 – java.sql.SQLException: Invalid column type in OAFSeptember 15, 2017 - 9:39 am
- How to Find Duplicate Row in OAF Page?April 26, 2017 - 5:17 pm