Re: Problem with 'C' transaction

We are on 405 CD MM
The help for INV500 is based on standard transactions, and is not going to
change when you change transaction effects.  BPCS software is not that
sophisticated.
Check the inventory documentation in BPCSDOC file from DOC menu for
specific rules for reserved transactions such as 'C'.
Even though it would appear from INV355 that you can tailor any field of
ITE file rules to meet your business needs, some fields are locked in
(reserved) by how some programs function.
There are some types of transactions which do not support doing a negative
correction, in which you have to have some other way of accomplishing an
opposite direction transaction.  (For example negative shop transaction PR
CI corrections via JIT600.)  I don't suppose CST100 (which generates a '#')
will cut it for you?
There is no on-hand quantity field in BPCS.  It is dynamically computed
from opening balance, receipts, issues, adjustments, in files IIM IWI ILI ILN
Warehouse Master IWM Location Master ILM are just used to designate what
warehouses and locations exist.
Be careful when reading the help when it comes to interpreting which files
will be updated.
I believe that if you take any location inventory into the negative or
possibly just even zero, it gets flagged for cycle counting.

>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

-
Al Macintyre (macwheel99@sigecom.net via Eudora)