Hierarchy
⤷ CA-GTF (Application Component) General Application Functions
⤷ BAM (Package) Technical Application Analysis
Basic Data
Data Element | VBSKL00001 |
Short Description | Documentation for key figure VBSKL 00001 |
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
These figures should provide you with an overview of how frequently a certain function or transaction has been used.
You can then use it to determine when the system is under pressure and when you can optimize performance.
If the times at which the functions are used coincide with when the system is not performing well, other transactions being used at the same time will also be adversely affected.
For example:
In your company, the transportation logistics and shipping departments do all their preparations for the coming day between 7 and 11 am. So that deliveries can begin at 2 pm without any problems, they prepare and print all the delivery, goods, shipping and freight papers.
Between 12 and 1 pm, everyone goes to lunch.
Between 10 and 11:30 is a peak time for telesales department who deal with all sales orders and inquiries, only some of which can be processed while on the phone, and others only with long waiting times. Some of the customers and sales prospects might, in the meantime, have gone to a competitor, where it is likely their orders will be processed more swiftly.
The management commissioned a study which has shown with 99.89% certainity that the main business times in each department clash with each other between 9:53 and 11:06 when the system can only just continue to perform.
What can be done?
Structure and use of detailed displays
The detailed displays here show how often each transaction is used on different days and at different times (in a 24 hour period) during the whole test.
You can select a required cell in the table, choose "Sample" and the "Additional info" to reach a dialog box where the system branches to the underlying log. If you choose "Additional info" without "Sample" you branch to a general selection screen that displays the logs.
How to optimize performance
There are many ways of optimizing performance in a case like the above example:
1. Automatic background processing during the night
Only use the function online in exceptional cases and store the main work until the night time when you can use background jobs.
As well as improving system performance, this would have the pleasant side effect of printing all the required documents by the start of the working day, allowing the users to start subsequent processes and worksteps sooner and potentially being able to process more deliveries. A more relaxed personnel in all departments will be the result!
2. Running worklists at the same time
If the volume of all sales orders due for shipping can't be processed in one run or during the night time available, you can also run several jobs at once thereby using resources in more than one application.
To prevent the jobs from affecting each other adversely, for example, by database serializations, you should make suitable data selections and use appropriate split criteria for the documents for each job.
See the notes and recommendations from the SAP service systems as well as any documentation in SAP TechNet.
3. Limit how often worklists are processed and use background jobs during less popular periods in the day
Another way to improve organization in the above example would be to only create deliveries with a delivery worklist online in exceptional cases (for example, for express deliveries) and then only with very restrictive selection criteria (definitely not between 10 and 11 am). You should deal with urgent cases during that time with the transaction for generating individual deliveries.
Divide the activities up from both departments by moving telesales to another server. This option is immediately available and does not require any other measures.
As well as these inexpensive and relatively simple options for optimizing your workload in technical and organizational terms, there are many other alternatives that cannot be listed here, due to the restricted space (see below).
Note
See the relevant notes, recommendations and documentation in the SAP service systems.
Also note the relevant legal and internal requirements of the company involved.
History
Last changed by/on | SAP | 19990223 |
SAP Release Created in |