Save Satellite Data in Separate Client

SATxx_CLIENT

* Available from Allevo version 3.2

Via this constant it is possible to store data of a satellite table in a separate client (CLIENT-SPECIFIED): i.e. when reading and editing this table, Allevo accesses the data from another client; in the current CO-client, no data can be extracted via SAP standard transactions like SE16.

Background: This function can be useful especially for a personnel planning where data protection regulations do not allow saving the personnel data in CO-clients. See the constant RFC_DEST as an alternative.

The write- and read functions are supported in the Allevo planning transactions, in satellite maintenance and in Shuttle.

The constant is activated by entering X in column Value from. At the same time, the client MUST be specified in column Value to. Otherwise, the constant remains inactive. Allevo does not check the availability of the target client.

The constant is only valid in the * layout: the dependency on the client applies thus with regard to controlling area and object type (but independently of the layout).

The name of the constant must contain the satellite number: e.g. SAT02_CLIENT for defining the client when accessing the Allevo satellite table /KERN/IPPSAT02. In general, different clients can also be used depending on the satellite table (however, can be useless in case of practical application).

Note:

The constant SATxx_CLIENT is not displayed in F4 selection aid: it must be directly specified in the desired characteristic (e.g. SAT02_CLIENT). Once this constant is established, the data of the satellite tables from the indicated client are read and saved there. Data, which have possibly been already saved in the current CO-client before, don’t appear in Allevo any longer. As usual, the affected satellite tables must be activated by the constant ACTIVE_SAT.