Problem Description

An APM user with Assetwise Interop connection to SAP found that inbound work orders were failing with an error stating that it could not create a new record because "....Asset ####### already exist". When the message was received, the UUID for the Asset was supplied as "000000-000000-.." even though in the same message, the Asset Number was also supplied as "457513". To APM, the "000000-..." message indicates that an Asset has not yet been created in APM but exists in SAP. Comparison of both APM and SAP did result in finding the referenced Asset, the asset creation had been launched in APM via an Asset Creation Request, ACR, as part of a Solution Package . The Solution Package including the ACR was pushed to SAP but the ACR had not been Acknowledged and Approved in SAP before a Maintenance Order was also launched from SAP as part of the full solution package. Because the ACR was not Acknowledged, the Maintenance Order in SAP was not sent with the Asset's UUID which consequently resulted in APM attempting to create a new Asset but erroring due to the referenced Asset Number already being in APM.

Solution

Assetwise Interoperability, AWEIS, usually handles this situation well when using an out-of-the-box MIMOSA formatting but, in this particular case the user was using a custom middleware to communicate between SAP and AWEIS and APM. This custom middleware was then updated to include the UUID of the related Asset in it's outbound messages for all work documents. This corrected the issue for all new Assets created via the ACR & Solution Package functionality of APM & APM Remote. Assets created in error prior to this fix needed to have the identity table entries corrected via a script.