Skip to Content

LICC and LX26

Hi,

We plan to use cycle counting at the WM level and are looking at LICC (quant level) and LX26 (bin level). I know how the tcodes work, which fields they update and when. I have also gone thru various posts but I cant see anywhere a way to count an A (monthly) item in the entire warehouse (we use random storage and mixed storage with batch management) in one stock taking activity. With LX26 I would be forced to count all mtls (A,B,C,D) in a bin even if one mtl becomes due to be counted on a particular day. With LICC, I have quant level counting and we could receive the same mtl/diff batch on various days of the month. In that case its not possible for the warehouse ppl to keep track of the various quants then decide when to count the "A" quants and "B" quants so on. How have others solved this. Basaically what we need is count all the A materials and all their quants 12 times a yr, B 6 times a yr and so on. Do I need to enhance LICC ?

Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Nov 23, 2017 at 01:19 PM

    Dear Gautam,

    We are using LICC for the count verification in our warehouse. As you are aware of the t-codes working, the proposal for counting a particular quant of a material is dependent of the ABC Analysis. further note that the quant number is a perishable unit. i.e. once the quant is empty, the quant no longer exist. Therefore, the proposal of the be counted will be based on the available quants along with the time the quant is there in the system. so if a quant is created two days before the planned counting, the quant may not appear in the plan.

    My two cents will be, count all the quants that are available in the store on the particular date. also, engage the ABAPer for the creation of a report that will show all the quants that have been counted throughout the counting period.

    Hope this addresses your query.

    Regards,

    Barakzai.

    Add comment
    10|10000 characters needed characters exceeded