	Product(s):	APM Implementation and Performance Management
	Version(s):	7.11
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem

After running with APM's SAP Gateway (SAP Interoperability) for several months, the user deleted several ABC Indicator values from SAP. This caused the APM FLOC and Equipment dataload jobs to error with the following:

"2019-06-13 19:00:08.3626 Error DOMAIN\APMServicenameINT01$ Ivara.DataLoader.BaseDataExchangeJob`1 [54] Exception occurred processing job 'FLOC SYNC PROD-Thursday, June 13, 2019 2:00:07 AM'. Written to statistics. Context='OnPreProcessJob' The exception message was:An attempt was made to access an object (CLSID:1000031442 OID:4)that has been deleted. EXCEPTION OCCURRED:ObjectDeletedException An attempt was made to access an object (CLSID:1000031442 OID:4)that has been deleted. at Ivara.EXPLink.OQ.ObjectResolver.get_UnManagedCaxContainerPtr()

at Ivara.EXPLink.OQ.oCAXContainerObject.IsMemberRelevant(Int32 iMemberID)

at Ivara.EXPLink.EXD.SAPABCIndicator.get_ABCIndicator()

at Ivara.EXPLink.IVSTAGE.DataLoaderAssetBaseExchangeJobExtensions.BuildABCIndicatorToPriorityDict(Dictionary`2& abcIndicatorToPriorityDict)

at Ivara.EXPLink.IVSTAGE.DataLoaderAssetSAPFLOCDataExchangeJob.OnPreProcessJob()

at Ivara.DataLoader.BaseDataExchangeJob`1.Process(PersistentObjectReference apmProcessJob, CancellationTokenSource token"

Solution

Although this same error message may result from incorrect SAP Credentials, it will also indicate when there is an issue with the ABC Indicator mapping with an APM Criticality or APM Consequence Priority. The telling sign in this case is the OID referenced by the object "(CLSID:1000031442 OID:4)". If there is an SAP Credential issue, the failure will typically indicate OID:1 as being deleted.

To diagnose the source of the problem.

1. Check the that shared SAP user credentials are ok for the External Data Provider. First launch APM as an Administrator from the Server running the Dataload Processing Job using the same credentials as the SAP user. On the Enterprise level \ Integrations view \ External Data Providers tab, open the External Data Provider and Test Connection.

If the test connection is successful, the problem is likely to do with the mapping of the APM Criticality/Consequence Priority with SAP Indicator.

2. Check the SAP ABC Indicators for the Site and make note of the values. Open the Site's Administration pulldown menu and select "SAP Settings" and go to the "ABC Indicators" tab:

3. Check the Consequence Priority mappings for the Site. Open the Site to the Assets view > Settings tab > Consequence Priorities sub-tab, open each Consequence Priority one at a time to the CMMS Info tab. Check that the ABC Indicator is properly selected. Repeat for all Consequence Priorities and make sure no SAP Indicators are not mapped.

4. Once you know all of the ABC Indicators, go to the database and run the following scripts:

"select SAPABCINDICA_OI, * from MNT.AssetCriticality
where SAPABCINDICA_OI is not null

select * from exd.ABCINDICATORSET"

Make note of any SAPABCINDICA mappings that aren't accounted for.

5. In APM, return to the Site to the Assets view > Settings tab > Consequence Priorities sub-tab, open each Consequence Priority one at a time to the CMMS Info tab. For any that have a blank ABC Indicator, change the ABC Indicator to a value, select one, click OK to commit the change, then reopen it and select "(None)", click OK to commit the change. Repeat for all unmapped Consequence Priorities.

6. Rerun the scripts in step 4 to verify that the changes have been propagated

7. Once the changes have been made try reprocessing the FLOC and Equipment Process Job.

Deleting SAP ABC Indicator after turning on APM SAP Gateway (interoperability) causes FLOC and Equip

Problem

Solution