INDEX

Installing the template file 2-3

Adding a report to oracle application 4-10

Adding forms to existing module 11-17

Adding a new module to oracle applications 18-23

Adding a responsibility 24-25

Technical Notes 26-29

Installing the Template Form

FIRST STEP: DOWNLOAD RESOURCE FROM THE SERVER

1) Download the folder resource from the server from the following path:

/e1/vision/visionappl/au/11.5.0/resource

2) Copy Template.fmb and appstand.fmb from /e1/vision/visionappl/au/11.5.0/forms/us (the template for inherits some packages from the appstand.fmb)

3) Put the two fmb files into resource that you downloaded in the first step. (Not necessary)

4) Open regedit and add the path of resource into form60-path.

SECOND STEP: OPEN THE TEMPLATE FORM

Open form builder and open TEMPLATE form and do the following steps:

1) Delete the detail block if you don’t want a master detail relation.

2) Rename the block “blockname” block to the name of your data block you are intending to add.

3) Delete its fields and insert the fields of your block.

4) Change the canvas name to the name of your first block.

5) Change window name to the name of your first block.

6) Change the block name in the pre-form trigger

app_window.set_window_position('BLOCKNAME',

'FIRST_WINDOW');

7) change the app_custom package body, find the following statement

if (wnd = '<your first window>') then

change <your first window> to the first block name.

NOTE: if you want to add any new block you are free to add it manually.

Third STEP: SETTING ITEMS PROPERITES

In most cases your items must have standard properties, in order to make any item standard item do the following:

1. Open the item property palette.

2. Press the button beside the subclass information field.

3. Select the property class.

4. From the property class name select the proper type of your item.

Do the same above steps for all your items and finally save the form and exit.

NOTE: make sure that you don’t save on the same template form.

Adding a report to oracle application

1. create the report using report builder and from administration go to convert and do the following:

a) Determine the path of the source report(RDF)

2. determine the path of the destination report(RDF)

3. From option tab set the destination unit value to character.

2. open oracle application and go to system administrator responsibility

3. go to concurrent to program to executable and set the following:

1. executable: name of the original report(i.e. TST OM 002).

2. Short name: the same name above.

3. Application: the application you want to add your report to

(I.e. Order Management).

4. Execution Method: set it to Oracle Reports.( it will be set auto )

5. Execution file name: same as executable name(TST OM 002)

6. All remaining are optional. ( non colored fields is optional ) .

4. go to define and set the following:

1. program: the report name that will appear to the user.

2. Short name: the same name.

3. Application: order management.

4. Style: landscape.

5. Executable – name: TST OM 002

6. Executable – method: oracle reports.

Note: if your report has no parameters stop here.

5. push parameter button and set the following:

1. set parameter sequence number and name

2. value set: the set of accepted values of the parameter.

3. Token: the name of the parameter on the original report.

6. go to Security to responsibility to request and do the following:

1. Search for the application request groups (press F11 and put Order Management in the application field).

2. Select the OM REPORTS group.

3. Press new and select the program name and application.

7. switch responsibility to order management application and go to reports, Requests to run report to single request and do the following:

1. Select the report name.

2. Set the parameters if the report has.

3. Press submit.

8. The report will not work because he can’t find the rep file on the server.

9. Press VIEW-- LOG to see the error where you will find the path that your report should be.

10. Open FTP and copy the rep file to the location specified on the previous step.

11. Rerun the report it shall work now.

NOTE: from view press requests you will see the entire requests submitted.

NOTE: from help press record history which views the source view of a marked

field.

NOTE: from help press diagnosis then examine to see the query that generated the screen

Adding forms to existing module

FIRST STEP: GENERATING THE FMX

1) You need to have FTP software and a tool to connect to a server.

2) Add your form to au forms (i.e e1/vision/visionappl/au/forms/US/ORDER.fmb)

The AU directory contains all the FMB files for all the applications.

3) Go to the application top (i.e e1/vision/visionappl)

4) run the APPSVISION_(server name).env file

(i.e . APPSVISION_oracle-server.env where oracle-server is the server name)

5) Go to au/11.5.0/forms/US

6) Generate the form on the desired destination using f60gen

The following session generate the ORDER.fmb under ont (order management application)

$ cd /

$ cd e1

$ cd vision

$ cd visionappl

$ ls *.env

$ . APPSVISION_oracle-server.env

$ cd au

$ cd 11.5.0

$ cd forms

$ cd US

$ f60gen Userid=APPS/APPS Module=$AU_TOP/forms/US/XX_FDC_SETUP.fmb output_file

=/e1/vision/visionappl/ap/11.5.0/forms/US/

XX_FDC_SETUP.fmx module_type=FORM

batch=no compile_all=special

You shall see the following

. . . . .

Created form file /e1/vision/visionappl/ont/11.5.0/forms/US/ORDER_INFO.fmx

SECOND STEP: ADDING THE FORM TO ORACLE APPLICATION

1) Go to application developer responsibility.

2) Go to applications to form and do the following:

1. Set the form value to the form name without the extension.

2. Select the application name.

3. Set the user form name which will be the form name that will be used in the next steps. ( the text that will appear to the user ) .

4. Save and exit.

3) Go to application to function

1. In the description tab set the function name that will be used in the next steps.

2. Select the user form name that you determined in the previous step.

3. Go to form tab the function name you determined in a will appear set your function and application name.

4. Save and exit.

4) Go to application to menu

1. select the menu of the application you are intending to add the function to

2. Press add new button.

3. Set the sequence to any valid unique value.

4. Prompt will determine what will be the function name in the menu.

5. Because we are adding a function leave the submenu field empty and put the function name in the function field.

6. Make sure that grant checkbox is checked and save.

7. Pressing view tree button will allow you to make sure that the function was added to the correct place.

8. exit.

5) Next time you logon on the application you will see the form.

Note: if you don’t know the menu of your application do the following:

1) Switch to system admin responsibility

2) go to security to responsibility to define.

3) press F11 and set the application field to the name of the application you are intending to add your and press CTRL+F11 the menu name will appear in the menu name.

ADDING A NEW MODULE TO ORACLE APPLICATIONS

FIRST STEP: adding a folder for your new module

1. Make directory with the name of the new module you are intending to create under e1/vision/visionappl (i.e. XX_TEST). It’s recommended to prefix it with XX to avoid duplication with oracle modules for future. Inside the directory make a new directory and name it to the version number (i.e. 11.5.0).

2. Inside the version number directory add directories according oracle standard.

3. Inside form and reports directories add a directory for each language your system has.

SECOND STEP: ADDING THE CUSTOM APPLICATION ON UNIX

1) Go to the path where you created the file (i.e. /e1/vision/visionappl).

2) List the environment files.

The shell commands :

$ pwd

/export/home/vision

$ cd ../../..

$ pwd

/

$ cd e1

$ cd vision

$ cd visionappl

$ ls *.env

APPSORA.env VISION_oracle-server.env

APPSVISION_oracle-server.env VISION.env

3) open APPSVISION_oracle-server.env using the more command

$ more APPSVISION_oracle-server.env

:

# $Header: APPSORA_ux.env 115.5 2003/04/01 07:38:39 isikdar ship $

# =============================================================================

# NAME

# APPSORA.env

#

# DESCRIPTION

# Execute environment for Oracle and APPL_TOP

#

# NOTES

#

# HISTORY

#

# =============================================================================

# This file is automatically generated by AutoConfig. It will be read and

# overwritten. If you were instructed to edit this file, or if you are not

# able to use the settings created by AutoConfig, refer to Metalink document

# 165195.1 for assistance.

#

# ###############################################################

#

# Source the custom file if it exists

customfile=/e1/vision/visionappl/customVISION_oracle-server.env

if [ -f $customfile ]; then

. /e1/vision/visionappl/customVISION_oracle-server.env

fi

. /e1/vision/visionora/8.0.6/VISION_oracle-server.env

. /e1/vision/visionappl/VISION_oracle-server.env

4) Create the file mentioned above in red

$ vi customVISION_oracle-server.env

5) Add the following

OM_TEST_TOP="/e1/vision/visionappl/OM_TEST/11.5.0"

export OM_TEST_TOP

Assuming our new module name is OM_TEST.

6) Press (:) and (wq!) To save the file and go back to the shell prompt.

7) to make sure that the environment file was created list the environment files

again the customVISION_oracle-server.env shall appear.

8) run the APPSVISION_oracle-server.env file using the following command:

$ . APPSVISION_oracle-server.env

THIRD STEP: RESTARTING THE ORACLE SERVER

In order for the oracle application to see your new application you shall restart the server to do so follow these steps:

1) go to ‘e1/vision/visioncomn/admin/scripts/ VISION_oracle-server/

2) run adstpall.sh

Using the command $ adstpall.sh apps/apps

3) run adstrtal.sh

Using the command $ adstrtall.sh apps/apps

Fourth step: adding the new module on the oracle applications

1) Go to system administrator responsibility.

2) Go to application to register and set the following:

1. application: the name you want for your application

2. short name: the directory name (i.e. OM_TEST)

3. Base path: the variable name we defined in the

customVISION_oracle-server.env files (i.e. OM_TEST_TOP)

3) Go to security to oracle to data group and do the following:

1. Set the data group field to standard.

2. Add the application to the data group.

4) Go to oracle to register and set the following:

1. Database user name: the user name of the database you created.

2. Password: the password of the database you created.

3. Save and exit.

HINT: don’t use apps/apps because it just store a reference to other applications Schemas

ADDING A RESPONSIBILITY

• Adding a responsibility

When you create a new module you shall grant privilege to users to do so you shall do the following:

1) Define a responsibility on the new module menu.

To define a responsibility on the menu switch to system administrator responsibility, then go to security to responsibility to define and set the following:

a) responsibility name: any name

b) application: set the application name you are intending to add

the responsibility name.

c) responsibility key: same as responsibility name.

d) menu: select the menu name.

e) data group: standard.

2) Grant the responsibility to users

Go to security to define and do the following:

1. Search for the user F11 name CTRL+F11 if you are trying to add the responsibility to an existing user or enter the user name directly if you want to assign the responsibility to existing user.

2. Go to direct responsibilities tab and add the responsibility

3. Save and exit.

Technical Notes

Flex fields

Flexfield is a set of segments each segment holds a value of varchar2, the flexfield is used to avoid the need to change the oracle applications source forms if you want to add additional fields to your form, you define the flexfield in the database as a row in a table called combination table which have the following description (Unique ID, structure id, segments(from segment1 to segment n)).

ID	STRUCTRE ID	Seg1	Seg2	Seg3	……	segn

Form triggers

Some of the main forms triggers

Post login, when check box changed, when image pressed, when list activated, when radio changed, when tab page changed, when window closed, when window resized.

Report builder

In the report builder each group represent a database table.

Reports types according to the groups the report holds:

1. Tabular in the tabular report the report consist of one group the report just list some or all the report fields

Employee number employee name employee salary

. . .

. . .

. . .

2) Master detailed in master detailed report the report consist of two groups one is the

Master and the other is the detailed.

Department number ….

Employee number employee name employee salary

. . .

. . .

. . .

3. Matrix two masters and one detailed

Customer …

Product … ……. …….

3. form like report in this report each record appears on different page.

Reports types according to how report appears

1. group left

Master …….

…….

…….

2. group above

Master

………

………

………

3. tabular the same as above.

Notes

• in the data model if you want to create a master-detail relationship between two group make a data link from the master group to the detailed group or you may get all the master and detailed fields on one group and then drag all the master group fields in a new group above

• In the layout model if you want to create a master-detail relationship between two group draw a repeating variable frame for the master group then inside the frame draw another repeating variable frame for the detailed group.

• Conditional formatting allow you to set some fields properties according to some conditional statement.

• Object elasticity:

1. fixed keep field on original size.

2. Expand >=original size.

3. Contract <= original size.

4. Variable < or = or > original size.