Service Loss Category: Unsaleable Stock

Use

The service loss reasons of the service loss category Unsaleable Stock define that service loss occurred because at the service loss reference date/timethe customer-requested product was in quality blocked stock or stock in quality inspection at the following locations:

First stockholding location

(service loss reasons Stock in Quality Inspection and Quality Blocked Stock )
All contract packagers assigned to the first stockholding location

(service loss reasons Stock in Quality Inspection at Contract Packager and Quality Blocked Stock at Contract Packager )

The quantity that can be assigned to these service loss reasons is restricted to the quantity of stock in quality inspection and quality blocked stock.

Prerequisites

In Customizing for SAP Supply Chain Management (SAP SCM), you have defined a process category for stock history so that the stock history can be updated. If the stock history is updated regularly, service loss analysis can access information about the quality blocked stock and the stock in quality inspection.

For more information, see the Implementation Guide (IMG) for SAP SCM under Start of the navigation path Advanced Planning and Optimization Next navigation step Global Available-to-Promise (Global ATP) Event-Driven Quantity Assignment Other Process Categories Define Process Category for Stock History End of the navigation path .

Features

Since the system saves the stock history in hourly time buckets, each bucket contains the quantity in quality blocked stock or of stock in quality inspection at the end of the hour, if goods movements took place during the time bucket. If goods movements did not take place, the bucket does not contain an entry about the stock history.

Service loss analysis uses the entry of the bucket that contains the stock history of the full hour before the service loss reference date/time. This ensures that no goods movements after the service loss reference date/time update the bucket, as this would lead to inconsistencies during quantity calculation in service loss analysis.

Example Example

For example, the service loss reference date/time is December 12, 2005, 10.30 AM. Service loss analysis uses the information about the stock history that was saved in the bucket on December 12, 2005 between 9.00 AM and 9.59:59 AM (the last complete hour before the service loss reference date/time).

If service loss analysis were to use the bucket from 10.00 AM to 10.59:59 AM, this could lead to inconsistencies during the quantity calculation if the following were to occur:

End of the example.

Service loss analysis occurs before 11.00 AM.
No further goods movements occur between the start of service loss analysis and the end of the bucket (10.59:59 AM) that update the entry about the stock history in the bucket.

If multiple customer-requested schedule lines refer to the same bucket, the bucket quantity is still the maximum amount that can be assigned to the service loss. If the bucket quantity is zero, these service loss reasons cannot be assigned to the service loss quantity.

Caution Caution

Note that these service loss reasons only offer a rough evaluation of the actual service loss due to quality blocked stock or stock in quality inspection. This is because there is no information in the system about how long a product has been in quality blocked stock or in stock in quality inspection.

End of the caution.

Recommendation

We recommend that you regularly reorganize the stock history using program /SAPAPO/SRVF_RR_STOCK_HISTORY. Otherwise, database access will be slower.

End of the recommendation.

Activities

The system calculates the following:

The start of the last hour for each service loss reference date/time
The information from both buckets of the calculated hour

For each service loss reference date/time, the system calculates the start of the last hour and then reads the last two buckets of the stock history.
The quantity from the bucket that was already assigned to other service loss schedule lines