Transporting Global Area Objects

Procedure

The global area contains cross-client objects. Therefore, transporting these objects always means moving them to another system.

In the global area, an object's development class determines whether or not it can be transported. Local objects (those in temporary development classes) cannot be transported. All other objects are entered into a correction request whenever they are created or changed. Transport then takes place in the normal manner using the Change and Transport Organizer (transport request release).

Whenever an object is transported using the Change and Transport Organizer, you are unable to check the Query objects being transported for compatibility with the target system. This means that there may be inconsistencies in the target system's Query datasets. A typical inconsistency of this sort would be transporting a Query whose corresponding InfoSet does not exist in the target system. Therefore, when transporting Query objects in the global area, it is important to check and see if all current dependent objects already exist in the target system. If this is not the case, then these objects must be transported as well.

Note

To check the consistency of query datasets in the target system after they have been transported, choose Start of the navigation path Goto Next navigation step More Functions Consistency Check End of the navigation path in the InfoSet maintenance component. You can choose which objects to check and a log is generated containing a list of any inconsistencies discovered.

If inconsistencies are discovered, the action you take to eliminate them depends on the type of inconsistency. Some inconsistencies must be eliminated in the system, for example if users appear in a user group that no longer has a user master record. Other inconsistencies can only be eliminated by completely re-transporting the objects from the source system. A good example of this kind of inconsistency is the Query transport without its corresponding InfoSet, mentioned at the beginning of this section.

If no catalog entry is found during a consistency check or there are objects in the catalogs that no longer exist, you can choose Start of the navigation path Goto Next navigation step More Functions Reconstruct Catalogs End of the navigation path to reconstruct these catalogs. A selection screen appears where you can choose which catalogs you want to reconstruct.

Query variants can only be transported if these variants have been created as system variants (see Global Area Query Variants in Query Areas). All other variants cannot be transported.

The following entries are included in a correction request when any Global Area Query Objects with transportable development classes are changed:

User groups

R3TR AQBG bbbbbbbbbbbb

This transport object only contains the catalog entry for a user group. The user assignments and InfoSet assignments of this user group are neither recorded nor transported.

Changes to the user/user group assignment or the InfoSet/user group assignment can be made without being entered in a correction request. When the transport request is released, it includes InfoSet/user group assignments, but not users/user group assignments.
InfoSets

R3TR AQSG ssssssssssssssssssssssss

This transport object contains the catalog entry for an InfoSet, its definition, and its user group assignments. When the transport request is released, the InfoSet's current user group assignments are transported as well.
Queries

R3TR AQQU bbbbbbbbbbbbqqqqqqqqqqqqqq

This transport object contains the catalog entry for a Query, its definition, and the Query itself.
System variants of queries

R3TR AQQV rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrvvvvvvvvvvvvvv

This transport object contains one system variant of a single Query. System variants can only be created when their Query is not assigned to a temporary development class. You should also note that this transport object cannot be locked and can therefore appear in different correction requests simultaneously. If the Query is transported together with the system variants because of this, make sure that the system variants are included in the same correction requests as the Queries.

Changes to the user/user group assignment or the InfoSet/user group assignment can be made without being entered in a correction request. When the transport request is released, it includes InfoSet/user group assignments, but not users/user group assignments.