Reading orders via cost center/Profit Center

READ_ASSIGNED_OR

* as of ProCED-Version 3.0

When calling ProCED with the object type KS, the data of the respective internal orders can be called in as well. (as of Allevo 3.2 also for “PC” object types). Optionally, the selection of the order data can also be made via the Profit Center to which the cost center is assigned.

For the selection of the relevant orders, customer specific criteria (e.g., the order status), in addition to the assignment to a Profit Center, can be important. In order to be flexible in this regard, a selection variant with the appropriate criteria must be available for the orders. All criteria entered there are then taken into account in ProCED; only the cost center or Profit Center itself is replaced by the current value set when ProCED is called.

In the field Value from for the constant READ_ASSIGNED_OR, you can enter how the called object should be included when selecting an order. The following options are available (the corresponding fields of the master record table AUFK are shown in brackets):

• X = Default (treated like V for KS, like P for PC)

• P = Read via the Profit Center of the cost center (PRCTR)

• Z = Selection variant is implemented without any reference to the master record

Additional options when starting via a cost center:

• V = Responsible cost center (KOSTV)

• A = Requesting cost center (AKSTL)

• B = Actually posted cost center (CYCLE)

• R = Cost center for basic settlement (KOSTL)

• E = Receiving cost center (ABKOSTL)

• C = All orders for the company code of the starting cost center (BUKRS), as of Version 3.2.33

In the field Value to, you must enter the name of a selection variant, with which the data are to be read (assigned via the transaction OKOV). The entry of the constant is made without the usual period (.) at the beginning.

Note:

The constant must be saved in the settings for the cost center (together ALLEVO_ACTIVE). The assignment of the fields, on the other hand, is always read from the constants for the order. Do not simultaneously use the constants SORT_BY_KSTAR and MULTIPAGE_MODE! An equivalent function is also available for the reading of WBS elements and cost centers (see constant READ_ASSIGNED_PR / READ_ASSIGNED_KS). Important: for each scheme, a specific selection variant should be used. When changing a parameter in Value from, the selection variant must be manually checked (if necessary, removing earlier selection characteristics).

* neu as of ProCED-Version 3.2

Selection can now also be made with PC as the starting object; there only X and P are available as options in Value from.

If necessary, multiple selection variants can be entered in Value to (comma separated).

Background: a selection variant remains locked by the current user until the respective master data have been determined. Another user can not call this variant during this time. If multiple entries are made, Allevo searches for the first free selection variant.

The selection of the posting combinations can also be taken into account by 1:n groups of Allevo (see the Allevo constant ONETON_PROCED).

* new as of ProCED-Version 3.3

Normally, selections made via selection variants for the relevant posting combinations, are carried out via an object number, depending on how you start (see the list of options above). In some special cases, it can be useful to simply use a predefined selection variant (example: actually posted cost center is not saved in the statistical order, if it is used for multiple cost centers.

This is now possible with the option Z: in this case, the selection variant is no longer locked / changed / unlocked, but is rather only executed with the standard resolution. Via option C, it is possible to read all orders for the company code of the starting cost center.