Defaulting Date Types in IT0041

Hi All,
I have a issue in defaulting Date Types in IT0041,
There is a feature DATAR for defaulting Date Types in IT0041. When I create new IT0041 by PA30, values from feature DATAR is getting defaulted.
But, when i run Hiring Action and at that time vaules from feature DATAR is not being called, its defaulting some other date types.
Is there any other place where Date Types are defaulted?
Please let me know if you want any more information
With Regards
Shyam

Hi All,
Current problem is rectified,
Solution : I have used INSS instead of INS. In this case values from DATAR is getting defaulted
New issue is there,
Some dynamic action is automatically updating with Date Types those which are not there in DATAR. I dont know from where these values are being picked....
I will continued my research and let you guys know the status.
I request others to share their thoughts..
Regards
Shyam V

Similar Messages

Default date type for IT0041 in action

Hi,
I configure feature DATAR to set 01 as default date type for IT0041, but when I do hiring action, default date type will be 01,02,12.
Don't know where to change the default.

Hi,
Please verify if there is any dynamic action in table V_T588Z set-up for same which may cause override over default.
Also, verify if your DATAR feature is set up correctly for relevant country grouping and activated.
Thanks,
Ameet

Automatic Benefit Plans based on Date Types in IT0041

Hi
I am having an issue with a re-hired employee. We have two date types in IT0041. Current Hire date and Service Award Date. If somebody is hired for 1st time, both the date types are same( e.g 12/12/2008). and this case the automatic benefit plans follow the config rules properly and some start from the hire date and some from the 1st of following month as per the config ruel.
But If we are re-hiring an employee, in this case Current Hire date( 12/12/2008) would be different from Service award date ( because of his previous experience with this employer). In this case all the automatic plans are starting from the date when the re-hire action is performed, not even the re-hire date and do not follow the config rule at all.
We have never made any dependency of benefit plan on IT0041 anywhere in config, but why this is happening? Any suggestion would be appreciated,
Thanks
Wills

Nope. we never configured the dynamic eligibility part. So that makes it more strange. Because if all the date are same it works fine , but if the dates are different, it gives wrong result

User exit for adding more date types into IT0041

Hi all,
I have a requirement where in HCM infotype IT0041 I need to add couple more custom date types besides standard date types in IT0041. So if I use user exit, what are the steps to do this? what enhancement name should be used?
Thanks,

Ben - Unfortunately I haven't implemented a BAdI as I do more functional work. I found a few documents on line that may help (gotta love Google!). Maybe someone on SDN who is more technical can provide additional information.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb99702?quicklink=index&overridelayout=true
http://sapient.wordpress.com/2007/05/25/implementing-business-add-ins-badi/
http://it.toolbox.com/wiki/index.php/Document_on_BADI#BADI_Implementation
Good luck!
Thanks,
Danialle

Error while saving default data type

When I try to save system wide Default Data Format of any of the columns, an error pops out. Seems like an XML error:
The current xml is invalid with the following errors:
Bad xml instance!
<?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Division Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Group Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Dept Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Class Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Item As Was"."Subclass Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Chain Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Area Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Region Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."District Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Organization As Was"."Store Number""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Business Calendar"."Fiscal Week""><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:text" textFormat="plain"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName=""HT Catalog"."Unit Inventory"."U BOP""><saw:displayFormat><saw:formatSpec suppress="repeat" wrapText="true" visibility="visible" hAlign="right" vAlign="top" imagePlacement="right"><saw:dataFormat xsi:type="saw:number" whistlerFormat="#,##0" commas="true" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
Line:2, Col:8982, Attribute 'whistlerFormat' is not declared for element 'dataFormat'
Any suggestions?
Thanks

HI,
Its known bug in obiee11.1.1.5. version try to apply obiee11.1.5.5.BP bug fixes version.
fyi,
bug 13370386 - 'THE CURRENT XML IS INVALID WITH THE FOLLOWING ERRORS: BAD XMLINSTANCE!' OCCURS
bug 13249783 - OBIEE 11G THROWS BAD XML INSTANCE
Thanks
Deva

JPA - How can I use the table's default Date types? e.g. CURRENT_TIME

Once again, can't find an answer anwhere.
I would like to know if/how one can use the default date/time/datetime types as declared for the target table when attempting to persist an entity having these fields set as null.
create table item
     item_id INTEGER NOT NULL PRIMARY KEY DEFAULT AUTOINCREMENT,
     date_created DATETIME NOT NULL DEFAULT NOW(*),
     date_updated DATETIME NOT NULL DEFAULT NOW(*),
);Now how can I get the above table to work when attempting to em.persist(myItem) whereby dateCreated and dateUpdated are both null?

I should also mention that TopLink has always supported the ability to retrieve the current time from the database for use in optimistic locking. The TimestampLockingPolicy offers the ability to configure the next value being retrieved from the database instead of using the local time from the JVM. Our extended optimistic locking configuration does not currently support setting this option but it could be done using a descriptor customizer which can be configured in your persistence unit properties.
Using optimistic locking may be a good solution for the last modified date since it will also ensure that you do not corrupt the database if someone else has incremented this value since your last read.
Doug

IT0041 - employee with more than 12 date types;

Has anyone had an instance where an employee has had more than 12 valid Date Types on IT0041? If so, how did you enter their 13th date type? We have just created our 12th date type in the table and we will probably be creating a 13th date type in the near future. We have a number of employees who already use 11 date types and could use the 2 new ones as well. I tried to create a new Subtype for my new Date Type - but the new Subtype requires that Date Type 01 be entered. I am not comfortable with having two identical Date Type 01s in IT0041 (one on Subtype 0001 and one on Subtype 0098).
Has anyone used more than one Subtype on IT0041?

Thank you for your responses. I don't think changing the Time Constraint class is the best solution for our organization. We did look at that option. I don't want to have multiple valid records; I want the ability to have more than 12 date types (values) on one record. Also, if we allow more than one record, SAP forces us to have Date Type 01 on both valid records - I would be concerned that these values may not match, and then Time Eval would bomb.
I'm also still curious if anyone has used more than one Subtype on IT0041? Again, we did try this, but SAP forces a Date Type 01 on both Subtypes.

The data type of the variant is not compatible with the data type wired to the type input.

Hello all..
Iam curently struggling with the following:
On my main(top)_VI, I have a mix-signal graph which will output several or one signals depending on the user. I also have an inner subvi which has the analisys i want to give the the data before outputing it to the main(top) VI, which has the mix-signal graph control.
Now, I created a reference from the mix-signal graph and Iam imputing this reference into the subVI (which inside has a property node type_control_mix-signal graph in which Iam connecting the refnum from the top VI to view the output data). The data consists of an array of clusters of 2 arrays of doubles each.
-- let say I create the property node type control mix-signal graph and i choose value property; it lets me put the array of clusters of 2 arrays of doubles each without problems; Now the second I connect the refnum pointing to the mix-signal graph on the Main_VI it brakes the cables and only accepts one cluster of two arrays os doubles instead.
--if on the other hand I connect the refnum to the property node type_control_mix-signal graph before connecting the imput it doesnt complain until I run the VI where it gives the error 91.
I have also notices a (strict) parenthisis at the end of the property node sometimes. [what does this (strict) means?]
FInally if instead of creating the refnum from the Main_VI, I create either a xy graph or a mix-signal praph it lets me connect the an array of clusters of 2 arrays of doubles each without any problem. The refnum connection seems to be the problematic factor, but by the same tolken I dont know any other means of sending that data from the inner to the outter VI.
I have the feeling Iam missing on one or more Labview fundamentals regarding refnums.
Any help will be apreciated

You almost found it on your own. The refnum needs to be 'strict', that means that the data type of the graph is set (2D dbl), otherwise it will use the default data type. To do this you create the refnum directly from the graph after you have wired the correct data type to the terminal. In this case the refnum wire will break if you change the data type of the graph.
Independend of this issue, I suggest you not to use the value property on the graph but directly wire the data (e.g. the 2D double) to the SubVI. The property value is by far the slowest way to get data, and 2D arrays are really some amount of data.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Dynamic structure of "string" data type. Please help.

ABAPers,
I am calling cl_alv_table_create=>create_dynamic_table method to dynamically create a structure. The input structure definition is as follows:
data: xfc type lvc_s_fcat.
data: ifc type lvc_t_fcat.
* define Fld1
clear xfc.
xfc-fieldname = 'Fld1'.
xfc-datatype = 'string'.
append xfc to ifc.
* define Fld2
clear xfc.
xfc-fieldname = 'Fld2'.
xfc-datatype = 'string'.
append xfc to ifc.
Although the call to create_dynamic_table does not throw any exceptions, it appears Fld1 and Fld2 are not of "string" data type. I don't know of a way to see what type they are. However, they do have a length limit of 10 characters.
After some experimenting, it turns out that the method simply ignores "datatype" value if it doesn't understand it and creates the field with some default data type.
I would appreciate it if someone can show me how to create fields of "string" data type.
Thank you in advance for your help.
Pradeep

That's right, use STRG as the datatype. Please see the example program.
report zrich_0003.
type-pools: slis.
data: new_table type ref to data,
      new_line type ref to data.
data: xfc type lvc_s_fcat,
       ifc type lvc_t_fcat.
field-symbols: <dyn_table> type standard table,
               <dyn_wa>,
               <fs>.
start-of-selection.
clear xfc.
xfc-fieldname = 'Field1' .
xfc-datatype = 'STRG'.
append xfc to ifc .
clear xfc.
xfc-fieldname = 'Field2' .
xfc-datatype = 'STRG'.
append xfc to ifc .
* Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
    exporting
      it_fieldcatalog = ifc
    importing
      ep_table        = new_table.
assign new_table->* to <dyn_table>.
* Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
assign component 1 of structure <dyn_wa> to <fs>.
<fs> = 'This is string 1'.
assign component 2 of structure <dyn_wa> to <fs>.
<fs> = 'This is string 2'.
append <dyn_wa> to <dyn_table>.
* Write the values of internal table.
loop at <dyn_table> into <dyn_wa>.
    do.
      assign component sy-index of structure <dyn_wa> to <fs>.
      if sy-subrc <> 0.
        exit.
      endif.
      write:/ <fs>.
    enddo.
endloop.
REgards,
Rich Heilman

Rep-1340 error for date type

I want to transfore forms date directly to report. then i use run_report_object function. But in forms i use datetime type replace of default date type. then the item can show time. then i revoke the report.rep-1340 error get. Who have better solution. thanks a lot.

Hi ...
pass thedate by a parameter list
but transform the date into char
with to_chat(the_date,format)
in report's query you will may do like this:
select ..... where query_date = to_date(the_parameter,format);
the formats must be the same.
Good look !
Ovidiu ANCUTA
[email protected]

Default Date in IT0041 On Executing Promotion Actions

Dear Colleagues,
I have written a Dynamic Action for defaulting the Promotion date in IT0041. It's working perfectly fine.
However system is throwing an error on executing Promotion action for the same employee second time.
Here client wants that the latest promotion date should get defaulted in IT0041.
Please guide.
Regards,
Garima

Yeah..sure.
It's actually giving that Date Type is already maintained...
Code is
04 81 PT001P-MOLGA='40'
04 82 P P0000-MASSN='05'
04 83 I COP,0041,,,(P0000-BEGDA),(P0000-ENDDA)/D
04 84 W P0041-DAR07='R5'
04 85 W P0041-DAT07=P0000-BEGDA

How to Get Default Value of a Data Type in SQL Query.

Hi all,
I am creating a procedure which will take input the table name and Column Name.
In the Output i would like to have the data type and default value of that data type which will be used by a another procedure to blank the selected column in the database.
I tried with SET NULL on the column but as the database is of navision the table have property set to NOT NULL.
Here is what i have done till now.
Create Procedure Get_Column_type
@parm_table_name nvarchar(200),
@parm_column_name nvarchar(20),
@parm_result nvarchar(20)OUTPUT
AS
BEGIN
select @parm_result =
DATA_TYPE from INFORMATION_SCHEMA.COLUMNS IC
where TABLE_NAME = '[' + @parm_table_name +']' and COLUMN_NAME = '[' + @parm_column_name + ']'
END
GO
Now instead on write a case statement for so many data types in SQL, i was thinking is it possible someway that above procedure also returns the default value which i can set in another procedure.
Let me know if its possible or not? Thanks in advance.

Do you looking for something like this?
create table t10 ( c int default 1)
SELECT so.name AS table_name,
sc.name AS column_name,
sm.text AS default_value
FROM sys.sysobjects so
JOIN sys.syscolumns sc ON sc.id = so.id
LEFT JOIN sys.syscomments SM ON sm.id = sc.cdefault
WHERE so.xtype = 'U'
AND SO.name = 't10'
ORDER BY so.[name], sc.colid
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

IT0041 : Same date type with different values in the same infotype

Hi,
Is it possible to store in the 0041 infotype, the same type date but with a diffentent date.
Example :
IT0041
employee 1000:
date type : xx 01.05.10
date type : xx 02.05.10.....
Thanks

Hi there,
My two cents.
I don't think it can be done in standard. Also copying IT 0041 would limit you to enter only 12 dates.
My suggestion:
Create a custom infotype with subtype field and a date field like IT 0015.
On the screen you will only be seeing subtype and date. And assign time constraint 3 to it.
In this way with the same subtype you can record several dates.
cheers
Ajay

How to set a default date for a custom field of Date type in project server 2010.

hi,
can somebody help me.
How Can i set the default date for a custom field of date type in project server 2010 ?

Dear Rohan,
You can set default value to custom field thru Lookup table. Assign lookup table to custom field and set default value to some lookup value (Note: check the “Choose a value to use as a default when adding new item” checkbox).
Regards,
Avinash kumar | Blog:http://avigr8.wordpress.com | If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

How to set default value to date type attribute.

Hi,
How to set default value to date type attribute.
E.g I want to set u201C01/01/1999u201D to date attributes.
First i want to set value and then i want to fetch the same & want to check equals.
please suggest solution.
Regards,
Smita

Hi,
In wdinit() method u can set the date
DateFormat df = new SimpleDateFormat("MM/dd/yyyy");
Date today = Calendar.getInstance().getTime();
String reportDate = df.format(today);
wdContext.currentContextElement().setFromDate(reportDate);
Another way you have set the this formate like that
1. Create a Simple type under "Dictionaries->SimpleType" called DateFormat
2. Select the type as "date"
3. Go to the "Representation" tab and set the format as "dd/MM/yyyy" (or whatever u want, but month should be MM)
4.Bind the context attribute to the type created now.
Hope this helps u.
Best Regards
Vijay K

Defaulting Date Types in IT0041

Similar Messages

Maybe you are looking for