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