Use the Lookups window or page 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.
The following describes the Lookups window.
The Lookups block contains the following fields:
Enter the type of your Lookup. You can define a maximum of 250 Lookups for a single type.
The user name is used by loader programs.
Enter the application associated with your Lookup type.
If you use windows specialized for a particular Lookup type, the window uses this description in the window title.
The access level restricts changes that are possible to a lookup type. The possible levels are:
System - No changes to the lookup codes are allowed.
Extensible - New lookup codes can be added. However, you cannot modify seeded lookup codes.
User - You can change any lookup code.
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.
If you would like to query records by a code attribute, such as the Enabled check box, then do the following:
Query the lookup type.
Move the cursor to any field in the lower region on the window.
From the View menu, select Query By Example, Enter.
Enter your query criteria.
From the View Menu, select Query By Example, Run.
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.
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.
You can display the description along with the meaning to give more information about your Lookup.
Optionally enter in a tag to describe your lookup. The tag can be used to categorize lookup values.
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.
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.
The Lookups page is available from the seeded Functional Administrator responsibility, Core Services tab.
The user name is used by loader programs.
A code for the lookup. You can define a maximum of 250 Lookups for a single code type. Note that this field cannot be updated once your record is saved.
If you use windows specialized for a particular Lookup type, the window uses this description in the window title.
Enter the application associated with your Lookup type.
The access level restricts changes that are possible to a lookup type. The possible levels are:
System - No changes to the lookup codes are allowed.
Extensible - New lookup codes can be added. However, you cannot modify seeded lookup codes.
User - You can change any lookup code.
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.
The following are fields for each lookup 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.
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.
You can display the description along with the meaning to give more information about your Lookup.
Optionally enter in a tag to describe your lookup. The tag can be used to categorize lookup values.
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.
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.
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.
Before using this window to specify your table information, do the following:
Register your application using adsplice. See: AD Splicer, Oracle E-Business Suite Setup Guide and My Oracle Support Knowledge Document 1577707.1, "Creating a Custom Application in Oracle E-Business Suite Release 12.2."
Create your table in the database.
The following fields are shown.
End users see this title when they review audit results. The default for this field is the value in the Table Name field.
This field records hosting-related metadata to be used by deployment utilities and as general documentation.
Valid types are:
Interim - Table is used only temporarily.
Seed Data - Table stores primarily setup data.
Special Flexfield Data - Table is used by flexfields.
Transaction Data - Table stores primarily transaction data.
The initial and next extent sizes in kilobytes for your table. Values must be greater than 0.
A value between 1 and 100 per cent. A Percent Free value must exist such that the sum of the Percent Used field and the Percent Free field is between 1 and 100.
A value of 1 extent or more for the minimum extents value. The maximum extents value must be greater or equal to the minimum extents value. A low value for maximum extents helps prevent fragmentation of your database table.
Indicates whether the table should be larger or smaller for different customers. 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.
Choose a button to open a detail window where you supply more information about your table. The detail windows are: Indexes, Primary Keys, or Foreign Keys.
Indexes - Choose this button to open the Indexes window with the following information for each application index: name, purpose, and default parameters.
Primary Keys - Choose this button to open the Primary Keys window where you specify your primary keys.
Foreign Keys - Choose this button to open the Foreign Keys window for foreign keys.
The following fields are shown:
The order of the column in the table. For example, the first column in the table can have Sequence=1.
End users see this title when they review audit results. The default for this field is the value in the Column Name field.
Valid types are:
Character
Date
Long
Long Raw
MLS Label
Number
Raw
Raw MLS Label
Row ID
Varchar
Varchar2
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.
You cannot enter this field if your column is one of the following types: Date, LONG, LONG RAW,, MLS Label, Raw, Raw MLS Label, or ROWID.
Different values apply depending on the column type. For type Character, the value must be between 1 and 256. For type Number, a value must be between 1 and 40. For type RAW, a value must be between 1 and 256. The values cannot be changed 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.
The length of numbers past the decimal point at which you want to calculate the number for this field. This field is applicable only if your column is type Number. This value must be between 1 and 40. For all other column types, the value is NULL.
The scale of the column. This field is applicable only if your column is type Number. This value must be between -40 and 40. For all other column types, the value is NULL.
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 generate the ODF file, the expression is not evaluated. The ODF Comparison Utility will just use whatever value is specified 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
Indicates whether the values in this database column can be translated. This field is applicable 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.
The name of the database index and indicate whether the index is unique.
The initial and next extent sizes in kilobytes for your table. Values must be greater than 0.
The percent free value for your table. This value must be between 1 and 100 per cent.
The initial number of transaction entries that are allocated within each block. This value must be between 1 and 255.
The maximum number of transactions that may update a data block concurrently. This value must be between 1 and 255.
Indicates whether the index should be larger or smaller for different customers. In general, seed data tables should have AutoSize unchecked.
The following fields are shown.
Valid types are Developer and Alternate. Only one Developer primary key is allowed per table.
Sequence - The order of the column in the primary key. The default value for this field is 1 or the last highest sequence number for this primary key.
Name - You can pick any column in your table that has type Number, Character or Date. You cannot choose a column of any other type, such as LONG or LONG RAW.
The foreign keys for your table. Conditional foreign keys can be defined by specifying a WHERE clause condition for the foreign key reference.
This field supports functionality to be implemented in a future release.
The type of cascade delete behavior for this foreign key. The value of this field specifies 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.
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.
If the specified foreign key is conditional, this field shows 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.
Application - The application name that owns the primary key table to which your foreign key points.
Table - The primary key table.
Name - The name of the primary key in the primary key table to which your foreign key points.
The Cascade Value field supports functionality to be implemented in a future release. This field applies only if your foreign key's behavior is Update.
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:
Define your application with Oracle E-Business Suite.
Create or alter your sequence in the database.
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.
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.
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.
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.
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.
Check if you want the sequence to generate additional numbers when the end of the sequence is reached. Otherwise, leave the check box off.
Check if you want the sequence to generate numbers in order of request. Otherwise leave the check box off.
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:
Define your application with Oracle E-Business Suite.
Create or alter your view in the database.
Enter your view's name and the application to which it belongs.
Specify the columns in your application view.