Budget and Total Planning: Availability Control

 

ACTIVATE_AVAIL

This constant activates the availability control for budgeted projects during background processing (entry X in column Value from).

 

Note:

Activation type “2“ must be set in the used budget profile.

See also manual section “Budget and Total Costs Planning“.

 

Activate Direct Call from the Allevo Main Module

 

ALLEVO_ACTIVE

The constant activates the current scheme for the direct call from the Allevo main module (entry X in column Value from).

When transferring plan data in the Allevo main module, all FP schemes with the active constant ALLEVO_ACTIVE are executed.

You can optionally restrict the execution of a scheme to single Allevo layouts. Enter the layout in column Value to (possibly various, separated by comma):

Please note:

·         If you do not enter any scheme in the selection parameter upon execution of FP via the dialog transaction, all schemes with the active constant ALLEVO_ACTIVE X will be executed. If you enter * for the scheme, all satellite schemes will be executed!

·         Referring to an Allevo layout is necessary for some constants during FP execution (e.g. for reading an Allevo column definition): when calling directly from the Allevo main module, the layout is included; in the dialog mode, FP uses the first layout of column Value to (or the layout * if none is stored in the constant).

Relevant data are selected via the field COOBJECT in the satellite (according to “Starting Object“).The constant SEL_AS_RECEIVER optionally allows selection via “Receiver“ (from version 3.4.4).

 

Note:

If activity planning is performed for a sending cost center (in field FD_SENDER) different from the start object, also the constant DUPLICATE_INCL should be activated (X) in case FP is actively integrated in Allevo.

Reason: other „start objects“ might be planning for the same sending cost center. To ensure that postings do not overwrite each other, the satellite will be searched for data records with identical sender/receiver characteristics (duplicates), values will be added up and posted together.  

 

FP Allocation Type

 

ALLOC_TYPE

*effective from version 3.2 (extended to 3.4)

ALLOC_TYPE defines the allocation type of the current planning process. You can directly enter an allocation type in column Value from. This represents an alternative to the field mapping via the constant FD_ALLOC_TYPE.

The following allocation types are available (in brackets: object types that the respective allocation type is available for):

AT        Activities, capacities and prices (KS)

PC       Primary costs (KS, OR, PR, BP)

DA       Activity allocation (KS, OR, PR, BP)

OS       Secondary order settlement (KS, OR, PR, BP)

SK       Statistical key figures (KS, OR, PR, BP, PC)

BD       Budget and Total Costs Planning (OR, PR)

BP       Equivalent to BD

AC       Simple posting with account (PC)

PP       Posting to account & partner profit center (PC)

FA        Posting to account, partner profit center & functional area (PC)

PT        Posting to account, partner center & functional area & company ID (PC)

AA       Posting to balance sheet account (PC)

Special feature for the selection of satellite data: if constants FD_ALLOC_TYPE and ALLOC_TYPE are entered simultaneously in the mapping, only data records whose allocation type in the field FD_ALLOC_TYPE corresponds to the entry in ALLOC_TYPE will be processed. 

Allevo Object: when working with the Allow own object type KX, all plan data will be written into an Allevo own data base table (e.g. /KERN/ACOSP). Here, individual allocation types apply:

AP        Primary costs

AS        Secondary costs

AK        Statistical key figures

 

Note:

The constant is a mandatory fields required in every FP scheme. These are:

·         FD_ALLOC_TYPE and/or ALLOC_TYPE,

·         FD_OBJECT_TYPE and/or OBJECT_TYPE

·         FD_RECEIVER.

See constant OBJECT_TYPE for a list of the available object types.

* New from version 3.4

Using Flexible Planning with posting to Allevo object is defined via new allocation types (see above).

Type of Budget and Total Costs Planning

 

BUDGET_ACTIVITY

Budget and total costs planning for orders and projects (with (FD_) ALLOC_TYPE „BP“)

This constant controls the transfer of budgeting and total costs planning independent from cost elements for orders and projects. For projects, additionally the transfer of total revenue planning independent from cost elements.

In column Value of for the constant, the following entries are possible:

·         KBUD (original budget),

·         KBN0 (supplement),

·         KBR0 (return),

·         KBFR (release for projects),

·         KSTP (total costs planning),

·         KSTR (income for projects)

 

Value to: X means for projects: Scroll up within project hierarchy

 

See also constant CHECK_PLAN_DATA to activate the consistency check for total costs planning.

 

Note:

See also notes in the section “Budget and Total Costs Planning“ of the manual.

 

Cancellation Feature

 

CANCEL_ACTIVE

The functionality of Flexible Planning to address data records in the satellites allows high flexibility but also bears certain risks. What happens to data records in the satellite that are completely deleted or whose key data are modified after posting data in SAP?

If the user adjusts data in Excel, he/she also expects full adjustment of the respective data in SAP. This means that not only the new data record must be posted, but that adjusting the posting for the old data record may also be required. This functionality is implemented by a cancellation feature running in the background.

In order to activate the cancellation feature, the constant CANCEL_ACTIVE must be created or activated (X in the field Value from) in the relevant execution scheme.

 

 

Note

See also detailed notes in the section „Cancellation of Rows Modified or Deleted in Excel“ of the FP manual.

Observe:

Activating this feature should be considered carefully. It is highly recommended to activate the feature only if the complete process executed by Allevo FP has been well tested and the constants of the scheme have been verified. If the cancellation feature is already activated, modifying the scheme has consequences that must be considered in detail!

Cancellation features are not supported with the satellite included (see constant SATELLITE_INCL.).

 

 

Activate Consistency Check

 

CHECK_PLAN_DATA

*effective from version 3.1

 

A consistency check and an availability control are usually carried out if plan values are being transferred in budget and total costs planning. For total planning (activity KSTP and KSTR), the consistency check may be activated using the constant CHECK_PLAN_DATA (Value from = X).

The availability control is performed additionally.

 

Note:

This constant replaces NO_DATA_CHECK in former FP versions (2.9 to 3.0).

 

Column Definition of an Allevo layout

 

COLDEF

*effective from version 3.1

 

The constant COLDEF defines a column definition of the calling Allevo layout, so that values regarding the runtime can be transferred from there.

Relevant are: main planning year, plan version, period from & to and currency type. 

If, however, direct mappings of these characteristics are maintained in the constants as well, these will be overwritten. Example: If the constant PLANYEAR is available, the value here will overwrite the plan year of the column definition.

 

Note:

You can alternatively read the column definition via mapping of the field parameter FD_COLDEF from the satellite.

Upon direct call via transaction (without calling from Allevo), FP checks if the constant ALLEVO_ACTIVE is set in the scheme. Possibly, the first layout in column Value to will be adopted; otherwise the layout * will be used!

 

Multiple Years Planning: Adopt Year/Version from the Allevo Layout

 

COLDEFY

*effective from version 3.2

This constant is used to adopt specifications on year and version from an Allevo column definition in the context of multiple years planning.

Enter the column definition in column Value form: entries will only be considered if YEARY and VERSIONY are not set simultaneously (see documentation there).

 

Note:

In the case of COLDEFY – other than with COLDEF or FD_COLDEF of the main planning year (!) – only year and version are considered. The period frame is set to 01-12: always complete years are considered (also in the case of different settings in the respective column definition).  

Upon direct call via transaction (without calling from Allevo), FP checks if the constant ALLEVO_ACTIVE active in the scheme. Possibly, the first Allevo layout will be adopted from column Value to; otherwise, the layout * will be used!

 

Determine Currency Type

 

CURRENCY_TYPE

The constant CURRENCY_TYPE defines the currency for planning:

„C“ stands for controlling area currency (default)

„O“ for object currency

„T“ transaction currency (available from version 3.1)

 

Note:

For option T = transaction currency, an ISO currency (3 digits) must additionally be specified in the field Value to. 

Alternatively: Mapping of the field parameter FD_CURRENCY.

 

FP Read: SAP Business Transactions for Direct Activity Allocation

 

DA_TRANS_READ

The constant defines SAP business transactions that shall be considered for direct activity allocation (DA = Direct Allocation). The constant is only relevant for reading data (FP Read).

 

Activate the constant by entering the desired business transactions in column Value from as a comma-separated list. Example: “RKP3,RKP7“ for direct activity allocation.

 

Note:

See constant OS_TRANS_READ for equivalent features for order settlement.

 

Activate Delta Planning

 

DELTAPLANNING

* effective from version 3.4.4

In the standard case, Flexible Planning interprets the entered plan value as total value. Optionally, you can use the constant DELTAPLANNING to perform planning via delta values and quantities. An example of application would be the planning of transfer postings between cost centers (transaction KB11N).

Activate the constant by X in column Value from. Subsequently, all postings will be processed as delta values for the current scheme (also following years!).

Note:

Delta postings create the risk of posting multiple entries (e.g. by double posting of satellite data when executing Flexible Planning twice).

Appropriate arrangements are to be made in the project flow. Please contact our support before activating this feature.

The feature of delta planning is available also as parameter of the column definition in the Allevo standard. If FD_COLDEF is set, this setting is transferred to FP.

 

Distribution Key Fix

 

DIST_KEY_FIX

* available from version 3.4

Key for the distribution of annual values to periods; the distribution key may therefore only be used for annual planning.

 

Enter the distribution key fix into column Value from; e.g. „2“ (= analog distribution). Available values are provided for example by the F4 value list for planning via KP26.

 

There is no default key available when planning via FP: it therefore must be included by the constant here or by a satellite field of constant FD_DIST_KEY_FIX.

 

Note:

See also constant FD_DIST_KEY_FIX.

See also DIST_KEY_VAR (distribution key variable) for activity-dependent planning.

 

Distribution Key Variable

 

DIST_KEY_VAR

* available from version 3.4

 

Distribution key variable. May only be used for annual planning.

Enter the distribution key variable in column Value from.

 

Note:

See also constant FD_DIST_KEY_VAR.

 

Distribution Key Activity Price Fix

 

DK_PRICE_FIX

* available from version 3.4

Planning of activities, capacities and prices (allocation type AT): the distribution key for activity price fix can be set permanently (referring to the transferred values for FD_PRICE_FIX).

 

Enter the distribution key for Activity Price Fixed in column Value from.

 

See the FP manual for default value of the distribution key.

 

Note:

See also constant FD_DK_PRICE_FIX.

 

Distribution Key Activity Price Variable

 

DK_PRICE_VAR

* available from version 3.4

Planning of activities, capacities and prices (allocation type AT).

 

Distribution key for activity price variable (with regard to FD_PRICE_VAR).

 

Enter the distribution key for activity price variable in column Value from.

 

See the FP manual for the default value of the distribution key.

 

Note:

See also constant FD_DK_PRICE_VAR.

 

Avoidance of Duplicates in Activity Planning

 

DUPLICATE_INCL

Background:  If activity planning is performed for a sending cost center (field FD_SENDER) different from the start object and if FP is actively integrated in Allevo, other “start objects” might possibly be planning for the same cost center.

 

In this case, the constant DUPLICATE_INCL should be activated so that postings do not overwrite each other (entry X in column Value from).  

 

Note:

FP then searches for data records with identical sender/receiver characteristics (duplicates) in the satellite, adds up values and posts them together.

DUPLICATE_INCL is only valid for the selection of satellite data via the option „Start object/Sender“. Do not set the constant when starting via the option “receiver”, since multiple postings might occur.

 

Default Setting for Equivalence Number

 

EQUI_NO

* available from version 3.4

 

This constant allows to transfer the equivalence number to SAP (only years) during activity-dependent planning: it serves to distribute cost center costs planned regardless of the activity to available activity types.

In case that this constant is active, the value in table COSL will be used; or 1 if no data record was found in COSL. FP therefore behaves in the same way as transaction KP26.

Enter the equivalence number in column Value from.

 

Note:

See also constant FD_EQUI_NO.

 

Factor for Quantities/Values

 

FACTOR

* available from version 3.2.19

You may enter numbers with length 15 and up to 3 decimals in the constant FACTOR, using a dot as decimal character!

The factor will be considered for all quantity/value fields: 

·         FD_QNTY_FIX, FD_QNTY_VAR for planning annual values,

·         FD_QNTY_MNTH_FIX and FD_QNTY_MNTH_VAR for planning period values

·         FD_QNTY_FIX0-9, FD_QNTY_VAR0-9 for planning following years.

 

Note:

Erroneous entries, e.g. a wrong separator, will be retained and the factor will be set to 1 without a comment.

The constant FD_FACTOR may be used as alternative to FACTOR.

 

Field Mapping for the Allocation Type

 

FD_ALLOC_TYPE

Defines the allocation type of the current planning process.

Enter the corresponding satellite field in column Value from.

 

If the constant ALLOC_TYPE is used as well, only data records with the allocation type in field FD_ALLOC_TYPE corresponding to the entry in ALLOC_TYPE will be used!

 

The following allocation types are available (in brackets: object types that the respective allocation type is available for):

 

AT        Activities, capacities, prices (KS)

PC       Primary costs (KS, OR, PR, BP)

DA       Activity allocation (KS, OR, PR, BP)

OS       Secondary order settlement (KS, OR, PR, BP)

SK       Statistical key figures (KS, OR, PR, BP, PC)

BP       Budget and total costs planning (OR, PR)

AC       Simple posting with account (PC)

PP       Posting to account & partner profit center (PC)

FA        Posting to account, partner profit center & functional area (PC)

PT        Posting to account, partner center & functional area & company code (PC)

AA       Posting to balance sheet account (PC)

 

NN       This row is ignored when reading satellite data

 

If satellite data are to be processed using different schemes (e.g. for deviating allocation types respectively), different columns per allocation type are to be used in the satellite (with the corresponding mapping per scheme).

 

If the constant ALLOC_TYPE is used as well, only data records with the allocation type in FD_ALLOC_TYPE corresponding to the entry in ALLOC_TYPE will be processed!

 

Note:

The constant is a mandatory field in every FP scheme:

FD_ALLOC_TYPE and/or ALLOC_TYPE,
FD_OBJECT_TYPE and/or OBJECT_TYPE
and FD_RECEIVER.

See constant FD_OBJECT_TYPE for a list of available object types.

 

Field Mapping for the Column Definition

 

FD_COLDEF

*available from version 3.1 (modified in 3.4)

 

Field name for the column definition of an Allevo layout.

The constant FD_COLDEF defines a column definition for the calling Allevo layout, so that values on the runtime period can be transferred from there.  Relevant are: planning year, plan version, period from & to and currency type (from vers. 3.4.4 also the setting on delta planning).

Direct mappings of these characteristics that are also maintained in the constants will be overwritten. Example: If constant FD_PLANYEAR is available, the entry here will overwrite the plan year of the column definition.

 

Note:

The column definition may optionally be predefined via the constant COLDEF.

When calling directly via transaction (without calling from Allevo), FP checks if the constant ALLEVO_ACTIVE is set in the scheme. Possibly, the first Allevo layout will be adopted from column Value to, otherwise the * layout will be used!

New from 3.4.4:

Transfer setting on delta planning; see also constant DELTAPLANNING

Field Mapping for the Currency

 

FD_CURRENCY

*effective from version 3.1

 

Field name for currency code (ISO code)

If constant CURRENCY_TYPE sets that posting shall be performed using the transaction currency, the currency code may be adopted in this field.

 

Note:

The entry here overrides the currency code in Value to for constant CURRENCY_TYPE.

 

Field Mapping for Distribution Key Fix

 

FD_DIST_KEY_FIX

Distribution key fix. May only be used for annual planning.

 

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant DIST_KEY_ FIX.

 

Field Mapping for Distribution Key Variable

 

 

FD_DIST_KEY_VAR

Distribution key variable. May only be used for annual planning. 

 

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant DIST_KEY_ VAR.

 

Field Mapping Distribution Key Activity Price Fix

 

FD_DK_PRICE_FIX

Planning of activities, capacities and prices (allocation type AT):

Distribution key for activity price fix (with regard to FD_PRICE_FIX).

 

Enter the corresponding satellite field in column Value from.

 

See FP manual for default value on the distribution key.

 

Note:

See also constant DK_PRICE_FIX.

 

Field Mapping Distribution Key Activity Price Variable

 

FD_DK_PRICE_VAR  

Planning of activities, capacities and prices (allocation type AT):

Distribution key for activity price variable (with regard to FD_PRICE_VAR).

 

Enter the corresponding satellite field in column Value from.

 

See FP manual for default value on the distribution key.

 

 

Note:

See also constant DK_PRICE_VAR.

 

Field Mapping for the Equivalence Number

 

FD_EQUI_NO

* available from version 3.1

Field name for the equivalence number.

This constant allows to transfer the equivalence number to SAP (only years) during activity-dependent planning: it serves to distribute cost center costs planned regardless of activities to available activity types.

In case that this constant is not active, the value in table COSL will be used; or 1 if no data record was found in COSL. FP therefore behaves in the same way as transaction KP26.

 

Note:

See also default setting via constant EQUI_NO and constant PLAN_AEQUZIFF and AEQUZIFF_READ in the Allevo main module.

 

Field Mapping for the Factor Quantities/Values

 

FD_FACTOR

* available from version 3.2.19

Enter the corresponding satellite field in column Value to.

You may enter numbers with length 15 and up to 3 decimals in the field FD_FACTOR.

The factor will be considered for all quantity/value fields: 

·         FD_QNTY_FIX, FD_QNTY_VAR for planning annual values,

·         FD_QNTY_MNTH_FIX and FD_QNTY_MNTH_VAR for planning period values

·         FD_QNTY_FIX0-9, FD_QNTY_VAR0-9 for planning following years.

 

Note:

If no value can be found in the field FD_FACTOR, the factor will be set to 1 without a comment.

The constant FACTOR may be used as alternative to FD_FACTOR.

 

Field Mapping for the Cost Element

 

FD_KSTAR

Cost element

 

Enter the corresponding satellite field in column Value from. 

 

Note:

By using multiple years planning, the cost element may also be assigned to the quantity fields FD_QNTY_FIXy, see constant FD_QNTY_FIXy.

 

Field Mapping for the Object Type

 

FD_OBJECT_TYPE 

Defines the object type for the current planning process.

 

Enter the corresponding satellite field in column Value from. The following object types are available:

KS       Cost centers

OR       Internal orders

PR       WBS elements

BP       Business process

PC       Profit center

Special cases for data selection:

·         The satellite field for the object type may also contain the entry NN, which is equivalent to an empty data field: the respective row will be ignored during selection (the function is available from 3.2.11).

·         If constant OBJECT_TYPE is active as well, only data records with the object type in field FD_OBJECT_TYPE corresponding to the entry in OBJECT_TYPE will be processed!  

·          

Note:

The constant is a mandatory field in every FP scheme:

·         FD_ALLOC_TYPE and/or ALLOC_TYPE

·         FD_OBJECT_TYPE and/or OBJECT_TYPE

·         and FD_RECEIVER.

See constant FD_ALLOC_TYPE for a list of available allocation types.

 

Field Mapping for the Plan Controlling Area

 

FD_PLANKOKRS

* New from FP version 3.0

 

The plan controlling area is specified via the constant PLANKOKRS or via the FP selection screen (or as parameter when calling from Allevo). The constant allows postings spreading over several controlling areas (example: during project planning, also costs for a target project assigned to a different controlling area shall be entered).

If constant FD_PLANKOKRS is active, the controlling area will be transferred from the entered field of the satellite.  Enter the corresponding satellite field in column Value from.

 

Note:

This function is available only when calling via sender object (also when calling from Allevo); should therefore not be used when starting via receiver.

 

Mapping for Period from

 

FD_PLANPERIODFROM

* New from FP version 3.1

Mapping for Period from. This constant allows to restrict annual values to a period frame and in that way post them for example as quarterly values (as in Allevo).

 

Note:

Alternatively, the period frame may be defined via constant PLANPERIOD.

This option of period restriction is not available for the object type profit center (from FP version 3.2).  

 

Mapping for Period to

 

FD_PLANPERIODTO

* New from FP version 3.1

Mapping for Period to. This constant allow to restrict annual values to a period frame and in that way post them for example to quarterly values (as in Allevo).

 

Note:

Alternatively, the period frame may be defined via the PLANPERIOD.

This option of period restriction is not available for the object type profit center (from FP version 3.2) !

 

Field Mapping for the Plan Version

 

FD_PLANVERSN

Usually, the plan version is defined by the constant PLANVERSN.

Alternatively, the version may be adopted in the planning mode also from the satellite: for this purpose, the constant FD_PLANVERSN must be defined.

 

Advantages:

·         Postings can be performed via multiple versions without separate schemes required.

·         Normally, also data processing in the Excel Master will be simplified (e.g. since only one column must be addressed with the allocation type, which will then be relevant for all versions).

Enter the corresponding satellite field in column Value from.

 

Note:

from FP version 3.1:

Application of the fields FD_PLANYEAR, FD_PLANVERSION and FD_PLANKOKRS, as well as PLANYEAR, PLANVERSION and PLANKOKRS is possible for all allocation types and therefore allows unrestricted planning row by row via multiple versions.

 

Field Mapping for the Planning Year

 

FD_PLANYEAR

The planning year is usually defined by the constant PLANYEAR.

Alternatively, the planning year may be adopted in the planning mode also from the satellite: for this purpose, the constant FD_PLANYEAR must be defined.

 

Advantages:

·         Postings can be performed over multiple years without separate schemes required.

·         Normally, also data processing in the Excel Master will be simplified (e.g. since only one column must be addressed with the allocation type, which will then be relevant for all years).

Enter the corresponding satellite field in column Value from.

 

 

Note:

From FP version 3.1:

Application of the fields FD_PLANYEAR, FD_PLANVERSION and FD_PLANKOKRS, as well as PLANYEAR, PLANVERSION and PLANKOKRS is possible for all allocation types and therefore allows unrestricted planning row by row via multiple versions.

 

Field Mapping for the Amount Activity Price Fix

 

FD_PRICE_FIX 

Planning of activities, capacities and prices (allocation type AT): Amount of price fix.

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant FD_PRICE_UNIT for price unit.

 

Field Mapping for the Price Unit

 

FD_PRICE_UNIT 

Price unit for planning activities and capacities (annual planning).

Background: Number of units with a price (valuation: 1, 10, 100, 1000, 10000).

Enter the corresponding satellite field in column Value from.

If there is no mapping available for this constant, the posting interface will try to read the previous vale (table COKL) and reuse it. If the price unit is not determined (no matter if in the satellite or as value), 1 will be transferred.  

 

Note:

For period planning, the existing price unit is used (or default 1).

Planning prices (and price units) to exact periods is not possible so far.

 

Field Mapping for the Amount Activity Price Variable

 

FD_PRICE_VAR

Planning activities, capacities and prices (allocation type AT): Amount for price variable.

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant FD_PRICE_UNIT for the price unit.

 

Field Mapping for Quantity Fix

 

FD_QNTY_FIX

Annual planning: Quantity fix, depending on current allocation type

 

Enter the corresponding satellite field in column Value from.

 

Note:

Enter an X for Value to of the constant PLANYEAR if the value in field FD_QNTY_FIX is to represent the total instead of annual budget in budget/total planning (allocation type BP).

 

Multiple Years Planning: Quantity Fix

 

FD_QNTY_FIXy

Often, a display with multiple planned quantities entered in a single Excel row (across multiple columns) is desired. This constant realizes two application cases:

·         Multiple years planning and

·         Posting to different cost elements (column by column)

These FP planning functions can be realized for up to 10 columns.

Note:

In both cases, the parameters FD_QNTY_FIXy and YEARy or COLDEFy (y from 0 to 9) form a unit that is to be maintained in the constants.

If the corresponding mapping for VERSION0-9 is missing, the version of the main planning year will be used. This is beneficial e.g. for budget planning, with the version usually being irrelevant anyway.  

 

1st Application: Multiple years planning with Quantity fixed

Name of the fields containing the fixed quantities for the years 0 – 9.

 

2nd Application: Assign primary cost elements via columns

As an alternative to multiple years planning, the quantity fields may also be permanently attached to a primary cost element. In this case, the information on the cost element will not be taken from the data record via FD_KSTAR but from the constants.

Enter the respective primary cost element in the constants FD_QNTY_FIX0 to FD_QNTY_FIX9 in the field Value to.

New from version 3.1:

Using fixed primary costs on quantity columns (Value to of FD_QNTY_FIX0 to FD_QNTY_FIX9) is in principle possible for all allocation types and not only for primary costs. If the respective Value to field is empty, the cost element will be read from the field FD_KSTAR.

Note:

Both procedures differ only in the entry for Value to: an entry must involve a valid cost element.

 

Period Planning: Quantity Fixed

 

FD_QNTY_MNTH_FIX

Period planning is activated via the constant MONTH_ACTIVE (see notes there).

 

Up to 12 satellite fields contain the fix period quantities; these must carry the same basic field name but differ in the last two digits (01 to 12). This basic field name is to be entered in the constant FD_QNTY_MNTH_FIX_.

 

 

Note:

The constant FD_QNTY_FIX and FD_QNTY_VAR for quantity fields in annual planning may not be active in period planning.

 

 

Note:

Not in all cases of application, all 12 periods are actually used for the entry of plan data and possibly not all corresponding fields are created in the satellite.  In this case, used periods may be entered in Value to for MONTH_ACTIVE separated by comma (otherwise, FP will try to read data for all 12 periods from the satellite).

 

Period Planning: Quantity Variable

 

FD_QNTY_MNTH_VAR  

Period planning is activated via the constant MONTH_ACTIVE (see notes there).

 

Up to 12 satellite fields contain the fix period quantities; these must carry the same basic field name but differ in the last two digits (01 to 12). This basic field name is to be entered in the constant FD_QNTY_MNTH_FIX_.

 

 

Note:

The constant FD_QNTY_FIX and FD_QNTY_VAR for quantity fields in annual planning may not be active in period planning.

 

 

Note:

Not in all cases of application, all 12 periods are actually used for the entry of plan data and possibly not all corresponding fields are created in the satellite.  In this case, used periods may be entered in Value to for MONTH_ACTIVE separated by comma (otherwise, FP will try to read data for all 12 periods from the satellite).

 

Field Mapping for Quantity Variable

 

FD_QNTY_VAR

Annual planning: Quantity variable (or quantity of capacity), depending on the allocation type.

 

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant FD_ALLOC_TYPE for a list of available allocation types.

 

Multiple Years Planning: Quantity variable

 

FD_QNTY_VARy

The FP planning feature may be extended to up to 10 additional year, provided that the satellite includes supplementary fields for the fix and possibly variable quantities.

The constants FD_QNTY_VAR0 to FD_QNTY_VAR9 contain names for the fields providing the variable quantities for the years 0 to 9 (only for activity allocation dependent on the activity type; for primary cost planning it is the value).

 

 

Note:

FD_QNTY_VARy is an optional parameter.

The parameters FD_QNTY_FIXy and YEARy or COLDEFy (with y from 0 to 9) for further annual planning form a unit that is to be maintained in the constants.

 

Field Mapping for the Receiving Activity Type

 

FD_RCV_ACT_TYPE

Defines the receiving activity type for activity type dependent planning in the current planning process (with regard to the cost center).

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant RCV_ACT_TYPE.

 

Field Mapping for the Receiving Resource

 

FD_RCV_RESOURCE  .

Defines the receiving resource for resource-dependent planning in the current planning process.

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant RCV_RESSOURCE.

 

Field Mapping for the Receiver

 

FD_RECEIVER 

Defines the field used for the name of the receiver in the current planning process. Together with the constant FD_OBJECT_TYPE and OBJECT_TYPE, this constant results in an explicit posting object.

Enter the corresponding satellite field in column Value from.

Background: The corresponding satellite field must contain the receiving object (e.g. the cost center), that costs are posted to.  The receiver is therefore equivalent to the starting object of a standard Alllevo planning transaction.

In the FP dialog mode, the field in FD_RECEIVER can also serve as characteristic for the selection of satellite data. m

Note:

The constant is a mandatory field in every FP scheme:

 (FD_)ALLOC_TYPE, (FD_)OBJECT_TYPE and FD_RECEIVER.

See also constant FD_ALLOC_TYPE for a list of available allocation types.

See also constant FD_SENDER for the meaning of COOBJECT when working with FP.

 

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.

 

Field Mapping for the Sign

 

FD_SIGN

* available from version 3.2.11

The sign of quantities/values shall in some cases be reversed prior to planning. This is useful when planning the receiver debit from the sender perspective; as credit there with inverse sign.

The sign is usually determined via the constant SIGN_MINUS.

Alternatively, the sign can be adopted from the satellite in the planning mode: the constant FD_SIGN must be defined for this purpose.

The correspondingly mapped satellite field should be one of the CHAR type. If the (first) sign is a <minus>, quantities/values will be multiplied by -1.

 

Note:

See also constant SIGN_MINUS.

 

Field Mapping for Activity Type Sending Cost Center

 

FD_SND_ACT_TYPE

Activity type of the sending cost center for activity allocation and secondary order settlement (allocation type “DA“ and “OS“).

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant SND_ACT_TYPE.

 

Field Mapping for the Statistical Key Figure

 

FD_STAGR

Planning of statistical key figures via allocation type SK or KF.

 

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant STAGR.

 

Field Mapping for the Switch Scheme in Cost Component Splitting

 

FD_SWITCH_LAYOUT

Mapping for the switch scheme in cost component splitting when planning activites, capacities and prices (allocation type AT).

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant SWITCH_LAYOUT.

 

Field Mapping for Amount Fix

 

FD_VALUE_FIX

* available from version 3.4

 

Annual planning: Amount fix, depending on the current allocation type (e.g. for primary costa nd profit center planning).

 

Value of budget and total planning for allocation type BP

 

Enter the corresponding satellite field in column Value from.

 

Note:

Enter X for Value to oft he constant PLANYEAR if the value in field FD_VALUE_FIX is to display the total instead of annual budget in budget/total planning (allocation type BP).

 

Multiple Years Planning: Value Fix

 

FD_VALUE_FIXy

* available from version 3.4

 

Often, a display with multiple plan values entered in a single Excel row (across multiple columns) is desired. This constant realizes two application cases:

 

·         Multiple Years Planning and

·         Posting to different cost elements (column by column)

These FP planning functions can be realized for up to 10 columns.

Note:

In both cases, the parameters FD_VALUE_FIXy and YEARy, or COLDEFy (y from 0 to 9) form a unit that is to be maintained in the constants.

If the corresponding mapping for VERSION0-9 is missing, the version of the main planning year will be used. This is beneficial e.g. for budget planning, with the version usually being irrelevant anyway.  

 

1st Application: Multiple years planning with Quantity fixed

Name of the fields containing the fixed quantities for the years 0 – 9 (especially for primary cost planning).

 

2nd Application: Assign primary cost elements via columns

As an alternative to multiple years planning, the value fields may also be permanently attached to a primary cost element. In this case, the information on the cost element will not be taken from the data record via FD_KSTAR but from the constants.

Enter the respective primary cost element in the constants FD_VALUE_FIX0 to FD_VALUE_FIX9 in the field Value to.

Using fixed primary costs on value columns (Value to of FD_VALUE_FIX0 to FD_VALUE_FIX9) is in principle possible for all allocation types and not only for primary costs. If the respective Value to field is empty, the cost element will be read from the field FD_KSTAR.

 

Note:

Both procedures differ only in the entry for Value to: an entry must involve a valid cost element.

 

Period Planning: Value Fix

 

FD_VALUE_MNTH_FIX

* available from version 3.4

 

Period planning is activated via the constant MONTH_ACTIVE (see notes there).

 

Up to 12 satellite fields contain the fix period values; these must carry the same basic field name and differ in the last two digits (01 to 12). Enter the basic field name in the constant FD_VALUE_MNTH_FIX.

 

Note:

The constants FD_VALUE_FIX and FD_VALUE_VAR for value fields in annual planning may not be active during period planning.

 

 

Note:

Not in all cases of application, all 12 periods are always used to enter plan data; and possibly not all corresponding fields are available in the satellite. In this case, the used periods may be entered in column Value to of constant MONTH_ACTIVE separated by comma (otherwise, FP tries to read data for all 12 periods from the satellite). Nicht in allen Anwendungsfällen werden immer alle 12 Monate für die Eingabe von Plandaten verwendet und ggf. sind auch nicht alle zugehörigen Felder in der Satellitentabelle angelegt. In diesem Fall können die verwendeten Monate kommagetrennt in der Spalte Wert bis von Festwert MONTH_ACTIVE eingetragen werden (sonst versucht FP die Daten für alle 12 Monate aus dem Satelliten zu lesen).

 

Period Planning: Value Variable

 

FD_VALUE_MNTH_VAR  

* available from Version 3.4

 

Period planning is activated via the constant MONTH_ACTIVE (see notes there).

 

Up to 12 satellite fields contain variable period values; these must carry the same basic field name and differ in the last two digits (01 to 02). Enter this basic field name in constant FD_VALUE_MNTH_VAR einzutragen.

 

 

Note:

The constants FD_VALUE_FIX and FD_VALUE_VAR for value fields in annual planning may not be active in period planning.

 

 

Note:

Not in all cases of application, all 12 periods are used for the entry of plan data and possibly not all corresponding fields are available in the satellite.  In this case, used periods may be entered separated by comma in Value to for MONTH_ACTIVE (otherwise, FP will try to read data for all 12 periods from the satellite).

 

Field Mapping for Amount Variable

 

FD_VALUE_VAR

* available from version 3.4

 

Annual planning: Amount variable, depending on the allocation type (e.g. for primary costs and profit center planning).

 

Enter the corresponding satellite field in column Value from.

 

Note:

See also constant FD_ALLOC_TYPE for a list of available allocation types.

 

Multiple Years Planning: Value Variable

 

FD_VALUE_VARy

* available from version 3.4

 

The FP planning function may be extended to up to 10 additional years, provided that the satellite includes supplementary fields for fix and possibly variable values.  

The constants FD_VALUE_VAR0 to FD_ VALUE _VAR9 contain the names of the fields providing the variable values for the years 0 to 9 (for primary cost planning, for activity allocation dependent on the activity type, it is the quantity).

 

Note:

FD_VALUE_VARy is an optional parameter.

The parameters FD_VALUE_FIXy and YEARy or COLDEFy (with y from 0 to 9) for further annual planning form a unit that is to be maintained in the constants.  

 

Activate Period Planning

 

MONTH_ACTIVE

Period planning can be performed for a business year. Following years may be planned using annual values.

 

Note:

This only applies for the respective execution scheme. By creating multiple schemes that are executed one after the other, period planning may also be used for multiple years.

* from version 3.1:

In combination with constant FD_PLANYEAR, period planning may also be performed within a scheme over multiple years (with period values of the different years still in different satellite rows).

 

Enter X in column Value from to activate MONTH_ACTIVE.

Plan values must be provided by the constants FD_QNTY_MNTH_FIX, FD_QNTY_MNTH_VAR. Indicate the name of the periodic quantity/value fields of the satellite table without the last two digits (these stand for periods 01 to 12).  

The quantity/value fields FD_QNTY_FIX and FD_QNTY_VAR intended for annual planning may not be used.

 

Note:

Not in all cases of application, all 12 periods are used for the entry of plan data and possibly not all corresponding fields are created in the satellite.  In this case, used periods may be entered separated by comma in Value to for MONTH_ACTIVE (otherwise, FP will try to read data for all 12 periods from the satellite).

 

 

Switch off Consistency Check

 

NO_DATA_CHECK                      

*effective up to version 3.0

 

A consistency check and an availability control is usually carried out if plan values are being transferred. The consistency check may be switched off for total planning (transaction KSTP and KSTR) via the constant.

NO_DATA_CHECK (Value from = X). The availability control will still be performed.

 

Note:

Alternative for this constant is CHECK_PLAN_DATA (from version 3.1).

 

Avoidance of Empty Data Records

 

NO_ZERO_DELTA

*effective from verison 3.1

 

Prior to posting, the value to be planned (or the quantity to be planned) is compared to the value already existing in SAP. Posting will be initiated via BAPI only if there is a deviation.

Activation is performed by X in field Value from.

 

Note:

See further notes on the constant of the same name in the Allevo main program.

 

Object Type

 

OBJECT_TYPE  

*effective from version 3.2

 

OBJECT_TYPE defines the object type for the current planning process. 

You may directly enter an object type in column Value from. This provides an alternative to the field mapping via the constant FD_OBJECT_TYPE.

 

If the field FD_OBJECT_TYPE is mapped as well and the constant OBJECT_TYPE is being used, only data records with the object type in the field FD_OBJECT_TYPE corresponding to the entry in OBJECT_TYPE will be processed!

 

The following object types are available:

 

KS       Cost centers

OR       Internal orders

PR       WBS elements

BP       Business process

PC       Profit center

 

Note:

The constant is a mandatory field in every FP scheme:

FD_ALLOC_TYPE and/or ALLOC_TYPE,
FD_OBJECT_TYPE and/or OBJECT_TYPE
and FD_RECEIVER.

See constant ALLOC_TYPE for a list of available allocation types.

 

FP Read: SAP Business Transactions on the Order Settlement

 

OS_TRANS_READ

The constant defines SAP business transactions that are to be considered for plan postings on the order settlement (OS = Order Settlement). The constant is only relevant for reading data (FP Read).

                                                                                                               

The constant is activated by entering the desired process in columns Value from as a comma-separated list. Example: „RKPW,RKPX“ for secondary order settlement (automatically: KOAP).

 

Note:

See constant DA_TRANS_READ for similar features for direct activity allocations.

 

Controlling Area for Planning

 

PLANKOKRS

* New from FP version 3.1

 

If planning shall be performed in a controlling area different from the starting controlling area, you can use this constant and enter the controlling area in field Value from.

 

Note:

The constant may also be transferred from the satellite: see constant FD_PLANKOKRS

 

Planning with Period Frames (from/to)

 

PLANPERIOD

* New from FP version 3.1

Using this constant, annual values can be restricted to a period frame and thus be posted e.g. as quarterly values (as in Allevo).

Period from and to must be entered in column Value from and Value to.

Note:

The period frame can optionally be transferred from the satellite; see constants FD_PLANPERIODFROM und FD_PLANPERIODTO.

This option of period restriction is not available for the object type profit center (from FP version 3.2).

 

Plan Version

 

PLANVERSN

* New from FP version 3.1 (replaces the former constant VERSN_INITIAL)

 

Plan version und plan year are defined by the constants PLANVERSN and PLANYEAR (in field Value from). In case that these constants are missing, entries according to the selection screen will be used instead.  

 

See also notes on the constant PLANYEAR

 

Note:

Both values may alternatively be transferred from the satellite table in the planning mode: the constants FD_PLANVERSN and FD_PLANYEAR are available for this purpose.

 

Main Planning Year

 

PLANYEAR

* New from version 3.1 (replaces the former constant YEAR_INITIAL)

 

Plan year and plan version are defined by the constants PLANYEAR and PLANVERSN (in field Value from). In case that these constants are missing, entries according to the selection screen will be used instead.  

 

Both values may alternatively be transferred from the satellite table in the planning mode: the constants FD_PLANYEAR and FD_PLANVERSN are available for this purpose.

 

Note:

Value to controls an additional feature in budget planning (allocation type BP): for entry X, the total budget will be planned via the field FD_QNTY_FIX instead of an annual budget (posting without planning year!)

 

Receiving Allocation Type

 

RCV_ACT_TYPE

* available from version 3.3.21

 

Defines the receiving allocation type for activity type dependent planning in the current planning process (with regard to the cost cener).

Enter the activity type of the receiver in column Value from.

 

Note:

See also constant FD_RCV_ACT_TYPE.

 

Default Setting Receiver Resource

 

RCV_RESOURCE

* available from version 3.4

 

Defines the receiver resource for resource-dependent planning in the current planning process, if not included by FD_RCV_RESSOURCE.

 

Enter the resource in column Value from.

 

Note:

See also constant FD_RCV_RESSOURCE

 

Read Data from Two Identical Satellites

 

SATELLITE_INCL

FP is able to merge data from two satellites and process them simultaneously upon program execution if controlled by this constant.

Background: Depreciation data from existing investments and new orders are sometimes stored in separate satellites; although identical cost elements might be used. FP posting should then be cumulative.

Conditions:

·         Both satellites must have the exact same structure (same append structure; using the same Include is recommended). FP itself only performs simple checks for correspondance.

·         An FP scheme is required only for one of both satellites

·         The constant is active if Value from contains the number of the second satellite.

·         Satellite data are saved in Allevo in the sequence of satellite numbers (Sat.01, Sat.02 …). The included satellite must have a lower number for the data to be relevant when processing via FP.

 

Observe:

Cancellation features are supported from Allevo 3.4 for included satellites (see constant CANCEL_ACTIVE).

 

Create Log for SLG1

 

SAVE_LOG

FP offers the possibility to write (error) messages into the SAP Application Log. Entries are displayed via the SAP transaction SLG1 with selection parameters /KERN/ALLEVO as object and FP as sub-object.

Writing the log must be explicitly activated; the specification in Value from on the constant SAVE_LOG controls the conditions for creating entries:

•           With „N“, no log is written (as with an inactive constant)

•           with „E“ only in case of an error,

•           with „W“ already in case of warnings

•           otherwise (I or X or S), all ouputs are saved.

Besides, the screen output may be controlled via the parameter “Output Level” in the FP selection screen.

Note:

When calling FP from the Allevo main program, the execution log is additionally transferred to Allevo and, if desired, displayed also in the dialog. The Allevo constant MESSAGE_LEVEL controls what contents are relevant for being displayed (see documentation on Allevo constants).

Especially if FP is executed in the background upon calling from Allevo, it may be useful to write into the Application Log (see Allevo constant ACTIVE_FP_PARAM).

 

Data Selection via Receiver Field

 

SEL_AS_RECEIVER

* effective from version 3.4.4

Background: when calling FP directly via Allevo (see constant ALLEVO_ACTIVE), data selection is performed according to the option „start object/sender“ (corresponds to field COOBJECT of the satellite).  This constant allows for selection via the option „receiver“ (see also start screen of the FP dialog transaction).  

The constant SEL_AS_RECEIVER is activated via an entry X in column Value from.

Data are subsequently selected to the transferred CO object via the satellite field entered in the FP constant FD_RECEIVER.

 

Note:

The constant will NOT be considered during execution of the FP dialog transaction.

 

Reverse Sign

 

SIGN_MINUS

Using SIGN_MINUS, the sign of the quantity can be reversed prior to planning.  This is useful when planning the receiver debit from the sender perspective; as credit there with inverse sign.

The constant SIGN_MINUS is activated by X in column Value from. It applies for all allocation types.

 

Note:

From version 3.0.6, the constant can be used also during reading. FP Read identifies activity allocations for a cost center that originated from this same cost center. Commonly, a negative sign is used for the display.

 

Activity Type of the Sending Cost Center

 

SND_ACT_TYPE

* available from version 3.3.21

 

Activity type of the sending cost center with activity allocation and secondary order settlement (allocation type DA and OS).

Enter the activity type of the sender in column Value from.

 

Note:

See also constant FD_SND_ACT_TYPE.

 

The Statistical Key Figure

 

STAGR

* available from version 3.3.21

 

Planning statistical key figures via the allocation type SK or KF.

 

Enter the statistical key figure in column Value from.

 

Note:

See also constant FD_STAGR.

 

Treatment of Allevo Status in FP

 

STATUS_INFO

* New from version 3.2

In order to use FP for writing plan data, the corresponding planning object must have a valid entry in the Allevo status management. This ensures that Allevo license terms will be complied with also when planning with FP.

In the standard case, FP creates the entry on the status itself upon the first posting to a new planning object (e.g. upon the first posting to a cost center): the status information „3“ is automatically written in the current planning year: with „FP“ as name for the corresponding Allevo layout and simultaneously as abbreviation for the version.

This constant allows to modify this default behavior.

 

 

Note:

Layout “FP“ and version “FP“ are not obligatorily required to be available in the system; it is however recommended to create at least the Allevo layout FP (without further data), in order to obtain an overview of objects that have been posted by FP so far via the status management.

 

FP cancels the posting if an object has been blocked for planning via Allevo status 4 (=completed) or higher.

A different behavior may be defined via the constant STATUS_INFO. The following entries are possible in column Value from:

1              Status is NOT set automatically, must be entered explicitly via the Allevo status management before. If the status is invalid (other than 01,02 or 03), no postings will be performed; instead, an error message will appear in the FP log.

2              Posting is also performed if Allevo status is 4 = completed; the entry on the status will automatically be reset to 03.

The column Value to may contain an individual abbreviation for layout and version (as alternative standard entry „FP“). Entries must be made separated by comma; e.g. „KST,0“ to write into layout KST using version 0. With an entry „?“ on layout and/or version, FP takes the respective specification from the layout provided by the Allevo call.

 

Switch Scheme in Cost Component Splitting

 

SWITCH_LAYOUT

* available from version 3.4

 

Entry for the switch scheme in cost component splitting when planning activities, capacities and prices (allocation type AT).

 

Enter the switch scheme in column Value from.

 

Note:

See also constant FD_SWITCH_LAYOUT.

 

Layout for Reading Pay Scale Indicators

 

TARKZ_LAYOUT

* from FP version 3.1 no longer relevant (see constant ALLEVO_ACTIVE)

 

Reference to the Allevo layout that the pay scale indicator is read from (possibly various, see Allevo constant TARIF_KZ). This indication is only necessary if FP activities shall be planned without prices, so that existing prices shall be adopted from SAP.

Enter the Allevo layout in column Value from.

 

Note:

If the entry on the Allevo layout is missing, FP will search for the indicators in the * layout.

 

Multiple Years Planning: Specification of the Version

 

VERSIONy

The FP planning feature may be extended to up to 10 additional years, provided that the satellite includes supplementary fields for the fix and possibly variable quantities.

The constant VERSION0 to VERSION9 contains the specification of the respective version in multiple years planning.

 

Note:

The parameters FD_QNTY_FIXy, YEARy and COLDEFy (y from 0 to 9) for further annual planning form a unit that is to be maintained in the constants.

In former versions, also the mapping VERSIONy had to be established. From FP version 3.1, the version of the main planning year will be used if the entry on the version is missing. (interesting e.g. for budget planning with the version usually being ignored anyway).  

 

Default Value for Version

 

VERSN_INITIAL

* Only valid up to FP version 3.0

 

The constant was replaced by PLANVERSN (see documentation there).

 

Multiple Years Planning: Specification of the Year

 

YEARy

The FP planning feature may be extended to up to 10 additional years (multiple years planning), provided that the satellite includes supplementary fields for the fix and possibly variable quantities.

The constant YEAR0 to YEAR9 defines the year that plan data shall be applied for. There are two types of entry in column Value from:

·         Direct entry of the year (4 digits) or

·         Relative to the main planning year (e.g. +1). FP automatically recognizes the relation by the leading sign (+ or -). This feature is available from version 3.3.29.

 

Note:

The parameters FD_QNTY_FIXy and YEARy or COLDEFy (with y from 0 to 9) for further annual planning form a unit that is to be maintained in the constants.

 

 

Main Planning Year

 

YEAR_INITIAL

* Only valid up to FP version 3.0

 

This constant was replaced by PLANYEAR (see documentation there).