Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | LIKP00016 |
| Short Description | Documentation for key figure LIKP 00016 |
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 key figure for analysis purposes
This key figure should gove the observer an overview of the procedures used.
Optimization measures are only required, if only a few procedures are used often.
In cases where only a few procedures are used, these can be set up so that they apply to as many business transactions as possible.
This means that the whole complexity of partner-relevant relationships such as customers, forwarding agents, purchasing organizations, commission receivers and so on as well as organizational dependencies must be represented in fewer procedures. Unless these relationships are not really complex and are therefore easier to represent.
Maintenance of complex models and the non-trivial simulation of expected results requires a lot of personal resources and careful work, depending on experience. Being able to produce a simplified version makes things easier and faster and leads to much more comprehensible results.
Notes for optimization
There are several measures for optimizing large procedures:
Breaking down into smaller procedures and assigning these in procedure determination. Assignments are made at sales and distribution document and item category level.
Eliminating unused or unnecessary partner functions.
These steps should always be carried out when possible.
If these measures cannot be implemented, there are other approaches, relating to objects within the procedures, for example, setting requirements.
Tolerances
It is recommended that you use at least five (5) different procedures.
Using three or less procedures only allows very simple processing and / or unsuitable modelling.
A partner determination procedure should contain at least ten (10) partner functions.
A partner determination procedure should contain at least three (3) partner functions with partner hierarchies.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
