This content has been marked as final. Show 9 replies
In the Integration Settings, select Enable Load, then uncheck the box. This will allow export of the .dat file, but will not load to HFM.
Thanks for the reply Larry.
In our case, for location where we need only .dat files, mapping is li'l different.The target column members are not the members which belong to target application which is HFM.In this case, we will get error during validate step, as members are not available in HFM. Is there any solution to over come this issue or using Pull adapter is the only solution
Also under Integration Settings is an option called, "Enable Intersection Validation". Uncheck this box and the Validation phase will be skipped.
Thanks Larry.The settings specified by you are Application specific which are valid for all the locations in FDM.
But we have only one location for which we will not load data to HFM, intsead will have .dat files in outbox.And for all other locations, data will be loaded to HFM.
Try this in the BefValidate script:1 person found this helpful
If this works, you'll have to do something similar in the BefLoad script.
strFMOptionID = API.IntBlockMgr.IntegrationMgr.PstrSysKey & "EnableChkIntersect" If strLoc = "Non-ValidatedLocation" Then API.DataWindow.DBTools.fGlobalOptionSet strFMOptionID, True, "EnableChkIntersect" Else API.DataWindow.DBTools.fGlobalOptionSet strFMOptionID, False, "EnableChkIntersect" End If
Edited by: Larry R on Apr 5, 2013 11:36 AM
Larry's suggestion should do the job, but as an alternative, If you are happy with using the HFM adaptor for this particular location and do not wish to write your export file details using the PULL adaptor, you could take a copy of the HFM adaptor and link that to this location. Although you would need to maintain a second set of control table information it does give you the ability to have a differetn set of integration settings independent of the other locaiotns using the existing copy of the adaptor.1 person found this helpful
Thanks for suggestions.
Our requirement is
1. one location we will have different set of maps where HFM members will be the source, where as for remaining locations HFM is the target.
2. Since, HFM is target application and in this scenario, HFM members are source members we just want .dat file to be generated and not exported to HFM.
We were able to achieve the 2nd point by just exporting file and not loading it with dummy maps.
But, for 1,when we use actual maps, Validate will fail as it tries to validate with existing HFM target members. I'm trying to complete this step for which I want to know if we need Pull adapter or can we implement logic as Larry suggested..
Try the code I provided earlier in the BefValidate script. If that works, you'll have to implement very similar code in the BefLoad script.1 person found this helpful
Thanks Larry for your suggestions. We have been suggested to use Pull adapter for our requirement