The new set concept in 4.0A resulted in changes to report maintenance.
Entering Sets in Report Maintenance
Because of the name range concept for sets, a set ID alone no longer determines a set uniquely. For instance, there might be a CO group with the same name.
If a set used in report definition is not determined uniquely by the set ID entered, a dialog box appears which requires the user to choose from among a list of sets.
Cross-Table Set Usage
You can use sets that were not created for a report table in a report to define general selection, rows, and columns. You may also use a set for a characteristic that is different from the characteristic for which it was created. The only requirement is that the characteristic in set definition and the characteristic for which the set is used are compatible.
Cross-table usage is only valid for basic and single sets.
As explained in the second example, entering a set in a row block no longer defines a characteristic of the row block uniquely. If the set entered can be used for more than one characteristic in the report table, a dialog box appears which requests the user to define the usage characteristic. The user can choose from all suitable characteristics that are part of report maintenance:
Beginning in Release 4.0A, you can create sets locally for a report. You can only use these sets in this report. When the report is deleted, they are deleted as well. They will also be deleted when they are no longer used in the report.
You can only create and maintain report sets in report maintenance. Report sets are always used for the characteristic for which they were created.
Set Maintenance from the Report
Beginning in Release 4.0A, you can branch directly from report maintenance to set maintenance. Before you go into set maintenance, however, the report must be saved. When a set that does not exist is entered in report maintenance, you are given the option of creating the set using set maintenance.