Updating Your Lawson License

, ,

You need to update your license file if you exceed the maximum number of application users. All application users are also Infor Lawson Environment users.

The license and applications information is stored in the %LAWDIR%\system directory.

Note:  To update your license, you must first have received a new license file via e-mail from Infor.

Shut down the WebSphere application server. Use the instructions provided with your application server to stop the server you configured to run Infor Lawson. The person who shuts down the application server must be a member of the group for Infor.

Stop the Infor Lawson system.

At the command line, specify this information:

stoplaw

Optional. If you want to keep a copy of your existing license, make a backup copy.

Copy the license content you received in email to %LAWDIR%\system. At the prompt to overwrite the existing file, select yes.

Start the Infor Lawson system.

To start the Infor Lawson servers, at the command line, specify this information:

startlaw

Restart the application server. Use the instructions provided with your application server to start the server you configured to run Infor Lawson. The person who starts the application server must be a member of the group for Infor.

Note: The web server must be running in order for the Infor Lawson system to run, but you do not need to start it before you start the Infor Lawson system.

Edit the Install.cfg Encrypted Values

, ,

Certain passwords in install.cfg are encrypted, and if those passwords change, you will want to update install.cfg before running patches.

To edit the file, first open a command line window with the environment set.  Then run the command

Java -cp %GENDIR%/java/thirdParty/installer.jar com.lawson.delivery.secure.PasswordAdministrator -s %LAWDIR%/system/install.cfg

First, you will be prompted to enter the password that was used to secure the Lawson system configuration.  If you don’t know this password, or if you need to change it, this is your opportunity.  Leave it blank and you will be prompted to enter a new password.  Then, you will need to rerun the command with the new password.

Once you enter the configuration passkey, you will be presented with a screen that contains all the encrypted passwords.  You can select the clear text radio button to show the passwords if desired.  Here, you can update ore view any of the passwords.

Click Finish and you’re done!

 

Dock Logging screen button changed on handheld

, ,

Issue: Using RAD > Dock Logging on the handheld, users noticed that in the upper right corner, the selection changed from ‘Print’ to ‘Send’

 

Resolution:

To change the value on the Dock Logging screen from ‘Print’ to ‘Send’ follow these steps:

In MSCM portal, go to Receiving and Delivery > Receiving > Configuration > on Misc Receipts tab

Scroll to the bottom and there is value for Dock Logging Configuration

If the Auto Print is on, the device will say ‘Print’ in the upper corner.

If the Auto Print is off, then it will just say ‘Send’

Turning off the printing is a Global setting and affects all users who use Dock Logging.

Turning the Auto Print on will show  the ‘Print’ selection on the device.

AP45.3 Add-Ins upload error Cannot change Payment Date delete and re-add record

, ,

Problem/Issue:

While attempting to utilize Lawson Add-Ins for Microsoft Office to upload data into AP45.3 (Non-AP Reportable Income Adjustment), some users may encounter the following error message: “Cannot Change Payment Date; delete and re-add record.” How can this error be resolved?

 

Resolution:

Luckily, this isn’t a serious error and it has a quick fix. To address this issue, simply follow these steps:

  1. First, check and make sure that you use “A” as the FC Code instead of “C.”
  2. Next, utilize the “Try to Add, then try to Change” option during the Add-Ins upload process.

The error message should go away and you will now be able to successfully change the payment data, delete and re-add records.

Debugging 4GL forms in Visual Studio

, ,

Sometimes compiling for trace, or adding display statements to a 4GL program, just doesn’t quite get you far enough with debugging.  Lawson is installed on a MicroFocus COBOL for Visual Studio, which can be debugged using Visual Studio.  Here are the steps to set up the debugger for a Lawson form:

  1. First, compile your program for debug (i.e. lawcmp -D <pdl> <system> <program>)
  2. Create a new Windows Application project for COBOL.
  3. Configure the application for Output Type INT/GNT, and open the “Environment…” to set a Path variable. This variable should contain <GENDIR>\bin;<JAVA_HOME>\jre\bin\server;<LAWDIR>\<pdl>\obj;<LUU_DIR>

  4. Under Debug, set the project to launch an executable. The executable should be <MF_HOME>/bin64/run.exe, and the Application Arguments should be <LAWDIR>/<pdl>/obj/<debug program>.int <pdl>
  5. On the COBOL tab, set the configuration to Active (Debug) and the platform and platform target to your current server platform. Set the COBOL dialect to Micro Focus.  Set the output path to .\bin\x64\Debug
  6. Add the “.cbl” file to the Visual Studio project that was generated from your compile in debug mode (step 1).
  7. You can set break points in that cbl file
  8. Now, it’s time to debug your form. Open the application using LID (lapm <pdl> <program code>)
  9. In a separate LID session, run the command tmmon and make note of the pid for your Lacobrts process.
  10. Now, in Visual Studio, select Debug > Attach to Process
  11. Select the process you identified in tmmon (it should be a run.exe). Now you can perform the process that you were trying to debug, and Visual Studio will stop at the break point you set.

 

Lawson CTP install error – failed to uncompress patch.tar.Z file

, ,

When trying to install a CTP you encountered the below error:

“Error – failed to uncompress “patch.tar.Z” file.” or “patch.tar already exists; not overwritten”

 

There’s a possibility of encountering this error due to the presence of an extra patch.tar file stemming from a prior or simultaneous CTP installation.

 

Upon executing the tar command, ensure that within the <versionfiledir> directory, where you’ve unpacked the CTP, only three files pertain to this CTP. Verify that you have obtained the following trio of files:

– x.x.x_patch_CTPnumber.readme.html

– Versions

– patch.tar.Z

 

Clear out any past CTP files from this location, particularly any patch.tar files, and proceed to rerun the lawappinstall.

 

For UNIX systems:

It’s possible that the lawson user lacks write permissions to a directory higher up in the hierarchy. The entire directory where the decompression is taking place should have permissions set to 777.

 

For Windows:

If you encounter this error on a Windows server, it may be due to spaces in the folder names along the path to the versions directory. If this is the case, you’ll receive a “failed to uncompress” message.

 

To resolve this, replace spaces with underscores (_) or use folders without spaces in their names, then proceed to rerun the lawappinstall command.

 

Typically when installing CTPs it is recommended to have a new directory for each CTP install.

Cannot Receive Purchase Order on MSCM Handheld

, ,

Problem:

Error receiving a Purchase Order on MSCM handheld. The error message reads: “PO not Available. PO contains no open PO lines.”

However, the PO has open lines in PO20.1.

 

Resolution:           

This error occurs when a PO’s Ship To location is not designated as a “Receiving, Ship To” location in MSCM.

To resolve this error, follow the steps outlined below:

From the MSCM web application, do the following:

  1. select Location Management.
  2. Select Modify from the Locations drop-down menu.
  3. Enter the Ship To location in the Location Id field.
  4. Click on the Search button.
  5. Check the Receiving, Ship To box.
  6. Click on the Modify button.
  7. Click on the Done button.