Data Selection and Data Sequencing

Data selection and data sequencing values are stored in JD Edwards EnterpriseOne Report Design Aid (RDA) specification (RDASPEC) files, which can exist on the client as well as on the server. In Terminal Server environments, multiple users share the same set of client RDASPEC files, so changes made to the specifications by one user are immediately visible to all other users of the same terminal server.

When you submit a batch version, you can modify the data selection and data sequencing from the Version Prompting form. Any modifications that you make to the batch version from this form affect the current submission only. Values that you enter during submission are used for processing, but are not saved and are not seen during the next report submission. If no prompting occurs, the values that exist locally at submission time are used by the system during processing. Values that you enter in Version List or in RDA are saved in the RDASPEC files.

This table provides some data selection and data sequencing scenarios:

Scenario	Description
Batch versions submitted locally from the Microsoft Windows client.	You might be prompted for data selection and data sequencing. The values that you specify during prompting are retained in memory, but are not saved to the local RDASPEC files. The values in memory are then passed along to the job as it processes. If you are not prompted for data selection and data sequencing, the job loads data selection and data sequence values from the local RDASPEC files at runtime.
Batch versions submitted on the server from the Microsoft Windows client.	The system copies the data selection and data sequencing specifications related to the version into packed files and sends them to the server. When the job processes on the server, the system merges the packed files into the specifications on the server, which are then used to run the job. If you are prompted for data selection and data sequencing during submission, the values retained in memory are copied into the packed files instead of the corresponding RDASPEC information. The system then uses the data selection and data sequencing values that you enter at submission when the job executes.
Batch versions submitted from the web client.	You can override data selection and data sequencing at runtime. You also have the option of defining data selection and data sequencing from the Row menu.

Scenario

Description

Batch versions submitted locally from the Microsoft Windows client.

You might be prompted for data selection and data sequencing. The values that you specify during prompting are retained in memory, but are not saved to the local RDASPEC files. The values in memory are then passed along to the job as it processes. If you are not prompted for data selection and data sequencing, the job loads data selection and data sequence values from the local RDASPEC files at runtime.

Batch versions submitted on the server from the Microsoft Windows client.

The system copies the data selection and data sequencing specifications related to the version into packed files and sends them to the server. When the job processes on the server, the system merges the packed files into the specifications on the server, which are then used to run the job.

If you are prompted for data selection and data sequencing during submission, the values retained in memory are copied into the packed files instead of the corresponding RDASPEC information. The system then uses the data selection and data sequencing values that you enter at submission when the job executes.

Batch versions submitted from the web client.

You can override data selection and data sequencing at runtime. You also have the option of defining data selection and data sequencing from the Row menu.

Note: When you define data selection and data sequencing outside of RDA, either at runtime or from the Work With Batch Versions-Available Versions form, the definition only affects the first level-one section of the report template. If you have other level-one sections in the report template that need to use the same data selection and data sequencing as the first level-one section, you must define these sections to adopt the settings from the first level-one section. You can accomplish this by calling system functions in event rules on the additional level-one sections.

Data selection uses Boolean logic to determine which records to include in the report. Boolean logic uses operators such as And and Or.

Use And to include only the data that two or more fields in a record have in common. For example, suppose you need a list of customers who are located in New York City. You might use the two fields Location and Search Type in the criteria:

Search Type = C (customer)

And

Location = New York

Use Or logic to include all records that meet one of the sets of criteria. For example, if you need to find any New York City record or any customer record, you would indicate the same information for Location and Search Type using these criteria:

Search Type = C (customer)

Location = New York

The Section Data Sequencing form that you see at runtime is slightly different from the one that you see in RDA. You can still see the Columns Available on the left and the Columns Sorted on the right. The form also indicates the sort order of ascending or descending and whether page breaks are set. You can modify both the sort order and the page break options on this form.