Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | VBSKL00005 |
| Short Description | Documentation for key figure VBSKL 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
Using the key figures for analysis purposes
This key figure informs you how efficient your worklist run was, along with information about what time of day and how often the functions were implemented.
You can judge how efficient the worklist run was, for example, by looking at the number of documents or document items that have been generated, the number of messsages and the number of read or processed index entries. It provides a range of critical messages that tell you why a document could not be created, perhaps because of Customizing settings or because the preceding documents were incomplete. Normally, the system reads a wide range of information (for example, preceding documents) and processes it until it terminates and sends a relevant message to the log of the worklist run.
You can view the messages in the detailed display.
You should analyse the messages so that you can optimize the run by preventing the system from creating critical messages and instead, creating more documents.
Structure and use of detailed displays
This figure shows how the messages are distributed between different days and times, enabling you to recognize how many messages have been created.
For 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
Here you can see that on 25.11.97 a total of 1500 messages were created. They appear throughout the day and it is clear that you need to check the log of the work run.
Select the required cell in the table and choose "Sample" and then "Additional info" to see a dialog box with a display of the underlying log. If you choose "Additional info" without the "Sample" button, you reach the general selection screen for displaying all the logs from the worklist run.
How to optimize performance
In order to avoid an unnecessary strain on the system, you should check the messages in the log regularly to see why documents could not be created.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
