on 02-04-2009 7:39 PM
Hello,
My company is in the process of upgrading from 4.6C to ECC 6. I have an issue in the ECC 6 system occurring when I assign a usage decision and SAP posts the stock from Quality Inspection to Unrestricted. The problem is that in doing this, SAP creates a new batch number. I need to have the original batch number retained. In our 4.6C system, when doing the same usage decision and posting stock from Quality Inspection to Unrestricted, SAP does not generate a new batch number.
The usage decision catalog selected set code Posting Proposal UD = To unrestricted use; Unrestricted batch status. I have checked several other configuration settings between the systems and it seems to be the same. I donu2019t understand why ECC is acting different than 4.6C. Has anyone else run into this issue? Please let me know if you have ideas for a solution.
Regards,
A. Scott
Angela, shymal joshi has given correct answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Angela,
I think the problem is here............
SPRO->Logistics - General->Batch Management->Creation of New Batches->Define Batch Creation for Goods Movements for goods movement 321/322 the value must be "No Creation" if it is not such as then system will ask you for new Batch at the time of posting the stock from QI to unrestricted.
Regards,
Shyamal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The SPRO settings for Define Batch Creation for Goods Movements for 321/322 were set to u201CAutomatic / manual without checku201D. It is the same setting in our 4.6C system. I did not change this setting to u201CNo creationu201D, although I agree this would have solved the issue u2013 but we were concerned as to why the setting which works in 4.6C does not work the same in ECC 6.
We had also submitted a request for help to SAP, and were given the following solution which fixed our issue:
For transfer movements, the sending batch is automatically copied to
the receiving batch, if not system message M7-199 is customized as
"Error" type. If this message is customized as "Error", the program
would rather try to create a new batch.
This is explained in note 43334.
My recommendation in this situation is to customize (transaction omcq)
system message M7-199 as a "Warning" message. Then the QA11 process
will work without problems.
This is also a configuration change, but we implemented it as suggested by SAP and it has solved our issue.
Again, thank you for your reply.
Regards,
Angela Scott
Respected Mam,
thank you very much for sharing the important information over here. your this information sharing reply has really accomplished the purpose of the forum 100% of knowledge sharing.
I am really very thank full to you for the same. Actually last year we had implemented some notes, and as reaction of that the same issue introduced in our beautifully working system and started interrupting the same way. I also pasted the query to services market place but unfortunately didn't found the solution timely. As we were in extreme urgency to close the issue because of it was interrupting production server, we had decided to solve it the same way as I had replied earlier and didn't waited for the reply from SAP.
But you have shown me the other way to solve.
Thanks again.
Shyamal
Hi Angela,
Go to transaction QS51, and compare the UD code which you are using in 4.6C with ECC 6 versions. Check the u201CPosting proposal UDu201D field in that. Both should be same.
Also check if some follow-up action is included in 4.6C version with the u201CCodeu201D.
Example:
Code group Code Valuation Posting proposal UD
UD-110 Accepted VEMENGE To unrestricted use.
Regards
Nikhilesh Ray
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Angela,
QM->Quality Inspection->Inspection lot completion>Maintain Catalogs for Usage Decisions--->Edit Code Groups and Codes
Enter relevant fields & Check for relevant UD is released.
The UD released must be same as like your earlier version. I hope this will solve your issue.
Any further help, pls post details.
VRMP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.