http://ofbiz.116.s1.nabble.com/Help-with-POS-behaviour-tp174892p174902.html
for returns. The negative quantity "process" is really a work around
done. In others words I suspect the correct thing to do is actually
> Iain,
>
> Unfortunatly POS is not using much (actually any for the moment) verbose. Please see "trace" and "Debug." in PosTransaction.java.
>
> For the 1st point I have no quick answer. I will take a look ASAP...
>
> Jacques
>
> ----- Original Message -----
> From: "Iain Fogg" <
[hidden email]>
> To: <
[hidden email]>
> Sent: Wednesday, November 29, 2006 5:45 PM
> Subject: Help with POS behaviour
>
>
>
>> If you process a customer return via the POS application, it always
>> seems to think that the payment type is CASH, whether you select CASH,
>> CHECK, or CREDIT on the payment screen. (In this context, "payment" is
>> actually a refund).
>>
>> Consequently, the accounting ECAs are updating the wrong account - CASH
>> IN REGISTER is credited instead of the default GL account for whatever
>> "payment" method you select (eg, IN TRANSIT FROM CREDIT CARD SUPPLIER
>> for a CREDIT CARD refund).
>>
>> Frankly, I can't see where the payment type is being set to CASH in POS,
>> so I'm starting to suspect there may be an ECA further downstream that
>> is assuming any negative amount (refund) needs to be handled as a cash
>> transaction, but that's just because I'm starting to clutch at straws :-)
>>
>> Also, can some kind soul tell me how to turn on verbose debugging in POS
>> - setting the global verbose flag in
>> framework/base/config/debug.properties doesn't seem to do the trick.
>>
>> Tips/pointers appreciated, Iain
>>
>>
>>
>>
>> --
>> No virus found in this outgoing message.
>> Checked by AVG Free Edition.
>> Version: 7.1.409 / Virus Database: 268.14.19/556 - Release Date: 28/11/2006
>>
>
>