Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | VBSKF00005 |
| Short Description | Documentation for key figure VBSKF 00005 |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | 1 |
| Medium | 15 | 1 |
| Long | 20 | 1 |
| Heading | 1 | 1 |
Documentation
Use of the key figure for analysis purposes
These key figure shows the efficiency of the work list runs. This is an important point along with what time the function is carried out and how often.
The efficiency of a run can be determined, for example, by the number of documents or document items created, the number of messages resulting from this and the number of read or processed index entries. There is a sequence of critical messages, which show that document creation was not possible due to problems such as the settings in Customizing or incompleteness of preceding documents. As a rule, however, a sequence of information (for example, preceding documents) is read and processed until the system cancels processing and a corresponding message has been noted in the log for the work list run.
You can use the detail display to display the messages.
An analysis of the messages should help to optimize the runs so that no more critical messages are created and that instead the number of documents created increases.
Structure and use of detail displays
This key figure shows the distribution of messages on different days and at different times of the day. The aim is to determine how many messages have been created.
Example
Day : 25.11.97
Total : 1500
0 - 6 : 100
6 - 8 : 0
8 - 10 : 200
10 - 12 : 300
12 - 14 : 0
14 - 16 : 400
16 - 18 : 300
18 - 20 : 100
20 - 24 : 100
This example shows that on the 25.11.97 a total of 1500 messages were created. These were distrbuted throughout the day. In this case, you need to check the logs for the work list runs.
After selecting the cell you require from the table and pressing the Sample key, you can use the Additional info key in the info box which then appears to branch into a display of the log. If you choose Additional info without using the sample key, you branch into a general selection screen for displaying the work list run logs.
Notes for optimization
To avoid unnecessary strain on the system, the logs should be regularly checked after messages, which have prevented documents from being created.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
