Show TOC

 Update Shelf Status

 

With the UpdateShelfStatus function, feedback can be provided to On-Shelf Availability in respect of an out-of-shelf situation. This feedback consists of status information and the information about what amount of the product has to be written off due to spoilage (if applicable). Providing this feedback forms a basis for follow-on activities and reports. For example, after providing feedback, you can receive a list of items to be refilled from the backroom after a confirmed out-of-shelf situation.

Input Parameters

This function requires the following parameters:

  • storeId: Technical identification of the store.

  • productNumber: Technical identification of the product. Out of the parameters productNumber and GTIN, only one needs to be specified.

  • GTIN: Technical identification of the product (for example, the EAN). Out of the parameters productNumber and GTIN, only one needs to be specified.

  • newStatus: The code of the new status that the product receives.

  • damagedQuantity: A report to the ERP system, containing the number of pieces of the product on the shelf that have been spoiled and have to be thrown away.

Example URL for calling the function

<gateway-server>/sap/opu/odata/sap/<endpoint-name>/UpdateShelfStatus?storeId='OSA1'&productNumber='123'&newStatus='0'&damagedQuantity='10'&sap-client=300

On-Shelf Availability Algorithm Product Statuses

The product statuses stored by On-Shelf Availability in the Product Shelf Status (/OSA/STATUS_LOG) table can be set and changed:

  • By the OSA algorithm, based on its calculations

  • By calling the UpdateShelfStatus function by an OData client application (for example a mobile application as front-end application for On-Shelf Availability)

The following diagram illustrates the possible sequence of status changes for a product at a given store in On-Shelf Availability:

Each of the status is described in more detail in the following table. The rightmost column describes an example how a store associate could set the status using a potential front-end application for On-Shelf Availability:

Product Status

Description

Possible Usage in a Front-End for OSA

0

The product does not have on-shelf availability issues.

For the selected store, no alerts are displayed for this product.

1

The OSA algorithm has determined that the product potentially has on-shelf availability issues.

For the selected store, an alert is displayed for this product.

2

The on-shelf availability alert has been reported as being false by a user of an OData client application.

A store associate has used a front-end to ignore a reported alert, for example, after examining a shelf and seeing that the product is available on the shelf.

3

The on-shelf availability alert has been confirmed or created by a user of an OData client application.

A store associate has used a front-end to confirm a reported alert by flagging a product as empty. This moves this product to the store associate’s worklist of products to refill. Alternatively, the store associate has used a front-end to manually add a product that is not available on the store’s shelf to the worklist.

4

The on-shelf availability alert has been immediately resolved by a user of an OData client application.

A store associate has refilled the shelf directly on the store floor (without using the OSA worklist) and has reported the product as refilled.

5

The user of an OData client application has reported the product as being out-of stock (non refillable)

A store associate has used a front-end to report that a product with an on-shelf availability alert cannot be refilled as it is out-of-stock.

6

The on-shelf availability alert has been resolved by a user of an OData client application.

A store associate has refilled the shelf after locating the product in storage (using the OSA worklist) and has reported the product as refilled.