Processing rules for defining equipment records within ESRI

See the following list of processing rules the system follows when automatically creating Infor EAM equipment records for GIS features you have created within ESRI:

• A GIS feature must reside within a layer that contains the GISOBJID attribute before you can create a corresponding equipment record.
• The system creates equipment records based on the field mappings defined for the feature’s layer. If a field mapping has not been defined, the system populates the field based on the GIS profile defined on the user’s default preference record for the layer.
  Note: If a field mapping for an attribute exists, the system always populates the equipment field based on the data of the attribute, even if the attribute value is empty and the GIS profile value contains data.

  Field mappings are not defined for Layer, Location X, and Location Y. The system creates equipment records based on an implied mapping where GIS is the owner and the data is automatically mapped to the Layer, Location X, and Location Y fields in Infor EAM. If a feature is a line or polygon feature, the system populates the Infor EAM Location X and Location Y based on the feature’s center point.

• If more than one GIS attribute is mapped to a single Infor EAM field, the system concatenates the data into the single field based on the Sequence and Delimiter values on the mapping record. Likewise, if a GIS attribute that contains concatenated data is mapped into more than one Infor EAM field, the system parses the data based on the Sequence and Delimiter values on the mapping record.
• The system automatically defines the equipment as an Asset record if a field mapping does not exist for the equipment type.
• The system assigns the equipment code of the equipment record based on any existing field mapping. If a feature attribute is mapped to the equipment code field, the system assigns the equipment code based on the field mapping even if the AUTOANUM installation parameter is set to Yes. If no field mapping exists for the equipment code, the system automatically generates an equipment code even if AUTOANUM is set to No.
• The Infor EAM Class, Location, Position, Parent, PO, and Part can be unique per Infor EAM organization. This organization may or may not be the same organization of the equipment record. If there is a mapping record for Class, Location, Position, Parent, PO, or Part, the system must also populate the organization of Class, Location, Position, Parent, PO, or Part. If you map data into these fields, you must also map the organization field for each of them.

  If a field mapping does not exist for the organization of Class, Location, Position, Parent, PO, or Part, the system populates the information based on the following:

  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to a single organization:

    The organization is copied.

  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to multiple organizations:

    An attempt is made to populate the organization based on the GIS profile defined on the user’s default preference record for the layer.

  • If the mapped value for Class, Location, Position, Parent, PO, or Part belongs to multiple organizations and there is not a default GIS profile:

    An attempt is made to populate the organization based on the organization of the equipment record.