Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE72000 |
| Short Description | Documentation for batch 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 batch determination within SAP Sales and Distribution processing.
The evaluation mainly looks at those strategy types, which carry out automatic access, in order to determine batches automatically. This does not apply to those strategy types, which have not been assigned an access sequence or have not been identified as "automatic". If condition tables are buffered, the access is merely stored in the system memory instead of creating database accesses. With this method however unnecessary accesses can not be avoided.
Batch determination can therefore lead to a bottleneck situation because it is often run within a document. It is normally carried out when creating a new batch-relevant item or when changing item data such as amounts, deadlines or special fields, which have been defined as batch-relevant.
Carrying out batch determination several times within a process chain is not always a good idea as it can affect the running time of a process and it should therefore be thought through carefully first.
Example:
Batch determination is carried out as part of an order. After agreeing on the batches by telephone with the customer, the amounts determined are then binding. If an order is delivered to the customer, all batches must be transferred unchanged according to this agreement.
By mistake an unrestricted "New Batch Determination" has been set up in document flow control or the parameters of the standard system have not been questioned and have not been properly transferred.
In this example batch determination has been carried out twice unnecessarily. Once when setting up the order and once when setting up the delivery. If at first we forget functional inconsistencies such as changes to stocks at batch level in the period between the order and the delivery, it is clear that the additional implementation of batch determination unnecessarily increases the load on the system.
The situation can be improved through comprehensive control of batch determination, particularly if the optimization measures below are not used or are used in incomplete form. This results in response times to a transaction to the nearest minute.
Batch determination is one of the SAP functions which has been carried out using condition technology. All functions which work in a similar way with procedures, types and sequences should undergo an optimization evaluation. Other SAP applications such as Purchasing or Production also use batch determination.
Focus points
Those function parts with high resource requirements are examined.
According to experience these are
the number and size of search procedures used,
non-used strategy types,
the number of permitted batch splits,
the sort sequences,
whether dialogues are planned or not,
the access sequences and their assigned accesses and tables,
and the use of optimization measures in the SAP standard system such as
the "initial value check" at field level within an access in an access sequence, with whose help accesses can be avoided.
Since batch determination is based on other system functions such as the classification system and is generally used together with the availability check, these functions and their bottleneck situations must also be taken into consideration. If neeed be batches which no longer show stocks are put to one side. The number of classification features assigned to a batch can unfavourably influence the length of processing.
In addition other system parts (e.g. User-Exits) which are normally the object of individual procedures and extensions as part of the SAP introduction are included in the examination.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
