Application Object Library

Overview and Definition of Concurrent Processing

Concepts of Registration of Custom Application in Oracle; Registering-
-Forms.
-Functions.
-Menus.

Defining the Concurrent Programs

-Defining Executables. -Types of Executables.
-Defining Value sets. -Types of Value Sets.

-Defining Parameters.
-Defining Request Set.

Characterstics of Concurrent programs:
-Long Running.
-Data Intensive tasks.
-Basic Application Development Needs
-Consistent Response time.
-Helpful to end users.
-Hardware Utilization.

Responsibility

Defines the privileges granted to the application user for Application.
Privileges -

- The functions that the user may access. Functions are determined by the menu assigned to the responsibility.
- The concurrent programs, such as reports, that the user may run.
- The application database accounts that forms, concurrent programs, and reports connect to
User

Forms

- Consists of program logic.
- Has its own existence.
- Can be navigated as it appears in Navigation window.
- As a whole can be designated as Function.
- Sub Functions.
- Content within a form, Cannot be navigated, Does not appear in the navigation window, and are called by PL / SQL units of the form.


Menus

- Hierarchical arrangement of functions and menus of functions.
- Each responsibility has a menu assigned to it.
- Compile Security.
- Menu compilation is necessary when a change is made to a menu.
- FNDSCMPI Concurrent Program.
- Function Security - Function security is the mechanism by which user access to applications functionality is controlled.


Executable An user given name. This name is to assigned to the concurrent program for association.
Short Name - Also an user assigned name.
Application - Enables the concurrent managers to find the execution file in the concerned directory structure.
Execution Method- Specify the method that concurrent managers adopt for the execution of a concurrent program. It can not be changed once assigned to a Concurrent Program and can be adhered with multiple Concurrent Programs.
Execution File Name - The name of the executable file in the local system or UNIX system.
Subroutine Name - The name of the pro* C or C Program.

Stage Function Parameters-
Host
Oracle Reports
PL/SQL Stored Procedure
Java Stored Procedure
Java Concurrent Program
Multi Language Function
SQL*Loader
SQL*Plus
Spawned
Immediate
Request Set Stage Function.

1) Enter the name of your value set. [Generally unique ]
2) Give a description.
3) Enter the list type.
-Pop list – Values ranging between 1-10.
-List of values – Values ranging from 1 – 200.
-Long list of values – Values > 200.
4)Enter the type of security you want.
5) Enter the type of format you want to use for your segment values. Valid choices include: Char, Date, Date-Time, Number, Standard Date, Standard Date-Time, and Time.
Formatting information specifies the format type, including information (include numbers only / within a certain range).


Types of Value sets

Validation type:

Independent,

Dependent,

Table,

None (non–validated),

Special, Pair,

Translatable Independent, or

Translatable Dependent.

[If Dependent, Translatable Dependent, Table, Special or Pair value set, choose the Edit Information button to open the appropriate window. ]


Program - Name in the Submit Requests window
Short Name - Name that Oracle Applications can use to associate the concurrent program with a concurrent program executable.
Application - The program’s application determines what ORACLE username your program runs in and where to place the log and output files.
Enabled - Indicate whether users should be able to submit requests to run this program and the concurrent managers should be able to run your program.
Executable - You can define multiple concurrent programs using the same concurrent program executable.
Options - Oracle Reports, support additional execution options or parameters. You can control the dimensions of the generated output with the
Method - The execution method of your concurrent program uses appears here.
Priority - The priority of program the user’s profile option Concurrent: Priority sets the request’s priority at submission time.
MLS Function - The MLS function, if any, used by the program. The Multilingual Concurrent Request feature allows a user to submit a request once to be run multiple times, each time in a different language.
Use in SRS - Indicates that users can submit a request to run this program from a Standard Request Submission window.
Allow Disabled Values - If you check the Use in SRS box, you can also check this box to allow a user to enter disabled or outdated values as parameter values.
Run Alone - Indicates whether the program should run alone relative to all other programs in the same logical database. You can enter any specific incompatible programs in the Incompatible Programs windows.
Enable Trace - Turns on SQL tracing when program runs.
Restart on System Failure - Indicates that this concurrent program should automatically be restarted when the concurrent manager is restored after a system failure.
NLS Compliant - This box is checked if the program allows for a user to submit a request of this program that will reflect a language and territory that are different from the language and territory that the users are operating in.
Format – Indicates the output format which can be HTML, PCL (HP’s Printer Control Language), PDF, PS (Post Script), Text.
Save - Indicate whether to automatically save the output from this program to an operating system file when it is run.
Print - Enter Yes or No to indicate whether to allow the concurrent managers to print.

Columns / Rows - Enter the minimum column and row length for this program’s report output.
Style - The print style you select depends on your system and printer setup. Landscape, Land wide, Portrait, A4.
Style Required - Specific print style
Printer - Restrict the program’s output to a single printer.

Parameters

Program parameters defined here should match the variables in the execution file.
Conflicts Domain Parameter - Enter the parameter which will hold the value of the conflict domain of the program.
Security Group - This field is for HRMS security only.
Sequence - Choose the sequence numbers that specify the order in which your program receives parameter values from the concurrent manager.
Parameter - Enter the parameter name. The value is case insensitive.
Enabled - Disabled parameters do not display at request submission time and are not passed to your execution file.
Value Set - Name of the value set you want your parameter to use for validation.
Default Type – Used to set a default value for the parameter. Valid types can be any literal value, current value in the user profile option.
Constant
Profile
Segment
SQL Statement
Default Value - Enter a default value for the parameter which automatically appears in parameter window. The default value can be a constant or a context–dependent value by choosing the default type. The default value should be a valid value for your value set.
Required – Mandatory for the concurrent program
Enable Security – To apply security rules
Display - Indicate whether to display this parameter in the Parameters window when a user submits a request to run the program from the Submit Requests window.
Display Size - Enter the field length in characters for this parameter.
Description Size - Enter the display length in characters for the parameter value description.
Prompt - A user sees the prompt instead of the parameter name in the Parameters window of the Submit Requests window.
Concatenated Description Size - Enter the display length in characters for the parameter value description.
Token - For a parameter in an Oracle Reports program, the keyword or parameter appears here. The value is case insensitive.


Request Sets

A request set is a collection of reports and/or programs that are grouped together allowing a user to submit several requests together using multiple execution paths.

Sets, Stages, and Requests –

A stage is a component of a request set used to group requests within the set containing one or more concurrent requests which execute in parallel at a time. Only one stage is executed at a time followed by further stages after completion of previous stage with particular linkages which depend upon the completion statuses of the individual stages.

The Standard Stage Evaluation Function takes care of the requests of the sets while calculating the completion status. Computes the stage completion status from the completion statuses of the specified requests in the set.

Returns a Success if all the requests in the stage have completed without any error.
Returns a error if one or more requests have completed with an error.
Returns a warning if one or more requests have completed with a warning message.

Request Set Completion Status
A request set exists when a stage completes for which no link has been defined.
Its completion status is the completion status of the previous stage executed by default.

Flexfields

A flex field is a field made up of sub–fields, or segments.
There are two types of flex fields:
Key Flexfields: A key flex field appears on your form as a normal text field with an appropriate prompt.
Descriptive Flexfields: A descriptive flex field appears on your form as a two–character–wide text field with square brackets [ ] as its prompt.

When opened, both types of flex field appear as a pop–up window that contains a separate field and prompt for each segment. Each segment has a name and a set of valid values. The values may also have value descriptions.

Profiles

Profiles are options that will determine how the application will behave. The changes will be effective when signing on the application or switching responsibility.
(N) System Administrator -> Profile -> System
Select the level
Site,
Applications,
Responsibility,
User.
Enter the complete profile option name, or partial name enclosed by percent sign (%)in the "Profile" field. For example, "%Supply%", then click on "Find" button.
Select a value from the list of values for "Site", "Applications", "Responsibility", or "User".
Save.

Profile Levels:
Site Level: This option impacts all users.
Application Level: This option affects all users within an application. This level overrides Site level.
Responsibility Level: This option impacts all users under a particular responsibility. This level overrides Site and Application level.
User Level: This option determines how the application will behave to a particular user. This level overrides all levels.