Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | COMB00013 |
| Short Description | Documentation for key figure COMB 00013 |
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
This key figure gives you an overview of the most important control parameters per checking group, as well as the frequency with which they are used.
Using the key figure for analysis
The key figure is used to determine the scope and emphasis of the check.
The information displayed allows you to plan your first optimization requirements.
You could, for example, determine whether, how, and in which checking group requirements are totalled and whether a check is required at all.
You would also probably only wish to use individual requirments where this suited the nature of the material or the transaction involved.
Example:
An international furniture company sells a saleable small component (e.g. a bracket or a screw) with individual requirements.
The part occurs in almost every sales order an is often also used for assembly in production. The incoming sales orders, resulting deliveries and some production orders cause the system to check the availability of the component several times every day. In the meantime, some of the departments are complaining about slow system reaction times. This component is actually better viewed as a bulk material and should be planned for according to use. The MRP controller realises this, but wants to keep an eye on the small component requirements and their causes, and refuses point-blank to do things differently.
What should be done in this situation ?
Setup and use of the detail display
By including additional columns, you can view further key terms.
Notes on optimization
In general, one should always question whether an availability check is needed at all. If so, the relevant materials should be checked separately.
If you resisted the temptation to sack the MRP controller in the above example, you could define a new checking group that sets requirements summation to at least a daily level, thus removing the accesses from the now rather large table for individual requirements. The individual requirements that already exist would eventually be replaced by the total requirements. Checks for individual requirements without using replenishment lead time could worsen the situation, as this method gives no termination criteria for the check and all requirement records must be checked.
When you are dealing with extreme situations (lots of individual requirments for lots of materials), it may make sense to convert to new checking groups with requirements totalling and also changing the originating documents. Using this method requires good knowledge of the help programs and should under no circumstances be carried out without the support of a qualified person or for trivial reasons.
Poor choice of parameters for the blocking of materials can also lead to severe bottlenecks in your system. This is especially true if you are also using system functions that change requirements, such as delivery due lists (background or online) or online transactions that try to process the same material simultaneously. The standard SAP system is released so that these clashing parameters do not occur.
When defining and changing checking groups, you need a good overview and understanding of the company and system complexity, especially if different enterprise areas area affected.
If new checking groups are created for materials, for which sales documents or items already exist, then the existing documents are not updated. Redundancy and their temporary will lead to the requirements records disappearing gradually, with system performance increasing at the same rate.
Links
See the relevant texts in SAP-TechNet.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
