on 12-20-2015 10:48 AM
Dear Experts,
We have done the Automatic batch configurations and now the client requested to filter expired batches from the determination. Currently client is using LOBM_HSDAT (Production Date) and LOBM_VFDAT (Expiry Date) and assinged these directly to the Material Master batch class and using the same class as selection class.
For filtering Expired batches, we created a new selection class with LOBM_VFDAT, LOBM_LFDAT and LOBM_RLZ. We assinged the value for LOBM_RLZ in condition record as >=30 d.
But during batch determination at Sales order level, Selection criteria is showing the value for LOBM_VFDAT as for example: 19.01.2016 instead of >=19.01.2016. Attached the screenshot for reference. Because of this all the expired batches are shown in Batch determination at sales order level.
How to make the value of LOBM_RLZ as >=xx.yy.zzzz instead of just date (xx.yy.zzzz)
Thanks & Regards,
Ramesh Balaji. N
Have a look at the following OSS notes:-
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lakshmipathi,
Thanks for your response.
We checked the Batch class and found that for LOBM_VFDAT, client created a customized characteristics but haven't added the dependency SL_MAX_COMPUTE which exists for LOBM_VFDAT.
When we tested with LOBM_VFDAT instead of customized one the relation operator is working fine but not for customized one.
So is the missing dependency assignment is the actual problem for the issue?
Thanks & Regards,
Ramesh Balaji. N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
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.