Oracle EBS R12.1 and 12.2 Difference

====================================
Application Front End Difference
====================================


1) New Profile :- Self Service Personal Home Page mode (Framework Simplified)
      Oracle Applications Look and Feel profile option to "Skyros Look and Feel"
   FND: Enable Rich Table Interactions profile option to "True"


2) OAF Admin Personalization Workbench - Redesigned (Easier Page Personalization with visual Design)
  - What You See Is what you get
  - Layered View of Personalization Levels, with Preview of Resulting Page
  - Drag and Drop to Move Page Elements
  - Personalizatoin inclue :
    = Expand Tables/ Add Columns
= Hide/Show Regions
= Reorder Page/ Region Elements
= Change Lables
= Set Default Values
Reordering columns
Resizing columns
Hiding and showing columns
Detaching tables from the base page (except HGrids)
Scroll horizontally if the contents of a table exceeds the browser width
Refresh a table by querying for the latest records
Reset a table back to its original definition

3) Added New Theams

4) Iprocurement  with information discovery
 - Auto-Suggest Catalog Items
 - Show Procurement Activities to Requesters
 - New Supplier Onboarding for non catalog
 - New Supplier Creation for Spoy Buy
 - Simplified Shopping cart

 Purchasing
--------------------------------------
 Automated Grouping of multiple requests to PO
 Validate agreement line amount during Order/Release Submission

 Procurement Contracts

 Content Search and Snippet Review (Search inside pdfs of the contracts)


 Payables
-------------------------------------


 Sending workflow approval notificaions in parallel.
 Invoice validation concurrent program support multiple child
 request based on the Purchase Order matched invoice.

 Profile Name  AP: Maximum lnvoice Validation Child Requests

 Customer and Supplier bank accounts can be created or searched

 on IBAN

====================================
 Database
====================================

 Dual File System
         (3 files for each object from 11.2.0.3)
- File System 1 - Run Edition
- File System 2 - Patch Edition
- FS NE - Non Edition File system
DB
- Run Edition , Patch Edition , Old Edition
 Online Patching

 Mobile compactability


====================================
 Technical
====================================
 Scripts required for 12.2.X custom table development

Table Names must be unique at 29 bytes or less
Column Names must be 28 bytes or less
Editioning View added (# suffix) to the base table.APPS synonyms now point to the Editioning View
Use Synonym to point to Global Temp Table
Materialized Views - Create a Logical View A Materialized View Definition must be stored in an ordinary view called MV_NAME||'#'

1) For new table creations - after creating the table in custom schema execute below script to generate editoning view and synonym for it in APPS schema.

exec AD_ZD_TABLE.UPGRADE('XXCUST','XX_CUST_TBL1');

2) For table alteratuons - after running the DDL run below script to regenerate the editioning view for syncing any table changes.

exec AD_ZD_TABLE.PATCH('XXCUST','XX_CUST_TBL1')

3) Table grants must be done through API to avoid invalids.

exec AD_ZD.GRANT_PRIVS('SELECT','XX_CUST_TBL1','XX_ROLE0')

4) To view objects in all editions..add _ae to the data dictionary views

select * from user_objects_ae;

5) To update seed data tables in Patch edition, execute prepare command.

example:
 exec ad_zd_seed.prepare('WF_MESSAGES');

The prepare will create a edition based storage for the run edition data for which the updates will be made. During cutover, the run time data will be synced using forward/reverse cross edition triggers.