on 01-23-2011 12:18 AM
<h5>Hello Experts,
We are using SAPu2019s WM (LE) module for our warehousing need. Our WM implementation is mostly vanilla with batch management activated. Our business users are asking that all the batch managed items be blocked (no delivery, picking, and shipping) if they are expired or near expiry. All the batch managed items we receive in has expiry date entered.
If we maintain our Material Master data such as u2018min. self life expiryu2019 , u2018storage %u2019, and u2018Total self lifeu2019 (and necessary configuration), is there a standard SAP batch program (or solution) which can expire all the batch items expiring in the near future automatically?
Based on our research so far, we think the above MM data can be used for SLED picking strategy but cannot be used for expiring batch items automatically.
Note: We do not have SAP Quality module activated. Can we use QA05 and QA07 transaction if the Quality Module is not activated?
Any help/comments will be helpful.
Tejas<h5>
You can use QA07 to block expired batches. QM inspections are not mandatory for this transaction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tejas,
Using batch determination you can avoid picking of expired batches (see notes 33396, 72771). Expired batches won't be blocked in this case, they just won't be picked.
If you want to block those materials or to move them to another storage location, etc, you have to do it manually in standard system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Csaba,
you do not have to do it manually. There is a standard functionality - help.sap.com:
[Triggering Inspections for Batches|http://help.sap.com/erp2005_ehp_05/helpdata/EN/2d/351b97448c11d189420000e829fbbd/content.htm]
[Recurring Inspections for Batch Materials|http://help.sap.com/erp2005_ehp_05/helpdata/EN/be/00bbcfca5311d2961800a0c930e04c/content.htm]
Andrzej
Tejas,
I do not have a solution to your exact requirement, but I do have a suggestion.
You can, in LQ02, change 'standard' stock to 'blocked stock' (325 movement). This program can be run periodically in Batch. 'S' type stock is typically not relevant for any business function, including picking. In addition, it is typically not relevant for delivery in SD, nor relevant for MRP planning. In this way, you could become aware of shortages long before you need to actually pick them.
Unfortunately, there is no standard selection parameter in this transaction for 'expiration date'. In addition to Warehouse, material, and storage type, batch number, and storage location, the selection criteria also include many characteristics derived from the quant or bin. I worked once in an environment where the naming convention of the Batch number included the manufacturing date, and from this we could impute the expiration date, and therefore automatically block the expired stock.
It also might be possible to achieve your business requirement with a small change in business process, such as moving expired batch inventory into, say, a different storage location at the moment it expires. A nightly LQ02 background run could then automatically change the category of that material to S.
Best Regards,
DB49
User | Count |
---|---|
89 | |
7 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.