The Search and Select window is called from many screens in Oracle LSH. It receives its context from the calling screen. For example, if you click the Search icon in the Create Program screen, the Search and Select function finds only Program definitions. Enter values in the following fields:
1. Domain. From the drop-down list, select the name of the Domain that contains the definition you need.
If the Domain you specified contains one or more child Domains, you can see the child domain in the Domain drop-down list with the name of all parent domains preceding it and separated by a right angle bracket (>). For example:
Domain 1 > Child Domain 1 > Child Domain 2 > Child Domain 3
The system populates the Application Area drop-down list with the names of Application Areas contained in that Domain.
2. Application Area. If the definition is contained directly in a Domain library, do not select an Application Area.
If the definition is contained in an Application Area, select the Application Area from the drop-down list.
3. Search By. If you know the name or version label of the object, select either Name or Version Label from the Search By drop-down list and enter either the name or version label in the field to the right. You can use special characters such as the % wildcard. For example, if you enter Study_12345% as a name, the system retrieves all objects whose name begins with Study_12345.
4. Display All Versions If checked, the system returns all versions of the object with the name you specified in the Search By field. If unchecked, the system returns only the latest version. (If you specified Version Label in the Search By field, the system returns only the version with that label.)
5. Display Not Null Version Labels If checked, the system returns only object versions with a version label. This checkbox is relevant only if Name is selected in the Search By field above.
6. Click Go. The system displays the results of the search, including, for each definition retrieved, its name, version number, version label (if any), validation status, the username of the person who created the definition, and the date on which it was created. The system retrieves object definitions only if they are currently checked in.
Note: For some object types this field is case-sensitive. If an object's name begins with STUDY_12345 and you enter Study_12345% the system does not retrieve the object because its name is not in uppercase.
Notes: You can set your Preferences to make the system return only definitions with a validation status of Production.
You cannot create a new object instance based on a definition whose validation status is set to Retired.
Creating and Reusing Objects
7. Select the definition you want by clicking the icon in the Quick Select column, or by clicking its radio button and then clicking the Select button. The system returns you to the screen you came from with the name of the object you selected entered.
Creating a New Definition and Instance
If no object definition exists that suits your needs, or that you can modify to suit your needs, you must create a new one.
When you create a new definition and instance at the same time, the system
simultaneously creates the definition in the current Application Area and an instance of it in the current Work Area. As you save your work, the system applies your changes to the appropriate object—definition or instance. The system applies the name and description you enter to both the definition and instance unless there is a conflict with either one; see "Naming Objects" on page 3-6.
Figure 3–2 shows the process of creating a new Program definition and instance. The process is similar for all object types. You first create the object as a whole, classify both the definition and the instance, then define component objects: in the case of Programs these include Table Descriptors, Source Code, Parameters, and Planned Outputs. All executable instances require mapping Table Descriptors to Table instances and defining at least one Execution Setup. You must install all object instances in their Work Area, assign user groups for object security and validate the definition and the instance according to your company's policies.
Figure 3–2 Creating a New Program Definition and Instance
Specific instructions for each object type are included in the section on each type: ■ Creating a New Table Definition and Instance on page 4-4; includes instructions
for creating an Oracle LSH Table from a SAS data set
■ Creating a New Program Definition and Instance on page 5-4 ■ Creating a New Load Set Definition and Instance on page 7-5 ■ Creating a New Report Set Definition and Instance on page 9-10 ■ Creating a New Data Mart Definition and Instance on page 8-3 ■ Creating a New Workflow Definition and Instance on page 10-3 ■ Creating a New Business Area Definition and Instance on page 11-3 There are also instructions for creating the following component objects: ■ Defining Parameters on page 6-6
■ Defining and Mapping Table Descriptors on page 3-36 ■ Defining Source Code on page 5-9
■ Defining Table Columns on page 4-10 ■ Defining Variables on page 6-2
Naming Objects