Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE60000 |
| Short Description | Documentation for availability check 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
The key figures refer to core areas of the availability check, which forms part of SAP Sales and Distribution processing. Those checking strategies currently available in the system such as the ATP check, planning and allocations are taken into consideration. As well as SD, the availability check is also used in other SAP applications, for example in Production Planning or Goods Movement.
This examination looks at those control elements, giving access to databases, in order to be able to propose product availability and inbound delivery deadlines.
The availability check can lead to a bottleneck situation, if it occurs too often within a document. It is normally implemented when creating a new check-relevant item or when changing item data such as amounts, delivery dates, plants, storage locations or special fields, which have been deifned as check-relevant.
It is not always a good idea to carry out the availability check several times within a process chain as this can restrict the running of a process.
Example:
An availability check is carried out as part of a sales order. Once the amounts and deadlines have been determined and confirmed, they are agreed as binding. Since in this order you may be dealing with a particularly urgent copy (e.g. express delivery), the delivery is
initiated immediately or within a few minutes. Competitive samples from other company areas such as Production do not feature in this example. Sales works with discipline and respect on the sales orders and delivery priorities of other colleagues.
In this ideal case, another check when setting up the deliveries is not necessary and can therefore be omitted.
Focus points
The main points in the evaluation are firstly the parts of the function, which have a high requirement for resources and can lead to bottleneck
situations.
Experience has shown that these are
the number of check groups used,
the feature of a checking rule in a checking group,
the use of individual or group requirements,
the use of disconnection procedures during the check.
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.
References
Please see the relevant pulications in SAP TechNet.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
