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



This is basically what MOP 96 states.

Richard




"John Leopard" <jleopard@infoalt.com>
Sent by: jbausers-l-bounces@midrange.com
01/28/2003 12:41 PM
Please respond to GEAC/JBA System 21 Users

 
        To:     GEAC/JBA System 21 Users <jbausers-l@midrange.com>
        cc:     jbausers-l@midrange.com, jbausers-l-bounces@midrange.com
        Subject:        Re: [SYS21]   Credit check failing to suspend orders



Try checking your Inventory descriptions field CRDC, minor code CRLV = 1
(for Credit Limit); minor code CRLD = x (where x = 0 - 5 for Credit Limit
Days).


Following is an excerpt I put together for a client.


Standard JBA Product Docs contain the following information regarding 
sales
order suspension through either order entry or advanced order entry.

In Accounts Receivable customer setup, 1/ARM Names and Addresses, two
fields affect the ability to suspend orders in SOP or OE.  These are the
Credit Limit and the Credit Limit Days.  The Credit limit, if populated
with an amount may then be used to check sale orders.  The Credit Limit
Days is set to 0 for no checking, or a value for the number of day.

Credit limit is effective to check sales orders if inventory descriptions
field CRDC is set up with minor code CRLV = 1.  Credit limit days is
effective only if inventory descriptions field CRDC is set up with minor
code CRLD = 1 ? Debtor days, 2 ? Days sales outstanding, 3 ? Average Days
to Pay, 4 ? Average Days Slow, or 5 ? Overdue days.

In Inventory descriptions file maintenance, 1/INM, three descriptions
fields are used:  CRDC ? set "0" to only allow existing credit checking in
SOP an AOE; "1" to use additional credit checking values set in customer
master file.

Credit Limit
CRLV, if set up as a minor code to CRDC and valued at "1" will cause 
orders
to be suspended if the credit limit check fails.
Credit Limit Days
CRLD must be set up as a minor code to CRDC and valued with 1-5 to cause
credit limit days to suspend an order.

If either check fails, the order will be suspended.

Also, if CRLD is set to 1, 3, or 4, Trend Parameters in Accounts 
receivable
must be maintained and run to update customer days, days to pay, or 
overdue
days.

Hope this helps.



John Leopard, CPA
Manager, Business Consulting
Information Alternatives, Inc.
9850 Redhill Drive
Cincinnati, Ohio  45242
513.793.2929, ext. 305
513.936.4040 fax
jleopard@infoalt.com


|--------+----------------------------------->
|        |          "Neil Thursby"           |
|        |          <neil.thursby@fone-logist|
|        |          ics.co.uk>               |
|        |          Sent by:                 |
|        |          jbausers-l-bounces@midran|
|        |          ge.com                   |
|        |                                   |
|        |                                   |
|        |          01/28/2003 11:53 AM      |
|        |          Please respond to        |
|        |          GEAC/JBA System 21 Users |
|        |                                   |
|--------+----------------------------------->
 
>--------------------------------------------------------------------------------------------------------------|
  |                                       |
  |      To:     <jbausers-l@midrange.com>        |
  |      cc:     (bcc: John Leopard/CIN/IAI)          |
  |      Subject:     [SYS21]   Credit check failing to suspend orders     
                            |
 
>--------------------------------------------------------------------------------------------------------------|




We use AOE, and have seen several orders pass credit checking when the
customer concerned was over their credit limit. These orders did not
suspend, and were despatched when they should not have been.

The circumstance this happens in is very simple; we don't use customer
hierarchies or anything complex.  Simply, the customer's account balance
was higher than his credit limit.

Just want to know if anyone else has seen this problem please as JBA are
unable to reproduce it.

Thanks in advance,

Neil.

_____________________________________________________________________
This transmission and any attachments are confidential and are intended
solely for the named addressee (s). If you are not the addressee, please 
do
not read, copy, use or disclose this transmission and please notify us
immediately by telephone on
+44 (0) 1670 594848 or by reply.  Please then delete this transmission 
from
your system.

Although we have taken steps to ensure that this email and attachments are
free from viruses, we advise that in keeping with good computing practice
the recipient must ensure that they in fact are virus free.

No contracts may be concluded on behalf of Fone Logistics LTD by means of
email communications.

_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.






_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-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.