The design of the Asset product allows you to configure which classes you are Asset Lifecycle managing. That way you don't get items showing up under Asset management that you are not Asset managing.
For example, few customers want to Asset Lifecycle Manage the BMC_People class. You can, but generally people don't like to be "lifecycle managed". We ship by default with what the majority of customers want to manage. If you want to manage a class that is not in the list by default, simply add it. If you want to remove a class that is in the list, remove it. As for having to create entries for existing items, you don't need to worry about that. The join between the CMDB and the AST:Attributes form is an OUTER join, That means an entry in the CMDB will be present in the join whether or not there is an AST:Attributes entry. The values for the fields will be NULL in the lifecycle area. If you assign values, a record will be automatically created to hold those values for you. There is no need to pre-create entries in the AST:Attributes form. And, as was noted in a later message, the customer simply added BMC_Account to the configuration and all started working as expected with no further action. I hope this helps explain how things are designed. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Adesanya Olufowobi Sent: Saturday, November 22, 2014 11:24 PM To: [email protected] Subject: Re: BMC Account Class ** Hi, Check the AST:ClassAttribute form to see if a record exists for BMC Account Class. If not, create one. You will need to generate entries in the AST:Attribute form for the CIs already loaded. HTH. Regards, Victor On 23 Nov 2014 05:10, "Santosh Kumar S" <[email protected]<mailto:[email protected]>> wrote: Hi All, Request you provide your inputs for the below: Records are not getting created in AST:Attributes form for CI data loaded to BMC_Account class.Reconciliation jobs has runned successfully and CI in Temp dataset is getting reconciled and record is created in BMC.ASSET as well. But, record is not getting created in AST:Attributes form for the recon id genearted. tested with other class such as Application,Computersystem, no issues here(records are getting created in AST:Attributes form after recon job). Any issues only in BMC_Account class? please let me know if you had come across this scenario. Regards, Santosh Kumar S -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/BMC-Account-Class-tp119901.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> "Where the Answers Are, and have been for 20 years" _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"

