Oracle Application Framework Training Material

TABLE OF CONTENTS
PURPOSE OF THE DOCUMENT..............................................................................................4 DOCUMENT USAGE...................................................................................................................4 DETAILS OF DOCUMENT.........................................................................................................4 1 OAF ARCHITECTURE .............................................................................................................4 1.1 ABOUT MODEL ...........................................................................................................................5 1.2 ABOUT VIEW .............................................................................................................................5 1.3 ABOUT CONTROLLER ...................................................................................................................5 2. KEY FEATURES .............................................................................................................................6 2.1 INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) ..........................................................................6 2.2 DURABLE PERSONALIZATIONS AND EXTENSIONS ...............................................................................6 2.3 CONSISTENT AND COMPELLING USER INTERFACE .............................................................................6 2.4 OBJECT ORIENTED REUSE ............................................................................................................7 3. OA FRAMEWORK ESSENTIALS ........................................................................................................7 4. IMPLEMENT THE MODEL IN OAF ................................................................................................9 5. IMPLEMENT THE VIEW IN OAF.............................................................................................11 6. IMPLEMENT THE CONTROLLER IN OAF ..................................................................................12 7. OAF KEY DO'S AND DON'TS (PART 1) - "TOP 10" GOLDEN RULES.................................................13 8. PRACTICAL PROBLEMS AND SOLUTIONS ..........................................................................................20 Display the message as Welcome <text item value> on the OAF page when you press the Go button.............................................................................................................20 Product Branding: ................................................................................................................23 In-Context Branding: ............................................................................................................24 How do display default string in Text Item when page is rendered.........................................26 How do hide Text item at runtime...........................................................................................26 How do disable the button at runtime.....................................................................................26 How do display message in different colour...........................................................................27 How do call the specified page from another page.................................................................27 How do display the Return Navigation link on the page.........................................................28 How do add a returnLink dynamically....................................................................................30 Connect to Database and return number of suppliers on the page..........................................30 How do call stored procedure from OAF page (Without using EO, VO).................................31 Display message by using AOL Message Name (Message Dictionary)...................................32 How do call D2K Form from OAF page.................................................................................33 Implement a Search Page.......................................................................................................33 How do display the drill down to details page according to criteria.......................................39 How do display custom copy right on OAF page....................................................................41 How do get the value of the checkbox when selected or deselected........................................41 How do insert data from OAF Page to Database table by using View Object ........................41 How do refresh the same page after the data has been entered...............................................44 How do set the values in poplist.............................................................................................44 How do hide the specified item when user selects the particular value from Poplist...............45 How do fire event? To display supplier name according to supplier id...................................48 How do create list box and add values to the list box dynamically..........................................49 Create a Shuttle Region..........................................................................................................50 About StackLayout, rowLayout, cellFormat region styles.......................................................52 About Browser Look and Feel (BLAF)...................................................................................53 About AdvancedTable Bean....................................................................................................55

OAF Training How do display Add another row button and totalling on column......................................58 How do iterate the number(Serial Number) in OAF by using Transient Attribute...................61 How do display latest serial number dynamically while creating row.....................................62 How do delete a selected record of Advanced Table using Delete Switcher ...........................63 How do clear the View Object at runtime...............................................................................66 BIBLIOGRAPHY :-................................................................................................................67

Page 3 of 67

OAF Training

Purpose of the document

OAF is used to develop self service web pages. This document describes about OAF concepts and gives solutions for practical problems. It is useful for developers to become OAF professional at the earliest. This document is user friendly document. The author has prepared this document theoretically and technically.

Document Usage
This document can be used to develop self service web pages. The developer can know from basic points to advanced points in OAF. This document is like a useful reference guide.

Details of Document
1 OAF ARCHITECTURE

OA Framework is based on the industry-standard J2EE MVC Design Pattern. M Model V - View C - Controller Developers manipulate the applications metadata using Oracle 9i JDeveloper OA Extension, while OA Framework uses the most efficient manner to execute the application. The MVC architecture is a component-based design pattern with clean interfaces between the Model , View and Controller. The Model is where the application implements its business logic. The View is where the application implements its user interface. The Controller is where the application handles user interaction and directs business flow. Find the following MVC diagram to understand relationship between Model, View and Controller.

Page 4 of 67

OAF Training

1.1

About Model

The OA Framework Model is implemented using Oracle Business Components for Java (BC4J). BC4J provides optimized, ready-to-use implementations of the J2EE design patterns. Development teams can focus immediately and only, on writing business logic and user interfaces instead of designing, coding, and debugging handcrafted application plumbing code.

1.2

About View

The OA Framework View is implemented using UI XML (UIX). UIX uses XML to describe the components and hierarchy that make up an application page. UIX provides runtime capabilities to translate that metadata into HTML output so that it can be shown on a Browser. The metadata used to describe the UI is loaded into a database repository, called Meta Data Services (MDS), at deployment time and optionally at design time as well.

1.3

About Controller

User and Application-driven interactions are handled by the OA Controller, which is pure Java Class implementation. Within the Model-View-Controller architecture, the OA Framework draws a clear distinction between client and server classes. Client classes (View and Controller) drive the HTML user interface. Server classes (Model code) can support any client (not just OA Framework user interfaces)

Page 5 of 67

OAF Training

2.

Key Features
Integrated Development Environment Durable Personalizations and Extensions Consistent and Compelling User Interface Object Oriented Reuse

2.1

Integrated Development Environment (IDE)

Oracle 9i JDeveloper with OA Extension is a world-class J2EE-based integrated development environment. Oracle customers and third party consultants have access to the same tools used by Oracle E-Business Suite developers to build complementary applications as well as extend the Oracle E-Business Suite applications.

2.2

Durable Personalizations and Extensions

Personalization is about declaratively tailoring the UI look-and-feel, layout or visibility of page content to suit a business need or a user preference. Personalization can be done at several levels by one of three authors: Application Developer Application Administrator End User Examples: Tailoring the color scheme of UI (UI means User Interface) Tailoring the order in which table columns are displayed. Tailoring a query result Extensibility is about extending the functionality of an application beyond what can be done through personalization. Examples: Adding new functional flows Extending or overriding existing functional flows Extending or overriding existing business logic

2.3

Consistent and Compelling User Interface

OA Framework offers developers a wide range of user interface components that make the building of applications into a more assembly process, freeing developers from the repetitive composition of common user interface constructs. OA Framework user interface components range from simple widgets such as buttons and fields to compound components such as tables-in-tables and hierarchical grids.

Page 6 of 67

OAF Training

2.4

Object Oriented Reuse

OA Framework applications can be abstracted into a series of concentric layers, like an onion.

(Note: Describe the objects mentioned in diagram in the following pages) Each layer only knows about the layers below it. This encapsulation allows reuse at any of the layer boundaries.

On User Interface Side, reusable components can be saved as Shared regions in the MDS repository and reused across several pages. Example for Shared region is LOV (list of values). It is independent object. We can attach the same LOV to text item in several pages.

3.

OA Framework Essentials

Key JSP Application Components 1) The Browser communicates with the middle tier using HTTP which involves sending a request message to which the middle tier replies with a response message. 2) A JSP is a file with some HTML and JAVA code that executes top to bottom. At runtime, it is compiled into a Java class which is actually a Servlet. 3) A Servlet is a Java web based application server extension program that implements a Standard API. 4) Page 7 of 67

OAF Training A Servlet Session is a mechanism for maintaining state between HTTP requests during a period of continuous interaction between Browser and Web Application. A Session may be initiated at any time by the application and terminated by the application, by the user closing the browser, or by a period of inactivity. A session usually corresponds to an application login/logout cycle. 5) A JavaBean (Bean for short) is simply a reusable component that implements specific design patterns to make it easy for programmers and development tools to discover the objects properties and behavior. 6) Any objects in the middle tier that communicate with the database use a JDBC (Java DataBase Connectivity). Diagram to understand the above points

Page 8 of 67

OAF Training

4.

Implement the MODEL in OAF

This chapter describes how to implement your model objects in generic terms. Business Components Packages All BC4J (Business components for Java) model components must belong to a Business Components Package. Business logic/data handling (Model) is done using BC4J. The below objects are BC4J Objects. 1) Entity Object Entity Objects encapsulate business logic and DML operations for application tables. Note: Entity objects can also be based on views, synonyms or snapshots. There is a one-to-one mapping between a table and an entity object, and all Oracle Applications entity objects should include all columns in their associated tables. Entity objects use a declarative mapping between their attributes and underlying database columns to automatically implement queries, inserts, updates and deletes. Two files will be created automatically after creating Entity Object(EO). They are i) EmployeeEO.xml ii) EmployeeEOImpl.java

EmployeeEO is name of the Entity Object (EO). The below methods are available under .java file (EmployeeEOImpl.java) We can write business logic in EO at entity level to meet business requirements (Example: validateStartDate ()) Methods under Entity Object:create() [Add attribute defaulting logic in this method] remove()[Add entity remove logic in this method] set methods [sets value as the attribute value] (Example: setEmployeeId, setFirstName etc) get methods [gets the attribute value, using alias name] (Example: getEmployeeId, getFirstName etc) validateEntity() Entity Object (EO) should have following attributes: CreationDate CreatedBy LastUpdateDate LastUpdatedBy LastUpdateLogin

Page 9 of 67

OAF Training

2) View Objects Encapsulates a database query Provide iteration over the query result set Primarily based on Eos (Entity Objects) May be based on plain SQL for certain types of tasks May be based on multiple entity objects if the UI is for update Provide single point of contact for getting and setting entity object values May be linked together by view links

Two files will be created after creating View Object (VO) They are 1) .java (Row level) 2) .java (Object level) 3) .xml file Example: i) EmployeeNamesVO.xml ii) EmployeeNamesVOImpl.java iii) EmployeeNamesVORowImpl.java We will write code in .java files. 3) Association Objects Association object is used to create relationship between Entity objects. There are two types of associations are given below. 1) Composition (Strong association) 2) Reference (Weak association) Composition: - The destination entity object can not exist independent of its source entity object. Example: A purchase order header is automatically locked even if you make changes only to its lines. Child is deleted when parent is deleted. Reference: - The source entity object simply references the destination object. Example: A purchase order header references a supplier, but the supplier can still exist regardless of whether a purchase order references it or not. 4) Application Modules o o o Application Module serves as container for ViewObjects and ViewLinks Application Module establishes database connection. Attach the Application Module to OA Framework page.

Page 10 of 67

OAF Training

5.

Implement the VIEW in OAF

The VIEW formats and presents model data to user. We have to define OAF page to display data. At development time, you specify the bean hierarchy for every page using the JDeveloper tool. OAF page comprised of regions and items. Items are simple widgets like buttons, images, fields and so on which contain no children. Regions are container objects that hold items and other regions. Regions include header, table and layout components. Each region and item that you define has a style property that tells the OA Framework what web bean object to instantiate for it at runtime. For example, if you define a region whose style property is "table," the OA Framework will instantiate an oracle.apps.fnd.framework.webui.beans.table.OATableBean All pages must have a single top-level region whose style is PageLayout. Regions and Items appear in JDeveloper page tree in sequence that tells Framework where to add these objects to runtime bean hierarchy.

Page 11 of 67

OAF Training

6.

Implement the CONTROLLER in OAF

CONTROLLER is used to enhance OA Framework page using logic for buttons, automatic queries, dynamic WHERE clauses, JSP forwards, and the Message Dictionary. Controllers for regions processRequest method (code for page initialization such as HTTP GET actions and so on) processFormRequest method (code for HTTP POST actions. When press the button the code will be executed)

Page 12 of 67

OAF Training Typical Locations for Code We could not call methods of Entity Objects (EO) from Controller directly. We have to follow below order to call method from location to other location. 1) 2) 3) 4) Call methods of ApplicationModule from Controller only Call methods of ViewObject from ApplicationModule only Call methods of EntityObject from ViewObject only EntityObject is based on Database table

Note: Please look ONION structure to understand above points.

7.

OAF Key Do's and Don'ts (Part 1) - "Top 10" Golden Rules

I don't know how many of you have come across this in the OAF Devguide, it was only by change that I found it, thought I'd share: There's a lot to learn when getting started with the OA Framework, but the following list of rules are so universal -- and so fundamental -- they should be familiar to anyone who's doing Framework development. 1) ALWAYS try to declaratively define your UI. Resort to a programmatic layout only if the UI cannot be implemented declaratively. Programmatic layouts are difficult to customize (they don't leverage the Personalization Framework) and may diverge from the UI Guidelines over time. 2) NEVER change your UI layout properties in processFormRequest(). ALWAYS make changes in processRequest(), even if that means handling an event in processFormRequest() and then redirecting back to the same page. This ensures that the web bean hierarchy is in a stable state when the page renders. 3) NEVER use index numbers to find beans when you want to change their properties. ALWAYS search by name. Index numbers can change during processing. 4) NEVER change the properties of a parent bean from a child bean. This is a poor design practice that hampers reuse while introducing fragile code (particularly if the child code executes too late in the page rendering cycle to properly affect the parent). 5) NEVER instantiate Beans using "new OA Bean()". ALWAYS use the createWebBean() factory methods available on the OAControllerImpl class. Not all Bean properties are initialized correctly when you use "new." 6) NEVER create Form Beans in code (this means NEVER add nested Form beans to a page; your Page Layout region should be the only form region). Multiple form Beans on a page are not supported and can result in strange runtime behaviors. 7) NEVER count on your Application Module using the same database connection in subsequent requests. For example, NEVER post and commit in separate requests. For performance reasons, the Framework will start pooling and reusing connections in 5.7 instead of holding onto a single connection throughout the life of an Application Module.

Page 13 of 67

OAF Training

8) NEVER use JDBC directly unless you're calling a PL/SQL routine (you should use a view object instead, and if possible, the view object should be defined declaratively and not programmatically). 9) NEVER add member variables UNLESS THEY ARE TRANSIENT OR FINAL to view objects, Controllers, entity object, view rows and Application Modules. 10) ALWAYS adhere to the Self-Service Performance Guidelines

Page 14 of 67

OAF Training 8.

Create Simple OAF WELCOME Page

Step 1: Open JDeveloper tool, Create New OAworkspace. Navigation: - right click on Workspaces option in system-navigator Window and select New OAWorkspace

Step 2: i) Enter workspace name in file name column as XXXOAWorkspace.jws, and press OK button. ii) Press Next button iii) Enter project Name in file name column as XXXOAProject.jpr iv) Enter Default package name as xxx.oracle.apps.ak.welcome.webui and press Next button twice.

We can see the package structure (train.oracle.apps.ak.welcome.webui) in myprojects folder. The package structure is used to place EO, VO, AM and Pages. Step 3: Enter .dbc file location in DBC File Name column [Location: E:\p4045639_11i_GENERIC\jdevhome\jdev\myhtml\OA_HTML\Secure\ xxxxx.dbc] Note: If you do not have .dbc file, then import the .dbc file from server ($ cd %APPL_TOP/fnd/11.5.0/secure/.dbc) and place in above path in your local system.

Page 15 of 67

OAF Training Enter User Name: operations5 (oracle application user name) Enter Password : xxxxxxxxx Application Short Name: AK Responsibility Key : FWK_TBX_TUTORIAL Press Finish button. Now, creation of OAWorkspace, OAProject and front-end connections successfully completed.

Step 4: Create new OA page Select project name (xxxOAProject) and click right mouse button, then select New option.

New window will be opened, and then select WebTier under categories list. Select OA Components option under Web Tier and select Page right side. Page 16 of 67

OAF Training

Press OK Button. Step 5: Enter page name as XXXWelcomePG in Name field. You can change the package name if you want otherwise leave it as it is because the package is already created at the time of workspace creation.

Press OK button, then page web bean (WelcomePG.xml) will be created.

Page 17 of 67

OAF Training

Now, we will run the .xml (WelcomePG.xml) to render the OAF page on the Browser. In above diagram, there is region1 called root region. It is container, consists items and other regions. Set the properties for root region (region1) in property inspector window. Property Name ID Region Style Window Title Title AM Definition Value MainRN PageLayout Welcome Window Welcome Page oracle.apps.fnd.framework.server.OAApplicationModule Note: we are not yet creating Application Module. So, this application module is using which is default.

Step 6: Create subregion (style: messagecomponentlayout) under the Pagelayout region. Select MainRN and click right mouse button, select region Option and set the below properties. Property Name Value ID SubRN Region Style Messagecomponentlayout Step 7: Create item under SubRN Select the region SubRN and click right mouse button, and then select the option messageTextInput and set the below properties.

Page 18 of 67

OAF Training Property Name ID Region Style Prompt Additional Text Value WelcomeTxt messageTextInput Enter Your Name Enter any string to display it on the page (It is like Tooltip text)

See below screen shot to select messageTextInput.

Save the project and compile the page (WelcomePG.xml) Steps to compile the WelcomePG.xml Select the .xml (WelcomePG.xml) and click right mouse button. Select Make WelcomePG.xml option, and verify the errors on log messages tool box (see bottom) if occurred.

Step 8: Run the OAF Page (WelcomePG) Select the page (WelcomePG.xml) and click right mouse button, then select Run WelcomePG.xml option. (See above screenshot for your reference)

Page 19 of 67

OAF Training See the below OAF page screenshot and verify the window title, page title and text item prompt with above properties.
Window Title of Root Region MainRN

Page Title of Root Region (MainRN)

Text Item Prompt. It is available under Sub Region (SubRN)

In this stage, there is no control on the OAF page. We have to create CONTROLLER on the root region and write the code to control the OAF page.

8.

Practical Problems and Solutions

Display the message as Welcome <text item value> on the OAF page when you press the Go button Step 1: Create button item under the sub region SubRN. Select the region SubRN and click right mouse button, select the option messagelayout (is used to place the buttons). Property Name ID Value ButtonLayout

Step 2: Create button item under the ButtonLayout. Select the region ButtonLayout and click right mouse button, and select the Option item.

Page 20 of 67

OAF Training

Set the Button item properties. Property Name ID Item Style Prompt Additional Text

Value Go submitButton Go Click the button

Step 3: Create Controller. Select the MainRN region and click right mouse button, and then choose the option Set New Controller.

Enter Controller Name: WelcomeCO and press the OK button. After press the OK button, one .java file will be created with Controller name as WelcomeCO.java See below screenshot:-

See below screenshot once and observe the methods processRequest and processFormRequest in the Java file (WelcomeCO.java).

Page 21 of 67

OAF Training

When press the Go button, the button related code will be executed from processFormRequest method (like Java POST method). The processRequest code will be executed at the time of initializing the page. Logic to display the message Welcome <value of text item> on OAF page. Add below code in the method processFormRequest . Code: if (pageContext.getParameter("Go")!=null) { String str=pageContext.getParameter("WelcomeTxt"); String message="Welcome "+str; throw new OAException(message,OAException.INFORMATION); } In above code, Go is button name (not prompt) which is used in if condition. WelcomeTxt is also text item id (not prompt). When user press the Go button, the browser will send the request to middle tier and after processing the middle tier responds to browser.

Page 22 of 67

OAF Training The OAException class is used to display the message on the OAF page. The second parameter is exception type INFORMATION. There are some more exception types available. They are: 1) CONFIRMATION 2) WARNING 3) ERROR 4) SEVERE Note: The exception types ERROR and SEVERE terminate the program. The exception types INFORMATION, CONFIRMATION and WARNING are continue the execution of the program. Now, run the page WelcomePG.xml and see output like below.

Output: Enter the text OAF students in text item and press the Go button, then display the message on MainRN (Root region). Message: WELCOME OAF students (Exception type: INFORMATION) Product Branding:

The productBranding is used to place image beside corporate branding image ORACLE. Select pageLayout components and click right mouse button, and select the productBranding option.

Page 23 of 67

OAF Training

Set the below properties for productBranding item Property Name Value ID Item1 (as you like) Item Style Image ImageURI /OA_MEDIA/FNDTAPPBRAND.gif Additional Text Click the button Set the system profile FND: Branding Size as Medium at site level. If you change menus or profile values etc, then we have to terminate the OAF page. Navigation: RUN->Terminate->Embedded OC4J Server (Menu bar) Compile and run the OAF page (.xml), check the output from below screenshot.

In above screenshot, Tutorial Application image is productBranding image. In-Context Branding: The in-context branding includes corporate branding and product branding images. Additionally, contextual information renders below corporate and product branding images. Select pageLayout Components region and click right mouse button, then select the InContextBranding option.

Page 24 of 67

OAF Training

Note: productBranding can contain only formattedText because In-ContextBranding is present. Set the properties for productBranding item style as formattedText and enter Text property as Sales Online. Set the properties for inContextBranding item. Property Name ID Item Style Text Value Item2 (as you like) formattedText Customer SUN MicroSystems-Menlo Park

We can use html tags to change font styles or display font in bold etc. Example: Customer <b> SUN MicroSystems-Menlo Park</b> Output:

Page 25 of 67

OAF Training How do display default string in Text Item when page is rendered

Code: OAMessageTextInputBean fieldHelloTxt= (OAMessageTextInputBean)webBean.findChildRecursive(WelcomeTxt); fieldHelloTxt.setText(pageContext, welcome to OAF students); Where WelcomeTxt is a Text Item ID. Write above code in processRequest method of CONTROLLER. Important Note: We have to import the class OAMessageTextInputBean. import oracle.apps.fnd.framework.webui.beans.message. OAMessageTextInputBean; import oracle.apps.fnd.framework.webui.beans.OAWebBean; How do hide Text item at runtime

Code: The Method setRendered is used to hide the text item. Pass the value false for this method. import oracle.apps.fnd.framework.webui.beans.message. OAMessageTextInpuBean; import oracle.apps.fnd.framework.webui.beans.OAWebBean; OAMessageTextInputBean hellotxt= (OAMessageTextInputBean)webBean.findChildRecursive(WelcomeTxt); Hellotxt.setRendered(false); Write above code in processRequest Method or processFormRequest of CONTROLLER according to condition. Like setRendered method, there are so many methods are available in text item Bean. The method setReadonly (true) is used to convert the item to read-only.

How do disable the button at runtime

Page 26 of 67

OAF Training Code: We have to use OASubmitButtonBean to change behavior of buttons at runtime. import oracle.apps.fnd.framework.webui.beans.form.OASubmitButtonBean; OASubmitButtonBean goButton = (OASubmitButtonBean)webBean.findChildRecursive("Go"); goButton.setDisabled(true);

How do display message in different colour Code: We can do it by using rawText style (Item property under MainRN). In Text property, we can use html tags. (Display message in red color) <b><i><font color="red"> Hello World Page</font></i></b> Dynamically, display the rawText by using OARawTextBean OARawTextBean rawtxt = (OARawTextBean)webBean.findChildRecursive("item3"); rawtxt.setText("Inventory Details are Transferred"); rawtxt.setText ("<b><i><font color= red> Inventory Details are Transferred</font></i></b>"); Display the message in red color. See below screenshot.

How do call the specified page from another page

I have two pages. One page is security page, if user enters the login details correct then open the other specific page. Solution: The API pageContext.SetForwardURL is used to open the other specific page. Design the security page with two text items and one button like below screen shot. (Note: This is not related to database. Just check the user name and password with static text like username=Venky and password=Venky) Code: (Write in Controller processFormRequest Method) if (uname.equals("Venky")&&pwd.equals("Venky")) Page 27 of 67

OAF Training { pageContext.setForwardURL("OA.jsp? page=/train/oracle/apps/ak/welcome/webui/WelcomePG", null, OAWebBeanConstants.KEEP_MENU_CONTEXT, null, null, true, OWebBeanConstants.ADD_BREAD_CRUMB_YES, OAWebBeanConstants.IGNORE_MESSAGES); }

Enter user name and password correct, and then press Go button. Note: Set text item property secret as True when enter password. User could not see the password while entering. The below page WelcomePG will be opened.

How do display the Return Navigation link on the page

Suppose, if user call second page from first page and perform some actions on the second page. Later, the user wants to go back to first page, then we have to use Return Navigation link. Select the region pageLayoutRN and click right mouse button, and then select the option returnNavigation.

Page 28 of 67

OAF Training

Set the properties for returnNavigation item. Property Name Value ID returnLink Item Style link Destination URI OA.jsp? page=/train/oracle/apps/ak/security/webui/SecurityPG&retain AM=Y Text Return to Security Page Output for returnNavigation link (Return to Security Page):See the below screenshot.

Page 29 of 67

OAF Training When user presses the Return to Security Page link, then the security page will be opened. How do add a returnLink dynamically Code:processRequest(OAPageContext pageContext, OAWebBean webBean) { super.processRequest(pageContext, webBean); OALinkBean returnLink = (OALinkBean)createWebBean(pageContext, OAWebBeanConstants.LINK_BEAN, null,"returnLink"); returnLink.setDestination("OA.jsp? page=/oracle/apps/dem/employee/webui/EmpSearchPG&retainAM=Y"); // Retrieve and set the translated link text. String linkText = pageContext.getMessage("AK","FWK_TBX_T_RETURN_TO_POS", null); returnLink.setText(linkText); // Add the return link to the page. ((OAPageLayoutBean)webBean).setReturnNavigation(returnLink); }

Following problems are related to work on Database data Connect to Database and return number of suppliers on the page

import oracle.apps.fnd.framework.webui.OAWebBeanConstants; import oracle.apps.fnd.framework.server.OADBTransaction; import java.sql.*; Write below code in process request() method or anywhere as per requirement. oracle.apps.fnd.framework.OAApplicationModule am = pageContext.getApplicationModule(webBean); String task2Info = null; PreparedStatement psProType = null; ResultSet rsProType = null; Page 30 of 67

OAF Training int task2Type = 0; Connection conn = am.getOADBTransaction().getJdbcConnection(); task2Info = "SELECT COUNT(*) FROM FWK_TBX_SUPPLIERS"; try{ psProType = conn.prepareStatement(task2Info); rsProType = psProType.executeQuery(); if (rsProType.next()) { task2Type = rsProType.getInt(1); } } catch(Exception e) {pageContext.writeDiagnostics(am,e.getMessage(),4);} throw new OAException(supplier count :+task2Type, OAException.INFORMATION); See below screen shot for output.

How do call stored procedure from OAF page (Without using EO, VO)

Code: Place the button Callable and write above code in processFormRequest method import java.sql.Connection; import oracle.jdbc.OracleCallableStatement; if (pageContext.getParameter("Callable")!=null) { try { String deleteStmt = "BEGIN DELETE_RECORD( " + "PARAM1 => :1); END; "; OADBTransaction trxn = am.getOADBTransaction(); Page 31 of 67

OAF Training CallableStatement delproc = trxn. createCallableStatement(deleteStmt,1) ; // Rebind parameters delproc.setString(1,"rahul"); delproc.executeUpdate(); } catch(Exception sqle) { pageContext.writeDiagnostics(am, sqle.getMessage(), 4); } //CallableStatement deleteSt=conn.prepareCall(deleteStmt); } First, create stored procedure DELETE_RECORD.

CREATE OR REPLACE PROCEDURE DELETE_RECORD(param1 VARCHAR2) AS BEGIN DELETE FROM emp WHERE ename=param1; COMMIT; END delete_record ; Display message by using AOL Message Name (Message Dictionary)

Solution: we can display message by using putDialogMessage Method. Code: import oracle.apps.fnd.framework.webui.OADialogPage; import oracle.apps.fnd.common.MessageToken; MessageToken[] tokens = {new MessageToken("EMP_NAME", rahul)}; // rahul is employee name OAException message = new OAException("AK", "FWK_TBX_T_EMP_DELETE_CONFIRM", tokens, OAException.CONFIRMATION, null); pageContext.putDialogMessage(message); --display message. See below screenshot

FWK_TBX_T_EMP_DELETE_CONFIRM is message name in AOL.

Page 32 of 67

OAF Training How do call D2K Form from OAF page Syntax: form:responsibilityApplicationShortName:responsibilityKey:securityGroupKey :functi onName Code: pageContext.forwardImmediatelyToForm("form:PO:PURCHASING_OPERATIONS:STANDA RD:PO_POXPOEPO"); Result: Write above code in controller for button. Opens the PO Form when click the button.

1) 2) 3) 4)

Implement a Search Page

Create project Create Business Component Package train.oracle.apps.ak.empsearch.server Create Entity object (EO) under the above package. Create Application Module (AM) under the package train.oracle.apps.ak.empsearch.server Application Module Name: EmployeeAM 5) Create an Employee-to-Manager Association (AO) for the self- join condition on the FWK_TBX_EMPLOYEE table.

Page 33 of 67

OAF Training

6) Select Manager Id in source table and Select EmployeeId in Destination table.

7) Click Add button

Page 34 of 67

OAF Training

Click Next button and verify Expose Accessor names.

Create ViewObject (VO) to display the data on the page. Here, VO is based on EO.

Page 35 of 67

OAF Training

Select EmpSearchEO object twice. There are two entity objects and linked the two Eos through Association Object (AO).

10) Select Next button, and select attributes from EmpSearchEO and EmpSearchEO1. 11) Select below columns from EmpSearchEO and EmpSearchEO1. o EmployeeId o FullName o EmailAddress 12) Changes attribute name and alias as meaningful. Page 36 of 67

OAF Training

Select Attribute EmployeeId1 FullName FullName1 EmailAddress EmailAddress1

Attribute Name and Alias Name ManagerId and MANAGER_ID EmployeeName and EMPLOYEE_NAME ManagerName and MANAGER_NAME EmployeeEmail and EMPLOYEE_EMAIL ManagerEmail and MANAGER_EMAIL

Select Next button, and observer Query. We can change query, if you select the check box Expert Mode. 13) Now, I want to include some other condition in the above query. QUERY: SELECT EmpSearchEO.EMPLOYEE_ID, EmpSearchEO.FULL_NAME AS EMPLOYEE_NAME, EmpSearchEO.EMAIL_ADDRESS AS EMPLOYEE_EMAIL, EmpSearchEO1.EMPLOYEE_ID AS MANAGER_ID, EmpSearchEO1.FULL_NAME AS MANAGER_NAME, EmpSearchEO1.EMAIL_ADDRESS AS MANAGER_EMAIL, Flkp.meaning POSITION_DISPLAY FROM FWK_TBX_EMPLOYEES EmpSearchEO, FWK_TBX_EMPLOYEES EmpSearchEO1, FWK_TBX_LOOKUP_CODES_VL flkp WHERE EmpSearchEO.MANAGER_ID = EmpSearchEO1.EMPLOYEE_ID(+) AND EmpSearchEO.POSITION_CODE=flkp.lookup_code AND flkp.lookup_type=FWK_TBX_POSITIONS Select Next button, and check mapping between Query Columns and Attribute names. Select Finish button. 14) Add the ViewObject (EmployeeSummaryVO) to Application Module.

Page 37 of 67

OAF Training 15) Select the application module (already created), and press right mouse button and select the option Edit EmpSearchAM, then select the ViewObject.

16) Attach the Application Module (EmpSearchAM) to your OApage. 17) Create the item under PageLayout Region. The item style is StaticStyledText. Set the below properties for the item. Property Value ID PageHelp Item Style StaticStyledText DataType Varchar2 CSS Class OraInstructionText Message Appl Short Name AK Message Name FWK_TBX_T_PAGE_GENERAL Test the page once and check the output on the page. Some text will be displayed on the page above. Configure RESULT-BASED Search. 18) Create region with style query under pageLayout Region. Set the below properties for the region queryRN. Property Value ID queryRN Item Style Query Construction Mode Result Based Search Include simple panel True Include View panel True Include Advanced search panel True 19) Adds a Results Data table to queryRN. Select the queryRn and press right mouse button, then select option Region using Wizard. 20) Select the viewobject EmployeeSummaryVO and select specified columns what you want to display on the OAPage. 21) Set below properties for ResultsTable.

Page 38 of 67

OAF Training

22) Set the properties for columns under ResultsTable. How do display the drill down to details page according to criteria. Steps:1) Create view object with SQL query. The query is: SELECT EmployeeId AS EMPLOYEE_ID, EmployeeName AS EMPLOYEE_NAME, Job AS JOB, Salary AS SALARY, Deptno AS DEPARTMENT_NUM FROM EMP 2) Select the items style as MessageStyledText. 3) Design the page with regions pageLayout (root region) and defaultSingleColumn (Sub region). 4) We can use region using wizard option under the region style defaultSingleColumn and then select displayed items by using the wizard. 5) The page name is EmployeeDetailsPG.xml. 6) Now, we have to call the EmployeeDetailsPG page and pass parameters to this page from the other page (search page). 7) Set the property Destination URI as OA.jsp? page=\train\oracle\apps\ak\employee\webui\EmployeeDetailsPG&employeeNumber= {@EmployeeId}&retainAM=Y&ADD_BREAD_CRUMB=Y for the item EmployeeName. The item EmployeeName style is MessageStyledText. Now, the employeeName item will be showing as Link 8) Now, we have to execute the query according to employeeId (depending on selection of employeeName ). 9) In viewobjectimpl.java (employeeFullVOImpl.java) file, create method as below. Page 39 of 67

OAF Training

Code: import oracle.jbo.domain.Number; import oracle.apps.fnd.framework.OAException; public void initQuery(String employeeNumber) { If (employeeNumber! =null) { Number empNum=null; Try { empNum=new Number(employeeNumber); } Catch(Exception e) { Throw new OAException(AK, FWK_TBX_INVALID_EMP_NUMBER); } setWhereClause(EMPLOYEE_ID=:1); setWhereClauseParams(null); setWhereClauseParam(0,empNum); executeQuery(); } } 10) From applicationModule, we can call view object procedure. Code: public void initDetails(String employeeNumber) { EmployeeFullVOImpl empvo=getEmployeeFullVO1(); Empvo.initQuery(employeeNumber); } 11) Create the CONTROLLER and call the procedure initDetails. 12) Write code in processRequest method Code: String empnum=pageContext.getParameter(employeeNumber); OAApplicationModule am=pageContext.getApplicationModule(webBean); Serializable[] parameters={empnum}; Am.invokeMethod(initDetails, parameters); Result: we can get the details of employee according to employee ID.

Page 40 of 67

OAF Training How do display custom copy right on OAF page

Solution: First, we have set the pageLayout region property AutoFooter as False. (This is very important). Select the pageLayout region, and press right mouse button, then select the option Copyright and set the property prompt as you wish. Run the page and observe the Copyright prompt at footer of the page. How do get the value of the checkbox when selected or deselected Solution: Bydefault, the checkbox returns on when selected. The checkbox returns null when deselected. According to on and null values, we can do validation on the checkbox. Code: Write code in processFormRequest method for any button String val= pageContext.getParameter("chkbox"); If (val.equals(on )) { System.out.println(Male); } If (val==null) { System.out.println(Female); }
http://forums.oracle.com/forums/thread.jspa?threadID=577666&start=0&tstart=165

In this site, code has been given regarding get value of selected checkbox from VO (Displayed multiple rows)

How do insert data from OAF Page to Database table by using View Object

Steps 1) Create view object with query. 2) Create application module and attach the view object 3) Create OAF page and attach application module. 4) Create Controller and write below code.

import oracle.apps.fnd.framework.OAApplicationModule; Page 41 of 67

OAF Training import oracle.apps.fnd.framework.webui.beans.message.OAMessageTextInputBean; import oracle.apps.fnd.framework.webui.beans.message.OAMessageLovInputBean; import java.text.SimpleDateFormat; import java.text.DateFormat; import java.util.Date; import java.text.ParseException; import oracle.apps.fnd.framework.server.OADBTransaction; import java.sql.*; Method: processRequest () ********************************** public void processRequest(OAPageContext pageContext, OAWebBean webBean) { super.processRequest(pageContext, webBean); OAApplicationModule am=pageContext.getApplicationModule(webBean); am.invokeMethod("initQuery",null); } Method: processFormRequest () **************************************** public void processFormRequest(OAPageContext pageContext, OAWebBean webBean) { super.processFormRequest(pageContext, webBean); if (pageContext.getParameter("Apply")!=null) { try { OAApplicationModule am=pageContext.getApplicationModule(webBean); // Date update_date=pageContext.getCurrentUserDate(); // System.out.println("current date="+update_date); OAMessageTextInputBean supplier_id = (OAMessageTextInputBean)webBean.findChildRecursive("SupplierId"); String sup_id_txt=supplier_id.getText(pageContext); int sup_id=Integer.parseInt(sup_id_txt); OAMessageLovInputBean sup_name = (OAMessageLovInputBean)webBean.findChildRecursive("SupplierName"); String supname_txt=sup_name.getText(pageContext); OAMessageTextInputBean onhold_flag = (OAMessageTextInputBean)webBean.findChildRecursive("OnHoldFlag"); String onhold_txt=onhold_flag.getText(pageContext); String sdate=pageContext.getParameter("StartDate"); // Date startdate_txt=sdate; //System.out.println("start date="+df.format(startdate_txt)); String edate=pageContext.getParameter("EndtDate"); // Insert row into the table FWK_TBX_SUPPLIERS String task2Info = null; Page 42 of 67

OAF Training PreparedStatement psProType = null; ResultSet rsProType = null; int task2Type = 0; Connection conn = am.getOADBTransaction().getJdbcConnection(); task2Info = "INSERT INTO FWK_TBX_SUPPLIERS(SUPPLIER_ID,NAME,ON_HOLD_FLAG,START_DATE,END_ DATE,LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY) VALUES(:1,:2,:3,:4,:5,SYSDATE,0,SYSDATE,0)"; psProType = conn.prepareStatement(task2Info); psProType.setInt(1,sup_id); psProType.setString(2,supname_txt); psProType.setString(3,onhold_txt); psProType.setString(4,sdate); psProType.setString(5,edate); // psProType.setString(); psProType.executeUpdate(); am.invokeMethod("apply"); } catch(Exception e) { System.out.println("error="+e.getMessage()); } //psProType.setDate(4,startdate_txt); // psProType.setDate(5,edate); } } Write below methods in Application Module which is corresponding to view object. // it is used to create row in view object cache, and then user can enter and insert data into table. public void initQuery() { SuppliersVOImpl vo=getSuppliersVO1(); Row row=vo.createRow(); vo.insertRow(row); } // it is for commit the transaction; otherwise not inserted the record into table. public void apply() { getTransaction().commit(); } Please find the below screen shot. The below data will be inserted into table when press the Apply button. See below screenshot for output.

Page 43 of 67

OAF Training

How do refresh the same page after the data has been entered

There is API forwardImmediatelyToCurrentPage used to refresh the same page when the user presses the submit button. Write below code in processFormRequest() method **************************************************************** import com.sun.java.util.collections.HashMap; HashMap params = new HashMap(); pageContext.forwardImmediatelyToCurrentPage(params,true, OAWebBeanConstants.ADD_BREAD_CRUMB_NO); How do set the values in poplist

Solution:1) Create View Object(VO) and write query to display the values in poplist. VO Name: SuppliersListVO Query:SELECT 'YES' MEANING,'Y' CODE FROM DUAL UNION SELECT 'NO' MEANING,'N' CODE FROM DUAL YES is used to show for user on the OAF page. Y is used for internal purpose. The value Y will be stored into database when user selects YES. Set the properties for an item:Property Item Style Picklist view Definition Picklist Display Attribute Picklist Value Attribute Value messageChoice train.oracle.apps.ak.suppliers.list.webui.SuppliersLis tVO Meaning Code

Page 44 of 67

OAF Training How do hide the specified item when user selects the particular value from Poplist

Solution:The concepts partial page rendering and SPEL should be used to get this solution. I have one poplist in OAF page and the list has two values YES and NO. If the user selects the value NO, then the specified item should be invisible on OAF page at runtime. Note: This example followed above screen shot page. Steps: 1) Create properties view object (PVO) and create two attributes. i) RowKey (Set the properties like below screenshot)

ii) EndDateRender (Set the properties as per below screenshot)

Page 45 of 67

OAF Training 2) Select the option Tuning for the same properties VO and select the check box like below screenshot.

3) Attach the propertiesVO (SuppliersListPVO) to application module (SuppliersAM). 4) Configure the list item (onholdflag item). Set the below properties. Property Disable Server Side Validation Disable Client Side Validation Action Event Submit Value True True firePartialAction onholdflagChange True

5) Configure the item which is invisible according to value of the list item. Here, the invisible item is EndDate. So, set the below property for the item EndDate. Property Rendered Value ${oa.SuppliersListPVO1.endDateRender}

6) Write below methods in application module (SuppliersAMImpl.java) public void onholdflagChange() { OAViewObject vo = (OAViewObject)findViewObject("SuppliersListPVO1"); OARow row=(OARow)vo.first(); OAViewObject suppvo=(OAViewObject)findViewObject("SuppliersVO1"); OARow supprow=(OARow)suppvo.getCurrentRow(); String onhold=(String)supprow.getAttribute("OnHoldFlag"); Page 46 of 67

OAF Training if ((onhold==null)||("N".equals(onhold))) { row.setAttribute("EndDateRender",Boolean.FALSE); } else { row.setAttribute("EndDateRender",Boolean.TRUE); } } public void init() { OAViewObject appPropsVO=(OAViewObject)findViewObject("SuppliersListPVO1"); if (appPropsVO!=null) { if (appPropsVO.getFetchedRowCount()==0) { appPropsVO.setMaxFetchSize(0); appPropsVO.executeQuery(); appPropsVO.insertRow(appPropsVO.createRow()); OARow row=(OARow)appPropsVO.first(); row.setAttribute("RowKey",new Number(1)); } } onholdflagChange(); }

7) Call the init() method from processRequest. am.invokeMethod("init"); 8) call the onholdflagChange() method from processFormRequest if ("onholdflagChange".equals(pageContext.getParameter(OAWebBeanConstants.EVENT _PARAM))) { am.invokeMethod("onholdflagChange"); } In the above code, the onholdflagChange is event name. The event of the item will be worked as form-submit. So, the above code (event related) has been written in processFormRequest. Run the OAF page and change the value of the list item. The item EndDate will not be rendered if the value of the list item is NO.

Page 47 of 67

OAF Training How do fire event? To display supplier name according to supplier id.

There are two text items on OAF page. They are I) SupplierId II) SupplierName Steps:1) Set the below properties for item SupplierId. Property Value Action firePartialAction Event supplierNameEvent Submit True 2) Write below code in processFormRequest method. if("supplierNameEvent".equals(pageContext.getParameter(OAWebBeanConstants. EVENT_PARAM))) { int supp_id = Integer.parseInt(pageContext.getParameter("SupplierId")); if (supp_id==195) { am.invokeMethod("supplierNameEvent"); } } 3) Write below method supplierNameEvent in an application module. public void supplierNameEvent() { OAViewObject suppvo = (OAViewObject)findViewObject("SuppliersVO1"); OARow supprow=(OARow)suppvo.getCurrentRow(); supprow.setAttribute("SupplierName","Ramprasad"); } Note: The webBean properties can not be modified in processFormRequest method (Ex: setText; setName etc). Result: Enter the value 195 in supplier id text item and press tab key, then the name Ramprasad will be getting displayed in supplier name text item.

Page 48 of 67

OAF Training How do create list box and add values to the list box dynamically

Solution: First, create a messageLayout region under messageComponentLayout region because we are creating Listbox item under messageLayout region using the below code. Write below code in processRequest() method of CONTROLLER. import oracle.apps.fnd.common.VersionInfo; import oracle.apps.fnd.framework.webui.OAControllerImpl; import oracle.apps.fnd.framework.webui.OAPageContext; import oracle.apps.fnd.framework.webui.beans.OAWebBean; import oracle.apps.fnd.framework.webui.beans.form.OADefaultListBean; import oracle.apps.fnd.framework.webui.OAWebBeanConstants; import oracle.apps.fnd.framework.webui.beans.message.OAMessageLayoutBean; public void processRequest(OAPageContext pageContext, OAWebBean webBean) { super.processRequest(pageContext, webBean); //Create List WebBean OADefaultListBean list = (OADefaultListBean)createWebBean(pageContext,OAWebBeanConstants.DEFAULT_LI ST_BEAN, null, "positionsList"); // Set the Viewobject name, display attribute and value attribute for list box. list.setListViewObjectDefinitionName("train.oracle.apps.ak.suppliers.list.webui.SuppliersL istVO"); list.setListValueAttribute("Code"); list.setListDisplayAttribute("Meaning"); list.setMultiple(true); list.setName("SupplierList"); OAMessageLayoutBean listBoxLayout = (OAMessageLayoutBean)webBean.findChildRecursive("listBoxLayout"); listBoxLayout.addIndexedChild(list); }

Page 49 of 67

OAF Training Create a Shuttle Region

Following is a brief outline of the steps to create a Shuttle region. Step 1: Create a page with a pageLayout region using OA Extension. Make sure the Form property on the pageLayout region is set to True. Step 2: Select the pageLayout region in the Structure pane, and choose New > Region from the context menu. Set the following properties on this new region (Required properties are marked with *): *ID - set the shuttle's ID property in accordance with the OA Framework File / Package/ Directory Standards. *Region Style - set the region style to shuttle. Add Indexed Children - make sure this property is set to True, so that OA Framework automatically generates the web beans under this web bean hierarchy. The default is True. Available Header - specify the header text of the first (leading) list. Selected Header - specify the header text of the second (trailing) list. If you want to implement just one list for Reordering, that is, you do not want to shuttle items between two lists, then leave this property blank. Ordering Allowed - set to True if you want to enable ordering of the contents of the Selected (second or trailing) list. If you implement only one (leading) list in the shuttle region to create a Reordering region, then setting this property to True enables ordering on that leading list. The default is False. Step 3: The Shuttle region can have a maximum of two list web beans, referred to as the leading and trailing lists. The trailing list is omitted when you want to implement a shuttle region with a single list for the purpose of reordering the contents of that list. When you define a shuttle region, OA Extension automatically creates a leading component for you, which contains a single list item. Be sure to set the following properties on the list item (Required properties are marked with *): *ID - set the list's ID property in accordance with the OA Framework File / Package/ Directory Standards.

Page 50 of 67

OAF Training *Multi-Select Allowed - set to True to allow the multiple selection of items in the list. The default is False. Picklist View Definition - specify the fully qualified view object name that is the data source to the List web bean. (For example, oracle.apps.fnd.framework.server.FndApplicationVO) *Picklist View Instance - alternately specify a view instance name for the data source of the list, if the Picklist View Definition is not available. Note that setting this property overrides the Picklist View Definition property. (For example, FndApplicationVO, which needs to be present in the ApplicationModule.) *Picklist Display Attribute - specify the view attribute name that serves as the displayed values of the list's content. *Picklist Value Attribute - specify the view attribute name that serves as the internal values of the list's content. This property, and not the Picklist Display Attribute property, uniquely identifies the elements in the list. Picklist Description Attribute - specify the view attribute name that serves as the descriptions of the list's content. Rendered - specify True to render this list. *List Height - specify the suggested display height of the list, in characters. The default is null. If this property is not set, the height is determined based on the lengths of both lists and their minimum and maximum values. The value should be in the range of 10 to 20. Note: The List Height is only a suggested value. Your browser application and UIX determines the final 446 height of the list based on the number of items in the list and the size of the browser window. Step 4: To create an optional trailing list, select the shuttle region in the Structure pane and choose New >trailing from the context menu. OA Extension automatically creates a trailing component for you, which contains a single list item. Refer to Step 3 for the list of properties that you should also set on the trailing list item. Make sure you specify names for the Picklist Display Attribute, Picklist Value Attribute and Picklist Description Attribute properties that match the corresponding property of the leading list item. Note: If you do not want to pre-populate the trailing list when the page initially renders, you can leave the Picklist View Definition, Picklist View Instance, Picklist Display Attribute, Picklist Value Attribute and PicklistDescription Attribute blank. OA Framework takes care of retaining user selected values in the trailing list when the page refreshes. Note: The Picklist Value Attribute uniquely identifies the elements in a list, so if you want to pre-populate both the leading list and trailing list with data, be sure to set the Picklist Value Attribute property to a different value for each list. Setting this property to the same value for both lists will result in undesirable behaviour, such as causing the values in the leading list to disappear. Step 5: You can include buttons or icons in the footer of each list, as shown in Figure 2. Select the shuttle region in the Structure pane, and choose New > leadingFooter (for a Page 51 of 67

OAF Training footer in the leading list) or New > trailingFooter (for a footer in the trailing list). OA Extension automatically creates a leadingFooter or trailingFooter component, respectively, each containing a flowLayout region. You can then add your buttons or icons to this flowlayout region. Note: If you set the Rendered property to False for either the leading or trailing list, the leading or trailing footer also does not render, respectively. Since the footer is directly linked to its respective list, if the list is not rendered, the footer is irrelevant.

About StackLayout, rowLayout, cellFormat region styles

We can design layout like below screen shot by using the stackLayout, rowLayout and cellFormat region styles.

pageLayoutRegion |-----stackLayout region |----rowLayout region |---------cellFormat region |-------spacer (item style) | (width: 400) |-------item (style: formattedText) (Text: <b>Authority For Expenditure</b> (Please look above screenshot for result) |------stackLayout region |----rowLayout region |----cellFormat region |-----spacer (item style) | (width: 400) |-----item (style: formattedText) (Property Text: <b>Co: 101 XXX Energy Inc</b>) |--------stackLayout region |-----rowLayout region Page 52 of 67

OAF Training |-----cellFormat region |------ table region |----- item1 (style: messageStyledText) |-----cellFormat region |------ table region |----- item2 (style: messageStyledText) |-----cellFormat region |------ table region |----- item3 (style: messageStyledText) Set the properties for item1, item2 and item3. The properties are Prompt View Instance View Attribute (Please see table region in above screenshot for result) How to display text items side by side Solution:pageLayoutRegion |-----stackLayout region |----rowLayout region |---------cellFormat region |-------item (messageTextInput) |---------cellFormat region |-------item (style: spacer; width: 50) Set the item properties for messageTextinput . The properties are prompt , view Instance and view Attribute (Please see above screenshot for result).

About Browser Look and Feel (BLAF)

A Look-and-Feel (LAF) controls the appearance of an OA Framework application. An LAF provides the rendering logic for each component along with a look and feel-specific style sheet. The OA Framework supports three LAFs. Oracle BLAF -- implements the Oracle Browser Look-and-Feel (BLAF) UI Guidelines.

Page 53 of 67

OAF Training

Minimum LAF (MLAF) -- generates "minimal" content to reduce the size of HTML pages and overall network overhead (for example, this LAF uses fewer images than the BLAF version)

Plain Text -- produces a plain text version of the page (typically used to send a plain text version of a page to an e-mail client). Note that the plain text LAF does not support all the existing component styles.

Note: The LafConstants class is in the oracle.apps.fnd.framework.webui.laf package.

Example: OA.jsp? page=/train/oracle/apps/ak/employee/webui/EmpDetailsPG&employeeNumber={@Empl oyeeId}&retainAM=Y&addBreadCrumb=Y&OALAF=minimal Call the page EmpDetailsPG from any another page and observe appearance of the EmpDetailsPG. Please find the below screen shot. (OALAF=minimal)

Page 54 of 67

OAF Training

From above screenshot, some text is showing in green color. Try for blaf and oaText LAFs like above.

About AdvancedTable Bean

Previously, OA Framework used

oracle.apps.fnd.framework.webui.beans.table.OATableBean, an Oracle Application implementation of UIX oracle.cabo.ui.beans.table.TableBean, to render tables. Now oracle.apps.fnd.framework.webui.beans.table.OAAdvancedTableBean extends OATableBean to provide declarative support for existing table features that previously required programmatic control. OAAdvancedTableBean also provides declarative support for features not available with OATableBean, such as column span in a table

column header. As of Release 11.5.10, oracle corp. recommend new tables be implemented as "advanced tables" based on oracle.apps.fnd.framework.webui.beans.table.OAAdvancedTableBean. You can create a table by specifying appropriate information in Oracle 9i JDeveloper OA Extension. Currently, you can declaratively specify the following features/components/attributes on a table:

Number of rows to display in a table Width of a table Header text for individual table columns Column span in column headers Table formatting Single selection and multiple selection on a table and adding other controls to a selection bar Sorting and initial sorting of a table on up to three columns Totalling a column Adding new rows Page 55 of 67

OAF Training

Detail Disclosure Row Headers Wrap Settings

Below is a brief outline of how to declaratively implement a table. AdvanceTablePG (.xml)

| |---PageLayoutRegion | |---create region (style: advancedTable; Set View Instance property) | |---create column | |---create item (style: messageTextInput; Set the View Attribute property) |---create column header (to display heading of the Column and sort the data) Set the prompt property in column header properties to display heading of the column (example: Employee Name) Set the property Sort by View Attribute to sort the data based on column. (Ex: - if Sort by View Attribute property value is EmployeeId , then sort the data based on EmployeeId attribute.) See below screen shot for reference.

Page 56 of 67

OAF Training

Design the table with other columns like above. We need to write code to display data like below screenshot.

Create controller (EmpAdvancedCO ) on PageLayout Region. public void processRequest(OAPageContext pageContext, OAWebBean webBean) { super.processRequest(pageContext, webBean); oracle.apps.fnd.framework.OAApplicationModule am = pageContext.getApplicationModule(webBean); am.invokeMethod("initQueryAdv"); //create row and execute query } Go to the corresponding Application Module and write below code to create row and execute query. (i.e. pagelayout region AM Definition property value) import oracle.jbo.Row;

Page 57 of 67

OAF Training public void initQueryAdv() { EmployeeFullVoImpl empvo=getEmployeeFullVo1(); Row row=empvo.createRow(); empvo.insertRow(row); empvo.executeQuery(); } In above code, the EmployeeFullVo1 is view object instance. Compile the code and run the page.

How do display Add another row button and totalling on column

In AdvancedTable, this is good feature to add row dynamically and display total on footer without write code. Declarative implementation Select the advancedTable region and press right mouse button and select the option footer.

After select the footer option, the footer and tableFooter1 components will be created. See below screenshot.

Select the tableFooter1 and press right mouse button and select the option addTableRow . See below screenshot.

Page 58 of 67

OAF Training Run the page once and you will get Add another Row button at the footer of advancedTable. Select total option to display total of particular column (salary). The option total showing in above screen shot.

We need to set one property Total Value as True for salary column (column4 in below screen shot) and run the page.

See the below screenshot to know the final output of advancedTable. (Add Another Row button, Recalculate button and total value for salary column)

Page 59 of 67

OAF Training

After press the Add Another Row button, one blank record will be created. See below screen shot.

User selects the Recalculate button to update the column total. Note: The total displays a double precision summation of all visible rows in the table. The total reflects only the current visible records and not all the records queried.

Page 60 of 67

OAF Training

How do iterate the number(Serial Number) in OAF by using Transient Attribute

Code: public void setItemDetailsSno() { OAViewObject vo = (OAViewObject)getCMCostchangeVO(); CMCostchangeVORowImpl row = null; int fetchedRowCount = vo.getRowCount(); // we use a separate iterator -- even though we could step through the // rows without it -- because we don't want to affect row currency. RowSetIterator insertIter = vo.createRowSetIterator("insertIter1"); if (fetchedRowCount > 0) { insertIter.setRangeStart(0); insertIter.setRangeSize(fetchedRowCount); for (int i = 0; i < fetchedRowCount; i++) { row = (CMCostchangeVORowImpl)insertIter.getRowAtRangeIndex(i); // For performance reasons, we generate ViewRowImpls for all // View Objects. When we need to obtain an attribute value, // we use the named accessors instead of a generic String lookup. row.setAttribute("SNo", new Integer(i+1)); //SNo is transient attribute in VO } } insertIter.closeRowSetIterator(); } See below screenshot and check the values of serial number

Check the values of serial number in above screen shot.

Page 61 of 67

OAF Training

How do display latest serial number dynamically while creating row

Write below code in proecessFormRequest Method of Controller. Code: oracle.apps.fnd.framework.OAApplicationModule am=pageContext.getApplicationModule(webBean); OAAdvancedTableBean tableBean = (OAAdvancedTableBean)webBean.findChildRecursive("AdvancedtblRN"); if (tableBean.getName().equals(pageContext.getParameter(SOURCE_PARAM)) && ADD_ROWS_EVENT.equals(pageContext.getParameter(EVENT_PARAM))) { am.invokeMethod("setSequenceNum"); } Note: From above code, ADD_ROWS_EVENT is event name for Add Another Row button. Write below code in Application Module which is added to your pagelayout region. Imp: Set the property insert rows automatically as False in addTableRow1 object at footer of advanced table. public void setSequenceNum() { SequenceNumberVOImpl seqvo=getSequenceNumberVO1(); int fetchedRowCount=seqvo.getRowCount(); RowSet rowset=seqvo.createRowSet("dd"); rowset.last(); rowset.next(); Row row=seqvo.createRow(); rowset.insertRow(row); row.setAttribute("SERIALNUM",new Integer(fetchedRowCount+1)); rowset.closeRowSet(); } Result: Display Serial Number (transient attribute) according to current row position dynamically after pressing the Add Another Row button.

See below screen shot, after press the Add Another Row button New row is created and added onto table, and SerialNumber is also incremented (from 6 to 7) and displayed on table. See below screenshot.

Page 62 of 67

OAF Training

How do delete a selected record of Advanced Table using Delete Switcher

Solution:First add Delete Switcher item onto advancedTable region.

From above screenshot, 1) The deleteSwitcher is a column of advancedTable region. 2) The DelSwitcher is a switcher under deleteSwitcher column. (Set viewAttribute property to enable the deleteSwitcher item) (Add the column in VO like below for deleteSwitcher. Check below decode statement. Add this in VO) decode(NVL(SequenceNumberEO.ON_HOLD_FLAG,'Y'),'Y', 'DeleteEnabled', 'DeleteEnabled') AS DELETE_SWITCHER 3) Set viewAttribute property as DeleteSwitcher 4) Create image item under case. Set the imageID as DeleteDisabled Set the imageURI property as deleteicon_disabled.gif 5) Create second image item under second case. Set the imageID as DeleteEnabled (same as in VO) Set the imageURI property as deleteicon_enabled.gif 6) Set the image items height and width as 24 7) Set the action property for DeleteEnabled image as fireAction and Event as delete. Set the parameters property under Event property as below screenshot.

Page 63 of 67

OAF Training

From above screenshot, the value of Name is supplierNUM. It is used to get serial number when user clicks the delete switcher at runtime. Value: ${oa.SequenceNumberVO1.SERIALNUM} [it is SPEL] After setting above properties, Write below code in Application Module for removing the selected record. public void deleteSupplier(String SupplierNumber) { int suppToDelete = Integer.parseInt(SupplierNumber); OAViewObject vo = (OAViewObject)getSequenceNumberVO1(); SequenceNumberVORowImpl row=null; int fetchedRowCount = vo.getFetchedRowCount(); System.out.println("fetchedRowCount " + fetchedRowCount); RowSetIterator deleteIter = vo.createRowSetIterator("deleteIter"); if (fetchedRowCount > 0) { deleteIter.setRangeStart(0); deleteIter.setRangeSize(fetchedRowCount); for (int i = 0; i < fetchedRowCount; i++) { row = (SequenceNumberVORowImpl)deleteIter.getRowAtRangeIndex(i); // Number primaryKey = row.getSupplierId(); Number primaryKey = row.getSERIALNUM(); if (primaryKey.compareTo(suppToDelete)==0) { row.remove(); //getTransaction().commit(); (if remove this comments, then the record will be removed from database) break; } } } deleteIter.closeRowSetIterator(); } Page 64 of 67

OAF Training Invoke above method from CONTROLLER. Write below code in processFormRequest method of CONTROLLER. public void processFormRequest(OAPageContext pageContext, OAWebBean webBean) { super.processFormRequest(pageContext, webBean); oracle.apps.fnd.framework.OAApplicationModule am = pageContext.getApplicationModule(webBean); if ("delete".equals(pageContext.getParameter(EVENT_PARAM))) {String supplierNumber = pageContext.getParameter("supplierNUM"); Serializable[] parameters = { supplierNumber }; am.invokeMethod("deleteSupplier", parameters); MessageToken[] tokens = {new MessageToken("EMP_NAME", supplierNumber)}; OAException message = new OAException("AK", "FWK_TBX_T_EMP_DELETE_CONFIRM", tokens, OAException.CONFIRMATION, null); pageContext.putDialogMessage(message); } } From the CONTROLLER code, the delete is event name in DeleteEnabled image. The supplierNUM is value of SPEL ${oa.SequenceNumberVO1.SERIALNUM} Run the page and get below output.

Press the Delete switcher of any record and then check the output. Now, the record still available in database because of not committed this transaction. After press the Save button, the record will be removed from the database.

If user wanted to show checkbox for onHoldFlag column, then we need to change the item style of the onHoldFlag item as messageCheckBox . Set the below check box properties checkedValue: Y ; uncheckedValue: N

Page 65 of 67

OAF Training

Check the onHoldFlag values in above screenshots.

How do clear the View Object at runtime

Code: Write below code in Application Module. Public void clearVO() { SupplierInfoVOImpl vo= getSupplierInfoVO1(); vo.remove() ;} Call above method from CONTROLLER (processFormRequest). OAApplicationModule am =pageContext.getApplicationModule(webBean); am.invokemethod(clearVO); Please see below screenshots

After press the clear button, the data will be cleared. See below screenshot.

Page 66 of 67

OAF Training

BIBLIOGRAPHY :-

Links for learning more about OAF:---------------------------------------------------http://oracle.anilpassi.com/oa-framework-training-tutorial-03.html [Practical example has been given about how to create row and save the row by using VO] Use the code provided in http://scripts4oracle.blogspot.com/2006/12/self-service-hr-script-3-to-allocate.html for sending mass emails from Oracle EBS. http://oracle.anilpassi.com/restart-or-bounce-apache-in-oracle-apps-11i-2.html [Restart or Bounce Apache in Oracle Applications 11i] http://oracle.anilpassi.com/master-detail-screen-in-oa-framework-part-i-2.html [Develop Master Detail screens in OA Framework]

Page 67 of 67