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



Eric,

I had stumbled across an incident about a year ago where we ran into
problems matching up the accounting 'C' transactions to the PO receipt 'U'
transactions if they were in different warehouses.  From what I remember the
warehouse the C transaction is looking for should be the warehouse that was
on the PO.  Our problems was that we created the PO against one warehouse
but we were changing the warehouse upon reciept - and then accounting
records were not matching up with the C transactions...since I don't work on
the accounting side I can't give you the details of their problems, but it
is something to look at.

Good luck,

Beth A. Norris

Production Control Manager
Fawn Engineering Corp.
Des Moines, IA
bnorris@wittern.com


-----Original Message-----
From: Eric Tam [mailto:eric-tam@mvphk.com]
Sent: Friday, June 21, 2002 9:07 PM
To: bpcs-l@midrange.com
Subject: RE: Problem with 'C' transaction


Thanks for Bill and Al's reply.  I've checked the parameters, we're running
costing by Facility.  Is this the reason why I was asked for the warehouse,
which is then used to identify the corresponding facility?

I've also read the BPCSDOC.  It gives nothing more than the help regarding
'C' transaction, as well as the Warehouse and Lot / Location Level.
Anyway, I've input a 'C' transaction with Warehouse Level  set to Y.  It
seems that no change has been made to IWM and IWI.

Eric

-----Original Message-----
From: bpcs-l-admin@midrange.com [mailto:bpcs-l-admin@midrange.com]On
Behalf Of Moy, Bill
Sent: Friday, June 21, 2002 9:54 PM
To: 'bpcs-l@midrange.com'
Subject: RE: Problem with 'C' transaction


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi Eric,

        It appears your C is set up to affect cost, are you costing by
Facility?

Bill

> -----Original Message-----
> From: Eric Tam [SMTP:eric-tam@mvphk.com]
> Sent: Friday, June 21, 2002 03:08
> To:   bpcs-l@midrange.com
> Subject:      Problem with 'C' transaction
>
> Hi,
>
> We are on 6.1 MM.  I try to enter a 'C' transaction of -ve qty through
> INV500 to reverse another 'C' transaction generated by vendor invoice
> posting.  However, a message comes up saying that the warehouse is
> invalid, which is actually not prompted for input.  The definition of
> transaction effect 'C' is as follows:
>
> Transaction Type    C
> Description           P.O. INVOICE RECEIPTS
> Ref No./ Description  P.O. NUMBER   Affect Resupply order
> Location Description  LOCATION      Check Resupply order
> Cost Description      ACT TOT COST  Affect PO Qty in Inspection
> Comment Description   INITIALS      Redesignate Transaction
> Opening Balance                     Affect Actual Cost    Y Affect Y/not Y
> Receipts                  Warehouse Level
> Adjustments               Lot Master                        CONTAINER
> Issues                    Cost Adjustment      Y
> Sales Units               Cost/Price Entry     Y   Trigger QA Activity
> Sales Amount              Multiple Issue
> Item Last Tran Date       Check Purch Order    Y   Spread Receipt
> Whse Last Tran Date       Check Shop Order
> Affect Shop Order         Check Purch U/M      Y
> Aff PO Quantity           Location Level
> Aff PO Cost           Y   Shop Order Issue
>                           Affect Cycle Count     Program/Procedure
>
> I try to clear the Location Description to see if it's the problem. But
> the Warehouse Level is then set to Y automatically.  Putting a value back
> to the description field even force me to put a Y to Location Level, which
> then again set Warehouse Level to Y automatically.  If Warehouse Level and
> Location Level are set to Y, what will be affected?  The help says that
> the Quantity field in the warehouse master and lot / location master will
> be updated.  But I can't find any quantity field in these masters.  I
> thought this transaction effect was used to update actual cost only, why
> is warehouse involved?
>
> Does anyone has a clue on what's going on?  Thanks in advance for any
> suggestion.
>
> Eric Tam
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
> or email: BPCS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.


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.