Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | VBRK00019 |
| Short Description | Documentation for key figure VBRK 00019 |
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
This key figure should give an overview of the procedures used.
Optimization measures are only required, if only a few procedures are used often.
In the case that only a few procedures are used, it can be set up so that these procedures apply for a large combination of business transactions.
This means that the whole complexity of text-related relationships such as customers, forwarding agents, shipping personnel, languages, products, agreements and markets as well as organizational dependencies must be represented in fewer procedures, to achieve fully-functioning day-to-day operations. Or: all these things are not really complex and therefore can be clearly represented.
Maintenance of complex models along with the non-trivial simulation of expected results requires a great deal of resources and careful work, depending on experience. Each time this representation can be made more compact, this generally leads to simplification, quicker operating time and more comprehensible results.
Notes for optimization
There are several measures for optimizing large procedures:
Splitting into several smaller procedures and their corresponding assignments in procedure determination. The assignments are made at customer master record and sales and distribution document level. For billing types, assignment of both procedures without their own item categories at document type level.
Eliminating unused text types.
Texts, that must be transported between documents, should if possible be defined with a reference.
The language origin of a text access must always be maintained.
These are useful measures to carry out.
If these measures cannot be carried out, there are only the optimization approaches, that refer to objects in the procedure, for example, access optimization and setting requirements.
Tolerances
It is recommended that you use at least five (5) different procedures.
Using three or less procedures allows very simple processing and leads to unsuitable modelling.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
