Solution for PO PRE-APPROVED status though the final approver has approved it.

Pre–Approved document is one in which a person with the final authority to approve the purchasing document approves it, but then forwards it to someone else for additional approval, thus changing its status to Pre–Approved.

OR

Check whether you are using Encumbrance accounting in Oracle Purchasing.If you are,then you may find this issue, in case no funds are reserved for the PO.So then we need to Reserve the fund before approving.It means your organization uses encumbrance budgeting (reserves funds for documents), and the purchasing document is eligible for approval but funds have not yet been reserved for it. Even if someone with sufficient approval authority approves this document, its status may still remain Pre–Approved if funds were not able to be reserved at the time of approval. Once funds have been reserved for the approved document, the document changes its status to Approved.

A Pre–Approved document does not show up as supply for planning module until its status changes to Approved.

Difference Between 11i and R12

11i	R12
1. If you want to change the OU then you need to change the responsibility in MOAC.	1. Without changing the responsibility you can change the OU.
2. Report server exists.	2. The Reports server is obsolete in Release 12. All reports are now run through the Concurrent Processing server manager via the rwrun executable, which spawns an in-process server.
3. 11i only forms basis application.	3. R12 is now forms and HTML pages.
4. 11i is particularly in set of books	4. R12 using in ledgers
5. In 11i, the Bank Accounts are defined at the Operating Unit level.	5. In R 12, Bank Accounts are defined at Legal Entity Level which can be accessed by multiple Operating Units.
6. In R11, there are only 6 validation types: - Dependent, Independent, None, Pair, Special and Table.	6. In R12, there are 2 additional validation types called ‘Translatable Independent’ and ‘Translatable Dependent’.
7. Set of Books 3Cs-Chart of Accounts, Functional Currency, Accounting Calendar.	7. Ledgers 4Cs – Chart of Accounts, Ledger Currency, Accounting Calendar, Accounting Method(Conventions).
8. Individual Product (AP, AR, etc.) accounting. i.e. Global Accounting Engine.	8. Sub Ledger Accounting Method (SLAM)
9. Operating Unit	9. Multi-Org Access Control (MOAC)
10. Multiple setups for accounting in GL	10. Accounting Setup Manager (ASM)
11. In personalization level set_lov_property is not available	11. In Oracle Apps R12 we can change the LOV.
12. Reporting Set of books	12. Reporting Currency
13. Operating Units assigned to set of books	13. Operating Units assigned to primary Ledger in an Accounting setup.
14. Reports/Forms 6i	14. Reports/Forms 10g
15.Inventory in 11i	15.In R12 ,Inventory have two types process manufacturing and discrete manufacturing
16. In 11i Only relation between customers at TCA.	16. In R12, Relationship between suppliers, customers, bank details at TCA.
17.No MOAC	17. MOAC(Multi Org Access Control)
18. Database Version in 11i (11.5.9 & 11.5.10) was 9i	18. Where as in Release 12 its 10g.
19. Tech Stack in Application Tier consist of iAS(1.0.2.2.2) & Developer 6i (Forms & Reports 8.0.6)	19. but in Applications R12 it is built on Fusion Middle ware (10g Web Server and 10g Forms & Reports)
20. Intercompany Accounts	20. Intercompany Balancing.

About SLA(Sub Ledger Accounting)

Sub ledger Accounting (SLA) has been introduced in Release 12 of Oracle Applications, SLA is an intermediate step between subledger products and the Oracle General Ledger and also Journal entries are created in Subledger Accounting and then transferred to Oracle General Ledger.

Sub ledger Accounting is a Service provided to Oracle Applications, not an Application/Responsibility.

Steps for Accounting Process:-

Transaction and Create Accounting -->SLA Journal Entry and Journal Import -->Journal Entry Import and Posting--> GL Balances

SLA (Sub Ledger Accounting) Joins with Other Modules:-

1) All accounting performed before transfer to the GL. Accounting data generated and stored in "Accounting Events" tables prior to transfer to GL.

2) Run "Create Accounting" to populate accounting events (SLA) tables. User can "View Accounting" only after "Create Accounting" is run. Create Accounting process
– Applies accounting rules– Loads SLA tables, GL tables– Creates detailed data per accounting rules, stores in SLA "distribution links" table.

3) Below are the key tables for SLA in R12
XLA_AE_HEADERS xah
XLA_AE_LINES xal
XLA_TRANSACTION_ENTITIES xte
XLA_DISTRIBUTION_LINKS xdl
GL_IMPORT_REFERENCES gir
Below are the possible joins between these XLA Tables
xah.ae_header_id = xal.ae_header_id

xah.application_id = xal.application_id
xal.application_id = xte.application_id
xte.application_id = xdl.application_id
xah.entity_id = xte.entity_id
xah.ae_header_id = xdl.ae_header_id
xah.event_id = xdl.event_id
xal.gl_sl_link_id = gir.gl_sl_link_id
xal.gl_sl_link_table = gir.gl_sl_link_table
xah.application_id = (Different value based on Module)

xte.entity_code =
'TRANSACTIONS' or
'RECEIPTS' or
'ADJUSTMENTS' or
'PURCHASE_ORDER' or
'AP_INVOICES' or
'AP_PAYMENTS' or
'MTL_ACCOUNTING_EVENTS' or
'WIP_ACCOUNTING_EVENTS'

xte.source_id_int_1 =
'INVOICE_ID' or
'CHECK_ID' or
'TRX_NUMBER'
XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types
xdl.source_distribution_type = 'AP_PMT_DIST'
and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id
---------------
xdl.source_distribution_type = 'AP_INV_DIST'
and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id
---------------
xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'
and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id
and AR_DISTRIBUTIONS_ALL.source_id = AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id
---------------
xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'
and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id
---------------
xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'
and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id
---------------
xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'
and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id
---------------
xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'

and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id.