Skip Headers

Oracle E-Business Suite Developer's Guide
Release 12.1
Part Number E12897-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Additional Features

Application Utilities Lookups and Oracle Application Object Library Lookups

Use the Lookups window to maintain existing Lookups and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No.

If you make changes to a Lookup, users must log out then log back on before your changes take effect.

Lookups Block

The Lookups block contains the following fields:

Type

Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type.

User Name

The user name is used by loader programs.

Application

Query the application associated with your Lookup type.

Description

If you use windows specialized for a particular Lookup type, the window uses this description in the window title.

Access Level

The access level restricts changes that are possible to a lookup type. The possible levels are:

Note: If there is a lookup type with an access level of SYSTEM and this lookup type is seeded by Oracle, then users can not add new lookup values to this lookup type.

If the lookup type is not seeded, that is, created by a user, then the user who created the data can add new lookup values but these lookup values cannot be deleted.

Security Group

This field is for HRMS security only. Refer to the HRMS implementation documentation for more information.

Only the security group of the current form session can be maintained using this form. Standard is the standard default security group. Custom indicates this lookup type is for a custom security group.

All global and cross-security group maintenance is done using the Generic Loader with the Lookups configuration file.

Lookups Values Block

If you would like to query records by a code attribute, such as the Enabled check box, then do the following:

  1. Query the lookup type.

  2. Move the cursor to any field in the lower region on the window.

  3. From the View menu, select Query By Example, Enter.

  4. Enter your query criteria.

  5. From the View Menu, select Query By Example, Run.

Code

Enter the code value for your Lookup. You can define a maximum of 250 Lookups for a single Lookup type. When you enter a valid Lookup meaning into a displayed window field, Lookups stores this code into a corresponding hidden field. For example, the Lookup "Y" displays the meaning "Yes" but stores the code value "Y" in a hidden field.

You cannot change the values in this field after committing them. To remove an obsolete Lookup you can either disable the code, enter an end date, or change the meaning and description to match a replacement code.

Meaning

When you enter a valid Lookup meaning into a displayed window field, Lookups stores the corresponding code into a hidden field. Lookups automatically displays the meaning in your Lookups field whenever you query your window. For example, the Lookup "Y" displays the meaning "Yes" but stores the code value "Y" in a hidden field.

Description

You can display the description along with the meaning to give more information about your Lookup.

Tag

Optionally enter in a tag to describe your lookup. The tag can be used to categorize lookup values.

Effective Dates

Enter the dates between which this Lookup becomes active. If you do not enter a start date, your Lookup is valid immediately.

Once a Lookup expires, users cannot insert additional records using the Lookup, but can query records that already use the Lookup. If you do not enter an end date, your Lookup is valid indefinitely.

Enabled

Indicate whether applications can use your Lookup. If you enter No, users cannot insert additional records using your Lookup, but can query records that already use this Lookup.

[ ]

The double brackets ([ ]) identify a descriptive flexfield that you can use to add data fields to this window without programming.

Tables

Identify your application tables and primary key information to Application Object Library. You should specify your primary keys before auditing your application. If you do not specify your primary keys, AuditTrail does not store primary key information. You can also use this window to register minor changes to your tables.

Before using this window to specify your table information, do the following:

Tables Block

Enter the following fields.

User Table Name

End users see this title when they review audit results. The default for this field is the value in the Table Name field.

Type

Valid types are:

Initial Extent/Next Extent

Enter the initial and next extent sizes in kilobytes for your table. You must enter values greater than 0.

% Free/ % Used

You must enter a value between 1 and 100 per cent. You must enter a Percent Free value such that the sum of the Percent Used field and the Percent Free field is between 1 and 100.

Min Extents/ Max Extents

Enter a value of 1 extent or more for the minimum extents value. Enter a maximum extents value that is greater or equal to the minimum extents value. You enter a low value for maximum extents to prevent fragmentation of your database table.

Auto Size

Indicate whether the table should be larger or smaller for different customer. If the Auto Size button is not checked, the table should have the same size for all customers. In general, seed data tables should have AutoSize = No.

Detail Buttons

Choose a button to open a detail window where you supply more information about your table. Choose the detail window which you want to update: Indexes, Primary Keys, or Foreign Keys.

Table Columns Block

Enter the following fields.

Seq

Enter the order of the column in the table. For example, the first column in the table can have Sequence=1.

User Column Name

End users see this title when they review audit results. The default for this field is the value in the Column Name field.

Column Type

Valid types are:

If the column name contains "ID" or "NUM", the default value for this field is Number. If the column name contains "DATE", the default value for this field is Date. Otherwise, the default value for this field is Varchar2.

Width

You cannot enter this field if your column is Type Date, Long, Long Raw, MLS Label, Raw, Raw MLS Label, or Rowid.

You can enter different values depending on the column type. For type Character, you must enter a value between 1 and 256. For type Number, you must enter a value between 1 and 40. For type Raw, you must enter a value between 1 and 256. You cannot change the value for types Date, Long and Long Raw.

The default for this field is 30 for Types Character, Varchar, and Varchar2; 7 for Type Date; 22 for Type Number; 240 for Type Raw; and 0 for Types Long, Long Raw, Row ID, MLS Label, and Raw MLS Label. You cannot enter 0 for any other type.

This field corresponds exactly to the LENGTH column in the ORACLE data dictionary.

Precision

Enter the length of numbers past the decimal point at which you want to calculate the number for this field. This field is enabled only if your column is type Number. You must enter a value between 1 and 40. For all other column types, the value is NULL.

Scale

Enter the scale of the column. You can only enter this field only if your column is type Number. You must enter a value between -40 and 40. For all other column types, the value is NULL.

Default Value

Enter the value which the ODF Comparison Utility should use before altering the column to NOT NULL. The ODF Comparison Utility makes a statement like:

update t set c = <expression you enter here>;

The default is 0 is Type is Number, 'N' if Type is Character, and sysdate if Type is Date.

This value is usually a constant; you can also use an expression. When you enter the value in the form, or when you generate the ODF file, the expression is not evaluated. The ODF Comparison Utility will just use whatever value you supply here, and evaluate it at the customer site.

So for dates, if you do not use sysdate, you should include todate:

todate('01-03-2007','MM-DD-YYYY') not 01-03-2007 

And for strings, you have to include quotes:

'ABC' not ABC

Translate

Indicate whether the values in this database column can be translated. You can enter this field only if this column is defined as type Character, Varchar, or Varchar2. You should not identify a column as translatable if it is either a primary key or a DataMerge key.

Indexes Window

Enter the name of the database index and indicate whether the index is unique.

Initial Extent/ Next Extent

Enter the initial and next extent sizes in kilobytes for your table. You must enter values greater than 0.

% Free

Enter the percent free value for your table. You must enter a value between 1 and 100 per cent.

Initial Transactions

Enter the initial number of transaction entries that are allocated within each block. You must enter a value between 1 and 255.

Max Transactions

Enter the maximum number of transactions that may update a data block concurrently. You must enter a value between 1 and 255.

AutoSize

Indicate whether the index should be larger or smaller for different customers. In general, seed data tables should have AutoSize unchecked.

Primary Keys Window

Enter the following fields.

Type

Valid types are Developer and Alternate. You can define only one Developer primary key per table.

Primary Key Columns

Foreign Keys Window

Define the foreign keys for your table. You can define conditional foreign keys by specifying a WHERE clause condition for the foreign key reference.

Cascade Behavior

This field supports functionality to be implemented in a future release.

Choose the type of cascade delete behavior for this foreign key. You use this field to specify what to do to a foreign key table when you delete rows from the primary key table. Valid types are Delete, Update, Check Parent and None.

Delete means that you delete rows in the foreign key table when you delete rows in the primary key table.

Update means that you update rows in the foreign key table using Cascade Values in the next zone whenever you delete rows in the primary key table.

Check Parent means that you do not delete rows in the primary key table if there are rows in the foreign key table that still reference the rows in the primary key table.

None means that you can delete rows in the primary key table without consideration for rows in the foreign key table.

Foreign Key Relation

Enter the type of foreign key relationship between the foreign key table and the primary key table. Valid types are Tight and Loose. DataMerge assumes that if a table has multiple "parent" tables, that only one of them is Tight and the others are Loose.

The default value for this field is Tight.

Condition

If you are entering a conditional foreign key, enter the WHERE clause for the condition. You can use the "&table" token in your WHERE clause to identify the current table. Applications DBA automatically replaces the "&table" token in SQL statements with the actual name of your table when it generates SQL statements that use conditional foreign keys.

Primary Key

Foreign Key Columns

The Cascade Value field supports functionality to be implemented in a future release. You can only enter a value in this field if your foreign key's behavior is Update.

Sequences

Identify an application sequence to Oracle E-Business Suite. You can also use this window to register changes to your sequences.

Before specifying your application view, do the following:

Start With

Enter the first number that this sequence should generate. The value in this field must always be between the Minimum Value and Maximum Value inclusive.

Increment

Enter the interval between sequence numbers. The increment can be positive or negative. If you enter a negative value, the sequence descends. You cannot enter a value of zero.

Minimum

Enter the minimum value this sequence can generate. This value is the lower bound for the sequence. You must enter a Minimum Value that is less than the Maximum Value.

Maximum

Enter the maximum value the sequence can generate. This value is the upper bound for the sequence. You must enter a Maximum Value that is greater than the Minimum Value.

The default value is 2,147,483,647.

Cache Size

Enter the number of sequence numbers to cache in memory, resulting in faster generation of sequence numbers.

You must enter a value greater than or equal to 0.

The default value is 5.

Cycle

Check if you want the sequence to generate additional numbers when the end of the sequence is reached. Otherwise, leave the check box off.

Guarantee Order

Check if you want the sequence to generate numbers in order of request. Otherwise leave the check box off.

Views

Identify an application view with Oracle E-Business Suite. You can also use this window to register changes to your view.

Before specifying your application view, do the following:

Views Block

Enter your view's name and the application to which it belongs.

Columns Block

Specify the columns in your application view.

Flexfields Test Form

This form is used to test the implementation of flexfield definitions with the help of your Oracle support representative.

Warning: Use this form only if your Oracle support representative has asked you to. This form is for diagnostic purposes only. Do not modify any data using this form. Oracle does not support modifications to data using this form.