The attempt to import a single dimension set fails. The error message GO154 "... Set ... for table ... is not unique" is displayed.
When attempting to import superior sets, the error message GO158 "& Unknown subset in set ... for table ..." may appear.
The set contains two intervals, that overlap, in its subordinate basic sets. (Here, single values are treated as intervals for which the from-value and the to-value correspond.)
On the other hand, it was determined for the single dimension set that an ambiguity check is to be carried out. (This is the standard setting in the header screen of the set maintenance.)
This unambguity of the single dimension set already exists in the system or client from which the set was exported. However, this did not cause an error there. This can happen since the ambiguity check during a set change is limited to the values in the set itself and in the subordinate sets. Overlaps with other sets that are contained in a superordinate set together with this set are not found.
First, the cause for the ambiguity must be found in the source system or the source client of the single dimension set.
Step 1: Listing the overlaps within the single dimension set with the help of the ABAP program RGSOVL00. You can also call up this program via the function "Ambiguity check" in the environment menu of one of the set maintenance transactions (GS01, GS02, GS03, or GS04).
Step 2: Then either the ambiguity of the single dimension set should be removed or the ambiguity check in the header screen of the set should be switched off. The ambiguity check for higher single dimension sets can to be switched off the same way, if necessary. You can create a list of all superordinate sets using the ABAP program RGUSTU00. (Beginning with Release 3.0, the program is called RGUSTU01.)
You can also call up this program via the function "Set usage" in the environment menu of one of the set maintenance transactions (GS01, GS02, GS03 or GS04).
Additional key words
SAPFGUTR, Set transport
No comments:
Post a Comment