Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Faizan_Rasheed Absent Member.
Absent Member.
739 views

Can we change the MODEL in Asset Manager tool?

Can we change the MODEL in Asset Manager tool, the existing Asset status -  IN USE ? If YES then how can we do so. If NO then why NO?

0 Likes
3 Replies
Absent Member.. _pc Absent Member..
Absent Member..

Re: Can we change the MODEL in Asset Manager tool?

Within Asset Manager the Nature record determines which records are created when you instatiate a model. You can have many natures in your system, but the key fields (which determine compatibility) are OverflowTbl and seMgmtConstraint.  You can change the model of an asset/portfolio item, provided that the new model has a Nature which is compatible with the original Model.

 

 

Paul Catley
Senior Consultant
HP Software & Solutions
Faizan_Rasheed Absent Member.
Absent Member.

Re: Can we change the MODEL in Asset Manager tool?

Hi Paul,

 

Thanks alot for your quick response. I need a favor could you please explain me the step wise process how can i change the MODEL who's status shows as IN USE?

 

Thanking you in advance.

 

Regards,

Faizan Rasheed

0 Likes
Absent Member.. _pc Absent Member..
Absent Member..

Re: Can we change the MODEL in Asset Manager tool?

Hi Faizan,

 

When an asset record is first created its data is spead over a number of tables, and the records that are created is determined by the Nature of the Model. If you later want to change the model of any asset, you must change it to a model that is linked to the same or another compatible Nature.

Changing the model of a Portfolio item has nothing to do with it's status (seAssignment).

 

Every model that you create in your system must be linked to a Nature, amongst other things, the Nature record tells Asset Manager (AM) which physical records to create when you create an item of that Model.

 

For Example:

If you have a Nature called Computer, it probably has the following fields set:

  • Create (seBasis) = Portfolio item - This tells AM to create a record in amPortfolio when we create an item with this Nature
  • Also create (OverflowTbl) = Computer - This tells AM to also create a record in amComputer when we create an item with this Nature
  • Management constraint (seMgmtConstraint) = Unique asset tag - Tells AM that any item that is created with be tracked by unique Asset tag, therefore AM will create a record in amAsset and there will be one asset record for every portfolio item record created with this Nature

When you create an asset record for a model which is linked to nature Computer it will create records in amPortfolio, amAsset, and amComputer, and link them all together.

 

So,  if you have a number of Models linked to Nature Computer, and a number of Portfolio item for each of those Computer models, you can easily change the model of any of those portfolio items to any other model that has the same Nature, because they use the same physical tables to store their attributes.

 

If you have a another Nature, called Monitor, it probably has the following fields set:

  • Create (seBasis) = Portfolio item - This tells AM to create a record in amPortfolio when we create an item with this Nature
  • Also create (OverflowTbl) = Monitor - This tells AM to also create a record in amMonitor when we create an item with this Nature
  • Management constraint (seMgmtConstraint) = Unique asset tag - Tells AM that any item that is created with be tracked by unique Asset tag, therefore AM will create a record in amAsset and there will be one asset record for every portfolio item record created with this Nature

This new Nature (Monitor) is not compatible with the original Nature (Computer) because, whilst each create a single record in amPortfolio and amAsset, Computer also creates a record in amComputer but Monitor creates a record in amMonitor.  The tables used by each of these Natures is different, therefore they are incompatible with each other, therefore you cannot interchange the model for these portfolio items.

 

The overflow tables are only created when the asset is first created and not when its Model changes, so it is important to ensure that you have the correct Nature set on any model because you start to created assets from it.

 

If you are in the situation where you have asset records allready created but againt the wrong Nature, I can only suggest that you create new assets with the correct nature,  copy the data across from the old asset to the new one and then Retire the old asset.

Paul Catley
Senior Consultant
HP Software & Solutions
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.