I think you need <%=odiRef.getSysDate("yyyyMMddHHmmSS")%>)
M in upper case are for months and m in lower case are for minutes in java.
But I don't understand why this command is not interpreted. Which technology did you choose for this new KM step ?
PS : Is your "Yellow Interface" problem solved ?
I am using File technology.
Just placing my Header i am using the syntax Create Header.
The below code i am using but not getting the correct Output.
create header (HSB9KT.KTPRTO.EBSDATA.D0000000 <%=odiRef.getSysDate("yyyyMMddHHmmSS")%>)
Just an idea
Can you test the same syntax but without "space" before the date ?
Just to see if the date will be displayed or not.
As I told you, in this tutorial your yellow interface should only be used as the source of a second interface. And then you should just execute the second one (the first doesn't need to be executed, it will only be used as a view by the second one). If you need more info about that, ask your questions in the other thread : Yellow Interface :)
I sent you a KM which can insert the custom headers and custom footer without modifying the existing codes in the KM.
Though the create header logic is fine but little mistake there will lead you array index out of bound exception (less or more than the target data store attributes.)
The best way is to go for java beanshell or jython.
I have tried in the below both ways but its not working..
I really appreciate your ideas but somewhere it is missing something....I am working on this
create header ('HSB9KT.KTPRTO.EBSDATA.D0000000 <%=odiRef.getSysDate("yyyyMMddHHmmSS")%>')
create header ("HSB9KT.KTPRTO.EBSDATA.D0000000 <%=odiRef.getSysDate("yyyyMMddHHmmSS")%>")
Quotes or double quote don't fix the problem ?
Try again your first solution with ODI variable.
But in the ODI variable, do a concatenation of a "space" with the date.
Example of variable refresh in Oracle :
select ' ' || <%=odiRef.getSysDate("yyyyMMddHHmmSS")%>') from dual
select ' ' || to_char(sysdate,'YYYYMMDDHH24MISS) from dual
In your KM step, call this variable. But prefix it with the name of the project code. Example : if your project code is PJ and variable is datevar, you must write #PJ.datevar. Or #GLOBAL.datevar if is it a global scope variable.