Archive for category: Frontpage Article

If you are compiling a form that generates an error “Program X Does Not Allow INVOKE”, that means that the invoked program needs to be set to allow invoke. To do that, from a LID session, go to the form in pgmdef (pgmdef <prodline> <system code>). Select Define (F6) > Program (A).  Set the property “Can Be Accessed Via INVOKE” to Yes. Compile the invoked form and then compile the custom form that does the invoking.

Define (F6) > Program (A)

The XML Node can be used to build or read XML in IPA.

For the Action tab, select Build or Parse depending on the function you are performing.  You can Build the XML input if you have a schema to point to in the Build menu.  The Evaluate on Condition field means that the XML will only be built if criteria that you specify are matched.  The Append Output To option allows you to append the XML string you are building to a node that exists in your flow (i.e. adding elements to a list within a data iterator).

NOTE: Variables are denoted with curly braces: {variable}.

When setting up Landmark queries for IPA or Spreadsheet Designer, it helps to know which business class and field you are working with.  You can get these values in any Landmark application form (web-based or in Rich Client) by typing ctrl+shift and clicking on the field.

Things to consider:

1. Do your addresses need to be cleaned up?
2. Do you have duplicate customers that need to be consolidated?
3. Do you currently have abbreviations in your addresses that you don’t need in your new system?
4. OR – do you not have abbreviations in your current ERP and need them in your next one?
   1. Create an abbreviation cross reference to easily make the abbreviations needed
5. Cleaning up the addresses is often very time consuming and can be expensive when waiting until the last minute paying a consultant to do it. Hire a temp now and get it done early and much less expensive
6. How much history do you want to bring over to the new ERP system?
7. If you are moving off Lawson, are you using National Accounts? If so, make sure to apply all open payments at the National Account level unless you are sure the new system will allow this same functionality.
8. Is there anything special about your AR processing that needs to be considered when moving to a new ERP?

Things to consider:

1. Can you pay off all your existing AP prior to transitioning to a new system?
   1. This is preferred whenever possible and start your new ERP with fresh AP
2. Consider the length of the address fields in your new ERP
   1. Do you need to come up with some abbreviations that work throughout your addresses in the new system?
   2. Have you used abbreviations you no longer need to use and therefore want to undo your abbreviations and make them full words in your new system?
   3. Do you have duplicate addresses that need to be consolidated prior to transitioning? If you are moving off of Lawson, Vendor locations often have duplicate addresses which other ERP systems can’t accept
3. Cleaning up of inactive Vendors or addresses
   1. This is work that should be done now instead of waiting to the last minute. Paying a consultant to clean up your addresses is expensive.  Hire a temp now and get it done early and less expensive.
4. Is there anything special about your AP processing that needs to be considered when changing ERP systems?