Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE99999 |
| Short Description | Documentation for user exit 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 | 1 | 1 |
| Medium | 1 | 1 |
| Long | 1 | 1 |
| Heading | 1 | 1 |
Documentation
Description
These programs and program parts are provided for those function enhancements, that use the parameter control options in the Business Engineer.
When modelling and maintenance of enhancements is carried out correctly, it enables the additional processing logic to be introduced simply and neutral to performance or for optimization purposes.
The functionality used can, for example, favourably influence the performance, by being subjected to a pre-defined or specific processing logic, depending on the business process, via the user exit parts.
When there is unsuitable modelling or implementation, this can, for example, lead to complex function failures, without at first having any visible effect on other applications, massive use of resources and disruptions to business processes, and eventually to a complete system standstill.
All program changes and enhancements carried out, including your own developments, which are not part of the SAP routines, must be examined before the start-up for their efficiency and processing speed and should be optimized, if necessary. Purely functional evaluations or tests are not sufficient for long term operating.
Along with technical optimization measures, modelling of individual enhancements determines the subsequent use of system resources. Particular examples given here are accesses to tables without qualified designation or assignment of key fields or the unsuitable choice of access paths.
Those programs labeled with an icon are undergoing repairs or correction and are assigned to transfer requests. You can use the drill down functions to branch into the program code.
Focus points
Those parts of the function, that have high resource requirements or are not properly implemented are examined. Experience has shown that these are the ABAP language elements
"SELECT"
"INSERT, UPDATE, DELETE, MODIFY"
"COMMIT"
"LOOP"
"PERFORM"
"CALL"
"SUBMIT"
"SORT"
and their program environment.
Those examples given here do not require completeness.
The use of user exits and their characteristic feature is not always recommended as it can affect the runtime of processes. To avoid unnecessary program changes and enhancements, all standard software options should be checked before implementation. Whenever possible, future developments should be taken into consideration.
The definition and change of individual program extensions requires comprehensive handling of business and technical system connections.
Particularly if different areas of the company are concerned.
These should not be carried out without support from experienced and specially trained employees.
Structured test scenarios as well as comprehensive function and performance tests are imperative.
Subsections.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
