Archive for category: Frontpage Article

Lawson provides the ability to query Lawson tables via URL.  These transactions are called “DME” queries, and can be quite useful in IPA processes, or in scripting bulk data calls.

To query data using a DME call, the URL is https://<server name>/servlet/Router/Data/Erp?.  To select specific fields, use the “FIELD” key word.  To filter the results, use the “SELECT” key word.  You will need to have knowledge of the data tables and columns to build these queries.  The dbdef command in LID can be quite useful for this.

GEN

To query GEN data, the syntax would be https://<servername>/servlet/Router/Data/Erp?PROD=GEN

For example, this URL would return the PRODUCTLINE and FILENAME fields for the FILEDEF record with prefix “API”:

https://lawson.company.com/servlet/Router/Data/ERP?PROD=GEN&FILE=FILEDEF&SELECT=PREFIX=API&FIELD=PRODUCTLINE,FILENAME

LOGAN

To query LOGAN data, the syntax would be https://<servername>/servlet/Router/Data/Erp?PROD=LOGAN

For example, this URL would return the VERSION data in the LOGAN data area

https://lawson.company.com/servlet/Router/Data/ERP?PROD=LOGAN&FILE=VERSION

Data Area

To query your desired data area, the syntax would be https://<servername>/servlet/Router/Data/Erp?PROD=<data area>

For example, this URL would return the CUCODE “USD” from the CUCODES table in the TEST data area.

https://lawson.company.com/servlet/Router/Data/ERP?PROD=TEST&FILE=SELECT=CURRENCY-CODE=USD&FIELD=CURRENCY-CODE,DESCRIPTION

Output

The default output type is XML, but you can also output in CSV format.  To do that, in the URL, append the command “&out=csv”.

Infor recently updated handhelds and MSCM for a cloud environment. The test user was able to download the Infor CAB files to the handheld but was unable to download the PlatformDLL file. The error message kept coming back with “Internet Explorer cannot download file”

After ensuring all permissions were set for the user and running several tests, rechecking the configuration setup. We finally located the issue from the update and it turns out a port was reset to a default value and we had to change the Service Type to LHC. Below are the steps you can take to resolve this if you’re experiencing a similar issue.

1. Login into MSCM with Server Administration group rights.
2. Select MSCM Configuration >> Additional Settings
3. Select Service Type LHC and under Handheld Service Properties, ensure you’re using the correct port. For us we had to update it to 1447

4. We updated both LSF and handheld ports to 1447 and the user was now able to download the file.

Hope this was helpful!

If you have suddenly noticed in Lawson Security Administrator that certain users have different attributes in their addins field other than ALLOW or DENY, don’t worry as this was setup by design back before LSF version 9.

These values were removed in version 9+ because Lawson User Security (LAUA) and Lawson System (LS) security can now secure these actions on specific tables and records.

If you want to convert the old Addins Attributes like to Allow or Deny, simply edit the users RM info and change the Addins field to Allow or Deny.

If you prefer to stay on the older attributes, see the table below for in-depth access descriptions:

You’ve applied a patch to your system and it caused more problems than it fixed or it was not the solution to your problem and there is no point in pushing it to PROD. Today we are going over simple steps to uninstall a CTP which is similar to how you install a patch via lawappinstall.

1. Ensure security is turned off and it is typical to bring down websphere before starting so no user can login during this process.
2. In LID, start with the uninstall command:
   • perl %GENDIR%\bin\lawappinstall uninstall <productline> <patchxxxxx>
3. Run lawappinstall STAGE (optional but recommended)
   • perl %GENDIR%\bin\lawappinstall stage <productline>
4. Verify stage compilation complete:
   • qstatus | wc -l (this command will return the number 4 when compiling is complete)
5. Check for compiling errors:
   • ls %LAWDIR%\<productline>\*\*.err
     • If any errors found, recompile failed programs with this command:
       • qcompile productline SystemCode ProgramCode
6. Run lawappinstall VALIDATE:
   • perl %GENDIR%\bin\lawappinstall validate <productline>
7. Run stgcmp
   • stgcmp list <productline>
     • If the program’s status is FAILED or RECOMPILE REQUIRED, submit the program to the compile queue using the -A option.
8. Finally, Activate
   • perl %GENDIR%\bin\lawappinstall activate <productline>
     • You should see the patch(es) you ran the initial uninstall for, confirm, verify any other prompts.
9. Verify Non-stage compilation (if you didn’t run stage):
   • qstatus | wc -l
10. Turn security on, turn websphere on, run your typical post smoke tests as if you were applying a patch.

Hope this was helpful!