Read Activity Price Indicator and Price Unit

TARIF_KZ

Information on the activity price appear in Allevo column definitions with extensions PV, PF and PU if the corresponding button “Read Activity Price Rate” is set in the column definition. The constant TARIF_KZ defines the activity price indicator and price unit that are to be considered when reading prices (activity type planning).

The activity price indicators which are to be read (multiple entries separated by comma without space, e.g. 1,3) must be entered in column Value from. The function is activated once the entries have been made.

Note:

The specification on the activity price indicator is also used in FP; see constant TARKZ_LAYOUT there.

The price unit may be predefined in column Value to (standardization). The following entries are possible:

· No entry:
Neither activity prices nor their units are read (however, before the actual planning of quantities, reading does take place: i.e. a blank entry is treated like 0)

· Entry 0
The activity prices are read and written the way they are stored in SAP (KP26). The unit stored there is made available via the respective column definition and suffix “PU”.

· Entry 1, 10, 100, 1000 or 10000 (specifications like in SAP value-range):
In this case, Allevo uses the same units for all activity types with prices. However, via suffix “PU” it is further on possible to read the unit originally stored in SAP.
Note: rounding errors cannot be excluded with this option, since SAP prices are always calculated down to 1 piece and subsequently multiplied by the indicated factor.

If an entry is made in column Value to, the activity price for the current unit is read from the table COST (hence, planning data must be available already).

If the unit is provided during posting through column definition CX_WW_PU, it will then be used instead of the one specified in Value to. Without any specification, the activity price for the unit 1 will be posted.

Note:

In the range definitions for activity planning M (activity quantities) and N (capacity relating to activity) activity planning, the price which is valid for the above defined unit and corresponding to the activity price indicator is also read from the value column in Excel. Maintenance of all used activity price indicators is important also for activity planning M (activity quantities) and N (capacity relating to activity) if no prices are planned via Excel. This is due to the functioning of the BAPI which would overwrite any existing price with a 0 if no price information is available. Allevo determines the existing price (specified for the indicator!) in advance and integrates it into planning again.

* new from Allevo version 3.4.13

The entry in column Value to is now read also with primary costs. Example for application case: Entry of values for secondary costs that are posted as quantities in the background; the required conversion in Excel must then of course be performed based on a standardized activity price unit.