Answers – Sakthivarman – 094

25/3/11 – 03.30 pm

1.a) create table XX_EMP_TEST(

Empno varchar2(10) not null,

Emp Name varchar2 (60),

Joindate date ‘DD-MON-YYYY’,

Salary number,

Manager varchar2(10));

b) LOAD DATA

INFILE *

INTO TABLE XX_EMP_TEST

TRAILING NULCOLS

TERMINATED BY ‘,’ OPTIONALLY ENCLOSED BY ‘ “” ‘

(EmpNo, EmpName, Joindate,salary,manager)

BEGIN DATA

E1011, Rajkumaran, 01-JAN-2010, 12345.75, E1010

E1012, “Sakthi, Varman”, 01-FEB-2010, 12345.75,
E1013, Francis, 01-MAR-2010, 12345.75, E1010
E1014, Suresh P, 01-APR-2010, 12345.75, E1010
E1015, Sriram, 01-MAY-2010, 12345.75,

C) LOAD DATA

INFILE XX4I_EMP_TEST.bat

INTO TABLE XX_EMP_TEST

EXAMPLE1.BAD

EXAMPLE2.DSC

TRAILING NULCOLS
 TERMINATED BY ‘,’ OPTIONALLY ENCLOSED BY ‘ “” ‘

(EmpNo, EmpName, Joindate,salary,manager)

BEGIN DATA

E1011, Rajkumaran, 01-JAN-2010, 12345.75, E1010

E1012, “Sakthi, Varman”, 01-FEB-2010, 12345.75,
E1013, Francis, 01-MAR-2010, 12345.75, E1010
E1014, Suresh P, 01-APR-2010, 12345.75, E1010
E1015, Sriram, 01-MAY-2010, 12345.75,

2.) Data conversion is reading the data from the flat file and loading them into the database tables.

Interfaces acts as the intermediate between the staging table and the database table. Certain
validations and invoking of subprograms is necessary so as to affect the database tables.

3.) Form personalization can be made through the user menu itself whereas in custom.pll it is not
possible.

5.) Steps followed after the completion of custom forms and reports:

 Move the form to the $AU_TOP/forms/US

 Compile through the command f60gen <form name> apps/apps

 Form is to be registered to the corresponding application and the responsibility.

 New responsibility is to be created when no valid responsibility exists.

 Application developer  form and then the function

 After the registration move it to the base application path. Ex : XX4I_TOP/forms/US

Custom report steps

 Go to concurrent program and define the execution method.

 Define the concurrent program.

 Create a new request group

 Finally attach to the corresponding application

 Submit a new request.

  View the output.

6.) steps to be followed to implement a find window:

 Reference the query find object group from the appstand form.

 A datablock , canvas and a window will be created.

 Rename all the above three.

 Delete the query find object group from your form after referencing so that we can
create a another find window in the future.

 Create the necessary items for find window.

 Edit the W-B-P trigger in the new button so that the user may go to enter the new
record in the main form when the find window automatically pops up.

 Edit the W-B-P trigger in the find button for execute query.

 Edit the clear button to clear the record entered in fnd window.

 Copy the code from find button and paste in the key next block trigger of QF block.

 Resize the canvas.

 Mention the resullt block window,query find block and query find window in the pre-
form trigger

 In the W-N-F-I trigger call the query find trigger.

7.) Look ups are similar to that of the value set. For small values and either option cases we go for look
ups.

Example – Gender and for Yes/No options.

9.) ebiz/testappl/testappl/<appl_top>/11.5.0/forms/US

ebiz/testappl/testappl/<appl_top>/11.5.0/reports/US
10) DFF is nothing but the extra information .

We define the DFF in attribute columns.

In KFF we have predefined combination structures.

We define the KFF in segment columns.

12) To have a DFF in custom form.

 Register the DFF

 Query and define the segments.

 Mention the extra fields and the corresponding attribute columns.

 Save ,freeze and then compile.

 Create a flex field column in the database block

 Subclass it as TEXT_ITEM_DESC_FLEX

 Create a procedure in the name of the DESC field

 Create the following eight triggers in the database block:

o W-N-B-I

o Pre-query

o Pre-block

o Post_query

o Post_block

o When validate item

o When new item instance

o When validate record

 Call the form level package and the event procedure

  FND_FLEX.EVENT( trigger name )  should be in all the above triggers.

 In the W-N-F-I decsribe the

Object name

Block name

Field name

DFF name

Null)

13. Go to the record history in the user menu to find the base table and the view name of the

Seeded table.

14. Date field LOV can be enable by setting the field LOV as

ENABLE_LIST_LAMP

Validate from list  No

Key-listval trigger  calendar.show;

15. Concurrent program is necessary to invoke the executables such as reports,SQL*Loader and PL/SQL

Scripts.

All the .rdf files can be run only through it in oracle apps.

Each and every time when the program is run a request is submitted and compiled. These group of
requests which are in process are said to be as Concurrent Request Sets.

16. Folder is used for end user’s convenience. The Object can be found through the table

FND_FOLDERS

Select * from FND_FOLDERS where object like ‘%sak%’;

17. In folder options we give the prompt texts in the initial value of the prompt block.
19.a) In Form function we give the function name for the form we are going to register.

b) Menu is nothing but the header which contains the list of forms. We attach the form under specific
menu or submenus, before that we need to define the menu or we can attach in the existing.

c.) Request group is created and under which we attach our rdf files and view the output.

d.)Responsibility holds all the applications.

e.) Users are for giving priveleges. i.e which applications are valid for them.

20.)

o Copy the template.fmb and save it in local

o Rename it to your form.

o Change the window name and subclass.

o Modify the pre-form trigg and mention your window.

o Modify the app_custom package body and give your window name in it.

o Use the data block wizard and create the form.