Creating and Editing Data Set Definition
This section describes how to:
Search for and create data sets.
Manually define a data set.
Generate a data set from a component.
Searching For and Creating Data Sets
Use the Data Set Designer search page (PTADSDEFNSEARCH) to search for, add, generate, or delete a data set.
Image: Data Set Designer Search page
This example illustrates the fields and controls on the Data Set Designer Search page. You can find definitions for the fields and controls later on this page.
The Data Set Search page has three tabs Search, Add and Generate.
Search is the default action for Data Set Designer. Users can search for existing data sets and open an existing data set for modification. Users can also delete one or more data sets from the search result set.
You can search for an existing data set using:
Data Set Name
Basic and advance search is provided so users can search based on one or multiple search keys. The search result produces a grid. Users can select one or multiple data sets in the grid to delete. Users can open the data set for modification using the link for the data set name.
Image: Data Set Search Results
This example illustrates the fields and controls on the Data Set Search Results.
Create New Data Set
Select the Add tab to create a new data set.
Enter a Data Set Name and a description for the new data set. Data Set Name and Description are mandatory fields. When you click the Add button, the identity page is displayed.
Generate is used to create a new data set implicitly from a component.
Manually Defining the Data Set
Use the Identity page (PSADSDEFNPAGE) to identify the top-level properties of the data set.
Image: Identity page
This example illustrates the fields and controls on the Identity page. You can find definitions for the fields and controls later on this page.
- Data Set Name
Uniquely identifies the data set definition. Each data set definition describes a distinct shape, and there can be many instances of that type.
A description of the data set instance. Instances are distinguished by having distinct bindings.
- Long Description
A long description providing additional information such as guidance, limitations or cautions regarding this data set.
- Owner ID
Identifies the product that will own the data set definition and content.
- Is Copyable
Selecting this check box indicates that the data included in the data set definition is suitable for copy from one database to another. Data is suitable for copy only if doing so will produce a valid object on the target and not corrupt any other data on the target. This field is only editable if Allow setting Copy Compare attributes on ADS definitions is selected for the users Data Migration security profile.
- Derivation Type
This indicates if the data set definition was created manually or generated from a component using the Generate tab on the Data Set Search page.
- Add Record to Root
Select the parent record, which will become the root record and is placed in the Record Hierarchy section.
This section shows the record hierarchy for the data set. Use the Insert Record icon to add additional child records.
There is at least one row for every record in the data set definition. Related language tables are automatically added by the system and should not be deleted.
Note: If you delete a related language record, you can not add it back. You will need to delete the parent of the related language record and add the parent back.
Use the Insert Record icon to build the record hierarchy.
Image: Icon to insert record
Icon to insert record
When you insert records, the list will be restricted to records that include all keys (and possibly additional keys) of the corresponding parent record and have not already been selected for the current parent record name.
When you select the Insert Record icon, a child record insertion dialog will open with child record lookup. A child record is a record having the same keys as parent record. The child record may also contain additional keys. The lookup shows only those records which qualify to be the child record of the original record.
In record hierarchy, the related language record plays a significant role. When a record added to a data set definition (either as root record or as a child record) has a related language record, it is implicitly included in the data set as a child record.
- Show Key(s)
When a user adds records to the data set, the keys are pre-populated from the keys of the root record. Up to 14 keys can be specified in a data set. The keys of the data set will be the same as the keys of the root record. When you select the data content in the Project Designer, these keys must be explicitly bound to one or more values. Clicking the Show Keys button brings up a modal dialog that shows the key fields.
Note: All records in the data set definition must have at least these selected keys
Image: Data Set Key Map page
This example illustrates the fields and controls on the Data Set Key Map page. You can find definitions for the fields and controls later on this page.
The records in data set definitions have the following restrictions:
Application Data Set definitions containing views or derived records are not copyable or comparable – they can be used only for documentation purposes.
The 8.53 data set designer allows a record to appear only once in the record hierarchy, whether the data set was manually created or generated from components.
All records in a data set must have unique keys as defined in the key view of the record in Application Designer.
The keys of the parent record must also be keys of the child record, though a child record may have some keys that are not in the parent record.
The keys of the child record should be in the same order as the parent record keys.
There is a limit of 32 records in a data set definition in 8.53.
The root record cannot be deleted from the data set hierarchy.
Generating Data Set From a Component
Use the Generate page (PTADSDEFNSEARCH_GC) to generate a data set implicitly from a PeopleSoft component structure.
Image: Generate Data Set from Component page
This example illustrates the fields and controls on the Generate Data Set from Component page. You can find definitions for the fields and controls later on this page.
The component look up allows the user to select an existing component to generate the data set definition.
Market look up allows user to select a particular market for that component.
- Data Set Name
The data set name is generated based on the component. The data set name is the component and market prefixed with COMP_.
Enter a description for the data set.
When you click the Generate button, the Data Set Identity page is displayed, with the following:
Record hierarchy tree is generated according to the record level of the component.
Derivation type is Loaded from Component.
You can make any necessary modifications to the data set and then save it.
Note: Only the physical records in a component will become part of the data set definition. It is the responsibility of the user to verify that the generated data set definition reliably copies data.