Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE68000 |
| Short Description | Documentation for text determination 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 core areas of text determination which form part of SAP Sales and Distribution development.
The evaluation looks at those text types, which cause automatic accesses, to determine information and descriptions automatically. This does not include text types, that have not been assigned an access sequence.
Text determination can lead to a bottleneck situation, if carried out too often within a document. It is normally implemented when creating a new, text-relevant document and every text-relevant item.
Example:
Text determination is carried out as part of a quotation, the verbal explanations agreed here should apply to all follow-up documents.
If the customer then executes the quotation and places an order, all text types will be transferred unchanged.
However by mistake text is copied instead of a simple reference being set up in the Business Engineer. This setting lead to the text being physically copied instead of merely receiving an indicator to the previous document. In this example text determination is not suitable, the load on the system at the relevant points being unnecessarily increased.
The situation can be tightened up by a comprehensive control of text determination, particularly if the optimization measures listed below are not used or are incomplete. Response times to a transaction to the nearest minute can be a result of this.
Control of text determination is very similar to that for condition technology and should be subjected to an analogue optimization evaluation. It is also used for other SPA applications.
Focus points
Those parts of the function, with a high resource requirement are examined.
According to experience these are
the number and size of text procedures used,
non-used text types,
frequent use of text types, which work by copying instead of referencing,
access sequences and the number of assigned accesses and text objects,
and the use of optimization measures in the SAP standard such as
conditions (User-Exits), which control processing at the level of an access assigned to an access sequence,
using these accesses can be avoided.
In addition further system parts (e.g. User-Exits) are included in the examination, which are normally the object of individual procedures and extensions as part of the SAP introduction.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
