Appendix D: HMS - EAM ION integration guide setup - HxGN EAM - 12.0 - Feature Briefs - Hexagon

Set up HMS and EAM products as per install guides and enable Databridge modules. Ensure the tenant id on both installs are the same.

Browse to ION Desk on the Model | Connection Point screen and create partner for EAM.

Name—Enter a simple name for partnered, this will be used in Logical ID.

Logical ID Type—Select EAM.

Type—Infor Application.

Tenant—Check this and enter the tenant id of EAM install.

Select Database and enter the Database, Port and Schema name or the Advanced URL ex jdbc:jtds:sqlserver://demoEAM.gdeinfor2.com:1433/EAMHOSP_WITHCONFIG

Schema Name—EAMHOSP_WITHCONFIG.

Enter User Name and Password for the user with access to the EAM schema.

Go to the Documents tab for EAM partner, and then add the following documents:

• AssetMaster – Process – Receive in Application

• Code Definition – Sync – Receive in Application

• Maintenance Order – Sync – Send from Application

• Maintenance Order – Process – Receive in Application

Create a partner for HMS like in EAM in the step above.

Go to the Documents tab for HMS partner in ION, and then add the following documents:

• AssetMaster – Process – Send from Application

• Code Definition – Sync – Send from Application

• Maintenance Order – Process - Send from Application

• Maintenance Order – Sync – Receive in Application

Browse to Model | Document flow, and then create a new flow as follows:

1. Enter an application and specify name as EAM, and then add the application partner created above for EAM.

2. Add another application point as HMS and add the application partner for HMS created above.

3. Add one more application point called EAM again as in the step above.

4. Select the document icon between first EAM and HMS application, and then add the Maintenance Order Sync BOD.

Select the document icon between HMS and second EAM application, and then add the AssetMaster Process and CodeDefinition Sync BODs.

• Save the document flow.

In EAM apply the Hospitality configuration using configuration manager.

On the System Codes screen, modify System Default of Equipment Type ‘P’ to ‘RM,’ so new positions created from HMS via ION are created as type of Rooms.

Ensure the Job Types in EAM are set up to match Work Order Reason Codes.

On the Field Filter Setup Screen, for Rooms, Vehicles and Facility screen (Screen code: OSHPRM, OSHPVH, OSHPFY) Check the flag for Filter type.

On the Field Filter Setup Screen, for Work screen (Screen code: WSJOVH). Check the flag for Filter type and enable WO Types.

Go to Databridge Partner Screen, and then activate the Infor-ONRAMP partner.

Partner ID—Name created in ION (in step above for ION EAM partner screen (ex: EAM55).

User ID and Password—Use a user ID that has connector access and ensure the user ID has rights to all properties used in integration.

DATABRIDGEINTERNALUSER—Leave as is.

On the Partner | Subscriptions Tab, enable the following Events:

• CODEDEF (ProcessCodeDefinition

• CODEDEF (SyncCodeDefinition)

• SYNCMAINTORDER (Sync MaintenanceOrder)

• SYNCOBJP (SyncAssetMaster)

On the Databridge Setup screen, enable the Work Order Outbound option, and then ensure Databridge CDKEY is populated.

In HMS go to the Databridge Partner Screen, and then activate the ION partner.

Partner ID—Enter the FULL logical id of the partner created in ION.

Infor HMS User ID and Infor HMS Password—Enter the user ID and password for the user with access to HMS with connector rights and access to all properties that are part of integration.

Address—Enter the jdbc address for the database Ex: jdbc:sqlserver://HMS2012-DB:1433;DatabaseName=HMSDEMO_NEW

Login ID and Login Password—Enter database user and password to connect to the schema set up on the address field.

Browse to the Databridge Partner | Subscriptions tab and enable all Events.

Run the following script in HMS – Change the line set @propertyCode = 'DEVPRP'. Replace the ‘DEVPRP’ value with the property code used in integration. Run it multiple times if more than one property is being used in integration.

alter table P5XREFMAPDEFS drop constraint R5UNQSQL2_XMD
go

alter table P5XREFMAPDEFS drop constraint R5UNQSQL3_XMD
go

create unique index P5UNQSQL2_XMD on P5XREFMAPDEFS (XMD_PROPERTYCODE, XMD_SOURCESYSTEM2ID, XMD_MAPPINGNAME)
go

alter table P5XREFMAPDEFS drop constraint P5FOK2_XMD
go

alter table P5XREFMAPDEFS drop constraint P5FOK3_XMD
go

alter table P5XREFPOINTVALUES drop constraint P5FOK1_XPV
go

alter table P5XREFPOINTVALUES add constraint P5FOK1_XPV foreign key (XPV_LISTNAME)
references P5XREFPOINTLISTDEFS(XLD_LISTNAME)
go

declare @propertyCode nvarchar(15)
declare @partner nvarchar(30)
declare @mappingName nvarchar(50)
declare @mappingID nvarchar(30)

declare @propertySpecific nvarchar(1)

declare @derivedPropertyCode nvarchar(15)

declare @tempID nvarchar(30)

declare @tempIDInt int
begin

set @propertyCode = 'DEVPRP'
set @partner = 'ION'
print 'Insertintg into P5XREFMAPDEFS / R5DESCRIPTIONS ...'

declare c_base cursor local for
select XMD_MAPPINGNAME, XMD_MAPPINGID, XMD_PROPERTYSPECIFIC
from P5XREFMAPDEFS where XMD_PROPERTYCODE='*' and
XMD_SOURCESYSTEM2ID='*' and XMD_MAPPINGNAME like '%.ION' order by XMD_MAPPINGNAME

open c_base
fetch next from c_base into @mappingName, @mappingID, @propertySpecific
while @@FETCH_STATUS = 0 begin

if @propertySpecific = '+'
set @derivedPropertyCode = @propertyCode

else
set @derivedPropertyCode = '*'

set @tempID = null
select @tempID=XMD_MAPPINGID from P5XREFMAPDEFS
where XMD_MAPPINGNAME=@mappingName and
XMD_PROPERTYCODE=@derivedPropertyCode and XMD_SOURCESYSTEM2ID=@partner if @tempID is null begin

exec GetNextSequence 'XREFMAPDEFS', @tempIDInt output
set @tempID = CAST(@tempIDInt as nvarchar(30))

insert into P5XREFMAPDEFS(XMD_PROPERTYCODE, XMD_SOURCESYSTEM2ID,
XMD_HMSDEFAULTMETHOD, XMD_DEFAULTMETHOD2,
XMD_MAPPINGID, XMD_MAPPINGNAME, XMD_HMSLISTNAME, XMD_LISTNAME2,
XMD_DESC, XMD_PROPERTYSPECIFIC)

select @derivedPropertyCode, @partner, XMD_HMSDEFAULTMETHOD, XMD_DEFAULTMETHOD2,
@tempID, XMD_MAPPINGNAME, XMD_HMSLISTNAME, XMD_LISTNAME2, XMD_DESC,
XMD_PROPERTYSPECIFIC
from P5XREFMAPDEFS where XMD_MAPPINGID=@mappingID

insert into R5DESCRIPTIONS(DES_ENTITY, DES_RENTITY ,DES_TYPE, DES_RTYPE, DES_CODE, DES_LANG, DES_TEXT, DES_ORG, DES_TRANS)

select DES_ENTITY, DES_RENTITY, DES_TYPE, DES_RTYPE,
@tempID, DES_LANG, DES_TEXT, @derivedPropertyCode, DES_TRANS

from R5LANGINST join R5DESCRIPTIONS a on 1=1

where a.DES_ORG='*' and a.DES_CODE=@mappingID and a.DES_RENTITY='XRMP'
and a.DES_RTYPE='*' and a.DES_LANG=LIN_CODE
and not exists(select 1 from R5DESCRIPTIONS b where b.DES_ORG=@derivedPropertyCode and b.DES_CODE=@tempID and b.DES_RENTITY=a.DES_RENTITY and b.DES_RTYPE=a.DES_RTYPE and b.DES_LANG=a.DES_LANG)

end
fetch next from c_base into @mappingName, @mappingID, @propertySpecific

end
close c_base deallocate c_base
print 'Done'

end

go