Wrong Timestamp in Performance Header

Hi Friends,
I am opening SXMB_MONI (Perfoamance header ) there it is showing timestamp (yyyymmddHHmmss.SSSS) which is 5 hours ahead to our time zone(New York).
<SAP:Timestamp type="begin" host="SAPDEV">20100927171451.261493</SAP:Timestamp>
</SAP:RunTimeItem>
Sent time is: 171451
Any idea how to fix it?
Thanks,
Sandeep Maurya

Hi,
System shows the GMT Time, I think we can not change this time as the system saves this time in database to uniquly work for all systems throught out the world.
We have few reports to show this Time where we are externally modifying by adding 4/5 hrs based DST.
Thanks,
Satya.

Similar Messages

Wrong value in message header on target system | "test" -- "production"

Hi all,
need some help with this.
When sending a message with RNIF Adapter to target system there's something wrong with the Message Header.
GlobalUsageCode has the value "test" but should say "production".
Any ideas where i can change that value on PI side ?
Cheers
Lars

may be u can change it in the mapping . it should be definitely possible using abap mapping

Performance header in message monitoring

Hello
I have scenario XI -> synch RFC Receiver.
In message monitoring I select response message and performance header part.
There are entries:
INBOUND, Request MAPPING, OUTBOUND, CALL ADAPTER, Response MAPIING
Does this time include RFC call through RFC Adapter?
Or it includes only IE processing like mapping.
What will include the time: <b>last time entry - first time entry</b>?
Whill it equal: request mappingRFC callresponse mapping?

Hi Denis,
the best way to monitor the performance
is the performance monitor tab in RWB
have you tried it?
you can monitor single interfaces and
also aggeregated
Regards,
michal

SXMB_MONI time difference in performance header

Hi,
I've noticed the time in the performance header trace in sxmb_moni is 5 hours later than the real time (System time).
Even the time sent is 5 hours later. Exp :
<SAP:TimeSent>2009-11-24T21:13:09Z</SAP:TimeSent>
When it was actualy sent at 16:13:09 ?
However , the start and end time in the alv list for sxmb_moni is correct.
I've seen the other thread on user preferences (timezone) but this is not it ... any ideas ?
Thanks Guys

Dear Thierry,
the reason for this difference in time is that the PerformanceHeader object needs to be filled with continous values. Discontinuities (for example, caused by daylight-saving time) might lead to tremendous deviations. Thus, timezone UTC is used to store performance data to that header object. Timezone UTC is also used for storing dates and time to the trace header object.
Best regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

Invoice created with wrong net values at header & item

Hi Guys
Due to a wrong user exit, system created few invoices with wrong net values at header & item.
Now system does not allow to cancel those billing documents, showing error message - inconsistency in data.
Eg: Billing Header net value is 10000
Billing Item net value is 5000
when I try to cancel this billing document, cancellation document created with header net value as 5000 & item net value also 5000. So, it says original invoice & cancellation invoice having different values. It is not possible to cancel.
Please suggest me how to correct wrong values at original invoice, which are already released to Accounting. Or else, how to cancel those kind of invoices.
Thanks in Advance
Regards
Uma

Hi,
In the original invoice and cancellation invoie is created there is a difference in 5000. It will not allow further cancellation of the invoice because it is already cancelled. I don't know whether there is anyway to reverse the cancellation invoice document.
If it is there then reverse the cancel invoice document and create an invoice correction request document (RK)
Try to replicate the scenario in your test system.
Prase

Mails in Mail have wrong Timestamp

Hello Communitiy
I had a problem with my Mail, the Mails weren't downloaded, so i decided to rebuild the Index with "Mailbox > Recovery". After the rebuild, 50% of my Mails had a wrong Received Timestamp (the Timestamp from 50% of the Mails where set to the Timestamp where the rebuilding Process finished).
I tried to recover my System from a TimeMachine Backup, but I had no lick. After opening Mail the first time, the rebuild/index process started, and again 50% of the Mails the Timestamp was set to the Timestamp after the Indexin-Process finished.
I found in the Logs following entry:
30.01.14 06:59:50.883 Mail[3607]: Unable to parse date: "So Okt 02 08:03:17 2011"
Stripped string: "So Okt 02 08:03:17 2011"
Can anyone help me?
Best Regards
Patrick

i'm having similar issue. huge amounts of my "archived" mail are now have a recent date incorrectly applied.
the problem is pretty easy to reproduce and demonstrate in mavericks.   for example, if you dig down into one of the mailbox folders until you find files containing individual message (.emlx files), you can preview them (with quick look - i.e., space bar in the finder).   this will generate a parse error viewable in console.   the preview of the message shows it has having no date.    inspection of the text file shows a date header like this: "Date: Thu Feb 13, 2003 5:22:20 PM US/Eastern", which to my eye appears to be out of spec wrt RFC 2822.
according to that spec, allowable time zone specs are of the form of the GMT offset expressed as a string consisting of a '+' or '-' followed by a four digit offset.    there is also legacy support for "obsolete" timezone specs of certain legacy timezone formats such as "EST", etc. but not a full string like "US/Eastern".   also the standard does not seem to allow 12-hour time format, nor a single-digit hour format. thus "5:22:20 PM" is not allowed and should instead be written as "17:22:20".
the mail in question may have originated on some other system.   it was likely originated on a non-mac system.   however, i know that the same files were handled correctly by earlier versions of mail.app (than my current version, 7.3).
i will probably try using a perl script or something to go through and re-write the dates to conforming values, then see if doing a "rebuild" would correct the problem.   shouldn't be necessary to do this, however.   within reason, i think no version of apple mail should ever fail to process an earlier version of apple mail's files.   apple should have plenty of data to use for regression testing this kind of stuff.    if they are going to break compatibility, then they should provide a translator or import utility or something rather than just leaving people hanging.
the irony is that when i encountered this bug, i was trying to bring in mail not from some old dusty osx box from 2001, but instead from 5-day old backups of my current/personal machine that i just lost, also running the latest versions of mavericks/mail.

ACE: wrong IP in HTTP header HEALTHCHECK packet

Hi,
I encounter a strange problem with ACE when the blade performs a HTTP healthcheck towards a RSERVER.
Sometimes, ACE insert in the HTTP header a strange IP address, others then the IP address of the rserver, for which it performs a healthcheck.
Anyone encountered the same problem?
Thx, Wim

Hi Gillis,
I reported this issue to our integrator. I think they will open a cisco case right now.
We are able to reproduce this problem. So, that might not be the problem to troubleshoot at this moment.
For your information, we had version A1.6 running until last week. Now, we upgraded to A2, but the healthcheck issue is still present.
I assume you 'll informed via the support case?

Does CAST ( date as timestamp) causes performance issues

Hi
does casting from DATE to TIMESTAMP in a query or in a view causes the slow down of performance??
Please guide...
Thanks
Rimpi

Everything you do affect performance. How significantly is a question answered by testing not by asking questions on an OTN forum.
Create a loop doing it 10,000 times and find out.
And, in the future, always include your version number.

PSE 10 Organizer on Mac shows wrong timestamps and changes timestamps

Just installed PSE 10 on my Mac (OSX 10.6.8) performed an update to the raw converter (though I am NOT using raw files)
All photos that I add to the catalog show a time stamp of 1hr before the photo was taken. If I check the actual metatdata it shows correct for most of the fields.
Exif data before adding to organizer: (using Exif Viewer 2.7.1)
Image Created:          2012:03:21 07:27:26
Image Generated:          2012:03:21 07:27:26
          Image Digitized:          2012:03:21 07:27:26
I drag it into Organizer and it shows as being 3/21/2012 6:27am
The exif data still shows properly in Exif Viewer.
Ok, I can deal with that, it is very odd, but since it isn't changing the exif data it is somewhat ok.
Until....
Now, I right click on the image and say open with Photoshop Elements Editor and immediately the time changes on the organizer screen to be one hour earlier from shown: 5:27am.
PSE Editor File info shows the Created and Modified times on the desciption tab as 7:27, but on the Camera Data tab shows 3/21/2012 – 6:27 AM (the time organizer showed before I said to open editor)
now Exif Viewer says:
Image Generated:          2012:03:21 06:27:26
          Image Digitized:          2012:03:21 07:27:26
close editor, and organizer is still saying the time is 5:27am
Close organizer, open again, still shows 5:27am, exif data still shows:
Image Generated:          2012:03:21 06:27:26
          Image Digitized:          2012:03:21 07:27:26
I can repeat the open in editor and it again subtracts an hour from the time shown, and from the Image Generated exif data field.
It appears that the organizer updates the timestamp when you say open in editor, and then sees that the timestamp changed and shows its 1hr subtracted time.
Definate bug! It happens with JPG files from 3 different cameras (2 canon, 1 nikon) does not appear to happen with MP4 files from Flip. but does happen with MOV files from at least 1 of the canon cameras.
Any ideas? I haven't found the place to report bugs for PSE10 yet.
-Mike

found a place to report the problem:
http://feedback.photoshop.com/photoshop_family/topics/pse_10_organizer_on_mac_shows_wrong_ timestamps_and_changes_timestamps
or: http://gsfn.us/t/2qfku
If you have the same problem, please go there and click that you also have the problem to increase their awareness of the issue.

Wrong Availability check for Header Item in Sales BOM after BOP

Hi Guys
I am stuck with a very weird problem. Request your advice:
I have a Sales BOM with one item Lets header is 'A' and Item 'B'. On creation of Sales Order ATP check is performed and both the line items (with A and B) the committed qty and committed date.
Now when BOP runs, it deletes the allocation of A and changes it to '0'
Details:
'A' is a non stockable product
Req:
1. I am not sure whether I should include A in BOP selection, however even running it only with B it deletes the allocation of A and the committed qty changes to '0'
Can you please suggest the solution or standard way of running BOP for Sales BOM
Thanks in advance
-Rahul

Thanks for writing in Prasun
Yes I created a new Filter type however when you add a STO category and then you change the fields to include item category you will get the same error. I am also in V 5.0 of SCM
Normally we use SAP_NetChange filter type. So is it possible to restrict using item category for this filter some how!
On the otherhand I also wonder these should not ATP relevant as the header item is non stockable item! And I guess there should some catch to exclude if not item category as you mentioned!
So the order categories included are:
Customer Inquiry
Customer quotation
Sales Order
SD Scheduling Agreement
SD Scheduling agreement w/external
Contract
Delivery w/io charge
Independent requriement
Release from customer in plant
STO
Deplyometn release
TLB release for purc ord
Fields
Product
location
distribution centrer
MRP area
product Hierarchy
Location hierarchy
supplier location
These are std filter type and I cant be modified.. however we restrict our filter to location only!
Kindly advice!
Thanks in advance
-RK

How to find quickly what's wrong with the performance of a BW Query?

Hi All,
After a long time, I had to work on performance tuning of a query, Version BI 7.0 EHP 1, SP7.
Compression in done, BI Stats are running, showing that OLAP time is high almost 70%, compared to 20% DB Read time.
Aggregates cannot be created due to the nature of the cube, BIA is out of scope.
How to find quickly, step by step, what's wrong with a particular query.
Thanks in advance,
Best Regards,
- Shashi

Hi Sashi ,
1. OLAP time is more, you need to increase OLAP cache, you have different options for the query in RSRT t-code..
Select properties which makes to store the query result set in OLAP Cache for permanent.
Doc for the same :
http://www.sdn.sap.com/44A46FE1-6DC0-4F2C-A8CB-A1BB45DF0186/FinalDownload/DownloadId-ED38793C4C172FE2AFFDE727E36B3991/44A46FE1-6DC0-4F2C-A8CB-A1BB45DF0186/irj/scn/go/portal/prtroot/docs/library/uuid/f048c590-31a4-2c10-8599-bd01fabb93d4?QuickLink=index&overridelayout=true
2.Use only less no of Characteristics in the initial report. Place remaining in Free characteristics.
3.You need to check the query .It cmod code exist for any variable or your query have lots of navigational attributes then try to check for code efficiency .
4.If Front End time more then try to avoid the more characteristics in displaying the query result.
5.Use authorization objects on queries if possible .That will reduce data amount .
6.Use query read mode and global structures as when possible.
Some helpful links :
http://www.tli-usa.com/download/Expert_Tips_and_New_Techniques_for_Optimizing_Data_Load_and_Query_Performance__Part_Two_.pdf
how to increase the performance
Aggregates in SAP BW
bw statistics
What is the use of cube partition?
Create indices before or after compression
Regards,
Jaya Tiwari

DSC 8.6.1 wrong timestamps for logged data with Intel dual core

Problem Description :
Our LV/DCS 8.6.1 application uses shared variables to log data to Citadel. It is running on many similar computers at many companies just fine, but on one particular Intel Dual Core computer, the data in the Citadel db has strange shifting timestamps. Changing bios to startup using single cpu fixes the problem. Could possibly set only certain NI process(es) to single-cpu instead (but which?). The old DSCEngine.exe in LV/DSC 7 had to be run single-cpu... hadn't these kind of issues been fixed by LV 8.6.1 yet?? What about LV 2009, anybody know?? Or is it a problem in the OS or hardware, below the NI line??
This seems similar to an old issue with time synch server problems for AMD processors (Knowledge Base Document ID 4BFBEIQA):
http://digital.ni.com/public.nsf/allkb/1EFFBED34FFE66C2862573D30073C329
Computer info:
- Dell desktop
- Win XP Pro sp3
- 2 G RAM
- 1.58 GHz Core 2 Duo
- LV/DSC 8.6.1 (Pro dev)
- DAQmx, standard instrument control device drivers, serial i/o
(Nothing else installed; OS and LV/DSC were re-installed to try to fix the problem, no luck)
Details:
A test logged data at 1 Hz, with these results: for 10-30 seconds or so, the timestamps were correct. Then, the timestamps were compressed/shifted, with multiple points each second. At perfectly regular 1-minute intervals, the timestamps would be correct again. This pattern repeats, and when the data is graphed, it looks like regular 1-sec interval points, then more dense points, then no points until the next minute (not ON the minute, e.g.12:35:00, but after a minute, e.g.12:35:24, 12:36:24, 12:37:24...). Occasionally (but rarely), restarting the PC would produce accurate timestamps for several minutes running, but then the pattern would reappear in the middle of logging, no changes made.
Test info:
- shared variable configured with logging enabled
- data changing by much more than the deadband
- new value written by Datasocket Write at a steady 1 Hz
- historic data retrieved by Read Traces
- Distributed System Manager shows correct and changing values continuously as they are written

Meg K. B. ,
It sounds like you are experiencing Time Stamp Counter (TSC) Drift as mentioned in the KB's for the AMD Multi-Core processors. However, according to this wikipedia article on TSC's, the Intel Core 2 Duo's "time-stamp counter increments at a constant rate.......Constant TSC behavior ensures that the duration of each clock tick is
uniform and supports the use of the TSC as a wall clock timer even if
the processor core changes frequency." This seems to suggest that it would be not be the case that you are seeing the issue mentioned in the KBs.
Can you provide the exact modle of the Core 2 Duo processor that you are using?
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Java converts wrong Timestamp

The following code return the same date.
          SimpleDateFormat formater = new SimpleDateFormat();
             formater.applyPattern("yyyy-MM-dd hh:mm");
             Timestamp ts = null;
             try {
               ts = new Timestamp (formater.parse("2006-10-10 12:00").getTime());
               System.out.println(ts);
               ts = new Timestamp (formater.parse("2006-10-10 00:00").getTime());
               System.out.println(ts);
          } catch (ParseException e) {
               e.printStackTrace();
          }If you see I have put different hour 12:00 and 00:00. I need both in the database. System.out prints:
2006-10-10 00:00:00.0
2006-10-10 00:00:00.0So, I have only 23 Hours a day, instead of 24.
What was my mistake?

Note the difference between h and H in the formatting characters.

Wrong timestamp on videos

Over the last few days, my wife's iMac C2D (currently with OS 10.4.10) started reading the time stamps on our camera's AVI videos wrong. When the import screen comes up, the time stamp on all the pictures are correct, but the time stamp for the videos are about 7 hours ahead (and they all show the same wrong time). Interestingly, Image Capture shows the same erroneous times (so it does not appear to be an iPhoto-specific issue). Creating a new iPhoto album and creating a new user account does not fix the problem (so it does not appear to be a preference issue).
However, my MacBook reads the time stamps correctly (so it does not appear to be a camera/SD card issue). Also, the Finder reads the time of the video file correctly as well.
Given the pattern above, I suspect that there is some resource that OS X uses to read video metadata, and it must be corrupted. I have no idea what that resource might be or how to fix it.
Any suggestions? Thanks!

Usually this is caused by a custom setting of the time date format - in your time preferences set your time display to the default standard display and see if that clears the problem - if it does you can play with getting back to the custom one and see
LN

Received Mail has wrong timestamp

This has been discussed before (and archived), but it hasn't been resolved.
I am using MacMail (I don't have a .Mac account), POP3 incoming, SMTP outgoing.
I just switched from 10.3.9 to 10.4.4, and the timestamp on all my incoming mail is now displaying incorrectly. It is displaying in GMT, not my time zone (Central).
I opened Long Headers and can see that the timestamp on the message is given in GMT. However, I don't think it's my server's responsibility to translate that to the correct time zone - that's the responsibility of my computer's OS, since the OS knows what time zone I am using. (My server doesn't.)
Thus, this isn't a server problem, it's an OS problem. If someone official answers this, please tell me what the fix is for Tiger.
Thanks,
David

David, Apple, and others,
I have the same situation, and I've duplicated it using several Macs. Apple changed how Tiger's Mail 2.x displays the received time (compared to how Panther's Mail 1.x did). Apple needs to revert to how Mail 1.x adjusted the received time to your time zone.
Apple says that received time is when the mail server received the message. Great. That's no excuse not to convert the time to the time zone that your computer uses.
Until someone fixes it, you can change your view to display date/time sent, and not the received value. Or you can use a different email client.
Pat

Wrong Timestamp in Performance Header

Similar Messages

Maybe you are looking for