AWS Lambda Sql Connection

, ,

If you are creating a web app that uses lambda and a mysql database, there will be many times where you need to have sql information passing to and from lambda functions. A way to connect a lambda functions to a mysql database is using npm mysql. To set up the connection, there must be a connection variable defined. This variable must contain the mysql host name, user, password, and database. Once these are defined, the lambda function can connect to the mysql database with the code “connection.connect()”. Once this is ran, your lambda function can now run queries. These queries are written just like a regular sql query. Once you are done running your query make sure to declare your connection closed by stating “connection.end()”.

The process.env variables would be were you put your sql information.

 

**Note: You might need to configure your lambda function to be set up on the mysql database’s VPC.

Compiling Form Generates INVOKE Error

, ,

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)

Append to XML Node in IP Designer

, ,

To append XML elements to a parent element in IPA, use the “Append output to” property on the XML node.  First, create a root XML element in the start node.  In your XML builder node, check the “Append output to” property, and set the root element to the variable that you created in the start node and the element that contains the list.  So <root>.<listelement>.

IP Designer Series – XML Node

, ,

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}.

Transitioning Open POs from one ERP to another ERP

, ,

Here are some things to consider:

  1. Is there a cut-off date for open POs or are all open POs going to move over to the new systems?
  2. Will open (unmatched) receivers also be moved over to the new system for the open POs?
  3. When AP vendors are moved to the new system, will they have the same vendor number or is a vendor cross reference needed to import the open POs and receivers to the new system?
  4. Are your item numbers staying the same? If not, you will need an item cross reference for bringing the line items of the POs and receivers over to the new system.
  5. Is there anything special about your PO processing that needs to be taken into consideration when selecting POs or Receivers for conversion?

 

 

 

Get Business Class and Field Names for Landmark Applications

, ,

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.

Transitioning Open Receipts from one ERP to another

, ,

There are things to consider when transitioning your open receipts from one ERP to another:

  1. How old are the receipts before you will not move them to the new ERP?
  2. Are the POs still open for the open Receipts?
  3. Is there a new PO number that needs to be used for cross referencing purposes in the new ERP?
  4. How about the vendor number – did it change in the new ERP?
  5. What about your item numbers? – Do you need a cross reference between the old and new item numbers?

Transitioning Open AR from one ERP system to another

, ,

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?

SQL Server Copy Database Wizard

, ,

An alternative to a SQL database backup & restore is to use the Copy Database Wizard in SQL Server.

Right-click on the database, and select Copy. The source and destination can reside on different servers. You can opt to copy without taking the source database online. It will take longer, but it doesn’t require downtime. You can also copy to an existing database if you select the option to drop the database before adding if it exists. This tool is especially useful if you are trying to copy data from a new version of SQL Server to an older version such as 2008. We have come across that configuration many times in Lawson PROD to DEV environments.

Transitioning Open AP from one ERP to another

, ,

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?