Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE55050 |
| Short Description | Documentation for Prestep node |
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
Description
These key figures refer to the "Pre-Step" access optimization and should help you to decide whether "Pre-Step" can be used.
In the definition of an access sequence, the fields used to access the table as well as the condition table are given. These fields are either header fields (field from the structure KOMK) or item fields (field from the structure KOMP). Header fields contain values which apply to the whole document, e.g. sold-to party and item fields contain values which apply to the item, e.g. the material.
The Prestep is a test access to the condition table, which is only executed with the header fields. If during this test access no valid condition records have been found, no record can be found in the individual items either. These accesses are then no longer executed from the system in the document items. This can reduce the system resources used and particularly affects documents with lots of items.
Focus points
There is a list of criteria, which helps you to make the decision whether "Pre-Step" can be used or not:
No. of items > 1 for the majority of documents,
many accesses on the condition tables, which do not find any valid
records
These criteria can be checked :
if the access depth in the access sequence shows that valid condition records are often only found in the last accesses in the access sequence, you should consider switching on Prestep for the other accesses.
Since Prestep is always determined at condition type level, the number of condition records for a specific condition type in the condition tables is very important. For empty condition tables all condition types with access to the Prestep table should be defined. Prestep is also recommended for condition types, belonging to condition tables, which contain either none or very few condition records for this condition type. In both of the last two situations, you should of course always check whether or not conditions can be created for these these condition types in future. It is recommended you delete the corresponding accesses to the access sequences if in future no conditions are created. When using several access sequences in various condition types, new access sequences should be created if necessary.
References
Please see the relevant publications in SAP Tech-Net.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
