Activate ProCED for calling from Allevo

 

ALLEVO_ACTIVE 

ProCED can be started in three ways:

1.     Via the dialog transaction /KERN/IPPPROCED

2.     Via object-specific report transactions, such as /KERN/IPPPROCED_PR (available as of version 3.1). Variants can be saved in order to simplify recurring selections. Dort können Varianten hinterlegt sein zur Abbildung von Standard-Aufrufen.

3.     ProCED can also be called directly from Allevo: in this case, data selection is carried out for the specific object selected in Allevo.

For the third case, the constant ALLEVO_ACTIVE needs to be maintained on the ProCED-side:

·         ProCED is actiated for direct calling with an X in the field Value from

·         The Allevo planning layout for which the automatic execution is to be carried out needs to be entered in the field Value to. Multiple entries are possible (entries seperated by comma).

 

Note:

When calling directly from Allevo, the relevant satellite for ProCED also needs to be activated in the Allevo-satellite assistant. (see Allevo-constant ACTIVE_PROCED).

 

Restrict data selection via CO business transactions

 

BUSINESS_TRANS

General constants: By entering the CO business transactions in Value from, the selection of data is restricted to only these business transactions.

 

Note:

 

 

Filter objects by status information Objekte über die Statusangabe filtern

 

CHECK_STATUS

* as of version 3.1

ProCED usually determines its results list based on postings found within a given time range. Via the constant CHECK_STATUS, the list of objects can also be restricted to predefined status information.

The constant uses information that is usually made available via the constant FD_STATUS_LIST in order create a filter (i.e., only those objects that match the conditions of the filter are transferred to Excel).

In the field Value from, enter the status information which are to be included. Depending on the object type, there are a number of different possible cases:

·         Internal orders and WBS elements (OR,PR):
In this case, there is a system status exists directly in the respective master record. Value from can contain one or more key values from the system status. The identification codes are always in language EN according to the entries in table TJ02T. Multiple entries must be separated by comma (e.g., CRTD, SETC). Checking is done as a positive list, i.e. Only those objects path the filter, for which one of the entered status keys is matched.

·         Profit Center (PC):
The field "Lock Indicator" in the Profit Center master record is evaluated (CEPC-LOCK_IND) in order to filter out locked Profit Centers. In this case, an X  needs to be entered in Value from for the constant CHECK_STATUS.

·         Cost center (KS):

In this case a system status exists directly in the respective master record.

The constant FD_STATUS_LIST provides a list of fields for lock planning as a replacement for status information. Keys are the field names of CSKS that have no lock flag (see the F1 documentation for FD_STATUS_LIST).

Value from for CHECK_STATUS can include multiple key values in this case as well. The query is made as with the system status for OR and PR: only those objects, for which one of the entered status keys is saved will pass through the filter. You then enter which planning is desired (i.e. the fields without lock planning as a characteristic for transferring to Allevo).

Example: in the constant, „PKZKP,PKZKS“ is entered. A cost center will only be filtered out if both locks are set (i.e. if neither primary nor secondary cost planning is desired)

 

Note:

See the documentation for the mapping constant FD_STATUS_LIST.

Some of the functions described are only available as of version 3.1.

 

Selection via credit or debit indicators

 

DEBIT_CREDIT_IND

In this constant, the credit and debit indicators can be permanently saved for the selection of COSS and COSP data.

Background: SAP allows the receiver and sender to plan different quantities initially. As a result, for each debit posting a correction record for the credit posting appears for the sender. In this correction record, the sender and the source object are the same, the business transaction is RKP3 (same as the receiver posting), but the credit indicator is H.

The constant is activated with an X in the column Value from.

In the column Value to, enter the desired indicators (comma separated for multiple entries). Valid entries include A, H, L, and S according to the language independent requirements in the table TKABE: no conversion is executed.

 

Note:

See also the constant BUSINESS_TRANS and VALUE_TYPE for the restriction by business transaction and value type.

 

Restrict data selection via CO business transactions

 

DEFAULT_KSTAR

General constant: In addition to the cost elements of the result of the actual selection, additional cost elements can be taken into account using this parameter.

 

The following possibilities are available for controlling via Value from:

§  0  = no additional cost elements

§  1 = for those objects (WBS elements, internal orders, …), for which cost elements have already been determined via selection, the cost elements entered in Value to are also assigned

§  2  = all objects are assigned to the cost elements assigned in Value to

§  3 = only for those objects for which NO cost elements were determined by selection, cost elements that are entered in Value to are assigned.

 

Note:

The definition of this constant can be made in the ProCED start dialog under “additional data”. The entries there are automatically transferred to the constant.

 

Statistical key figures (default)

 

DEFAULT_STAGR

General constant analog to DEFAULT_KSTAR (see the description there), except that here it relates to statistical key figures.

 

Note:

 

 

Field selection from the order master record

 

FD_AUFK_1

Free field selection from the order master record (table AUFK). In Value from enter the field of the respective satellite table; in Value to enter the field from the AUFK table.

Note:

Only available for object type OR

 

Field selection from the order master record (2)

 

FD_AUFK_2

Free field selection 2 (see FD_AUFK_1)

 

Note:

Only available for object type OR.

 

Field selection from the order master record (3)

 

FD_AUFK_3

Free field selection 3 (see FD_AUFK_1)

 

Note:

Only available for object type OR.

 

Field selection from the order master record (4)

 

FD_AUFK_4

Free field selection 4 (see FD_AUFK_1)

 

Note:

Only available for object type OR.

 

Field selection from the order master record (5)

 

FD_AUFK_5

Free field selection 5 (see FD_AUFK_1)

 

Note:

Only available for object type OR.

 

Short text description for OR

 

FD_AUFK_K

Short text description for the order (language dependent)

 

Note:

Only available for object type OR.

 

Key of the OR

 

FD_AUFNR

Short text description of the order (language dependent)

 

Note:

Only available for object type OR.

 

Short text description for Profit Center

 

FD_CEPCT_K

Short text description for Profit Center (language dependent)

 

Note:

Only available for object type PC (Profit Center).

 

Long text description for Profit Center

 

FD_CEPCT_L

Long text description for Profit Center (language dependent)

 

Note:

Only available for object type PC (Profit Center)

 

Field selection from the Profit Center master record

 

FD_CEPC_1

Free field selection from the master record for Profit Center (table CEPC). In Value from enter the field of the respective satellite table, in Value to enter the field from the CSKS table.

Note:

Only available for object type PC (Profit Center).

 

Field selection from the Profit Center master record (2)

 

FD_CEPC_2

Free field selection 2 (see FD_CEPC _1).

 

Note:

Only available for object type PC (Profit Center).

 

Field selection from the Profit Center master record (3)

 

FD_CEPC_3

Free field selection 3 (see FD_CEPC _1).

 

Note:

Only available for object type PC (Profit Center).

 

Field selection from the Profit Center master record (3)

 

FD_CEPC_4

Free field selection 4 (see FD_CEPC _1).

 

Note:

Only available for object type PC (Profit Center).

 

Field selection from the Profit Center master record (3)

 

FD_CEPC_5

Free field selection 5 (see FD_CEPC _1).

 

Note:

Only available for object type PC (Profit Center).

 

Field selection from the cost center master data

 

FD_CSKS_1

Free field selection from the cost center master data. In Value from, enter the field of the satellite table, in Value to enter the field from the CSKS table.

Note:

Only  available for object type KS.

 

Field selection from the cost center master data (2)

 

FD_CSKS_2

Free field selection 2 (see FD_CSKS_1)

 

Note:

Only  available for object type KS.

 

Field selection from the cost center master data (3)

 

FD_CSKS_3

Free field selection 3 (see FD_CSKS_1)

 

Note:

Only  available for object type KS.

 

Field selection from the cost center master data (4)

 

FD_CSKS_4

Free field selection 4 (see FD_CSKS_1)

 

Note:

Only  available for object type KS.

 

Field selection from the cost center master data (5)

 

FD_CSKS_5

Free field selection 5 (see FD_CSKS_1)

 

 

Note:

Only  available for object type KS.

 

Short text description of the cost center (KS)

 

FD_CSKT_K

Short text description (language dependent)

 

Note:

Only  available for object type KS.

 

Long text description of the cost center (KS)

 

FD_CSKT_L

Long text description of the cost center (language dependent)

 

Note:

Only  available for object type KS.

 

Fieldname for the elimination Profit Center

 

FD_ELIM

Name of the field for the elimination Profit-Center (only GLPCT)

 

Note:

Only  available for object type PC

 

Fieldname for the elimination Profit Center text description

 

FD_ELIM

Name of the field for the short text description of the elimination Profit-Center (only GLPCT)

 

Note:

Only  available for object type PC

 

Preallocate fields with a fixed value

 

FD_FIX_VALUE_X

·       * as of Allevo-version 3.3

Usually, ProCED transfers additional information of a posting record from the corresponding SAP tables. In special cases it may be useful to specify the contents of a satellite field (e.g., for supporting Allevo rule planning).

The definition of these fields can be made via the constant FD_FIX_VALUE_X, where X is entered as a number between 0 and 9, e.g. FD_FIX_VALUE_0, FD_FIX_VALUE_1... (10 total entries are possible for this constant).

When using this constant, the relevant satellite field needs to be entered in the column Value_from: in this case the F4-value help displays a list of all fields in the current satellite table. The contents to be written to this satellite field must be entered in the column Value_to.

Examples:

Note:

F1 help is available for each constant

 

Text descriptions for hierarchy levels

 

FD_HIERT_X

If ProCED is executed via the object types by specifying a group, the fields in which the respective hierarchy structures of the selected group are entered can be defined in the satellite table. Thus, for each object, you can see which groups it is assigned to. The constant FD_HIERT_X can be used to display the texts of a node.

The constants FD_HIER_1 to FD_HIER_9 can be used; dependent on the number of necessary levels. FD_HIER_1 always contains the top node key.

 

Note:

See also FD_HIER_X for the node key.

 

Displaying hierarchy levels

 

FD_HIER_X

As long as Allevo ProCED is executed via object types with the specification of a group, the fields in which the respective hierarchy structures of the selected group are entered can be defined in the satellite table. Thus, for each object, you can see which groups it is assigned to.

The constants FD_HIER_1 to FD_HIER_9 can be used; dependent on the number of necessary levels. FD_HIER_1 always contains the top node key.

Note:

See also FD_HIERT_X for the text description of the node.

 

Field name for investment program position (internal representation)

 

FD_IMZO

·       * as of Allevo-Version 3.3

Name of the field for the investment program position of the object (SAP internal display).

In the column Value to the year in which the assignment is to be searched can be entered.

 

Note:

This field is only filled with object type PR for ProCED.

 

Field name for investment program position (external representation)

 

FD_IMZO_EXT

·       * as of Allevo-Version 3.3

Name of the field for the investment program position of the object in SAP external display.

 

Note:

This field is only filled with object type PR for ProCED.

 

Field name for the key of the cost element or statistical key figure

 

FD_INFOOBJ 

Name of the field for the cost element or statistical key figure, and if necssary, the cost element group if the constant NODE_AGGREGATION is active.

 

Note:

 

 

Field name for the long text description of the cost element or statistical key figure

 

FD_INFOOBJ_LTXT

Long text description of the cost element or statistical key figure. If the corresponding cost element has been added as the default value via the start dialog, the text description is only filled if a valid data master record is saved

 

Note:

See also FD_INFOOBJ_TXT for the short text description

 

Field name for the short text description of the cost element or statistical key figure

 

FD_INFOOBJ_TXT

Short text description of the cost element or statistical key figure. If the corresponding cost element has been added as the default value via the start dialog, the text description is only filled if a valid data master record is saved

 

Note:

See also FD_INFOOBJ_LTXT for the long text description

 

Field name for the year and period of the last update

 

FD_JAHRPER

Field name for the year and period of the last update

Background:

In order to avoid unnecessary run times, it is possible to specify that ProCED should only be executed with the Allevo main program: for this, ProCED compares the to-period according to CX_RR with the period in which ProCED was last executed. ProCED is only started if the to-period according to CX_RR is greater than or equal to the period of the last ProCED run. The date is entered in the format MMM.YYYY in Value from (only on a monthly basis).

This function is activated by entering an X in the field Value to of the constant FD_JAHRPER.

Note:

 

 

Field name for the cost element type or statistical key figure

 

FD_KATYP

Name of the field for the cost element type or the statistical key figure type (not for PC).

Note:

 

 

Cost center key

 

FD_KOSTL

Cost center key

 

Note:

Only available for object type KS.

 

Indicator for lock planning of the cost center

 

FD_LOCK

* available as of version 3.1

The corresponding field in the satellite table contains an X if all planning locks (PlnPri, PlnSek, PlnErl) are active in the master record of the cost center.

In Value from enter the field of the satellite table.

In Value to you can enter a year for which the check of the locks should be made,

 

Note:

The lock indicator is also assigned if the cost center for the entered year is not valid (no records will be found).

 

Field name activity type

 

FD_OBJACT

Name of the field for the activity type.

 

Note:

This field is only filled if the constant KS_ACTIVITY_MODE is active and starting with a “KS” object type.

 

Field name object number

 

FD_OBJECT

Name of the field for the object number (is filled for all object types).

 

Name:

This field is mostly used when the constant KS_ACTIVITY_MODE is activated.

 

Field name for object info type

 

FD_OBJINFOTYPE

Name of the field for the information type of the object. Possible values: "KSTAR" for cost elements, "SAKNR" for account Profit Center or "STAGR" for statistical key figures.

 

Note:

ProCED adds prefix “DEFAULT”, if corresponding value is created via defaults (e.g. DEFAULT_KSTAR).

 

Field name object (internal display)

 

FD_OBJKEY

Name of the field for the object in the SAP internal display (is filled  for all object types).

 

Note:

. This field is mostly used when the constant KS_ACTIVITY_MODE is activated.

 

Field name object (external display)

 

FD_OBJKEY_EXT

Field name for the object (external display).

 

Note:

This field is only filled if the constant KS_ACTIVITY_MODE is activated and starting with the object type “KS”

 

Field name object type

 

FD_OBTYPE

Name of the field for the object type (is filled for all object types).

 

Note:

This field is mostly used when the constant KS_ACTIVITY_MODE is activated, if different object types are possibly saved in a partner object.

 

Field name partner object

 

FD_PAROB

Name of the field for the partner object.

 

Note:

 

 

 

Field name for cost center quota in partner object

 

FD_PAROB_KOST

Name of the field for the cost center quota in a partner object

Note:

 

 

Field name partner object activity type

 

FD_PAROB_LSTA

Name of the field for the activity type quota in a partner object.

Note:

 

 

Profit Center key

 

FD_PRCTR

Key of the Profit Center

 

Note:

Only available for object type PC (Profit Center)

 

Field selection from the project master data

 

FD_PROJ_1

Free field selection from the project master data (table PROJ). In Value from enter the field of the satellite table, in Value to enter the field from the PROJ table.

Note:

Only available for object type PR

 

Field selection from the project master data (2)

 

FD_PROJ_2

Free field selection (see FD_PROJ_1)

 

Note:

Only available for object type PR

 

Field name for the external ID (project)

 

FD_PROJ_PSPID

Name of the field for the external ID of the hierarchically superior project/start object (as in PROJ-PSPID; displayed without formatting rules set in Customizing, e.g. "T3020").

Equivalent to FD_PSP_POSID on the WBS level.

 

Note:

Only available for object type PR

 

Field name for the external ID (project)

 

FD_PROJ_PSPIDF

Name of the field for the external ID of the hierarchically superior project/start object (as with FD_PROJ_PSPID, but with inclusion of the formatting rules from Customizing, e.g. "T-302.0).

 

Note:

Only available for object type PR

 

Field name for the external ID (project)

 

FD_PROJ_TXT

Name of the field for the short text description of the hierarchically superior project.

                                 

Note:

Only available for object type PR

 

Field name for the start object

 

 FD_PRPSP_ENTR

Name of the field for the start object (PR or WBS element).

PR if "Project" is entered in the field. The object number will then be shown.

Note:

Only available for object type PR.

 

Field selection from the WBS master data

 

FD_PRPS_1

Free field selection from the WBS master data (table PRPS). In Value from enter the field of the satellite table, in Value to enter the field of the PRPS table.

Note:

Only available for object type PR.

 

Field selection from the WBS master data (2)

LOGO

FD_PRPS_2

Free field selection 2 (see FD_PRPS_1)

 

 

Note:

Only available for object type PR.

 

Field selection from the WBS master data (3)

 

FD_PRPS_3

Free field selection 3 (see FD_PRPS_1)

 

Note:

Only available for object type PR.

 

Field selection from the WBS master data (4)

 

FD_PRPS_4

Free field selection 5 (see FD_PRPS_1)

 

Note:

Only available for object type PR.

 

Field selection from the WBS master data (5)

 

FD_PRPS_5

Free field selection 5 (see FD_PRPS_1)

 

Note:

Only available for object type PR.

 

Level of the WBS elements in the project hierarchy

 

FD_PSP_LEVEL

·       * as of Allevo-version 3.4

Level of the WBS element in the project hierarchy

Note:

Only available for object type PR.

 

Field name for the object number

 

FD_PSP_OBJNR

Name of the field for the object number of the (dissolved) WBS element (as in the table field PRPS-OBJNR; usually comprised of "PR" and the internal number of the WBS element in POSNR)

Note:

Only available for object type PR.

 

Field name for the external ID (WBS element)

 

FD_PSP_POSID

Name of the field for the external ID of the WBS element, e.g., in the table field PRPS-POSID (displayed without formatting rules set in Customizing, e.g. "T3020C01").

 

Note:

Only available for object type PR.

 

Field name for the external ID (WBS element) (2)

 

FD_PSP_POSIDF

Name of the field for the external ID of the WBS element, e.g., in PRPS-POSID (displayed without formatting rules set in Customizing, e.g. "T-3020.C01")

 

Note:

Only available for object type PR.

 

Field name for the internal ID (WBS element)

 

FD_PSP_POSNR

Name of the field for the internal ID of the WBS element (e.g. in PRPS-POSNR, numeric with 8 positions)

 

Note:

Only available for object type PR.

 

Field name (WBS element)

 

FD_PSP_TXT

Name of the field for the text of a WBS element

 

Note:

Only available for object type PR.

 

Field name for data record source

 

FD_SOURCETAB 

Name of the field for the data record source (possible contents: COSS, COSP, COSR, and empty for default KSTAR or STAGR)

By using this constant, you can see from which source table the respective data record is generated in the satellite table.

Note:

 

 

Allocation of status information to an object

 

FD_STATUS_LIST

* as of Allevo version 2.9 (expanded in v. 3.3.22)

This constant allows the user to access status information in the master record of the current object. This information can be especially useful for filtering by objects that have a particular status on the Excel-side. 

In the column Value from, enter the name of the satellite field that should contain the status information. Effects of the constant include:

·         For object types OR (= internal orders) und PR (= WBS elements), the display is the same as with the system status in the respective master record, e.g., “REL SETC”, the language is always EN, with entries separated by a space (see also SAP entries in the tables JEST and TJ02T).  

·         For object type KS, information regarding locks are shown (see details below).

 

For object types PR and OR, an entry in the Value to column controls the detail level of the transfer with the following options:

·         Empty        Transfer system status only

·         U               Transfer user status only

·         X               Transfer system status and user status simultaneously

 

Note:

Alternatively, the constant CHECK_STATUS allows you to directly set a filter for the status information, in order to reduce the number of transferred objects (see F1 documentation for this constant).

 

New as of Version 3.1:

For object type KS (= cost center), there is no status information in the master record. Therefore, in this case, alternative information regarding locks is provided when using this constant (if there are any locks in the master record).

Positive logic applies in this case as well: All field names of CSKS that have no lock flag are listed (separated by a space).

Example: If planning for primary costs to the cost center is allowed (i.e. not locked), then "PKZKP" is provided as info via the constant FD_STATUS_LIST.

 

New as of Version 3.3:22

Provision of user status in addition to system status for WBS elements and internal orders

Field name source object activity type

 

FD_UOBJACT

Field name for the source object activity type

 

Note:

This field is only filled when KS_ACTIVITY_MODE  is activated and starting with the object type “KS”.

 

Field name source object

 

FD_UOBJECT

Field name for the source object.

 

Note:

This field is only filled when KS_ACTIVITY_MODE  is activated and starting with the object type “KS”.

 

Field name source cost center

 

FD_UOBJKEY

Field name for the source cost center

 

Note:

This field is only filled when KS_ACTIVITY_MODE  is activated and starting with the object type “KS”.

 

Field name source object type

 

FD_UOBTYPE

Name of the field for the source object type

 

Note:

This field is only filled when KS_ACTIVITY_MODE  is activated and starting with the object type “KS”.

 

Validity of a cost center or Profit Center

 

FD_VALID_TO

* available as of Version 3.1

 

This constant shows the date until which the Profit Center or cost center is valid.

In Value from enter the field of the respective satellite table.

 

Note:

Only available for cost center or Profit Center.

 

Group hierarchy for additional read objects

 

HIERARCHY_GROUP

Background: ProCED can now also read data for object types that do not correspond to the starting object type (e.g. with READ_ASSIGNED_OR). Since the object type is different, the assignment within the hierarchy fails.

Via the constant HIERARCHY_GROUP you can define a group that, if the object type differs, reflects the relevant hierarchy of the starting group.

In Value from, enter the group for which the hierarchy should be determined. 

 

Read posting relationships from the sender’s perspective

 

KS_ACTIVITY_MODE 

ProCED usually reads posting relationships for which the start object (e.g., the cost center) is entered as the receiver (receiver’s perspective).

For object type “KS”, the constant KS_ACTIVITY_MODE allows you to see posting relationships from the opposite perspective: the display of a cost center from the sender’s perspective. In this case, you select data via the start object in the COSS table (USPOB field in COSS).

The constant KS_ACTIVITY_MODE is activated with an X in the field Value from.

Optionally, via an entry in Value to, you can set a restriction for certain receiver object types: thus, only rows with the specified object type are transferred to the satellite table (entries made as a comma separated list, e.g., “OR,PR”).

In this mode, also constants with additional information about receiver objects are filled (e.g. short and long text descriptions). This function is only available as of version 3.3.

Note:

This also applies to the freely definable master record fields (e.g., FD_AUFK_1 for orders). In order to use these fields, the respective field has to be entered for the constants for the start object type and be provided with mapping in the satellite table field.

Exception: The fields FD_PROJ_1, FD_PROJ_2 and FD_PROJ_TXT are not read as data for the project of a WBS element.

 

Language of the text descriptions for cost elements or statistical key figures

 

LANGU_KSTAR_FIX

Normally, ProCED transfers the text descriptions of a cost element or statistical key figure in the language of the currently logged on user (logon language). With this constant, you can define the language to be used.

The constant is activated with a two-character language key in the field Value from (e.g., EN to transfer English descriptions)

Activate MultiPage mode

 

MULTIPAGE_MODE 

If ProCED is called from the dialog (i.e. not automatically via the Allevo-interface), then the entries in a satellite table are made into a representative object (e.g., to the first cost center in a group). 

In MultiPage-mode, on the other hand, the data for the respective current object must be saved, in order to read it correctly per sheet in Allevo. To achieve this, the ProCED constant MULTIPAGE_MODE must be activated (activate with an X in the field Value from).

Read object type from PC from table GLPCT

 

NEW_GL

For object type PC, reading is done from table GLPCT by default. This constant switches to the new General Ledger; thereby reading is done with the table FAGLFLEXT (enter X in Value from).

 

Note:

Only available for object type PC (Profit Center).

 

Aggregation of cost element groups

 

NODE_AGGREGATION

In Allevo it is possible to plan for cost element groups or for the saved representative cost element. In this case, the posting combinations provided by ProCED should also be aggregated by cost element group.

All groups that are to be aggregated must be combined as sub-groups within a group. These superior groups are then entered in Value from for the constant NODE_AGGREGATION.

The aggregation is done for the sub-groups for which a cost element is directly assigned.

 

The aggregation has an impact on the following fields in mapping:

·         FD_INFOOBJ contains the ID code of the cost element group

·         FD_INFOOBJ_TXT contains the text description of the cost element group

·         FD_KATYP contains “99”

·         SOURCETAB is empty

If a cost element is not found to belong to any group, then it is displayed as a single row in the results list.

 

Usually, ProCED sorts the results list according to the entry for the cost element (in this case, according to the group). The entry of an X in Value to prevents this type of sorting. It will be output in the order that was previously read from the database. This should be the preferred way to sort, if reading is to be done across objects (e.g. with READ_ASSIGNED_OR).

 

Note:

The group entered in the constant NODE_AGGREGATION only functions to aggregate available posting rows: it is therefore NOT a filter for selection (to achieve this you still need to make an entry at the button |Restr. KoA Group| in the ProCED start screen).

For rows with aggregation by cost element group, not all ProCED mapping fields will contain meaningful data: the contents are usually transferred from the first cost element.

 

Field name in the satellite table

 

PSP_ACT_CUMULATE

This constant defines to which level a project should be relevant for Allevo, and if necessary only the WBS elements up to the defined level are written in the satellites. For the determination of the relevant cost elements, the subordinate WBS elements are also considered.

To have the correct display in Allevo-MultiObject, the constant of the same name should also be set. Then, the cumulative costs of all of the subordinate levels appear for the WBS of the selected level.

The level must be entered in the column Value from (differing from the entry of the constant of the same name in Allevo).

 

Note:

Only available for object type PR.

 

Dynamic determination of project level

 

PSP_MULTI_LEVEL

* as of ProCED Version 3.2

This constant determines the project level up to which WBS elements within a project are considered for the determination of posting combinations.

The level is not always constant, but is rather dependent on the structure of the respective project: therefore, this constant allows the level to be stored in any table of the project, e.g., the Append field in the table PROJ (see also the constant of the same name in the Allevo base package, which has the same meaning).

In the field Value from enter the name of the table (e.g., PROJ), and in the field Value to enter the name of the respective field in database table.  Reading is always done with the current project number. In the respective field you must enter a numerical value.

 

Note:

The constant PSP_ACT_CUMULATE can NOT be simultaneously active (otherwise PSP_MULTI_LEVEL is ignored)

 

Restrict selection of orders to object type PR

 

PSP_WITH_OBJECTS_OR

* as of ProCED Version 3.0

When starting ProCED with the object type PR, it is possible to also take related orders into account (incl. networks). Optionally, the constant PSP_WITH_OBJECTS_OR allows you to restrict the relevant orders by order type or category.

In the column Value from you can enter an order category: multiple entries should be made separated by a comma (depending on the application, the filter is applied via the table fields AUFK-AUTYP and AFPO-DAUTY).

In the column Value to you can enter order types: again, multiple entries should be made separated by a comma (depending on the application, the filter is applied via the table fields AUFK-AUART and AFPO-DAUAT).

 

Note:

A constant with the same name and functionality also exists in the Allevo basic package.

 

 

Reading the cost center via Profit Center

 

READ_ASSIGNED_KS

* as of ProCED-Version 3.2

When calling ProCED via a “PC” object type, the data for the respective cost center can be called in as well.

For the selection of the relevant orders, customer specific criteria, 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 cost centers. All criteria entered there are then taken into account in ProCED; only the Profit Center itself is replaced by the current value set when ProCED is called.

In the field Value from for the constant READ_ASSIGNED_KS, you can enter how the called Profit Center should be included when selecting a cost center. The following options are available when starting with a “PC” object type:

•           X = Default (is treated like P)

•           P = Read via the Profit Center (CSKS-PRCTR)

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 KM1V). 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. The only other constant that needs to be saved there is ALLEVO_ACTIVE. The assignment of the mapping fields, on the other hand, is always read from the constants for the cost center.

Do not simultaneously use the constants SORT_BY_KSTAR and MULTIPAGE_MODE!

An equivalent function is also available for the reading of orders (see constant READ_ASSIGNED_OR).

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).

 

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.

Reading WBS elements via cost center / Profit Center

 

READ_ASSIGNED_PR

* as of ProCED-Version 3.0 (expanded in 3.3)

When calling ProCED with the object type KS, the data of the respective WBS elements can be called in as well. Optionally, the selection of the WBS-data can also be made via the Profit Center to which the cost center is assigned. (as of version 3.2 also with direct start via Profit Center PC).

For the selection of the relevant WBS elements, customer specific criteria (e.g., the processing 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 can be saved for WBS elements. All criteria for the WBS element 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_PR, 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 PRPS 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)

Additional options when starting via a cost center KS:

•           V = Responsible cost center (KOSTV)

•           A = Requesting cost center (AKSTL)

•           B = Actually posted cost center (CYCLE)

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

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 CJ8V). The entry of the constant is made without the usual period (.) at the beginning. Alternatively, or additionally, a WHERE condition can be entered (see note below).

Important: At the moment, only the fields of table PRPS are taken into account when interpreting the entered WBS selection variant.

 

Note:

The constant must be saved in the settings for KS or PC. The assignment of the fields, on the other hand, is always read from the constants for PR object types.

Do not simultaneously use the constants SORT_BY_KSTAR and MULTIPAGE_MODE!

An equivalent function is also available for the reading of internal orders (see constant READ_ASSIGNED OR).

 

* new as of ProCED-Version 3.2

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

In addition to or instead of a selection variant, any WHERE condition can be entered in Value to for selection (as appropriate ABAP-coding, i.e. AND WERKS = 1000). The first three characters must be AND in order to switch into this mode. If both are used (a selection variant and a selection condition), separate these with a comma. 

 

Settings for determination

 

REP_OBJECT

This constant is only available for projects and controls the determination of the representative object. The following settings are available:

§  Value from:            Entry of the level, from which the WBS element is selected

                                    empty = first element according to "Value to"

§  Value to:                empty = first element (with or without planning indicator)

                                    1 = first element without planning indicator

                                    2 = first element with planning indicator

 

Note:

For additional information, see the section “Determining the representative object for a group (projects)” in the ProCED manual.

 

Selection parameter for ProCED execution

 

SEL_CRITERIA

In the selection screen of the transaction /ALLEVO/PROCED, specific characteristics that are not available when calling directly via Allevo planning can be set in the range "data selection criteria". This refers to the activation buttons for

·         Cost elements

·         Statistical key figures

·         Consideration of orders (incl. networks)

·         Consideration of business transactions

The selection by the user is saved in the constant SEL_CRITERIA (e.g., 1100 for reading cost elements and statistical key figures).

 

Note:

Entries here are also taken into account when calling via Allevo.

 

Selection parameter (2): Version

 

SEL_VERSION

The entries from the start dialog are automatically transferred.

 

Note:

The constant contains the selection data for the version (with the entry version from...to).

 

Selection parameter (2): Year

 

SEL_YEAR

The entries from the start dialog are automatically transferred.

 

Note:

The constant contains the selection data for the version (with the entry version from...to).

 

Cost element type for reading partner

 

SHOW_PARTNER

With this constant you can define the cost element type for which the partner data is read.

·         In Value from enter the cost element type (with Profit Center this is the business transaction),

·         In Value to enter the credit / debit indicator.

 

Note:

Multiple entries are separated with a comma.

 

Sorting cost element respective to the group

 

SORT_BY_KSTAR

* as of ProCED-Version 3.1.9 (expanded in 3.3.33)

In the standard case, the posting combinations determined by ProCED are only sorted according to the object number. Sorting is transferred on the level of the cost element /statistical key figure, as it is created when reading from the database.

Via this constant, the sorting for a cost element can be specified by an additional cost element group.

In the field Value from, enter a level for which the sorting should apply. Preferably, a 2, if sorting should still be carried out for objects at the highest level.

In the field Value to, enter the group: sorting will be carried out exactly as it appears in transaction KAH3. This group can not contain any subordinate hierarchies.

 

Note:

The cost element group should be complete and contain all cost elements relevant for ProCED/ If an entry in the group is missing, ProCED always enters the corresponding posting combinations at the end of the list, which is then transferred to Allevo (after all other combinations).

With the original conception of this constant, the cost element group in KAH3 could only contain single values for cost elements. Since version 3.3.33, areas (cost element to / from) are also taken into account.

 

Note:

For reading functions valid for all objects (e.g. cost center with READ_ASSIGNED_OR), the constant SORT_BY_KSTAR must be saved to the leading object type (in this example, for the cost center).

In this case, the constant MULTIPAGE_MODE must also be active, so that sorting according to the read objects can be achieved on the first level (i.e. in the chronological order of the orders).

 

Restrict data selection via value type

 

VALUE_TYPE

With the entry of the value types in Value from, the data selection is restricted to only these data types (for PC object types this is the record type).

Note: