Course Overview

Learn To:

• Identify the communication formats used by Form Builder.
• Write the code to handle errors, suppress system messages, create alerts and control alerts at run time.
• Run a form module in debug mode.
• Identify the concepts related to debugging PL/SQL code.
• Debug PL/SQL code.
• Identify the process involved in querying a data block.
• Write triggers to query a data block.
• Manipulate the query process.
• Perform validation, and navigate within a form by using triggers and built-ins.
• Identify the concepts related to transaction processing.
• Customize a Form Builder application by writing different types of commit triggers and overriding the default transaction processing.
• Write flexible code by using system variables and built-ins and by referencing objects directly and indirectly.

Skills-Based

Audience

Application developers, database administrators, designer/developers, and technical support professionals. Participants should have knowledge equivalent to the following courses: Oracle SQL: Basic SELECT Statements (61110); Oracle SQL: Data Retrieval Techniques (61111); Oracle SQL: DML and DDL (61112); Oracle PL/SQL: Basics (60113); Oracle PL/SQL: Procedures, Functions and Packages (60114); and, Oracle PL/SQL: Database Programming (60131). In addition, learners should have taken the first two parts of the Oracle Developer series: Oracle Developer: Forms Fundamentals (62211) and Oracle Developer: Enhancing the User Interface (62212).

Total Learning Time

6 - 8 Hour(s)

Course Contents

• Match the communication formats used by Form Builder with their descriptions.
• Write the code for detecting an error by using built-ins.
• Write the code to control system messages by using system variables.
• Write the code to explicitly fail a trigger by using the FORM_TRIGGER_FAILURE exception.
• Identify the uses of triggers for intercepting system messages.
• Create an alert by using the Create button in the Object Navigator.
• Write the code to control an alert at runtime by using built-in subprograms.

• Run a form module in debug mode by using the Run Form Debug button in the Object Navigator.
• Match the PL/SQL Debugger components with the tasks that they enable.
• Set a breakpoint in PL/SQL code by using the Source pane of the Forms Debugger window.
• Identify the user-defined debug actions that occur automatically during debugging.
• Match the debug commands with their functions.
• Debug PL/SQL code to identify the cause of an error by using the Forms Debugger window.

• Sequence the events that take place when a query is initiated on a data block.
• Identify the sources of the different clauses of the default SELECT statement.
• Write the code for a Pre-Query trigger at the data block level.
• Write the code for a Post-Query trigger at the data block level.
• Implement query array processing in a Form Builder application.
• Write the code for a trigger to fire in Enter Query mode by using the SYSTEM.MODE variable.
• Match the transactional triggers that override default query processing in Form Builder with their characteristics.
• Match the block properties with the associated built-ins that can be used to manipulate query information.

• Sequence the steps of the validation process used by Form Builder.
• Set the Validation Unit property of a form by using the pop-up menu.
• Validate a value entered in an item by using an LOV.
• Write the code for a trigger to validate user input at different levels.
• Match the built-ins used for validation with their functions.
• Sequence the Form Builder navigation units according to their navigation hierarchy.
• Match the navigation properties with their characteristics.
• Match the navigation trigger types at different levels with their uses.
• Write the code for the When-New-object-Instance trigger at different levels.
• Match the built-ins used for navigation with their functions.

• Identify the events that take place during the different phases of transaction processing.
• Sequence the events that take place during commit processing.
• Match the different types of commit triggers with the conditions under which they fire.
• Match the different types of commit triggers with their common uses.
• Write a Pre-Delete trigger to implement validation before the deletion of a row.
• Write a Pre-Insert trigger to assign sequence numbers to records.
• Write a Post-Update trigger to record audit information about the changes applied to base tables.
• Write the code to test the result of a DML operation in a trigger by using the attributes of PL/SQL implicit cursors.
• Identify the rules followed by Form Builder while issuing DML statements during commit processing.
• Write an On-Logon trigger to override the default logon process.
• Identify the different ways to run Form Builder against data sources other than Oracle.
• Match the commit status values returned by different system variables with their implications.
• Write the code to manipulate the commit status of a record by using built-ins in the code.
• Implement array DML processing in a Form Builder application.

• Identify the benefits of writing flexible code.
• Write the code to determine the block that should have the input focus by using system variables in the code.
• Write the code to perform an action based on the status of the current block by using system variables in the code.
• Write the code to retrieve information about the current application by using the GET_APPLICATION_PROPERTY built-in.
• Write the code to modify the properties of an item in the current application by using the SET_ITEM_PROPERTY built-in.
• Identify the benefits of referencing objects by using their Object IDs.
• Reference an object within the initial PL/SQL block by using its internal ID.
• Reference a local object outside the initial PL/SQL block by using its internal ID.
• Identify the characteristics of the built-in subprograms used to indirectly refer to objects.

Click here for Secure Yahoo Order: Oracle Form Builder R6: Writing and Debugging Code

Get Train in Oracle
Oracle Training CBT

Best Regards,
Oracle Database, SQL, Application, Programming Tips