cancel
Showing results for 
Search instead for 
Did you mean: 

unable to see Inspection lot stock tab in UD??? how to make it appear?

Former Member
0 Kudos

Hello Friends

Some how i am getting three unexpected observation

1. Inspection lot stock tab in UD is not there.....how to make it appear so that i can do the quantity posting can be done.

For your information this is against good receipt & QA32 quantity to be posted is showing the qty correctly.....which means stk is in quality

2. In MMBE transaction i am not able to view batch & qty posting

3 In MB51 i can see the document details but qty is showing in unrestricted....which means stk in unrestricted which contractdory to my first statement.

Kindly let me know

1. How to make Inspection lot stock table available in UD

2 Any clue for 2 & 3 point if possible.

Thanks & Regards

Swanand

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Though inspection is pending, the actual stock is in Unrestricted.

Please check in MM02> QM view. For the inspection type 01. "post to inspection stock" radio button might not have been activated. Pls tick on the radio button. For future lots, system will show you the inspection lot stock in UD.

Thanks

Sachin

Edited by: Sachin Upare on May 5, 2011 1:24 PM

Former Member
0 Kudos

Thanks for reply

But the problem is not of stock going to quality or not.....anyway i checked it and it's correct.

Problem is i am not getting Inspection lot stock tab in UD.......here this inspection lot is created due to good receipt (inspeciton type 01)

My query is not yet answered

Thanks & Regards

Swanand

Former Member
0 Kudos

what is status of the inspection lot?

have you checked authorization part of QA11 ?? This can be a reason

Former Member
0 Kudos

Hello All

During trial and error we found that when P.O. has a/c assignment Category as K the inspection lot->UD->inspection lot stock tab was invisible where as when we removed a/c ass. Category as blank the system behaves correctly.

Other things also corrected.

Thanks for your inputs

Regards

Swanand