Business Partner Info - Credit available/Credit columns not aceptable info on 0$ credit limit.

Description

When a Business Partner has 0$ Credit Limit ( defined in Business Partner > Costumer ), and you make an invoice (for example 100$ )and it is full pay , then you check in Business Partner Info - Credit available/Credit columns , it shows Credit Available =-100, Credit =100 , and should be Credit Available =0 and Credit = 0.
For case when Business Partner > Customer > Credit Limit is more than 0$, the Business Partner info shows the correct amount in Credit available/Credit columns.

Environment

Windows 7, Oracle 11g, Intel I7

Activity

Show:

Carlos Ruiz December 18, 2013 at 3:34 PM

The info windows are now configurable - so, this can be set per implementation preference

Boris Ghelman August 12, 2012 at 11:52 PM
Edited

Carlos - Technicality speaking, you are right, calculations are correct, but from point of view of regular user, in case of Business Partner has 0$ Credit Limit, is hard to understand the way AD shows the numbers in Business Partner Info (all my costumer claim about it) so I suggest :

Adempiere Actual Business Partner Info, shows this info ::
0 credit
credit limit = 0
open balance = 100
credit available (info) = -100
credit used = 100

Suggested changes in Business Partner Info:
0 credit
credit limit = 0
open balance = 100
credit available (info) = 0 <=== instead of -100
credit used = 0 <=== instead of 100

Regards
Boris Ghelman

Carlos Ruiz August 12, 2012 at 2:40 AM

Boris - I think it depends on how you read those values (the meaning you give to them).

According to your tests

0 credit
credit limit = 0
open balance = 100
credit available (info) = -100
credit used = 100

1000 credit
credit limit = 1000
open balance = 100
credit available (info) = 900
credit used = 100

IMHO it seems fine - the customer has no credit, but it used 100 - so the calculations are correct.

Regards,

Carlos Ruiz

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

Created August 10, 2012 at 7:07 PM
Updated May 2, 2014 at 9:57 PM
Resolved December 18, 2013 at 3:34 PM