Accounting entity/location setup - HxGN EAM - 12.0 - Administration & Configuration - Hexagon

HxGN EAM Configuration Guide for Infor ION

Language
English
Product
HxGN EAM
Search by Category
Administration & Configuration
HxGN EAM Version
12

For each HxGN EAM organization, follow these steps to associate it with an Infor ION accounting entity value.

  1. Open Organization form.

  2. Select the non-common Organization record you want to associate an accounting entity value, and then click on its Record View.

  3. Specify the Accounting Entity value.

  4. Save the organization record.

  5. Click on the Enterprise Locations tab.

  6. Enter a record for each type of BOD Group according to the table below. Click Submit after each record.

BOD Group

Enterprise Location

Asset

An Infor ION location code that best matches the HxGN EAM organization for business transactions that are related to HxGN EAM equipment master records.

Materials

An Infor ION location code that best matches the HxGN EAM organization for item master and inventory adjustments transactions.

Purchasing

An Infor ION location code that best matches the HxGN EAM organization for requisition and purchasing documents and transactions.

An Infor ION location code that best matches the HxGN EAM organization work orders and production requests documents and transactions.

Typically you need to repeat these steps for each HxGN EAM organization, except for the * organization (the common organization), which typically is not associated with an Infor ION accounting entity or a location code.

In general, master data, such as ItemMaster and SupplierMaster, can be imported into EAM for the common (*) organization if the master data is at the tenant level, for example there is no accounting entity specified in the BOD. Alternatively, they can be imported into an EAM’s specific organization if there is an accounting entity for the master data and the accounting entity is mapped to an EAM non-common organization as described above.

In some integration scenarios, locations are not consistently used in BODs among the applications, you may need to add and set install parameter @IGNLOC to Y in order for EAM to ignore the location differences when importing inbound BODs.