Learning Oracle Integration Cloud Services SOA | BPM

There are three types of columns in Oracle report. Placeholder Column : Placeholder column is used to store a value for a variable. Formula Column :  Used For doing mathematical calculations and returning one value Summary Column : The summary columns perform aggregate functions such as SUM, COUNT, MAX, MIN, AVG, and the like.

Bind variables are used in oracle reports  for replacing the single parameter in the SELECT statement. Example SELECT * FROM employee e WHERE e.emp_no = :empno;

Lexical Parameter is used to replace the where clause at run time. Lexical Parameter identified by & sign and are used to execute query dynamically. Example Select * from employee &where

When confine mode is on, the object cannot be moved outside its parent in the layout.   

When flex mode is ON, reports automatically resizes the parent when the child is resized.

After parameter Trigger : It will fire after the parameter form is displayed and here we can do validation on parameter values. Before Report Trigger : It will fire before the report is executed and after the query is parsed and date is fetched. 

We can set the message level using the system variable SYSTEM.MESSAGE_LEVEL or trap errors using the ON-ERROR or ON-MESSAGE  in Form level triggers. MESSAGE_LEVEL: 0     : Default value. All types of messages from the other levels of severity. 5     : Reaffirms an obvious condition. 10   : Indicates that the operator has made a procedural mistake.

Post-form commit fires once during the post and commit transactions process, after the database commit occurs. The post-form-commit trigger fires after inserts, updates and deletes have been posted to the database but before the transactions have been finalized in the issuing the command. The post-database-commit trigger fires after oracle forms issues the commit to finalized transactions.

Parameters provide a simple mechanism for defining and setting the values of inputs that are required by a form at startup. Form parameters are variables of type char,number,date that you define at design time.

1) Text_list 2) Pop_list 3) Combo box

1) Query Record Groups 2) Static Record Groups

The static LOV contains the predetermined values while the dynamic LOV contains values that come at run time

LOV is a property where as list item is an item. A list item can have only one column, LOV can have one or more columns.

When Validate from List is set to True, Oracle Forms compares the current value of the text item to the values in the first column displayed in the LOV. Whenever the validation event occurs. If the value in the text item matches one of the values in the first column of the LOV, validation succeeds, the LOV is not displayed, and processing continues normally. If the value in the text item does not match one of the values in the first column of the LOV, Oracle Forms displays the LOV and uses the text item value as the search criteria to automatically reduce the list.

Immediate Default Setting : The Detail records are shown when the Master Record are shown. Deffered with Auto Query : Oracle Forms defer fetching the detail records until the operator navigates to the detail block. Deffered with No Auto Query : The operator must navigate to the detail block and explicitly execute a query

Base Table Block  - based on database table/views Control Block - non-database items are placed here like Calculation values, buttons, checkbox etc.

B elow are the 5 canvas types available in Oracle Forms   (a) Stacked canvas (b) Content canvas (c) Horizontal Tool bar (d) Vertical Toolbar (e) Tab canvas

Following are three triggers which are created automatically as soon as we create a mater Details Block on oracle Forms. ON-CHECK-DELETE-MASTER ON-CLEAR-DETAILS ON-POPULATE-DETAILS

The various Master and Detail Relationships in oracle forms are: NonIsolated The Master cannot be deleted when a child is existing Isolated   The Master can be deleted when the child is existing Cascading   The child gets deleted when the Master is deleted.

Visual attributes are the font, color, and pattern properties that you set for form and menu objects that appear in your application's interface.

CALL_FORM : It calls the other form. but parent remains active, when called form completes the operation , it releases lock and control goes back to the calling form. When you call a form, Oracle Forms issues a savepoint for the called form. If the CLEAR_FORM function causes a rollback when the called form is current, Oracle Forms rolls back uncommitted changes to this savepoint. OPEN_FORM : When you call a form, Oracle Forms issues a savepoint for the called form. If the CLEAR_FORM function causes a rollback when the called form is current, Oracle Forms rolls back uncommitted changes to this savepoint.

Views are used in the data blocks of a standard form instead of mapping directly into the base tables because base tables have huge amount of data due to which if we work directly on the base tables, it will hit the performance.  Also, views are simplified versions of the base tables which are easy to understand and hence to work upon.

Custom.pll is used to implement any new PL/SQL code that you would need to write in customizing oracle forms.

Template Form is a form that is to be used for building a new form and this form references all the standard libraries like(FNDSQF,APPCORE,APPCORE2,APPDAYPK,CUSTOM) which are used to build a form as per the oracle standards. This Template form has been provided by Oracle.

Following are some of the Oracle Form triggers that must not be modified. CLOSE_THIS_WINDOW CLOSE_WINDOW EXPORT FOLDER_ACTION KEY-COMMIT KEY-EDIT KEY-EXIT KEY-HELP LAST-RECORD MENU_TO_APPCORE STANDARD_ATTACHMENTS WHEN-WINDOW-CLOSED WHEN-FORM-NAVIGATE