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



Indah,

I believe that you said that the transactions that were showing different 
work centers in the ITH was the (I) Shop Order Single Issue-Component. If 
so, you should check the Transactions Effect record (INV150) for that 
transaction code, and make sure that the field "Check Shop Order" is 
marked with a "Y" for Yes. This will require the person who is doing the 
transaction to input the correct data to match the shop order. The only 
other suggestion I would have would be to check that the shop isn't using 
alternate routings (Method Codes) that might account for the difference, 
but again, the FOD would reflect the routing version defined at shop order 
creation. Let me know what the Transaction Effect record is reflecting 
regarding the "Check Shop Order" field. 

Frederick C. Davy, CPIM, PMP
Business Systems Analyst
Interface Solution, Inc.
Phone: (315) 592-8101
Fax: (315) 592-8481
e-mail: fcdavy@xxxxxxxxxxxx




Indah <indah.kurniaty@xxxxxxxxx> 
Sent by: bpcs-l-bounces+fcdavy=sealinfo.com@xxxxxxxxxxxx
07/17/2006 12:14 AM
Please respond to
SSA's BPCS ERP System <bpcs-l@xxxxxxxxxxxx>


To
"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
cc

Subject
Re: [BPCS-L] For transaction type = I, where ITH/THWRKC comes from ?






Thanks for your reply Frederick.

In case that ITH/THWRKC doesn't represent FOD/OWRKC, it mean we should
create small program to update it? because ITH/THWRKC have relation too 
with
G/L macro in creating issuing journal. (as I know we can't create G/L 
macro
from FOD/OWRKC)

What is your opinion regarding why sometimes ITH/THWRKC can be not same 
with
FOD/OWRKC ?

Thank you.

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.