Step 1: Login to Infor Security Services (ISS)
Step 2: Goto SSO >> Manage Domains and click edit button as shown:
We are simply verifying the names of the displayed XML files:
Step 3: On the LSF server, go to the %LAWDIR%\security\domainauth\EXTERNAL directory to edit that XML
Step 4: Add an entry to an existing tree or create a new one:
That’s all that’s to it.
Step 1: Login to your LBI server and go to the Tools dashboard
Step 2: Select the Smart Notification link
Step 3: In Smart Notification interface, click the Admin button at the top right:
Step 4: Under Content section, select the Delivered Alert History link:
Final Step:
Select the between dates and click the “Get Delivered Alert History” button to see sent notifications. Below you’ll see all sent notifications on June 26th 2019. You can also filter down on the notifications by Alert ID and or Recipient. You can also redeliver these messages if needed.
Running BS531 creates two separate CSV files, one for employee benefits (BNBATCH) and one for dependent benefits (BNDEPBATCH).
Copy these files over to the D:\lsfprod\law\prod10\work\BNBATCH directory on your LSF application server (your directory names may differ slightly).
After creating your BN531 job, go in LID and use the jobdef command to locate it under the user you created it under.
Once located, press F6 and select “C. CSV File Attributes and verify”
Verify the File Name is BNBATCH and type is CSV:
Now run the BN531 job in report mode to verify there are no errors.
Run BN531 in update mode.
Once done, go back to the D:\lsfprod\law\prod10\work\BNBATCH directory and rename the BNBATCH to bnbatch_emp. Now rename bndepbatch file to BNBATCH. Run the BN531 again in report. Once verified there are no errors, run the BN531 again and confirm the data carried over.
Hope this was helpful.
Can’t Change Pricing on a Requisition or a PO?
There are settings in the Buyer (PO04) or Requestor (RQ04) setup. It allows control over defaulting in pricing from any contracts or vendor agreements that you might have in place. If you want a buyer or a requestor to be able to change the price on a PO or a Requisition, then consider the following changes:
PO04:
At the bottom of the Main tab in PO04 – you can setup a buyer to allow unit cost overrides from different costs. In this case, the user can’t override a cost that defaults in from a vendor agreement or Strategic Sourcing (Contracts). However they can override the cost on a PO line item if it defaults in from the last PO or Last Cost (Invoice cost or adjusted cost).
RQ04:
At the bottom of the Main tab in RQ04 – you have similar options. This user does not have the ability to override any cost that might default onto a requisition.
Creating a new interface? Doing an Upgrade? Don’t forget the Business Requirements Document (BRD)
Often we go through the process of meeting and discussing different aspects of a project. Those meetings are essential to understanding what is needed to be done. A good BRD is basically a bible for all to refer back to during and even after the process to make sure that everything has been done at the level that was decided upon.
It is also a good way to make sure that everyone goes into the project with the same understanding. It is important to keep the BRD up to date with any changes that are decided upon. This limits overlooking small aspects of a project that might have been referred to in – when did that email get sent again?
Based on client needs, we put together a BRD that reiterates what we think the client said. When you review and approve it, it means we are both are working under the same premise.
It helps to eliminate those famous cartoon moments:
Considering a Divestiture? Here are things to consider:
History: How much data do you need to extract to send with the divested division/company?
Consider each module that currently has data and determine if there is a similar module in the new system. If there isn’t a similar module in the new system, then how will the data be accessed? Possibly a separate database that stores the information for lookups as needed.
Fixed Assets: Do you have assets that need to be moved with the divested division/company?
What are the criteria for which assets need to be moved with the divested division/company?
What date will these assets be last depreciated in your current system and how will the depreciation continue in the new system?
Will you keep the original in-service date and depreciation history and continue depreciating the same in your new system?
AP Payments: How will you handle bank reconciliations and payment voids that occur after the division/company is divested?
Will there be on-going communication for this information to be sent?
Will there be a complete pay-off in the current system so that AP starts clean in the new system with no open invoices?
Do you have a consolidated AP process now that needs to be split into multiple AP processes? If so, when should you start this process of separation? Especially important if you have any EDI or other interfaces to AP that will need separation as well.
Vendors: How will you notify Vendors that invoices after a certain date should be handled differently? Are your vendors even aware that there are two different divisions or companies that they are currently billing? It is very important to start working with your vendors and any 3rd party AP interfaces sooner than later.
Purchases: How will any open POs and/or requisitions be handled?
Make sure that you have enough inventory on hand for the divested division/company prior to cutting off standard replenishment.
Problem: Workunits for Infor Process Automation are sitting in Ready Status and not processing.
Solution:
1. Via LmrkGrid (Grid Management), determine how many workunits may simultaneously process in your system. (see attached “DeterminingSimultaneous.docx”)
- Determine how many workunits are currently in a processing state.
NOTE: Please refer to attachment “DeterminingSimultaneous.docx” for instructions on determining simultaneous processes. In case you will need to engage support, you should screenshot this information to provide when you open the support incident.
– Command to count records in Ready Status: dbcount <DATAAREA> -f Status=\”1\” PfiWorkunit
– Command to count records in Processing Status: dbcount <DATAAREA> -f Status=\”2\” PfiWorkunit
– Command to count records in Completed Status: dbcount <DATAAREA> -f Status=\”4\” PfiWorkunit
It is a good idea to monitor and take counts of these records periodically. Are the number of workunits in Ready status growing? Are the number of workunits in Completed status growing? Is the number of workunits in Processing status equal to the maximum number workunits that can simultaneously process?
NOTE: If the number of workunits in Ready Status is growing and the number of workunits in completed status is not, then either:
- You have workunits that processing for a very long time holding up the system; use the Grid Management UI to determine which workunits are processing so long and determine if those are stuck in a loop; or if they are just processing normally large jobs. Consider cancelling the long running workunits, and scheduling them to run in off business hours.
- If you are on Landmark 10.1.0.x, there was a bug in this version of Landmark that periodically caused Async to stop picking up new workunits. This issue was resolved by a re-write of Asnyc and LPA nodes in 10.1.1.x Landmark versions. If you are on Landmark 10.1.0.x you should restart the Async Node, and the IPA node.
NOTE: The workunits that were already queued to an LPA node will not automatically start back up; the workunit polling frequency (default 30 minutes) will need to trigger before they are requeued to a new LPA node.
If you are acquiring a new hospital in the near future, below are 5 things to consider:
- Will adding the new hospital cause a difference in your GL structure?
- Are there different management hierarchies that need to be addressed in the new departments/cost centers?
- If you are using automated flows for approvals will the current structure work for the new location as well?
- Localized vs. Centralized purchasing and AP
- It is often thought that just centralizing purchasing and AP is the norm when acquiring a new hospital. This is often more difficult to achieve then it seems on paper.
- There are item number differences – how will those be handled? Is there some normalized data in the item master that will allow for consolidating the item master? Does the new hospital provide specialty services that requires adding many more items into the item master? Who will maintain the new items?
- There are long term contracts in place at both locations – often different prices and terms – Will these stay separate or renegotiated?
- Different locations often have different sales reps for the same suppliers. How will these relationships be affected? And what affect will it have on the local service if the local rep is no longer involved?
- What kind of reports are used at the new location that are not used currently in-house? Are the reports necessary? If these are not canned reports- how will the reports be created and maintained?
- What amount of history is necessary to bring over to the new system for each module that is being transferred to your ERP? How will older data be accessed when needed? Will the old data be available for research?
You can schedule your ProcessFlow to run on a weekly schedule by using the ProcessFlow scheduler. Recently, a client had asked if there was a way to schedule it bi-weekly. Great news – there is a way, and it’s easy to set up.
In Rich Client, Start -> Applications -> My Actions -> My Scheduled Actions -> Double click action you wish to modify
In this next screen, scroll down to Scheduling Details and click on Week Number
In order to schedule a process to run biweekly, you would want to use Even Weeks in the “Select Week Number” field and specify the day you want it to run (in this case, Monday)
Now you can have your ProcessFlow running every other week.
For a step-by-step guide to Scheduling a Process in IPA, check out this related article: Scheduling a Process in IPA