Archive for category: Frontpage Article

You can build a budget by Company – accounting unit and Account.  You can edit a budget in a number of ways.

What does it mean to edit a budget?

You create a budget at the detail level but you are only concerned that the budget for the accounting unit (cost center) stays under budget for the fiscal year.  Not each individual account.  Things change throughout the year and managers are responsible for moving budget dollars from one account to another as things change.

Using budget edits at the accounting unit level allows your personnel to enter transactions and not getting over budget messages when the entire budget for the accounting unit hasn’t been breached yet.

What you need to make this work:

• On GL10 you need to indicate that your budget edit is summarized. This is on the Budget tab.
• On FB11 – create budget groups that indicate the accounting unit and the group of accounts that you want the budget associated with. Some users do only their expense accounts, some do edits by summary account.  This is very flexible and can even include more than one accounting unit if a department has more than one.
• Build the budget edits. This can be done one at a time on FB11 or for all edit groups using FB111.  Keep in mind that the company- accounting unit – account combinations can only belong to a single budget edit.

That’s all there is to setting them up.  Now you have control over how you receive over budget messages throughout your system.

When setting up an SMTP host and user email inbox for LBI and or Smart Notifications, you may want to consider using an MX (Mail Exchanger) Record for your next setup via direct send. This can not only save you on license costs, but also skip the need for setting up an inbox.

If you’re not a network admin and solely working within Lawson, you’ll need to reach out to one to setup the MX Record for you. You can also read up more on this topic here if needed.

Once setup, the network admin will send you an MX Endpoint URL similar looking to this: contoso-com.mail.protection.outlook.com

1. Now in LBI go to Report Administrator
2. Under Server Administrator >> Select Email and Printer Settings
   
3. Under Device Type Tools >> Select Manage Device Types >> Select Email
4. Copy the MX Endpoint into the Host field, the From address could be anything you prefer
   
5. Now go to Smart Notifications (if needed).
6. Select Admin >> under Settings >> Select Install Validator
7. Under Field 16, select “Click here to modify”
8. Enter same settings:
   
9. Now run some smart notification and LBI tests to verify all is working. Make sure you check your junk mailbox. Good luck!

If you’re reviewing an Infor Process Automation log and notice the “Error: Unable to lookup RMI object rmi://localhost:16003/dbSecurity” or something similar firing on a FileAccess node, this means your bpm.ear config file got updated (possibly from an environment update) and needs to be fixed.

To resolve this, you’ll need to update the dbrmihostname field from “localhost” to the LSF server domain name in the bmp.ear file. See steps below.

To update the bpm.ear and bpm.war files follow the steps below:

1. You must run the command from the same directory as where the bpm.ear file and bpm.war file exist:

cd %GENDIR%/assembly/products/bpm/jar

2. Execute the perl script to rebuild the files, providing the new RMI port and hostname of your LSF machine:
   • perl %GENDIR%/bin/updateArchive.pl <RMI_PORT> <HOSTNAME>
   • Example: perl %GENDIR%/bin/updateArchive.pl 16003 lsfserver.domain.com
3. Redeploy bpm.ear in WebSphere from the %GENDIR%/assembly/products/bpm/jar directory.
4. Generate and Propagate the Plugin in WebSphere.
5. Restart Process Flow.
6. Restart the LSF WebSphere Application Server(s).
7. Restart the web server.