This is an old revision of the document!


In case of the ‘Cycle count’ flow, for processing the counted data open the ‘Process’ window from the Produmex menu. This window displays all the differences counted according the cycle count type.

Warehouse
The warehouse where the cycle count was performed.
Remarks
Remarks to be added to the issue and/or receipt.
Posting date
The posting date of the issue and/or receipt.
G/L Account receipt/issue
The G/L account to use for the issues and/or receipts. (This only needs to be set when using Perpetual Inventory and if this is set on the controller)

If there are multiple rows in the list, selected rows can be removed by pressing the ‘Delete’ button. This deletes the entries from the list to process but the data is not deleted from the database. Deleted rows will appear again after the list is refreshed.

It is possible to process the counted difference in multiple steps. Adjust the quantity on the grid before processing the row. Example: The quantity on the row is 64. If you would like to process only 20, change the quantity to 20. When processing the row, only 20 is processed, and the remaining 44 can be processed later.

The item cost will be the item cost for the given warehouse (OITW.AvgPrice) when the following verifies:

  • The Item Groups Valuation Method is ‘Moving Average’ (OADM.InvntSystm = ‘A’) for the company
  • The Manage Item Cost per Warehouse option is enabled (OADM.PriceSys = ‘Y’) for the company

In other cases this will be the item cost (OITM.AvgPrice).

A negative quantity means that there is not enough stock in the system. When processing this, a goods receipt will be booked to add stock to the system. A positive quantity means that there is too much stock in the system. A goods issue will be booked to correct this.

After pressing the ‘Update’ button, the selected rows in the grid will be processed. After processing, the system will inform the user that the processing has been done. After processing, the list will be refreshed.

Please note that goods issues can only be performed if the stock is not currently locked. If this is the case, the locking should be removed before processing the cycle count.

Recommendation when using cycle count type ‘LostAndFound’:
If cycle counting during other operations is used, or cycle counting is performed while other processes (Picking, production, …) still take place, it is recommended to regularly process the counted locations.

For example:
In the system there is no stock in the system of ProductA. Location A1 is counted, and 10 pieces of ProductA are found. On the LostAndFound location, the stock of ProductA is -10, and on location A1 there will be 10 pieces. The sum of that stock is 0, and that corresponds to the stock available in SAP.

Because there is now 10 pieces of ProductA on location A1, it is possible to make a pick list for this stock, and pick the items. But when the user will try to ship the items, an error will occur, because the stock is not known in SAP.

So the processing of the cycle count needs to be done first. A goods receipt of 10 pieces of ProductA will be booked, so the stock in SAP will contain 10 pieces of ProductA. Now the shipping of the pick list can be performed.

If there are multiple rows in the list, selected rows can be removed by pressing the ‘Delete’ button. This deletes the entries from the list to process but the data is not deleted from the database. Deleted rows will appear again after the list is refreshed.

It is possible to process less than the counted difference. For example the counted difference is -32. The quantity can be changed to -20. When processing the row, only 20 is processed and the remaining 12 will not reappear on the list. It is not possible to change the quantity to process to -34.

The item cost will be the item cost for the given warehouse (OITW.AvgPrice) when the following verifies:

  • The Item Groups Valuation Method is ‘Moving Average’ (OADM.InvntSystm = ‘A’) for the company
  • The Manage Item Cost per Warehouse option is enabled (OADM.PriceSys = ‘Y’) for the company

In other cases this will be the item cost (OITM.AvgPrice).

Contrary to the cycle count type ‘LostAndFound’, the processing of the positive and negative quantity is done oppositely.
A positive quantity means that there is not enough stock in the system. When processing this, a goods receipt will be booked to add stock to the system. A negative quantity means that there is too much stock in the system. A goods issue will be booked to correct this.

After pressing the ‘Update’ button, all rows in the grid will be processed. After processing, the system will inform the user that the processing has been done. After processing, the list will be refreshed. If there were deleted rows, they will appear again in the list.

Note: Goods issues can only be performed if the stock is not currently locked. If this is the case, the locking should be removed before processing the cycle count.

When the ‘Manually set price on processing the count‘ option is enabled on the Cycle Count Controller, the price of the items can be adjusted. Four additional columns are displayed on the screen:

  • Enter new price: Add the new price for the item to this field. By default it is filled with the value from the ‘Item Cost’ field. The price of a catch weight item cannot be adjusted on this field.
  • Price/weight: The price per weight ratio of the catch weight items. It is calculated based on: ((Total pieces x item cost)/Default weight ratio)
  • Enter new price/weight: Add a new price per weight ratio for the catch weight item on this field to adjust the price.
  • Total new price: the new total cost by item.
    • For normal items the new total price will be calculated based on: (Number of pieces x New price)
    • For catch weight items the new total price will be calculated based on: (Weight x New price/weight)

After processing the cycle count, the value from the ‘Total new price’ column will be added to the goods receipt/ goods issue document.

This topic does not exist yet

You've followed a link to a topic that doesn't exist yet. If permissions allow, you may create it by clicking on Create this page.