Let us discuss some difference in OAF pages and Oracle Forms. The below table lists out the differences between OAF and Oracle Forms.
OAF | Oracle FORMS |
OAF Follows MVC architecture and Client ServerArchitecture | Forms Follows only Client Server Architecture |
OAF pages are light weight components | Forms are not light weight |
OAF Pages can send through mobile devices | Cannot send to mobile devices |
OAF Pages can connect in Oracle Apps Local Machine | Cannot (NOT APPLICABLE) |
Look and Feel is good | Not better when comparing to OAF |
OAF pages are integrated with the Java Top | Forms are integrated with Application Top |
Commit always takes place in the Application Module’s (AM) Java code. When a commit takes place, the data from OA Framework Cache is transferred to the database. | The COMMIT_FORM or DO_KEY(‘COMMIT_FORM’) commands can be invoked from any trigger that allows restricted procedures. |
A page is divided into regions. Regions contain fields, buttons, tables, and other components. | A form is divided into blocks; blocks contain the fields, buttons, and other components |
Read Other OAF Tutorials:
- Architecture of OAF
- OAF Components~ View ~ MVC Architecture
OAF Components ~ Model ~ MVC Architecture
OAF Components -Controller - MVC Architecture
- How To Debug OAF Pages When Its Going Into Error!!
- OAF Interview Questions And Answers - Part1
- How To Migrate OAF Personalizations To Other Instances
- How to Enable Personalization link On OAF Pages
- How To Create A VO At Run Time In OA framework
- Implement PopList in OA Framework | OAF Tutorials
- How To Call A Concurrent Program From OA Framework Pages
COMMENTS