In Release 4.0A, the previous key fields for sets, table, and 12-character set ID have been replaced by a single, longer key field. As a result, you now have the option to allocate sets to different classes which each have a separate name range for set IDs. The name range for CO name groups in particular can be extended in this way. CO groups are technically stored as sets. (Also see Release notes for CO groups)
In the FI-SL application, sets will now be uniquely identified by the 24-character set ID; the table name is no longer a key field for a set.
Starting in Release 4.0A, sets can be used not just for the table field for which they were created, but for every compatible table field as well. A set created for GLT1-RACCT, for example, can also be used in a report in table GLFUNCT for field GLFUNCT-RACCT.
You can also use value and formula variables independent of tables in basic sets in reports beginning in 4.0A, as long as the table fields are compatible.
On the other hand, you can still only enter those sets and set variables in multi-sets that were created in the same table as the multi-set itself. This restriction also applies to the use of set variables in Report Writer and Report Painter reports.
Batch inputs in transaction GS01 should be brought up to date.
When entering a set ID in Release 4.0A, it may sometimes be the case that a set cannot be uniquely determined from the ID. It may be that there is already a group in CO with the same name which can also be used for the application being processed. In this case, all matching sets and groups are displayed in a dialog box for selection.
Old sets previously identified by a table and set ID will have the ID "Set ID.Table" in 4.0. For example, set "MYSET" in table "GLFUNCT" would become "MYSET.GLFUNCT". You can leave off the extra ".Table" when entering a set ID if there were several sets called "MYSET" in various tables. You can then choose the set you need from a dialog box.
These changes for sets affect the following applications:
Customer-specific programs that access sets or CO groups must be adapted. Access to sets with customer programs is documented in function group GSAC, and example programs RGSEXxxx were adjusted accordingly. More information is available in OSS in Note 92029.
Sets will be stored in transparent tables starting with 4.0A. However, there will not be an automatic conversion from the old tables. You can continue to work with the old sets. Only changed or newly created sets will be stored in the transparent tables.
You can use program RGSOLD2N to convert all sets to transparent tables. Because accessing sets in the old tables causes disadvantaged performance - especially in the possible entries function - it is absolutely in your best interest to run this program:
After you have made sure that the sets are functioning correctly, delete the remaining entries in old set tables in order to relieve the system of unnecessary data. Use program RGSOLDDL to carry out the deletion.
Please note that both programs only work in current clients.