on 07-31-2012 7:44 AM
Hi all,
I am facing an issue in revalidation of a batch.
I have a material with Batch no. say X at plant A.
Now, i have transfered a part of this batch X to plant B as there was an urgent requirement at plant B.
So now batch X exist at plant A as well as plant B.
Now, the status of the batch is restricted due to the QA07 job scheduled.
The quality personnel at plant B has tested the material and wants to revalidate the batch. But is unable to do so.
Error says : "You have no authorization for this transaction in storage location xxxx"
System is asking for authorization of plant A sto loc xxxx.
One of the solutions being used here was asking quality head who has authorization of all plants to revalidate the batch.
Is there a way the plant QC personnel can do this transaction?
Regards
Hello Neeraj,
did you solve your problem?
What is you batch level? If your batch level is plant, than the batches are independant and ever plant can change there own batch.
I have the opposite requirement: we are changing our batch level to material and we want the bahaviour you are describing: if batch A was created in plant A than only personal in plant A can change it. Is that standard behaviour? I can't test any of that right now, because our batch level is still plant.
Best regards,
Horst
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, the batch status changes to unrestricted at both the plants simultaneously.
Even if we i/p a specific plant while changing the status through MSC2N.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Neeraj,
Since the expiry date, next inspection date and batch status are a batch level, this data remain same across all plants. That could be the reason you are facing this problem.
As per my understanding, whosoever may be the user but he / she should perform MSC2N transaction only to change the batch status (or the user need same authorization object to carry out this change). Its solely your organization's decision which access to be granted to whom. I still think that you should discuss this issue internally with your business / IT authorities who decide user's roles and authorization.
Regards,
Anand
Thank you Anand
I understand that user roles and authorizations are internal decisions, but i am trying understand something else here.
Since the expiry date, next inspection date and batch status are a batch level, this data remain same across all plants. That could be the reason you are facing this problem.
So there is no way to have different status of the same batch at 2 different plants.??
To the best of knowledge no! However better if you can have suggestion from MM consultant!
Regards, Anand
Message was edited by: Anand Rao Stock type can be different (e.g. stock in plant A could be in quality inspection but in plant B it could be in unrestricted or block against the same batch ) but status (restricted or unrestricted) would remain same for both the plants.
Hi Neeraj,
Now, the status of the batch is restricted due to the QA07 job scheduled.
Ensure you use correct transaction code with appropriate plant. If system throws error for authorization, then I think it is self explanatory. Grant the authorization. I also believe that which user should perform which transaction is purely organization's decision and as per organization's policy. You may need to consult internally or this.
Regards,
Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
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.