Field Mapping for the Flexible Selection of Sender

FD_SENDER

Background: Normally, each cost center planning with Allevo records its own activities. The receiver of these activities must be stored in a satellite field when using FP (see constant FD_RECEIVER); costs are in the end posted to the receiving object. In addition, the sending cost center is stored in the satellite key field COOBJECT: constant FD_SENDER usefully contains a reference to this satellite field.

In some cases, however, it may be desired that a planning cost center may indicate also a different cost center as sender of an activity. Then, the plan data record will be entered as data record of the planning cost center in the satellite table (via COOBJECT), activity allocation, however, will be performed via a different sender recipient relationship.

In this case, the satellite must provide an additional field for the entry of the deviating sender. The field name is to be stored in FD_SENDER.

Note:

If a satellite data record contains a cost center here, this will be adopted as sender during posting. If there is no assignment or if the corresponding satellite field is empty, the sender will be adopted from the key field COOBJECT (condition: there is an object of the type cost center). See also constant FD_RECEIVER.