Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | VBSKL00006 |
| Short Description | Documentation for key figure VBSKL 00006 |
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 figure for analysis purposes
You can judge how successful an individual background job was by the number of documents or document items it generated, the number of messages it generated and the number of read or processed index entries.
You can use the detailed display to see the messages.
Analyzing the messages should help you to optimize runs so that the system no longer generates critical messages informing you that it could not create a document due to certain problems, such as settings in Customizing or because preceding documents were incomplete. Normally, the system reads a large range of information (for example, preceding documents) and processes them until the system terminates processing and adds the relevant message to the log for the job.
Structure and use of detailed displays
This key figure informs you how often messages appear in certain age classes, allowing you to see how often the message has appeared previously, so you should bear in mind the time period chosen for the analysis. The system also displays the message short text (either in the first or last column) which enables you to decide whether the message is critical to processing and wether you need to take any steps to avoid it re-occurring.
For example:
This extract from an analysis run displays the messages created and how frequently they appear.
Z Freq. Message
1 0009 VL 150 Only & & of material & & are available
2 0004 VL 096 The order is incomplete, please maintain
3 0002 VL 030 Item & is incomplete, please maintain sales order
4 0001 VL 309 Delivery type & is not defined
5 0001 VL 195 Schedule lines were rejected due to differing delivery date/time
6 0001 BS 001 No status object is available for &
7 0001 VL 123 Delivery group & is not complete (delivery group will be deleted)
8 0001 L9 023 Material & does not exist in warehouse &
9 0001 V1 526 Assigned ship-to party &1 is on boycott list for country &2
Interpretation:
The messages from lines 1 -4 and 8 note that data is incomplete or that the system is not being used properly.
They should only ever occur rarely and you should deal with the causes immediately.
At this point, it would be helpful to look at the extreme values that can occur.
If, for example, there is a stark discrepancy between generated documents or items and the messages (10:2000), you need to solve the problems immediately because every run will take place unsuccessfully, merely straining the system unnecessarily. This ratio of documents to messages is only useful for a rough estimate because a large number of messages arise from the preceding documents.
Select the required cell in the table, choose "Sample" and then "Additional info" in the following dialog box to display the underlying log. If you choose "Additional info" without the "Sample" key, you branch to the general selection screen for displaying the logs of the background runs.
Notes for optimizing performance
The example named above covers several scenarios:
The message from line 1 can have several causes
The material is really missing
The availability check was incorrect or incorrectly configured
Materials planning, procurement or warehouse management don't work properly (either in the system and/or in the organization)
etc.
For a problem-free run, maintain the underlying preceding documents and their master data correctly
Change the system controls (Business Engineer or Customizing) for the availability check
Change the system controls (Business Engineer or Customizing) for the document flow
Correct master data maintenance for line 8
Note
See the relevant notes, recommendations and documentation from the SAP service system.
Note the relevant legal requirements and the internal requirements of the relevant company.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
