Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | MSSX_00100 |
| Short Description | Docu for PP Monitor |
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 | 0 |
Documentation
Description
Number of records in the table with a current stock of 0.
Using the key figure to run an analysis
The system creates records in the table once the corresponding goods receipt has been booked. Any further movement of goods will change the stock. The record is not automatically deleted even if all the material has been removed from stock, instead the stock is set to zero. You can only delete the records by explicitly triggering a deletion run.
During the availability check, the system reads all the records for a material from a table, including those with no stock. A large number of records without stock will, however, impair system performance. This will be the case if you have not used a deletion run for a long time.
For example:
Records without stock 20000
Records with stock 10000
This means that the system reads two records without stock for each record with stock, in other words, three times as many records are read that are needed. This means that the database access will take three times as long.
How to optimize performance
Try to keep the number of records without stock as low as possible by running the deletion program.
You can use transactions MM73 and MM74 to delete the records online or in the background. You should implement the run periodically, depending on how frequently new records are created.
Note that the material processed during the run will be blocked for the duration of the run. This is particularly noticeable if a deletion run hasn't been implemented for a while and large quantities of data have built up for individual materials.
Therefore, we recommend that you run the program at shorter, regular intervals, for example, when the system displays "Age profile of records without stock".
There is no risk involved with deleting records. If a record is deleted because it didn't contain any stock when you ran the deletion run but later you want to post goods receipt for the same sales order, the system automatically creates a new record.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
