R12 Features ----------------------------1) Oracle JInitiator will no longer be required to run Oracle Forms in E-Busines s Suite R12.

Oracle Forms in R12 will run directly in the native Sun Java2 Standard Edition P lug-in 2) Java Servlet Access From HTML Based client i) The User clicks the hyperlink of a function from a browser. ii)The Browser makes a URL request to the Web Listener. iii) The Web Listener contacts the servlet engine (OC4J), where it run t hs JSP iv) The JSP obtains the content from the Applications tables and uses th e information from the metadata dictionary to construct the HTML page v) The resulting HTML page is passed back to the browser, via the Web se rver. 3) Total R12 Vision need to have minimum 160 GB for instalation. 4) Multi Org Access Control (MOAC) enables business to use shared Services. 5) Follow changes has been taken place in Suppliers 1) Suppliers becomes as a TCA Party -- AP_SUPPLIERS and HZ_PARTIES 2) Supplier Sites as TCA Party Site for each Distinct address - AP_SUPPL IER_SITES_ALL and HZ_PARTY_SITES 3) Contacts for each supplier/address, it means single supplier address and contact can be leveraged by multiple sites for each Operating Unit 4) HZ_PARTY_USG_ASSIGNMENTS stores the Supplier Type in the PARTY_USAGE_ CODE. 6) To set the Client info mo_global.set_policy_context('S', &org_id); New Column MULTI_ORG_CATEGORY in FND_CONCURRENT_PROGRAMS added Values are 'S' Means Single Org 'M' Multi Org In Upgrades Set these Values update fnd_concurrent_programs set multi_org_category={'S' or 'M'} where concurrent_program_name='{program Name}' 7) In R12 all tables will be created under each Module Schema. Example: PO. PO_HEADERS_ALL A synonym will be created under APPS schema referring to Module Table PO .PO_HEADERS_ALL Another synonym named PO_HEADERS will be created in APPS Schema referrin g to PO_HEADERS_ALL A row level security is applied to PO_HEADERS synonym using package MO_G LOBAL.ORG_SECURITY This can be verified by issuing following command. select * from all_policies where object_name='PO_HEADERS' The effect of this policy is that, whatever you access PO_HEADERS, oracl e RLS (Row Level Security) will dynamically append the WHERE_CLAUSE similar to below SELECT * FROM PO_HEADERS WHERE EXISTS (SELECT 1 FROM mo_glob_org_access_

tmp oa WHERE oa.organization_id = org_id) RLS can be applied against A Table, A View or A Synonym. And RLS can be applied against the APPS schema objects. All Multi Org Views has been replaced RLS Secured Synonyms(Virtual Priva te Database VPD). 8) What is MO_GLOBAL.INIT Purpose of the MO_BLOBAL.INIT is => It will check whether Multi Org Sec urity Profile has been set or not. If the new MO security profile is set, then mo_global.init inserts one r ecord, for each Organization in Org Hierarchy, in table mo_glob_org_access_tmp 9) When & from where is mo_global.init called ? This package procedure will be called as soon as you login or as soon as you switch responsibility. Just like FND_GLOBAL.INITIALIZE is called. It is safe to assume that Oracle will invoke MO_GLOBAL.INIT after FND_GL OBAL.INITIALIZE 10) Is mo_glob_org_access_tmp table a global temporary table? Yes, it is. Hence after Multi Org is initialised for your session, your session will have X number of records in table mo_glob_org_access_tmp. X is the number o f organizations assigned to MO Security profile [view org hierarchy or org list in security profile] 11) What is the purpose of MO_GLOBAL.ORG_SECURITY? The purpose of Row-Level-Security is to hide certain data[based on some conditio ns]. RLS does so by appending a where clause to the secured object. 1. MO_GLOBAL.ORG_SECURITY is a function that returns a predicate for the WHERE C LAUSE 2. The where clause will be appended to Table/Synonym/View for which Multi Org R ow Level security is enabled 12) What is the purpose of MO_GLOBAL.SET_POLICY_CONTEXT ? This procedure has two parameters p_access_mode Pass a value "S" in case you want your current session to work against Single ORG_ID Pass a value of "M" in case you want your current session to work agai nst multiple ORG_ID's p_org_id Only applicable if p_access_mode is passed value of "S"

13)From SQL*Plus, I wish to simulate login to a specific responsibility. How do I do this? a. Call FND_GLOBAL.INITIALIZE This will set your responsibility id, user_id etc b. call MO_GLOBAL.INIT This will read the MO profile option values for your responsibility/user , and will initialize the Multi Org Access 14) General Ledger Features SLA has been introducted. SLA means Subledger.

Ledger is nothing but formally known as set of books. Multiple Reporting Currencies is replaced with "Reporting Currencies" "Reporting Sets of Books" are replaced by "Reporting Currencies" Global Accounting Engine has been replaced with SLA (Sub Ledger Accounti ng) GL_SETS_OF_BOOKS is no more table in R12 instead it is GL_LEDGERS GL_SETS_OF_BOOKS TABLE SET_OF_BOOKS_ID column is replaced with GL_LEDGER S table LEDGER_ID Enhanced Drilldown capabilities when Journal Source level "Import Journa l References" has been selected. Enhanced Journal Line Reconciliation Capabilities. (Different standard C oncurrent programs to see the exceptions) Inbuilt ADI client-server ADI concept. (Set the profile ADI: Use Functio n Security) Profile 1) SLA: Enable Subledger Transaction Security in GL 2) SLA: Disable Journal Import This profile option only can set at site level so that it can se t for entire subledgers/modules. By default the value should be 'NO' and don't change to 'YES' be cause it breaks the connection between Sub Ledger (SLA) and GL.

15) All concurrent programs has been added a new Parameter i.e. Operationg Unit. Assigning default value for this parameter at concurrent program earlier we use to use profile Org id i.e. $PROFILES$.ORG_ID in R12 we need to use follow select statement after setting default type as "SQL Statement" SELECT mo_global.get_current_org_id from dual 16) New features in R12 OracleMetaLink Note 403349.1. Note 461705.1.Note 394692. 1,Note 404152.1.Note 403349.1.Note 215527.1 Note 557869.1. 17) Payables Features 1) Suppliers are defined as parties within the Oracle Trading community Architecture (TCA) 2) Invoice Lines are introducted between Invoice Header and Invoice Dist ributions. 3) Banks, Bank Branches and internal bank accounts are difined centrally and are managed in Oracle Cash Management 4) Payments and all funds disbursement activities are handled by new Mod ule Oracle Payments. 5) Oracle Payables introduces a new Trial Balance report 6) Run the Paybles health check script after upgrading : Note 416699.1 18) Payments Module (New Module) R12 introduces a new Module "Payments". This is a robust centralized pa yments engine for disbursing and receiving payments.

Oracle payments includes all the functionality of "iPayments" from previ ous version and "iPayments" is obsolute in R12.