× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello,
Based on the info you have given, I suspect the subject line should read 
"user problem". Sorry.
When the user converts the RMA to an order(Credit) type 1 class 7 and tries 
to accept, they are presented the ORD725 allocation detail screen. This screen 
displays all existing lots for this warehouse for this item. I think it is 
probably the same list and sequence and source as in ORD300/F19. It is not the 
system but the user that selects one or more of these entries or creates a new 
one if the returned lot does not match any on the display. It sounds like this 
user is always picking the first entry on the screen and putting the entire  
return quantity into that lot and location. Hope this helps.
Regards, Larry


In a message dated 5/28/2003 6:45:45 PM Eastern Daylight Time, 
Yoke.Fan@xxxxxxxxxx writes:


> Subj:RMA Problem 
> Date:5/28/2003 6:45:45 PM Eastern Daylight Time
> From:<A HREF="mailto:Yoke.Fan@xxxxxxxxxx";>Yoke.Fan@xxxxxxxxxx</A>
> Reply-to:<A HREF="mailto:bpcs-l@xxxxxxxxxxxx";>bpcs-l@xxxxxxxxxxxx</A>
> To:<A HREF="mailto:bpcs-l@xxxxxxxxxxxx";>bpcs-l@xxxxxxxxxxxx</A>
> Sent from the Internet 
> 
> 
> 
> Dear All,
> 
>      In eBPCS 6101 version RMA cause the inventory inconsistent. According
> to the error result, The whole return quqntity alway add to the first lot's
> issued qnantity on ILN table. someone has this same condition or  solution?
> 
> Best Regards,
> 
> Yoke 1994-1996
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.