Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | LIKP00015 |
| Short Description | Documentation for key figure LIKP 00015 |
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 the observer an overview of the procedures used.
Optimisation measures are only then required, if only a few procedures are used often.
In the event that only a few procedures are used, it can be set up so that these apply to 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 organisational dependencies must be dealt with in fewer procedures, to ensure that day to day activities are fully functioning. Or: all of these things are not really complex and can be represented simply.
The maintentance of complex models and their non-trivial simulation of expected results requires, depending on experience, a great deal of personal resources and careful work. If these can be represented in a straightforward version this simplifies and speeds up the process and leads to more comprehensible results.
Notes for optimization
There are several measures for optimizing large procedures:
Breaking down into several smaller procedures and corresponding assignment in schema determination. Assignments are made at sales doc. type and item type level. For billing document types assignment of both procedures is made at document type level when there are no item types.
Eliminating unused text types.
Texts, which must be transported between documents, should whenever possible be given a reference.
The language origin of a text access must always be maintained.
These are useful measures which should always be carried out.
If they cannot be carried out, there remains only the optimization approaches, which refer to objects within the procedures, for example, access optimisation and setting conditions.
Tolerances
It is a good idea to use at least five (5) different procedures.
Using three or less procedures means that on the one hand processing is very simple but on the other hand indicates unsuitable modelling.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
