How to Fix Lawson Backoffice Publish Issue
How to Fix Lawson Backoffice Publish Issue
This is a simple fix but sometimes hard to determine even if you’ve reviewed the Infor documentation.
So first lets make sure your FTP settings are setup correctly:
Lets assume you already published your report in LBI, for us we are doing CU201 for testing:
We run the job again so it will publish automatically via backoffice:
Problem:
The broadcast.csv and published.csv shows the CU201 report being transferred but the Instance is NOT being created.
Solution:
Give your Lawson Backoffice user write/read access to the LSF %LAWDIR% directory as well as FTP access to \Lawsonprod_Apps which most have setup already.
Results:
You should now see the instance created when you run the same CU201 job:
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.









