File Paths for MHC - Document Express

Does anyone have a master list of where Infor-Lawson outputs files to for Document Express? IE serverd$prodlawwork etc. I need the directory for the eRemit files, PO files, AP checks and PR checks. Thanks in advance!

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Each program puts out files in its report folder. Sorry I can't help with PR. All the others go under the user's print directory, in the folder underneath the job name. Say a processor named "JaneDoe" sets up an AP check run for company "Able" dept "Baker" with AP155 and the job name is "AbleBaker". So under %LAWDIR%print userIDablebaker1 the file "check" is the one you want. In our case, we are running Lawson 10x, and the path is (some names changed to generic names for security's sake)

\LawsonServer1DriveSharelintelawprintDOMAIN_JaneDoeablebaker1

In this case, because we've shared the Lawson drive on server "LawsonServer1" as "DriveShare".

There's a 'remit' file in the AP155 folders but it is empty.

We use AP160 to generate a useable 'remit' file for ACH. Again the location is based on the job name.

HOWEVER in the case of AP160, it also generates an ACH work file that is sent to the bank, and that one is located in the work folder: %LAWDIR%PRODUCTLINEworkAP160ACHTAPE

Same for the PO job folders. We use PO120 and the file Document Express grabs is 'p-form1'. At least that's what I find in my documentation.

This leads to complex setup. Since every processor has their own login, their print folder is separate and there are no shared output folders. Setup has to be done individually for each person, for every different job, even when the job names are the same. And of course, each processor has to have rights from the Document Express machine to the Lawson folders where the files are being accessed. Sometimes that gets a bit funky.

As you can see for ACH checks, that's the one case where _everyone_ writes to the _same_ bank file. Careful, careful, or one person can overwrite the file before the other person has sent it to the bank! I think that it's possible to change the output location for work files so maybe the output location can be standardized, but that's more than I have time for right now. If you do, you'll run into that very same problem, where employees can overwrite files if they're not careful.

unknown

LSF9 and LSF10 by default for PO, AP and PR160 files are placed in the processing user's print directory. Manual PR payments are placed in the root of the product linework directory as MAN-PMTOUT. On The Windows Lawson application server I have created two "Advanced" shares one on the PDLWork and one at the top level of the Print directory. This way member assignment to the groups is managed easily in Active Directory.

Notes:

* The user logged on to the MHC processing PC will need Full access to read and write to these shared directories as MHC program will need to rename (Write - append) name of imported files so that they are not re-imported at a later time.

* File sharing on the Lawson Application server is very touchy. If not done correctly, batch jobs will fail for all users and go into the Job Waiting queue. There is a Lawson Utility called permsmaint that will restore folder permissions but best if you don't need to do this. Seek details from Infor support on proper way to share these directories.

* Create drive mappings to the shared drives from above on the user MHC PC (s). Point each MHC setup to import parameter to these directories or go directly to the individual named under the Print directory. Click on the parameter for recursion so all folders under user name is searched for the payment file which that user named upon creating and running PR160 job. Hope this helps!

unknown

For AP I use PRTDEF to create a printer definition that executes a bat file - /lawprod/gen/bin/mhcprint.bat . When the user selects this to print the checks it sends the output to a temp directory and then to a folder that is accessible by MHC. The code is:

cat > D:lawprod empprtfile.%pid%

move D:lawprod empprtfile.%pid% D:dataacctpayapcheck

del D:lawprod empprtfile.%pid%

exit

For Payroll I created a flow that gets executed when a file is created and the PMTOUT file is copied to a folder accessible by MHC. I modified PR160/PR180 to create the file and then set up a file channel to detect the file and fire off the flow. I did this because I didn't want to have to rename PMTOUT to keep the flow from be executed again.

unknown

Similar to the other responses, for both our AP and our PR check jobs, we create path/file overrides to control the output file names and/or locations. This is accomplished using either the the filename field on the job submission forms or actually going into the jobdef record and defining them. Then, we simply update the import routines in MHC to import the appropriate files from those locations.

unknown

We have MHC script that will pull all our files regardless of where ever they are written and puts them in a central folder. The MHC file mover will then move the files to our local MHC install machine for processing. This includes AP, PR, PO, invoice etc... files. You can DM me if you need a hand with this set up.

unknown

Question please - does anyone know if on Lawson version 11, do you still need a 3rd party, like MHC, for check printing, or is it built into the software?

Copyright © 2025 Infor. All rights reserved.