I have a property named DOJ in EMPLOYEE Dimension where we are storing employee joining date (we require this field for one of the salary component calculations). This field is avaialbe in BI Cube(ZDOJ) and the date format is "DD.MM.YYYY" (ex. 09.06.2011) and the data type is "DATS". We need to import this date against every employee in BPC Dimension (EMPLOYEE) in the format 2011.JUN (for the above example). I created a conversion file, where I skip first three characters in the first step and later I am converting rest of the characters to the format required internally.
Conversion File (sample data):
My belief is I am not mapping "DATS" data type properly here. Please help me in fixing this conversion mapping.
1. Validation and process transformation file is successful.
2. Error on running Import BW Master data: "ZDOJ is not a valid command or column ZDOJ does not exist in source"
Thank you so much for your time.
I tried what you suggested, but unfortunately it dint work. Please find the sample data below. I still find the same error.
I also tried truncating first three characters using JS: %External%.substring(0, 3) and in Transformation file i have set "CONVERT_INTERNAL=YES"
I would truely appreciate your help in rectifying my mistake.
Hi, you welcome!
This way will not work. Because you have to use in "?" the values you want to keep, the year, for exemple.
Try to use four "?" replacing the space where we need the year value.
Oh! did you try:
This way you don't need to put every day of the month.
??.06.2011 *IF(js:%external%.substring(4,7)="06.2011" then "2011.JUN")
??.07.2011 *IF(js:%external%.substring(4,7)="07.2011" then "2011.JUL")
and please see
I tried all the above possibilities. But none are working in favour of me. I also requested BI team to give me fields with only months and year (ex: 201101 for 2011.JAN). This field is in NUMC Data type. But still I am facing the same error:
"ZDOJ is not a valid command or column ZDOJ does not exist in source"
Since mapping is fine, could that be because of this field in BI?
other similar fields are working fine in other transformations.