× 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.



Hi Jim:
I sat up a work file here and it has been worked
perfectly for me. Good luck.

--- Jim Mergen <jmergen@xxxxxxxxxxx> wrote:
> Hello,
> 
> I have a client running 4.05 . When they they post
> to a Shop Order(SFC600) the users all use '1'
> (Generic Emp) for the Emp/Line/Clock number. Now
> they would like to know user/workstation of any
> operation posted , but without requiring the users
> to enter a unigue Emp number.
> 
> Is there anywhere in BPCS that captures User/WSID
> when a user posts to a Shop Order? Looking at ITH I
> see issues and reciepts. FLT(if there was labor
> posted) shows the Emp#, but again they all use #1.
> FOD shows SO#, Op# , Qty but no WSID or user.
> 
> I was looking at creating a work file and each time
> they post I would capture this info, but wanted to
> make sure I am not overlooking something.
> 
> Thanks
> 
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing
> list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/bpcs-l.
> 


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.