Re: Invoice print sequence (Greg Wenzloff)

My name is Ken Anderson and Infor XA partner for Paperless Process
Management partner Quadrant Software. I work for a vendor.

I would also like to add that by using our electronic forms package,
Formtastic, you are able to re-sequence your output, by any field within
the document without any source changes. For example, in the case Greg
is describing, I would go into the form template for invoice in
Formtastic on the 400, page down to sort criteria, and F4 prompt and
select the first field I want to sort by (in the design of the form you
have named all the fields you are using), Invoice number. Then I might
choose to sort by customer name, then by zip code. No matter what order
the Invoices were in when the batch spooled file was created in, they
will arrive at the printer sorted by, Invoice number, then by customer
name, then by zip code.

People frequently do this with laser checks. They might have all checks
under $1,000 automatically signed, and everything over $1000 or
requiring more than one signature, sorted to the top of the pile to be
manually signed.

Best regards,




Kenneth Anderson, CDIA+
Quadrant Software
' (813)-971-9500 ext.330
* mailto:kanderson@xxxxxxxxxxxxxxxxxxxx
www.quadrantsoftware.com







----------------------------------------------------------------------

message: 1
date: Thu, 27 Mar 2008 13:51:25 -0400
from: "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx>
subject: Re: [MAPICS-L] Invoice print sequence

I just want to close the loop on this thread. We are now printing our
invoices in customer number sequence and it was quite easy to do.
Instructions are available on the MAPICS support site. You just need
to:

Have the proper version of program AMBFUXFR and UMBINVKR.
Have the source code for UMBINVKR and file MBDHRESU.

Then rename the file to something unique -- I used MBDHRESX --- and
change the key of the file to the sequence you want --- compile it.
<retain the first 2 key fields and add from there>
For customer sequence the key fields will end up DHBUCD, DHK0NB, and
DHCANB.

Change the file spec in UMBINVKR to the new name of the file you just
compiled and then compile that program.

The last thing you do is to turn on the user exit using the COM file
maintenance options.

On my system XAR4 system I had to add one record to the user exit file
MZD3CPP with this data:
APP ID = B
Process group = INV
API code = K
API flag = U
status = 0
program = UMBINVKR
description = Invoice Print Sequence

That's all there is to it; the users have said this makes bursting a
stack of invoices for mailing much easier.
Greg