One of my friend need some help as below they have a data flow like PeopleSoft(HR database)-->Sun Enterprise Directory--> Microsoft Active Directory Attribute(value) PeopleSoft Sun Enterprise Directory Attribute: Employeecode Attribute: Employeetype 100 Contractor I am using the following strategy: PF--->FIM Metaverse --->FIM Service --> Sun Enterprise Directory I created an HR MA, then HR Sync Rule though Portal to save the data AS-IS in MV like employeeType=100 Then same will be fed into FIM. After this I will create a set for Employeetype=100 then the workflow for Provision into Sun Enterprise Directory. My question is that, In best practices where should I modulate the data (100) into contractor. At the time of saving into MV? At the time of saving into FIM SERVICE DB? Or Is it needed to store PeopleSoft Attrs in MetaVerse?

Thanks for posting this question here Snehal - there really is no right or wrong answer though. My personal preference is to translate 100 into "Contractor" as part of the IAF INTO the FIM Metaverse, since the metaverse is supposed to be an aggragated meta directory that makes as much sense as possible across all connectors. This way you could potentially import other object classes into the same metaverse attribute as a meaningful string attribute ("Employee", "Temporary Staff", "Part Time Staff", etc.). Then you can define a more general policy (set definitions) in the FIM portal and isolate connector-specific knowledge in the IAF only. However as I said there is no right or wrong answer here ... it really depends on how many connectors share your "employeeType" attribute, and therefore what is the best common set of values across all connectors. As for importing into the FIM db, you can't do any transformations in the FIM MA anyhow ... so it's either an IAF (as I recommend) or not at all (in your case - just leave it in the set definition).Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

Sorry for Late Reply. thanks for help BOb.