Skip to Content

SAP MM:- Material tracking in GI

Hi Gurus,

We procure capex items using WBS element in account assignment. Our user want to track materials in GI as per GR or PO number. I've suggested them to activate batch management in material master. But it is not feasible to activate batch in those materials of which stock is already present. Also it is hectic work for MM department & they do not want to do. Is there any other option available to track materials in GI so that we can find, from which GR or PO, the material has been came from?

Thanks & Regards,

Biswajit Dey

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Best Answer
    Oct 14, 2017 at 11:50 AM

    Please print my blog and give it to your customer, may be can convince your customer more than what you told him:

    https://blogs.sap.com/2014/12/09/how-old-is-my-stock/

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 16, 2017 at 05:56 PM

    Dear Biswajit Dey,

    To me there is no other way then Automatic batch determination in GR and GR. As of now, you are unable to activate it because of Stock, so the only thing left is to manage the material physically by tagging it and once material is reduced to zero, then activate it by material by material.

    Hope you got my point.

    best Regards

    Mohsin Abbasi

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2017 at 03:03 AM

    Hi Biswajit,

    So far i know, only WBS, Batch number and serial number can be used to track and control the goods movement.

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 14, 2017 at 02:13 PM

    Hi,

    Hope JL has already answered your thread!.

    Stock addition and usage is like you filling your vehicle fuel and consuming it - it will be keep on filling in same tank and you can not identify fuel filled on which date is being used now.

    If you want to track the stock, you need to differentiate the stock based on the GR or any required criteria. The best and easy option is the batch management as you already mentioned. If the number of items for batch activation is huge, and there are huge number of dependencies, you may request the customer to get the report mentioned in the note: 53327616 Setting the batch management requirement and the doc: https://archive.sap.com/documents/docs/DOC-27880

    In order to reduce the burden on Stores, you may think about automatic batch numbering based on any required criteria like GR number or PO number etc and configure automatic batch determination for GI / PGI. With automatic batch determination settings, In GI, user can get the batches with a single click and in PGI system can deermine it automatically based on the settings. You may check the options and revert back.

    Regards,

    Prasoon

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 18, 2017 at 10:09 AM

    Thanks to all for your quick response.

    We need to track movement of Capex items which has no Expiration date. So SLED model is not applicable here.

    User need to make sure that movement of Capex items must follow FIFO logic. Since there is no tagging in material, stores dept. can issue material in random basis. Sometimes it happens that, materials physically belongs to one project has got issued in a different project. So there is no control over GI. At the time of assetization, cost calculation become more complex. User want to track the material movements & make the GR-GI synchronized. I think as you've said, Batch management will be the best solution. But the only difficulty is to activate batch in materials (having stock) individually.

    Thanks & Regards,

    Biswajit Dey

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 06:10 AM

    User will take decision whether they'll move to batch management or not. Thanks to all for the support.

    Thanks & Regards,

    Biswajit Dey

    Add comment
    10|10000 characters needed characters exceeded