Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | VBSKF00006 |
| Short Description | Documentation for key figure VBSKF 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
Use of the key figure for analysis purposes
Rating of a single work list run can be determined, for example, by evaluating the number of documents or document items created, the number of messages created and the number of index entries read in or processed.
You can use the detail display to show messages.
Analysis of these messages should help to optimize the runs, so that no more critical messages can be created that show that document entry was not possible due to problems. For example, creation of documents was not possible due to the Customizing settings or incompleteness of previous documents. As a rule a sequence of information (for example, preceding documents) has already been read and processed by the time the system breaks off processing and issues an appropriate message in the work list run log.
Structure and use of detail displays
This key figure shows the frequency that messages occur in specific age classes. You can see how often a message has occured in the past. You should pay attention to the chosen analysis period. As well as the frequency, a short text message is also displayed (either in the first or last column). The short text can be used to determine whether the message was critical for processing or if specific measures need to be introduced.
Example :
N Freq. Message
1 0009 VL 150 Only && of material && available
2 0004 VL 096 Order is incomplete - maintain the order
3 0002 VL 030 Item & is incomplete - maintain the sales order pflegen)
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 & is on boycott list for country &
This section of the analysis run shows the messages created and their frequency.
Interpretation:
The messages from lines 1.4, 8 refer to incomplete data or incorrect use of the system.
They should only occur in exceptional circumstances, as the cause of these errors should constantly be being dealt with.
In such evaluations it is always helpful to discuss extreme values.
If, for example, there is a discrepancy between documents or items and messages created (for example 10 : 2000), the causes must be determined, so that future runs can work without a problem and there is no unnecessary strain on the system. Quotient creation from documents and messages is only suitable for the first, general evaluation, as many of the messages are created from items from the preceding documents.
After selecting the required cell from the table and pressing the Sample button, you can use the Additional info key in the input box, which then appears, to branch into the log. If you choose Additional info without first pressing the sample key, you branch into a general selection screen for displaying the work list run logs.
Notes for optimization
There are several approaches to the above example:
there may be several reasons for the message in line 1
the material concerned is actually a missing part
the availability check is wrong or is not set properly
materials planning, procurement or stock management are not working properly (technical system and/or organizational)
etc.
Correct maintenance of the preceding documents and their master data, in order to achieve a program run without any problems.
Conversion of system control (Business Engineer or Customizing) for the completeness check
Conversion of system control (Business Engineer or Customizing) for the document flow
Correct master data maintenance in line 8
References
See the relevant notes, recommendations and publications from the SAP service systems.
Note the relevant legal requirements and internal stipulations of the company concerned.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
