Technology Changes in R12
Author Ajay Singh CreationDate:02-Jan-2011 LastModifiedDate:02-Jan-2011
Virtual Private Database (VPD) feature introduced will replace usage of CLIENT_INFO(Org Context) function in Multi-Org Architecture. end. Before Release 12. For eg. This feature allows users in a shared services environment to access/transact data within several operating units from a single responsibility at the same time restricting access to other users through a security policy. previously following script could be run for accessing information in po_headers view. Also custom forms and reports need to be initialized to secure access through security profile. This allows flexibility and convenience for shared service users.
.set_client_info('&org_id'). / But in R12 the above will not work unless we request access through Security Policy in the database. Reports. From Release 12 the Multi-Org Access Control feature. / select * from ap_invoices. Java Scripting (Replaces PL/SQL)
Existing objects in Oracle Forms. This is true with Workflow packages. BI Publisher. All calls made to previous org context function will not work any longer. Workflow Builder and PLSQL are working as it is but all the new development is done in OA Framework.Technology Changes in R12 Technologies Used: OA Framework (Replacing Oracle Forms) BI Publisher (XML publisher) (Replacing Oracle Reports and Discoverer) BEPL (Replacing Workflow Builder) Java. begin dbms_application_info. At same time you can prevent access to data from users who are not authorized to access this information. will enable users to access data in one or more Operating Units from a single responsibility. All such views/synonyms will need to be accessed only through security profile. BEPL. users were limited to access information only from within the context of their own operating unit from a single responsibility. MO_GLOBAL package can be used to obtain this access. Java and Java Scripting etc.
Multi Org Access Control (MOAC) is introduced. Discoverer.
Subledger accounting concept 1. These entries will be moved to GL by running the program "Transfer Journal Entries to GL" instead of CJE program. In 11i. 5.) in GL_JE_LINES and GL_BC_PACKETS. Encumbrance entries gets generated in a new table PO_BC_DISTRIBUTIONS in addition to GL_BC_PACKETS.. Below are the differences in Behavior between 11i and 12i: 1. Accounting entries can be created manually at SLA level and can be imported to GL by doing the journal import 4. 2.. As a part of Subledger Accounting. In 11i. PO details are not available in reference columns(reference_1. it is not possible to view the Encumbrance entries in Purchasing module. whereas in 12i. The linking columns between GL_IMPORT_REFERENCES and GL_JE_LINES are je_header_id and je_line_num
Let us take the example of Encumbrance Entries.instead it is linked through the subledger tables XLA_AE_HEADERS and XLA_AE_LINES. XLA_AE_LINES is mapped to GL_IMPORT_REFERENCES with the gl_sl_link_id and gl_sl_link_table columns. where as in 12i. Hence accounting entries in these tables can be retrieved only using SLA tables and GL_IMPORT_REFERENCES 6. addition of Operating Unit filed to your LOVs or joining your queries explicitly with org_id when tables or views have Operating Unit sensitive data. the entries can be viewed from SLA menu in Purchasing
. Encumbrance entries created in GL_BC_PACKETS will be directly moved to GL_JE_LINES by running the CJE program. Receiving Subledger is not directly linked to GL_JE_LINES.In your design you need to consider future possibility of the customizations and extensions being used in a shared services environment. The column set_of_books_id has been replaced with ledger_id in Gl Tables 2. new SLA tables XLA_AE_HEADERS and XLA_AE_LINES have been introduced.reference_2. Subledger Accounting (SLA) options has been introduced and accounting entries can be viewed at SLA menu 3. This will mean additional task for eg. Set Of Books is replaced by the term Ledger.
But in 12i. RFE a/c gets credited along with the PO Reservation ( budget a/c debit entry) and these entries can be viewed from SLA menu in Purchasing
Oracle Integration Repository is being introduced instead of API guide. In 11i.
. a Credit against the Reserve For Encumbrance a/c (RFE) can be seen only at the time of posting the Encumbrance Debit entry in GL.3.