Discoverer 2000 : Problem in sorting date field on report

Hello,
I am not able to sort on date field on report
it is giving error as
( illegal operation).

Thanks Savitha.
I found one more way of making that code work, just want to share this.
If we add the following statement, the same code works without having to add the time part along with date.
"DBMS_XMLSave.setdateformat(updctx, 'yyyy-MM-dd');"
note the format is case sensitive. Instead of MM, if you give 'mm' it won't work, it uses java format.

Similar Messages

Problem while saving date field in custom table

Hi,
Iam facing the following problem while saving a date field in custome table
i have a date field zdate in which the value is 02082010.
now when i try to insert this value in the custom table it is getting updated as 20/10/0208 , but it should be 08/02/2010
How can i correct it..
Regards
Kumar

just before saving u might have to use a string reverse FM and then save it..
CALL FUNCTION 'STRING_REVERSE'
EXPORTING
    STRING          = p_string
    LANG            = sy-langu
IMPORTING
   RSTRING          = r_string
EXCEPTIONS
   TOO_SMALL        = 1
   OTHERS           = 2

Problem updating a date field via UnitOfWork - TopLink 9.0.3

Hello,
we want to change an exisiting application that employs TopLink 9.0.3, Build 423.
The data is stored in an Oracle 9.2.0.6.
The specific table has a composite primary key consisting of four fields.
I can easily create a new Object (foo)
uow.registerNewObject(foo)
uow.commit()
and see the results in the database.
If I obtain an exising Object (bar) and change an integer
bar = (Bar) Session.readObject(Bar.class, expr);
cloneBar = (Bar) uow.registerObject(bar);
cloneBar.setSomething(42);
uow.commit()
everything is fine.
But if I dare to change a Date field
cloneBar.setSomethingElse(cal.getTime());
then
uow.hasChanges()
returns true
but the update does not happen. It is neither logged nor is the data changed in the database.
Is this a known bug?
What have I done wrong?
How can I avoid using hard-coded SQL to update my Bar object?
Bye,
Stephan

Hello,
it is very disturbing, but I finally found the reason for this problem.
After decompiling the Project class file (we have no source code of this third-party library), I saw that the mapping for this specific field is set to "readOnly".
I did not know that TopLink is able to have specific fields "readOnly" and others "readWrite", but it can handle this!
So it seems that the behaviour is not a bug but a feature :-(
We can change the mapping before creating the session, with the result that the field is updatable.
Have a nice day.

Sorting date Field

Hi,
      I am using groupField in Advanced Datagird, in that i want sort the date field. The date field sees like that 06/22/1986(Month/Date/Year). How i can sort it.
Regards,
Sivabharathi

Hi,
Thank you for your reply. I tried sortComparefunction. But it's not working perfect. Look at the example.
<?xml version="1.0" encoding="utf-8"?>

<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
    <mx:Script>
        <![CDATA[
            import mx.collections.XMLListCollection;
            import mx.events.FlexEvent;
            import mx.utils.ObjectUtil;
            public var reportXMLList:XMLList = new XMLList();
            public var listCollection:XMLListCollection ;
            private var tempXML:XML ;
            private function date_sortCompareFunc(itemA:Object, itemB:Object):int {
                var dateA:Date = new Date(Date.parse(itemA.dob));
                var dateB:Date = new Date(Date.parse(itemB.dob));
                return ObjectUtil.dateCompare(dateA, dateB);
            protected function init():void
                tempXML = new XML(<root>
                                <row col1="12/27/2010"/>
                                <row col1="12/29/2010"/>
                                <row col1="01/05/2011"/>
                                <row col1="01/07/2011"/>
                                <row col1="01/31/2011"/>
                                <row col1="02/15/2011"/>
                                <row col1="02/17/2011"/>
                                <row col1="02/18/2011"/>
                                <row col1="02/25/2011"/>
                                <row col1="03/11/2011"/>
                                <row col1="03/18/2011"/>
                                <row col1="03/19/2011"/>
                                <row col1="03/21/2011"/>
                                <row col1="03/22/2011"/>
                                <row col1="03/26/2011"/>
                                <row col1="03/30/2011"/>
                                <row col1="03/30/2010"/>
                                <row col1="03/30/2009"/>
                                <row col1="03/30/2015"/>
                              </root>);
                reportXMLList = tempXML.row;
                listCollection= new XMLListCollection(reportXMLList);
        ]]>
    </mx:Script>
    <mx:AdvancedDataGrid id="dataGrid" initialize="init()" dataProvider="{listCollection}"
                         width="100%" height="100%">
        <mx:groupedColumns>
            <mx:AdvancedDataGridColumn dataField="@col1"
                               headerText="Date of birth:"
                               sortCompareFunction="date_sortCompareFunc"
                               />
        </mx:groupedColumns>
    </mx:AdvancedDataGrid>
</mx:Application>

Is anyone else having problems with Apertures Date fields?

After experiencing a sysems failure I began restoring my images from backups. I have had no end of problems with Image dates. I have come to the determination that Aperture is NOT using either the "Create Date" or "DateTimeOriginal" as the image "Date" or "Date Created" data if other fields have other dates.
Here is a clip from my image metadata using exiftool:
File Modification Date/Time     : 2012:09:23 19:53:15-04:00
File Access Date/Time           : 2013:01:16 11:34:38-05:00
File Inode Change Date/Time     : 2013:01:16 11:31:32-05:00
Create Date                          : 2006:02:20 11:51:12.10
Date/Time Original              : 2006:02:20 16:51:12.10
Modify Date                          : 2006:02:20 11:51:12.10
And here is what Aperture utilized on import
Date:                               9/23/12 7:53:15 PM EDT
Date Created                         9/23/2012 7:53:15 PM
So Aperture utlized the File Modification Date/Time as the Create Date despite that the fact that the Create Date field is present and is properly formatted in the original image.
According to the Aperture mapping table, this shouldn't be happening.
Now, before someone recommends that I use Aperture's Date Adjust utility - I'm talking about slightly over 30,000 images. Editing images one at a time, or in blocks when you don't know what field Aperture is using as the Create Date would require individual inspection of each image followed by manual adjustment of each image. That approach isn't acceptable.

Hmm ok, let me restate the issue then, I thought I was clear. I could have pointed out in my original post however, that only the EXIF and IPTC date fields were displayed from the metadata dump.
The data set presented in my first post is the EXIF dataset from the file which clearly shows the image was captured by digital camera at
Create Date                          : 2006:02:20 11:51:12.10
Date/Time Original              : 2006:02:20 16:51:12.10
(The delta of 5 hours is the result of Zulu versus local time offset)
But, when I ingested it into Aperture, the import routine utilized the IPTC field
File Modification Date/Time     : 2012:09:23 19:53:15-04:00
which is updated by the OS whenever you move the file around outside of Aperture. (a number of image data fields are updated by the OS - filename for example is another.). This resulted in the image date fields being stamped in Aperture as:
Date:                               9/23/12 7:53:15 PM EDT
Date Created                         9/23/2012 7:53:15 PM
Which obviously came form the File Modification Date/Time field and not (either) the Create Date or Date/Time Original fields.

Problem with displaying Date field in the table.

Hi All,
I am trying to display data into a table UI Element.
In that data, i have one DATE type field. While displaying data in DATE field, it will display like this "01.02.2009".
Now my requirement is if i want to modify that DATE field, it will allow to modify "01.02.2009" to "26.02.2009".
But while modifying DATE field , I want to show the Calender of that month, in that i have to select the another date.
(Like normal Date UI Element will show that calender).
Can anyone please help me.
Thanks in Advance!
Regards,
Sreelakshmi.

Hi,
Go to the context attribute that was mapped to the DATE field of the table and change the perperty INPUT HELP MODE to AUTOMATIC and it works.
Regards,
Manne.

Problem with the date field in Table Control

I have created a table control in my module programming. One of the column in the table control is a date field which is I/O field.
Now if I enter a value in date field column and hit enter the date field is reset. I dont want the field to get reset and accept valid date field.
I have set type of the column as DATS and I havent used any dictionary fields. The column is from the internal table in the program.
Please suggest

In your PAI, in the LOOP AT <itab> did you
- check date validity
- update internal table
* Sample
LOOP AT itab.
FIELD itab-field MODULE checkfield.
MODULE updateitab.
ENDLOOP.
Look also at SAP documentation like [Table Controls|http://help.sap.com/abapdocu/en/ABENTABLE_CONTROL1_ABEXA.htm] or [Table Controls in ABAP Programs|http://help.sap.com/saphelp_nw04/helpdata/EN/9f/dbac9f35c111d1829f0000e829fbfe/frameset.htm]
Regards,
Raymond

Problem update a date field

Hi,
I have one table with a date field.
For display all rows in a table component i'm using a dateTimeConverter object with format 'dd/MM/aaaa' and work fine.
Bat when i update a data provider with follow code:
public String update_action() {
// TODO: Process the button click action. Return value is a navigation
// case name where null will return to the same page.
try {
myDataProvider.commitChanges();
myDataProvider.refresh();
} catch(Exception e) {
error("One error: " + e.getMessage());
return null;
return from brawser the follow message:
Number of conflicts while synchronizing: 1 SyncResolver.UPDATE_ROW_CONFLICT row 2 Data Exception -- No Applicable Cast Operator. from SQL type BINARY to SQL type DATE
Anyone help me!
Thanks.

If you are getting the date from a calendar you have to convert it before storing it, for example, in the following code, the date got from the calendar is converted to a java.sql.Date
java.sql.Date date1 = new java.sql.Date(calendar1.getSelectedDate().getTime());
I hope this helps =)

Date field in Reporting

Hello all ,
We need to display the Start date and the End date along with the time taken to complete the project in a report. I have created a measure called date and the type is a text field. I was able to load data into the date field. But , I am unable to bring the date field into the report. There is a error which is coming. Is it possible to display the date field in the report / KPI ?
Thanks
Vijay

Hi Ricardo ,
I am trying out both the methods. My client is a infrastructure company. It has a number of projects . The client wants to monitor the performance of each of his projects and the overall Delay. My requirement is to display a report which has the actual start date , planned start date , actual end date , planned end date , actual , budget and delay.
I tried to load the date fields into the PAS as a text field. The data load was successful. But when designing the report , I am getting an error. Is it a problem related to text variables ? Is it possible to bring the text variables onto the UI ?
Is there a way to build a report on the data from initiatives in SSM ? Do we need another reporting toll to achieve the same ?
Thanks
Vijay

DB link problem between active Data Guard and report application database

My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?

Fazlul Kabir Mahfuz wrote:
My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?
Check this note which is applicable for your environment
*ORA-01555 on Active Data Guard Standby Database [ID 1273808.1]*
also
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8908307196113

How to place a sign like '.' in front of a data field in report builder ?

Hello Everybody,
In the presentation of datas in my report , I must list the sub-elemnst of a group by plcaing a ' *.* ' in front of each one. Like
Persons
*.* Jean Fontaine
*.* François David
*.* Serena Joyau
How must I process to do it ?
Helps.
Regardly.

Thanks Vikas.
I do it as
SELECT ALL '.' || V_PRESTATAIRE_MALADIE.NOMBENEF, V_PRESTATAIRE_MALADIE.ADREBENE,
V_PRESTATAIRE_MALADIE.TELEBENE, V_PRESTATAIRE_MALADIE.LIBDETLI
FROM V_PRESTATAIRE_MALADIE
But in the field 'NOMBENEF' , more data does not appear. And too when I want to increase the lenght of the signal '.' or put it(the signal) in bold face , I have not possibility.
There has not other mean do realize it ?

Hyperlink on data field crystal report vs 2005

Please help!!!!
I can not set the hyperlink on a data field in *.rpt.
I also set the hyperlink type was A website on internet and filled the website address. But when report display i can not see any link.
Thanks in advanges,

Hello,
(from CR Help file)
You can select a report object on the Design or Preview tab and create a hyperlink to another location.
The hyperlink is saved with your report and is available to other users as a way of viewing additional information.
Note:    Crystal Reports also lets you create hyperlinks with Relative URLs, so your web reports retain independence from their location on any particular server.
To create a hyperlink field
Select a report object on the Design or Preview tab.
On the Format menu, click Hyperlink.
The Format Editor dialog box appears with the Hyperlink tab active.
Click the type of hyperlink you want to create.
The available types in the upper area are:
No Hyperlink
This is the default option. There is no hyperlink associated with the selected report object.
A Website on the Internet
Select this option if you want your report object to be linked to a static web address. Use the formula button to create a URL based on a field value. For example, you might enter the following formula if your Customer Name field contained information that would create a series of meaningful URLs:
"http://www." + {Customer.Customer Name} + ".com"
Note:    You can also use this option to connect to Business Objects, Web Intelligence, and OLAP Intelligence documents (this is also known as report linking). Use the openDocument function to create these hyperlinks in Crystal Reports.
Current Website Field Value
Select this option if you want the program to create a hyperlink out of the field you selected. The field must be stored as a proper hyperlink in your data source.
An E-mail Address
Select this option if you want to create a "mailto" address from the field you selected. Use the formula button to create an address based on a field value.
A File
Select this option to create a hyperlink to a file on a specific computer or networked computer. Use the formula button to create a file path based on a field value.
You can also use a hyperlink of this type to run an EXE with a command-line parameter. Enter the path and application name, and follow it by the parameter for the command.
Current E-mail Field Value
Select this option if you want the program to create an email hyperlink out of the field you selected. The field must be stored as a proper email address in your data source.
The available types in the DHTML Viewer Only area are:
Report Part Drilldown
For information about how to use this option, see The Report Part Drilldown option.
Another Report Object
For information about how to use this option, see The Another Report Object option.
Note:    Not all hyperlink types are available at all times. The object you select and its location on the report determine which types are available.
After you have chosen a hyperlink type, enter the appropriate hyperlink information (the URL of a web site, for example).
Click OK when you are finished.
The hyperlink is inserted as appropriate. Click it on the report to go to the web site, to send an e-mail, and so on.

Problem when sorting data based on date

I am trying to sort the following data based on the Transaction Receipt date column,unable to do it usi g the following syntax:
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
I have problem in converting the date in report to canonical date ,is there any other way to achieve the output without converting the date format.
<?xml version="1.0"?>

<RECDTREP>
<LIST_G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO104</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24636</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863063</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO107</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24641</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863068</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO123</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24658</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863086</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO75</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22190</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860842</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO116</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64271</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863077</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO92</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>22253</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860890</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO99</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22263</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860899</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO109</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>64204</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863070</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO135</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/18 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64296</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875546</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO101</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24618</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863046</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO120</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24653</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863081</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO122</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24657</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863085</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO127</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24662</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863090</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO100</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24585</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863033</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO110</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64265</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863071</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO130</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/13 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64275</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875487</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
</LIST_G_ASW_REC_DATE>
<CF_SORT_BY>Manufacture,Receipt Date,Organization,Item Code</CF_SORT_BY>
<CF_SERIAL_WHERE></CF_SERIAL_WHERE>
</RECDTREP>

HI Mahesh,
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
this is not a date,
so you should change the query to get you the format in xsd format : YYYY-MM-DDThh:mm:ss+HH:MM
otherwise, you have to write a custom sort function to decode and order it it.
if you dont do the custom order and use
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
the data will be treated as string and you will see the row is sorted on string.

Problem with sorting dates

I am taking date from the user in mm/dd/yyyy in the text field.
Since I am maintaing a document management system,
I need to sort docs with respect to dates. Latest date first.
Can anyone help me how do I do this.
I have to get docs from database(mysql) and I cant use order by ....
Please help

How you enter and what gets stored and what gets displayed are controlled by your formating and can be 3 different things.
If you use an sqldate as a type for the mysql then you have raw date data ( some big integer type). This you push through a format to display.
Calendar work = Calendar.getInstance();
java.sql.Date sqldate = new java.sql.Date(work.getTimeInMillis());String displayDate= sqldate.toString();
gives you todays date in the format yyyy-mm-dd
to use something else see:
http://java.sun.com/docs/books/tutorial/i18n/format/simpleDateFormat.html
In the mySQL dates are stored in a sortable format - how they show is NOT how they are stored.
I have dates in mySQL also, I have to display the records in ascending or descending order depending on the module.
Dates are a bitch to work with. You get it working on your local host and then you up load it to your server and it is running with a different date format and everything crashes.
Just wait till they ask for time, it is even worse.
so basically
1- input your date info
2 - tranfrom it into sql date format
3 store it inmysql as a date
4 search it and generate a datset in order of xdate desc
5 read through the data set and format your date for display
Lena

Problem with the Date Field in Production

In Development while using a variable with data element DATS , the variable gets initialised to 00000000.
But the same does not get initialised in Production.....
Kindly suggest?
Regards
Dilip

please see the link ...in this the datefields also included in the table control of the
Screen program .... how the fields are populated in the table using wizard ..
<a href="http://">http://www.sapdevelopment.co.uk/dialog/tabcontrol/tc_basic.htm</a>
reward points if it is usefull ....
Girish

Discoverer 2000 : Problem in sorting date field on report

Similar Messages

Maybe you are looking for