Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE99998 |
| Short Description | Documentation for sales information system 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 the Sales Information System, which is part of the Logistics Information System in SAP Sales and Distribution processing.
The evaluation looks at influencing factors such as those which cause automatic information updating.
This does not concern update rules, for which there are no assignments.
Updating statistical data can lead to a bottle-neck situation because it is carried out within a document. Normally it can be carried out when creating documents or items, or when changing item data such as quantities, values, deadlines or special fields which have been defined as relevant to updating.
Updating statistics within a process chain is not always recommended as it can affect the lead time of a process.
As well as technical optimization measures, modelling determines later use of system resources in the Sales Information and Logistics Informations systems.
Focus points
Those parts of the function, which cam lead to a high resource requirement are taken into consideration.
According to experience these are
the number of actively updating information structures,
update rules such as
the periodicity of LIS information, which influences the volume of tables,
the update session (V1 / V2 - Update), where an asynchronous update of V2 should be achieved,
the accompanying logging, which as a rule should only be needed during the test phases.
Due to potentially high resource requirements, use of the LIS should always be thought over first.
Defining and changing models in the statistics requires careful handling with regard to business and technical system connectivities.
Particularly if different enterprise areas are concerned.
In addition other system parts (e.g. User-Exits) are included in the evaluation, which as part of the SAP introduction are normally the object of individual procedures and extensions.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
