Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE69000 |
| Short Description | Documentation for output 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 output determination within SAP Sales and Distribution processing.
They can lead to a bottleneck situation as they very often occur as part of a document and are normally implemented during the creation of a new, output-relevant document and all output-relevant items.
In the past bottleneck situations in output control and output management were mainly due to the type of telecommunication (media), the transfer times and to output programs, which were often developed to suit individual needs, rather than due to output determination itself.
In some cases the unsuitable definition and handling of output hardware (e.g. printer) and spool systems has resulted in difficulties and high response times.
Example:
An output type is set for immediate output for organizational and historical reasons.
As a result of this, the document updating process waits until the output has been formatted and updated in the SAP spool tables, to aid synchronization.
When there are a large amount of transactions being carried out at the same time, this can lead to high response times from the key transactions.
In this example output determination is not really suitable as the load on the system is unnecessarily high at the relevant stages.
The situation can be improved by carrying out a comprehensive control of output determination, particularly if the optimization measures below are not used or are used in incomplete form. Response times can then be obtained to the nearest minute.
Output determination has been developed using condition technology and should undergo an analogue optimization examination as for pricing determination. Output determination is also used for other SAP applications.
Focus points
Those parts of the function with high resource requirements are examined.
According to experience these are
the output time,
the transfer medium (paper, EDI, ALE, Workflow etc.),
the logging run, which should generally only be needed during the test phases.
and the use of optimization measures in the SAP standard system, for example
requirements (User-Exits), which control processing and are assigned at access level in an access sequence, and with the help of which accesses can be avoided.
In addition other parts of the system (e.g. User-Exits), which are part of the SAP introduction and which are normally the object of individual procedures and extensions should be examined.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
