IBM Support

After an asset was moved from one site to another the attachment did
not move with the assets.

Question & Answer


Question

Why are attachments not moved with the asset when the asset is moved to a different site?

Answer

A choice of how to process attachments was implemented with the change
for APAR IV44271 in the latest IFIX releases for 7.5.0.7.

In new environments or environments that do not have any asset-related doclinks, Maximo can be configured to use a new relationship DOCLINKS_ASSETID instead of DOCLINKS. The DOCLINKS_ASSETID relationship uses the non-site specific ASSETID attribute instead of the site-specific ASSETUID attribute so that doclinks are maintained when an asset is moved across sites. The SYSTEMLEVASSETDOCS maxvariable was added to control whether asset-related doclinks are created using the site-specific ASSETUID or the system-level ASSETID.
Please note that this was added as an option (as opposed to a fix for a bug). The change described above was designed for new environments. If the change is made to an environment with already existing asset-related attachments then the existing attachments will not show in the View
Attachments dialog. Only those documents added going forward, after the change is made, would appear in the View Attachments dialog. The fact that documents did not move with assets was by design going back to the introduction of attachments.

[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Browser for Linked Docs","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5;7.6","Edition":"Standard","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 June 2018

UID

swg21883485