My ETL team is in search of a workaround to load a period data type with INFA 9.1. We've tried casting period(current_date,until_changed) as a string and nearly every other workaround we can think of.
Inserts work very nicely from bteq scripts and SQL Assitant of course, but we can't find the sweet spot using INFA. The folks at INFA are telling us we have to wait until 9.5, but we've got projects in flight that need this functionality.
Part of the problem is that Informatica Metadata Manager won't integrate with the bteq scripts and we loose the data lineage.
I can't believe we are unique to this particular problem, but nothing surprises me anymore....
what is the exact error message you're getting when loading period datatype, are you using loaders or TPT API.
Just so as you know with MM, you can create custom Xconnect to parse bteq scripts and INFA services Team has created utility to do that.
Let me know if you need more information for the same.