<vendor>
Good morning,
This response presumes that the vast majority of orders have less than 99 lines. I'm presuming here that you have been seeking an answer for an exceptional situation. Perhaps this is only for one order originator. Here's a work-around that merits significant polishing ... but, we're just at the conceptual "working mostly in the dark" level here:
a. Set those exceptional circumstance order transactions to summarize all the revenue into CEA on just one credit line.
b. Open a template spreadsheet that has all the possible credit account number destinations already populated so an analyst just has to drop in the monetary values in column A.
c. Analyze the exceptional order to populate >98 blank cells in column A with credit values until the summation of column A ties out with the summary $value credit amount. Having it in a spreadsheet enables a supervisor to review/initial the distribution before it is loaded into BCPS.
d. Automatically transport that spreadsheet data into CEF as a correcting journal
entry using Lickety-Split software.
http://www.unbeatenpath.com/software/dataentry/Lickety-Split.pdf.
That transport would take just seconds and whatever the supervisor initialed
in the spreadsheet as "OK" would not fall victim to a key-punch error.
Again, this is a "working mostly in the dark" conceptual idea ..... so, we don't know many things. However, it is conceivable that the template spreadsheet carries item codes and price logic over in columns K,L,M,N so that the user could just enter order quantities and then extension formulas would populate $$ into column A. Might not be too hard to get the Excel spreadsheet analysis done for those exceptionally long orders.
Again ..... if the user has this >98 lines problem on many orders, then this work-around gets to the point where you'll wear out Excel. But, if it is just once every week or something like that, then this conceptual approach might be easier than customizing the CEF AS/SET plumbing. The programming customization(s) would take way longer than the ~120 minutes needed to get Lickety-Split installed and the first data transport script humming.
By the way, Lickety-Split works for any spreadsheet to iSeries app, not just financial apps.
Warmest regards and God bless,
Milt Habeck
Unbeaten Path International
(888) 874-8008
(+USA) 262-681-3151
www.unbeatenpath.com
</vendor>
From: BPCS-L [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles DESBOIS
Sent: Wednesday, November 25, 2015 3:01 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Financial Orders
Hi,
Thanks for your suggestions, but I have to find this array because I can't summarize the journal, in fact the customer doesn't want it.
For the invoice with less than 99 lines, each line of the invoice are populated into the CEA journal and and the is one line of revenue per line of invoice.
I will continue to look for the program that populates the journal to find this array.
Sincerely/Cordialement
Charles
CDE Consult EURL
Charles DESBOIS
Tel : +33 6 07 398 901
E_mail : desbois.charles@xxxxxxxxx
midrange.com
