Activate the Direct Call from the Allevo main module

ALLEVO_ACTIVE

* effective from version 3.3

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

Enter X instead of R in order to call up the scheme in the satellite for reading data from CO/PA only and enter W for planning only in CO/PA.

In case that all column definitions of an Allevo layout are being used to determine the Read/Write parameters (and the corresponding interface table is completely blank), you may also use T to determine that all data per column definition shall be transferred to CO/PA at the same time as a table (according to the „total-or-single-marking“ in the last column of the Read/Write parameters).

When adopting plan data in the Allevo main module, all CO/PA schemes with the active constant ALLEVO_ACTIVE are being executed.

Optionally, you may restrict the execution of a scheme to single Allevo layouts: enter the layout in column Value to (possibly multiple layouts, separated by comma).

Note:

If you do not enter any scheme in the selection parameter upon Allevo CO/PA execution via the dialog transaction, again all schemes with the active constant ALLEVO_ACTIVE will be executed. If you enter * for the scheme, all satellite schemes will be executed!

For some constants, you will need reference to an Allevo layout when executing Allevo CO/PA (e.g. for reading an Allevo column definition): the layout will be included when calling directly from the Allevo main module; in the dialog mode, Allevo CO/PA uses the first layout in column Value to (or the * layout, if none is stored in the constant).

Enter Plan Data with Different Currency Erfassung

CURRENCY

* effective from version 3.0

This constant allows to enter plan data using a currency different from the currency of the operating concern or company code. When using this constant, all values of the satellite are assumed to be in the same currency.

If required, the Allevo CO/PA interface automatically performs a translation to the currency of the operating concern (as a basis for the posting via the used SAP BAPI). See constant EXRATE_TYPE for the exchange rate.

Activate this constant by entering the desired currency in column Value from.

Note:

Alternatively, the currency may be adopted from a satellite field (see constant FD_CURRENCY). Data may then be entered using individual currencies per satellite row.

If none of the constants is maintained, plan values must be entered in accordance with the default settings on the currency in the SAP system (see manual „Use of currency“).

Distribution of Plan Values

DISTRIBUTION

The Allevo CO/PA interface uses two different distribution functions that may be performed automatically before posting a plan value.

1. Distribution annual values to periods

Planning for CO/PA is often performed based on annual values per value field. In the standard case, entries will be distributed equally to periods. However, it may be desired to specify the distribution to periods (months) individually.

2. Distribution based on any characteristic

Planning for CO/PA may be performed less in detail than desired in the operating concern. It is possible to distribute planned values/quantities according to self-determined rules based on any characteristic (e.g. period values to sales days).

Both features are activated via the constant DISTRIBUTION and configured using additional tables (see manual).

· Value from contains the name of the additional table maintaining the percentages.

· Value to contains a field name prefix.

For the “Distribution based on any characteristic“, you must additionally enter the CO/PA characteristic used for the distribution in the field assignment and enter “D” in the RWX column.

If there is made in this characteristic field, the program will try to perform the „Distribution of annual values to periods“ in case that the CO/PA field PERDE is NOT assigned in the used scheme and MONTH_ACTIVE is not active, that is: annual values are planned.

Note:

The required settings are explained in detail in the manual of the CO/PA interface (see sections „Distribution of annual values to periods“ and „Distribution based on any characteristic“ ).

Course Type for the Translation of Currencies

EXRATE_TYPE

* effective from version 3.0

This constant determines the course type for the translation of currencies applying for example if a currency different from the one of the operating concern is set via the constant CURRENCY.

Enter the course type in column Value from, e.g. „M“ for standard translation using the average rate.

Note:

If you do not enter any course type, Allevo will adopt the entry from the attributes on the plan version in the operating concern (table TKEVS).

See the notes on the constant CURRENCY for further details.

Multiplication of Interface Data with a Factor

FACTOR

* effective from version 3.3.22

This constant allows multiplying values of the CO/PA interface with any factor. The feature is available both during reading and writing.

· Enter the desired factor in Value from. In order to e.g. reverse the sign of the value, enter “-1”.

· Use the column Value to to enter the CO/PA fields separated by comma that the factor shall apply for. E.g. „RABAT,PRABA“ to display these discount fields as negative.

An important application of this constant results especially for the reading function of the Allevo CO/PA interface: it is possible to store multiple value fields in the same satellite field in the mapping. In this case, Allevo automatically adds up contents. By using the constant FACTOR, you may combine addition and subtraction.

Example:

If the value fields ERLOS, RABAT and PRABA are stored in a common satellite field, the calculation for the corresponding satellite field would be the following (using the entries above): ERLOS minus RABAT minus PRABA.

Field Mapping for Plan Values of Individual Currency

FD_CURRENCY

* effective from version 3.3 (before FLD_WAERS)

This constant allows to enter plan values using an individual currency per satellite data row. Features correspond to the ones of constant CURRENCY (see documentation there). The field containing the relevant currency is adopted from the satellite.

Enter the name of the satellite field in column Value from.

Note:

Alternatively, the currency may be predefined (see constant CURRENCY).

If none of the constant is maintained, the CO/PA interface will stick to the settings on the operating concern (see manual „Use of currency“).

Value and Quantity Field Mapping („FP Mode“)

FD_ELEMENT

* effective from version 3.4.35

This constant allows to use a different satellite structure for posting to CO/PA. Characteristics of different value and quantity fields are no longer provided by separate table columns but only by a single column. CO/PA value and quantity field names are assigned to these values/quantities in a different column.

These two table columns are defined by the constant FD_ELEMENT as follows:

· Enter the satellite column containing the CO/PA value and quantity field name in Value from.

· Enter the satellite column containing the characteristics, meaning values and quantities, in Value to. These may be period columns (without period suffix) as well as an annual column. Annual values may still be distributed using a distribution table. Annual values may also still be distributed using a distribution table.

Note:

There should be no value (“V“), quantity (“Q“) and unit fields (“U“) mapped in table „Field assignment“ of the CO/PA constant maintenance.

Since there must always be a unit included when posting quantities, also the constant FD_UNIT is required in this case (see there). This is not required if only values are posted.

The setting ‚T‘ in column ‚TS‘ of the Read/Write parameter triggers an aggregation routine merging the related data records. In doing so, this routine also ensures that satellite rows are added up with identical characteristic combinations.

Mirror Partner Object for Plan Data

FD_SENDER

* effective from version 3.3 (before: FLD_SENDER)

The CO/PA interface offers a feature to mirror satellite data (call via button |Mirror Plan Data| in constant maintenance; see also the corresponding section in the manual) in order to display sender recipient relationships.

Two satellite tables that are identical in their structure are required for this feature. Two functions are being performed:

· Contents of two satellite fields are exchanged: this is first the field COOBJECT (sender), the name of the second field (receiving object) is to be entered in column Value from..

· In addition, signs are reversed for data of relevant value fields (to be entered for „Field assignment value fields“).

Note:

Source and target table require an identical table append. The append must contain a field ZZ_STATUS (NUMC1).

Status of a Data Record in the Satellite

FD_STATUS

* effective from version 3.3 (before: FLD_STATUS)

The CO/PA interface may be started in a way that only data records with modifications in their contents are posted (see flag „Only unmarked“ in the start screen of the interface program).

A status field must be available in the satellite for this purpose (field type CHAR1): 1 in this field blocks the data record for processing.

Enter the name of the status field in column Value from of constant FD_STATUS.

From the perspective of the planning process, there are two options to handle the status field of the satellite table:

· It will simply be left out on the Excel side. This leads to the field being blank again each time data in the cost center are being updated.

· The field is operated actively on the Excel side, either through manual entry by the planer or by means of a formula.

Note:

If no status field and no mapping is available, each data record will be posted.

Unit Field Mapping („FP Mode“)

FD_UNIT

* effective from version 3.4.35

This constant is usefully applied only in interplay with constant FD_ELEMENT (see there). It is essential when addressing also quantity fields via this constant, since there must always be a unit included for these fields. Analogously, one column for the unit field names and one for their characteristics are required.

These two table columns are defined by the constant FD_UNIT as follows:

· Enter the satellite column containing the CO/PA unit field names in Value from.

· Enter the satellite column containing the characteristics, i.e. the units, in Value to.

Note:

There should be no value (‘V‘), quantity (‘Q‘) and unit fields (‘U‘) mapped in the table “Field assignment” of the CO/PA constant maintenance.

Display of Period Value sin Columns

MONTH_ACTIVE

* effective from version 3.3.22 (extended in 3.4)

Normally, the CO/PA interface expects data of single periods in different satellite rows. In single cases, it may be useful to display data in separate satellite columns (12 period columns, e.g. for a simplified entry of plan data). The constant MONTH_ACTIVE must be active for this purpose.

The display of period values in columns is available for reading and writing (planning). Also working simultaneously with annual values for different value fields is possible.

The constant MONTH_ACTIVE is set up as follows:

· Entry X in column Value from activates conversion to period values. The program then tries to interpret quantity and value fields (RWX column = “V” or “Q”) as prefix of a satellite append field in the field assignment: if 12 fields carrying this prefix as well as ending 01 to 02 are available in the satellite, period data are stored or expected there.

· Entry X in column Value to for the constant allows a defined sorting of read CO/PA period data, which is useful especially with new SAP versions (see notes below, „Value from“ does not need to be active at the same time).

Note:

When using the CO/PA reading feature, the characteristic PERDE must be active for reading („R“) for the use of MONTH_ACTIVE.

See the Allevo CO/PA manual for further details.

* effective from version 3.4.5

The BAPI for reading CO/PA data usually provides them sorted (by periods). This sort sequence is not always ensured in new SAP versions (e.g. for HANA). This may lead to unwanted results especially when importing data to period columns.

In this case, resorting data before adopting them to the satellite is necessary. This may be accomplished with an entry X in column Value to of constant MONTH_ACTIVE. MONTH_ACTIVE itself does not need to be active here, resorting may therefore also be performed for other purposes. However, it is recommended to activate sorting only if necessary, that is: if test runs showed that data are returning from the SAP system in an unsorted way.

Operating Concern

OP_CONCERN

* effective from version 3.0

Defines the operating concern that data shall be read from and plan data shall be posted to.

Enter the name of the operating concern in column Value from.

Note:

Mandatory field

Currency Key for Reading Actual Data

PALEDGER

* effective from version 3.0

The currency key is only required to read actual data. Enter the currency key in column Value from.

Typical currency keys in the SAP system:

10 Company code currency

12 Company code currency, profit center valuation

B0 Operating concern currency

B2 Operating concern currency, profit center valuation

Note:

The currency key is e.g. the basis for the default suggestion of the currency when posting plan values (according to operating concern or company code). Der Währungsschlüssel ist z.B. Basis für den Standardvorschlag zur Währung bei Buchung von Planwerten (nach Ergebnisbereich oder Buchungskreis).

* effective from version 3.4.35

Reading actual data from the account-based operating concern requires another parameter, the valuation type. It is by default set to 0. If anything else is desired, you may adjust this in Value to of the constant PALEDGER.

0 Legal Valuation

1 Group Valuation

2 Profit Center Valuation

Store Messages in Application-Log (SLG1)

SAVE_LOG

Allevo CO/PA allows 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 Flexible Planning 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.

When calling from the Allevo main program, control is performed via the Allevo constant MESSAGE_LEVEL (see documentation Allevo constants).

Note:

Separately (and independently), the screen output may be controlled via the parameter „Output level“ in the CO/PA selection screen.

Type of the Operating Concern

TYPE_OF_PA

* effective from version 3.5

Normally, Allevo CO/PA works with a costing-based operating concern. This applies if constant TYPE_OP_PA is not being used or if the entry in Value from is blank.

Reading and planning with a costing-based operating concern may be activated via the constant TYPE_OF_PA. Possible entries in column Value from are:

1. For the costing-based operating concern: 1 or C(osting-based)

2. For the account-based operating concern: 2 or A(ccount-based)

Note:

In Allevo versions 3.3. and 3.4, planning in the account-based operating concern was already possible while reading was only possible from the costing-based operating concern.

Type of Business Transaction

VRGAR

* effective from version 3.0

Defines the type of business transactions that shall be used to read or write plan data. Hier ist die Vorgangsart festgelegt, mit der die Plandaten gelesen bzw. geschrieben werden sollen.

Business transactions are defined separately:

· Enter the transactions relevant for reading in column Value from (e.g. F for invoice data or D for overhead costs): multiple entries are possible (separated by comma).

· During writing, postings will be made using the transaction type entered in column Value to. The transaction type can also be taken from a satellite field (mapping e.g. via ZIPP_VRGAR): this field must be flagged (RWX flag Z, X or W). The entry in the satellite replaces the constant.

Note:

The constant VRGAR is today interpreted differently than in the previous version (up to version 2.9). This possibly needs to be considered for migration.