This content has been marked as final. Show 9 replies
go to DAC and find out which task in the task group failed. Also, if needed try to get the error log from the Informatica session log. we need more info to assist. This is usually because of issues w the flatfiles for code dimensions.1 person found this helpful
This are the Tasks that are failed during Full Load.
When I checked the session logs of Informatica it shows that the $$CATEGORY parameter have a null value.
Thanks for your immediate action regarding my problem.
So, immediate place to look is whether $$CATEGORY has been set in the DAC. The majority of parameters are set at system level, but some are set at task level too; I recall this dimension has the values set at task level. That being said, I believe that these should be set out-of-the-box.1 person found this helpful
Also, do you get anything from the DAC status description? I always look there before going into Informatica logs.
On the Current Run, go to the Task Group, right-click and choose Details to display the list of tasks within the group. Scroll to the column "Status Description", place your cursor in the cell and click the green check box.
Finally, is the parameter being referenced within the mapping or within a mapplet inside the mapping? If the latter, make sure you have set the overrideMpltVarWithMapVar property to Yes in the Custom Properties of the PowerCenter Integration Service. This will pass mapping level parameters to any referenced mapplets.
Please mark if helpful / correct,
Thanks, It helped me too... 'overrideMpltVarWithMap Var' changed to 'overrideMpltVarWithMapVar' solved the problem(space between Map & Var).
Glad I could help, please mark my comment as correct and flag the thread as answered.1 person found this helpful
I solved it by adding MPLT_ADI_CODES. Goto Design -->> Subject Areas (select subject areas (mine is Financial - General Ledger)) -->> Tasks (select tasks name that are failed during execution) and click NEW under parameters tab and and input MPLT_ADI_CODES.$$CATEGORY and copy the existing value of $$CATEGORY. Removed the old $$CATEGORY parameter..
Thanks for your help..
Well done Eli, although I would recommend setting the Informatica variable described above otherwise you will encounter this issue for other mappings where parameters are used within mapplets.
Please mark if helpful/correct,
How can it be that $$CATEGORY pass a value to parameter file and when it execute the workflow in Informatica the the $$CATEGORY now become null. But when you add the mapplet name it will return a value. Is it bug or something.?
I am not aware of any such bug. Did you check the aforementioned Informatica property which passes the mapping-level parameter values into the mapplet? If this is not set to Yes, then the mapplet will not be able to "see" the parameter value, which is passed by the DAC to the Informatica mapping.