Hierarchy
⤷ CA-GTF (Application Component) General Application Functions
⤷ BAM (Package) Technical Application Analysis
Basic Data
Data Element | LIPS00023 |
Short Description | Documentation for key figure LIPS 00023 |
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.
Optimization measures are particularly required, if only a few procedures are used but often.
In cases where only a few procedures are used, they can be set up so that they are valid for a large number of business transactions.
This means that the overall complexity of text relevant dependencies such as customers, forwarding agents, shipping personnel, languages, products, agreements and markets as well as organizational dependencies must be covered in fewer procedures, in order that day-to- day activities can fully function. Unless: all of these things are not really complex and therefore can be covered quite easily.
The maintenance of complex models as well as the non-trivial simulation of expected results requires a lot of personal resources and careful work. Whenever things are put together in reduced form, this generally leads to quicker, simplified and more comprehensible results.
Notes for optimization
There are several measures for optimizing large procedures:
Dividing into smaller procedures and their assignment in procedure determination. Assigments are made at sales document type and item type level. For billing document types assignment of procedures takes place at document type level.
Elimination of unused text types.
Texts, which have to be transported between documents, should whenever possible be given a reference.
You should always maintain the language origin of a text access.
These measures are relevant steps, which should always be carried out.
If you cannot carry out these measures, there remains only the optimization approaches, relevant for objects within a procedure, such as access optimization and setting conditions.
Tolerances
It is normally a good idea to use at least five (5) different procedures.
Using three or less than three procedures on the one hand enables simple processing but on the other leads to unfavourable modelling.
History
Last changed by/on | SAP | 19990223 |
SAP Release Created in |