Tips about interfacing

You can interface non-Lawson assets into Asset Management with the same basic steps used to interface non-Lawson data into other Lawson applications. Consider these guidelines:

• You must consider carefully plan what data you need to interface and what data you can add later.

• The non-Lawson files must be in an importable data format such as a comma-separated-value (CSV) file with fields that exactly match the position, size, and data types of the fields in the corresponding Lawson interface files.

  Note: The Financial Management File Layouts in KB2218730 for the Lawson interface files are available in Infor Customer Portal.

  This non-Lawson file	Must match this Lawson interface file
  Asset file	Asset Interface file (AMASSETCNV, DBAMACN)
  Asset item file	Asset Item Interface file (AMASTITCNV, DBAMITC)
  Asset book file	Asset Book Interface file (AMASTBKCNV, DBAMABC)
  Asset transaction file	Asset Transaction Interface file (AMASTTRCNV, DBAMTNC)
  Asset attribute file	Asset Attribute Interface file (AMASTMXCNV, DBAMMCV)

  Note:  AMASSETCNV, AMASTITCNV, and AMASTBKCNV, DBAMACN, DBAMITC, and DBAMABC must always be interfaced together.

Asset Management uses one program to interface these five Lawson interface files. You can interface all five files simultaneously. You can also interface AMASTTRCNV, DBAMTNC and AMASTMXCNV, DBAMMCV separately, after you have interfaced the asset, asset item, and asset book records they are associated with.

You correct interface errors at three stages in the process:

• You can modify the non-Lawson data file before you import it.

• You can modify the records in the Lawson interface files before you interface them. You can even add entire records to the files.

  • After you interface records successfully, the interface asset records are deleted from the Lawson interface files and become added, unreleased asset records in the Asset Management application. You can modify the records in Asset Management until you release the assets.