Posts

Querying Lawson Drill Around Comments

WHER ARE MY COMMENTS?!  Many Lawson screens have comment buttons that open a drill-around screen with different comment types.  If you have ever wished to query these comments for reporting or other user interfaces, you may have noticed that they are difficult to find.  Infor has “hidden” them in tables with the “L_H” prefix.  The naming convention is “L_HXXX” where “XXX” is the prefix of the table that feeds screen where you add the comments.  For instance, Requisition Header comments can be found in “L_HRQH”.  And APINVOICE comments can be found in “L_HAPI”.  Join the comments to your main record using the “L_INDEX” column.

I hope this tidbit has saved you some time!!

Running MSCM Install Scripts

Sometimes the install wizard for MSCM installs and updates doesn’t work quite the way you would hope.  In many cases, I have found that I needed to uninstall MSCM, run through the wizard without actually installing, and run the scripts manually so I can trap and fix errors.

All of these scripts are located at the MSCM install directory, in the cofig folder.

Here are the scripts that you would run in order to uninstall your current version of MSCM:

  1. uninstallmscm
  2. undeploymscm

If you are trying to install a new version, run the wizards to unpack the installer and generate the configuration files.  Then, run the install scripts in the following order:

  1. webspheregraft
  2. deploy
  3. installschedulertableprefix
  4. installmscm
  5. deploywithdb

Follow the instructions with each script, because in some cases, you will need to stop the application server and in some cases you will need to start it.

MSCM Scheduler Crash

MSCM uses a Quartz scheduler to bring transactions from Lawson into the MSCM database.  Sometimes on of these events will crash and cause the entire scheduler to crash.  If you notice that details are not making it into MSCM from Lawson, here are some troubleshooting steps:

  1. Check the mscm_server.log located at <WAS_HOME>\profiles\<appserver>\logs
  2. Search for the word “outbound” and start looking for error messages such as “AbortRecoveryException” around the outbound scheduler informational messages.
  3. If you see an aborted recovery, check the EVENT_HEADER and EVENT_DETAIL tables in your database for threads that may be hung (they might have a relatively old HH timestamp or create/last modified date)
  4. If you suspect any threads may be hung, one way to bypass them would be to se the RETRY_COUNT to 99 in the EVENT_HEADER and EVENT_DETAIL tables for that EVENT_HEADER_ID. Then restart MSCM and watch to see if your items start coming over into MSCM.

IP Designer Series – User Action Node – Action Task

Before you can assign work to users in the User Action node, you will need to create the appropriate tasks and add users to those tasks.

*Before you perform this process, you will require Process Server Administrator access.

Log into Rich Client and navigate to Start > Applications > Process Server Administrator > User Configuration > Tasks.

Click Actions > Create, or click the “new” button. Give the task a name, description, and select the inbasket you want the users of that task to have (default “Standard Inbasket”).

To add users to your task, you must first make sure the users exist in the user configuration. Navigate to Start > Applications > Process Server Administrator > User Configuration > Users. Search for your users that need the new task. If they do not exist, click the “new” button or Actions > Create to add them (they must be existing Landmark users).

On the Tasks screen, at the bottom left, Click Actions > Create to add users to the task. Search for your user, give them a start date of when you want the task to be effective, and an end date if the task is temporary for this user. Click “Filter Is Enabled” if you plan to use filters on this task. Select a notify option.

In your IPA process, you can add the tasks on the User Action node. This will determine who is notified (and who should take action) when that node is processed.

 

IP Designer Series – User Action Node – Action Subject

One of the properties options for a User Action node is “Action Reason”. You can require that the approver enter a subject, reason code, and comment. Before you set up the User Action Node, you will want to create your Action Subject in Rich Client. It is important to note that the user creating Action Subjects must have a role with the GlobalUIConfigAccess_ST security class.

Once you have the proper security, log into Rich Client and switch to the data area for which you are creating the subject. Go to Start > Configure > Application. Select “DataArea”.

Click “Add Subject” and give your subject a name.

After you add your subject, you can add it as a Reason Subject on the actions for your User action Nodes.

Listing IPA Scheduled Processes

If you are like me, you find it frustrating that you can only see the scheduled IPA processes that you created.  As an administrator, this can make tracking down process triggers quite difficult.  It is also difficult to determine which process is triggered by which schedule in the front-end Rich Client.  I have created a query that can show all schedules, and which process is triggered by the schedule.  Feel free to take this and make it useful to you!

 

ORACLE

 

SELECT NAME, SUBSTR(AAR.ACTIONPARAMETERS, INSTR(AAR.ACTIONPARAMETERS, ‘<field name=”FlowName” id=”FlowName”><![CDATA[‘)+46,

INSTR(AAR.ACTIONPARAMETERS, ‘]]>’, INSTR(AAR.ACTIONPARAMETERS, ‘<field name=”FlowName” id=”FlowName”><![CDATA[‘)) –

            (INSTR(AAR.ACTIONPARAMETERS, ‘<field name=”FlowName” id=”FlowName”><![CDATA[‘)+46)) FLOW,

SCHEDULEWEEKDAY,SCHEDULEHOUR,SCHEDULEMINUTE,TIMETOEXEC

from LMK_LAWSON.ASYNCACTIONREQUEST ASYNCACTIONREQUEST INNER JOIN

LMK_LAWSON.S$AAR AAR ON AAR.ASYNCACTIONREQUEST = ASYNCACTIONREQUEST.ASYNCACTIONREQUEST

WHERE “GROUP” = ‘pfi’

ORDER BY NAME

SQL SERVER

 

SELECT NAME, RIGHT(LEFT(AAR.ACTIONPARAMETERS, CHARINDEX(‘]]>’, AAR.ACTIONPARAMETERS, CHARINDEX(‘<field name=”FlowName” id=”FlowName”><![CDATA[‘, AAR.ACTIONPARAMETERS)+46)-1),

CHARINDEX(‘]]>’, AAR.ACTIONPARAMETERS, CHARINDEX(‘<field name=”FlowName” id=”FlowName”><![CDATA[‘, AAR.ACTIONPARAMETERS)+46) –

(CHARINDEX(‘<field name=”FlowName” id=”FlowName”><![CDATA[‘, AAR.ACTIONPARAMETERS)+49)),

SCHEDULEWEEKDAY,SCHEDULEHOUR,SCHEDULEMINUTE,TIMETOEXEC

from LMKPRODGEN.ASYNCACTIONREQUEST ASYNCACTIONREQUEST INNER JOIN

LMKPRODGEN.S$AAR AAR ON AAR.ASYNCACTIONREQUEST = ASYNCACTIONREQUEST.ASYNCACTIONREQUEST

WHERE “GROUP” = ‘pfi’

ORDER BY NAME

How to update your TaxLocator version for BSI TaxFactory 10

  1. Download the TaxLocator bulletin from mybsiconnect
    1. Log into mybsi
    2. Choose product
    3. Select TaxLocator Data
    4. Select the appropriate Locator Bulletin
    5. Download the pkg file
  2. Log into your company’s BSI TaxFactory URL
  3. Go to System Tools > Database Load
  4. Browse to the pkg file you downloaded
  5. Click Upload
  6. Select load all files
  7. Click Process

New locator package is updated

BEFORE

AFTER

  1. Validate the TaxLocator in Lawson
    1. Log into LID
    2. Navigate to lapm <PDL> prtf
    3. Click the TaxLocator buttons

 

How to perform a cyclic update for BSI TaxFactory 10

  1. Download the client package for Windows. 
    1. Log into your MyBSI account
    2. Navigate to Product Maintenance
    3. Select your product
    4. Cyclic Bulletins
    5. Select your bulletin
    6. Click on your TF10 Client Package

  1. Download the Server Package. 
    1. From the Cyclic bulletins screen, select the appropriate server download for your server configuration
  1. Download the Cyclic Data File. 
    1. From the Cyclic bulletins screen, click Cyclic Data File
  1. Uncompress/Unzip the client software. 
  2. Install the client software.



Password can be fund under the Bulletin Information link

Skip any environments that are not installed

  1. Uncompress/Unzip the server software.


Password can be fund under the Bulletin Information link

  1. Transfer/move/copy the server software to your payroll system location.  (on Windows this location is C:/Windows/System32)
  2. Apply the Cyclic Data. 
    1. Log into the new cyclic URL (eTF10x, where x is the new bulletin letter)
    2. Select your dataset
    3. Go to System Tools
    4. Under Maintenance Tools, select Manual Update
    1. Browse for the data package you downloaded earlier
    2. Click Process



Cyclic bulletin is updated

  1. Verify BSI in Lawson
    1. Log into LID
    2. Navigate to lapm <pdl> prtf
    3. Click Refresh Ver
    4. Click the appropriate test buttons

MSCM Data Migration

If you are upgrading MSCM and need to test against production data, you may want to have multiple testing passes.  This article will help you to refresh your MSCM database, even if the versions differ.  (The MSCM install procedure updates the database for you when an older version is found).

Uninstall MSCM

  1. Log into the server as Lawson (or as the install user)
  2. Open a command prompt as administrator
  3. Navigate to <installdir>/config
  4. Run the following commands
    1. uninstallmscm
    2. undeploymscm
    3. Verify services as prompted
  5. Verify that the MSCM application has been removed from WebSphere

Restore Database

  • Overwrite the destination database with the desired data set

Re-install MSCM

  1. Log into the server as Lawson (or as the install user)
  2. Open a command prompt as administrator
  3. Navigate to <installdir>/config
  4. Run the following commands
    1. webspheregraft
    2. installschedulertableprefix
    3. installmscm
    4. deploy
    5. Verify services as prompted
  5. Start the mscm application in WebSphere

IP Designer Series – User Action Node

The User Action Node is typically used for Approval Flows. It is uses with the IPA inbasket to allow users to take action on items as part of an automated process.

Select the task associated with the user action (this must be configured in IPA Rich Client prior to creating your user action node).

Configure actions associated with this task (such as “Approve” or “Reject”)

Decide when the action should proceed

Configure the timeout settings

Configure the notification settings

Configure the displays for various platforms

Decide if/how reminders will be handled