The Journal Posting (GL190) program output states the message “Another job currently processing for company (0).”
This error indicates that another updating job is currently processing, in needs recovery, or was deleted from recovery.
Go to Job Scheduler and choose all users and verify that an update job is currently running for this company. If so, you will need to allow this job to complete before you can run GL190. If no active jobs, check waiting and resolve any jobs in needs recovery.
If there is not another job being processed or needing recovery, you will need to update the record that will allow GL190 to run. Create a paint a screen to update the GLSYSTEM file in the IF System Code and change the Updating field to 00 or blank out the field entirely.
GL190 may also create a GLMONITOR record that needs to be cleared. To clear this record, go to GL15.1, GLMONITOR Maintenance, and Inquire on the program that is running (in this case, you would Inquire on GL190). If a record appears, but the job is not actually running, delete the record.
There is a simple way to check the WAS Server status. First, open the command (cmd) prompt. The command to check which servers are running in WAS is in WAS_HOME/profiles/<profile>/bin. To check all the servers, supply the switch “-all”. Otherwise, provide a server name. See the screenshot below for a visual reference for checking the status of your WAS Server.
Follow these steps to update the server certificate in Infor OS.
- Log into the Infor OS server as an admin
- Mount the InforOS iso installer file. You’ll need the iso for the version that you are currently on. If you don’t have it already, download it from the Infor Concierge archives.
- Open command line as admin
- Navigate to the drive that was created when you mounted the ios
- Run command exe -v”CERTIFICATEUPDATE=true”
- Wait for installer to load
- Select “Modify”
- Enter the location of the new certificate, and the password. This should be a pfx file with a password.
- Click install, and wait for a successful completion.
Sometimes you may find that your scheduled flows have not run, seemingly with no explanation. When this happens, there is a good possibility that there was an error in the scheduler that needs to be resolved. To check the scheduler, log into Rich Client or your IPA Web Administrator as the user who owns the schedule. Search for “My Scheduled Actions”.
Find the schedule of the flow that didn’t run, and verify if there is an error. Double-click on the failed instance at the bottom of the screen to get more detail on the error.
Once you have resolved the issue that caused the error, right-click on the instance and select “Requeue”. Note that this will cause your schedule to run immediately.
After the schedule has run successfully, there will not be any more items in the “Action Instances” tab.
If you’re an On-Premise Lawson client and your Windows user profiles were wiped and you you’re your shortcuts to Rich Client. You can still access Rich Client directly with the local Lawson user account.
First, find out the local lawson account in services on the Landmark server:
Use Windows Remote Desktop Protocol (RDP) to login into the Landmark server with the .\lawson local account which should show the domain as the Virtual or Physical machine name:
Find and run the the Command Window for Lawson Landmark as Administrator.
Type canvas64 gen and press enter
This brings up Rich Client with full access
Purchase order PO140 – program information has some useful functions. For instance, you can run Receiving Release and Delivery (PO140) to release receivers and are able to print a list of all released receivers as well as a list of unreleased receivers with errors. PO140 is also able to create and print Delivery and Putaway tickets. Additionally, it can also update the ARRIVAL file for Mobile Supply Chain Management) tracking. Once the delivery ticket is printed then it will update the delivered quantity in the POLINESRC table. This is what Mobile Supply Chain Management, or MSCM, uses to update the Quantity On Order.
For this example, we will be granting access on a restricted function code on GL45.1. The function code is the Q – Quick Post.
On the Lawson form to get more information, select the function code field and press CTRL + SHIFT + O
We care about LINE-FC and parent column DT0.
- In LSA create your security class and click add rule.
- Grant all access to GL45 system code:
- Now expand GL45.1 and search for column DT0, then expand it.
- Find LINE-FC and select it
- On the right, select the Unconditional Access for Action and click in the blank white box, you’ll see a list of codes you can grant access to. For this example select Q for Quick post.
- Now click Apply and you’re done.
You can also restrict this by creating a Conditional Rule Access.
Good luck!