Timestamp in FI

Hi Friends,
I read this document on FI
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a?QuickLink=index&overridelayout=true
But could not get a clear idea of Timestamp and FI GL extraction.
Can anyone explain me how these FI extractors are enhanced and the delta mechanism in FI.
Help is appreciated,
Regards,
Sahasra

The link below are giving the different features of new FI datasources. And enhancement is easy if that filed is available in FAGLFLEXA/T table.
http://help.sap.com/saphelp_nw04s/helpdata/en/e6/f16940c3c7bf49e10000000a1550b0/frameset.htm
On right side open up the datasource section and there you will find 5 different datasources mentioned earlier.
GO thru it. FI is very vast area, one can not make general comment. Its depends upon you requirement which one you are going to use.
First ask you ECC team are they using FAGLFLEXA, FAGLFLEXT table functionality given by SAP ECC, then only these datasources are useful.
As I told earlier, this is new features given by SAP.
Regards,
Vinod

Similar Messages

  • Each time I try to synch photos from my Windows 7 PC to my iPad2, iTunes stops working, and the error report says Problem Event Name:     APPCRASH   Application Name:     iTunes.exe   Application Version:     10.3.1.55   Application Timestamp:     4deec35

    Each time I try to synch photos from my Windows7 PC to my iPad2, iTunes stops working and the error message is:
    Problem Event Name:                          APPCRASH
      Application Name:                             iTunes.exe
      Application Version:                           10.3.1.55
      Application Timestamp:                    4deec351
      Fault Module Name:                          ntdll.dll
      Fault Module Version:                        6.1.7601.17514
      Fault Module Timestamp:                 4ce7ba58
      Exception Code:                                  c0000005
      Exception Offset:                                0002e3fb
      OS Version:                                          6.1.7601.2.1.0.768.3
      Locale ID:                                             1033
      Additional Information 1:                  0a9e
      Additional Information 2:                  0a9e372d3b4ad19135b953a78882e789
      Additional Information 3:                  0a9e
      Additional Information 4:                  0a9e372d3b4ad19135b953a78882e789
    I reloaded iTunes 10 (64 bit) successfully, but the problem remains the same.
    Any suggestions?

    I looked in the folder from which I want to synch photos, but there is no such thing as an "ipod photo cache" in that folder, or sub-folders, as suggested in the link which you were nice enough to provide.
    I have also tried removing photos from my iPad2 Photos App, and "iTunes has stopped working" shows up  again as soon as I click on the "Synch photos from" button.

  • Changing of the timestamp in sender file adapter in archive mode

    Hi,
    I have a requirement where in I have to archive a file with timestamp different from that generated by XI.
    Please let me know if this can be done and if so how can we handle the changes to be made to the timestamp in the sender adapter in archive mode.
    regards,
    Srinivas.

    Srinivas,
    Option 1) Create a bat file..to run the perl script you call..
    Perl script..
    #!/usr/bin/perl -w
    print("Starter that you want to change: ");
    chomp($badex = <STDIN>);
    print("Starter that you want added: ");
    chomp($goodex = <STDIN>);
    foreach $file (<$badex*>){
        @fields = split(/$badex/,$file);
        $goodfile = ("$goodex" . "$fields[1]");
        rename("$file","$goodfile");
    Run that on the os
    That should fix it.........
    Option 2) On your local Machine create a java file..add this code to it
    public class Utils
         public static int Randomizer(){
              int randomInt = 0;
              randomInt = (int) (Math.random()*1000);
              return randomInt;
    public static void main(String[] args)
         Randomizer();
    save and compile..
    Create a bat file to add the number returned from the random to your targetFilename
    so it would be something like..
    mv oldFileName Newfilename+randomizer... and also get this command written to a file..helpful later on.........
    Hope that helps
    Regards
    Ravi Raman
    PS:Dont forget the points if helpful

  • Adding Hours To Timestamp Values In A Materialized View

    Is it possible to add x hours to a TIMESTAMP column in a materialized view?
    (I'm using Oracle 10g.)

    In what context?
    DOM@DOM11gR1>CREATE MATERIALIZED VIEW mv1
      2  AS
      3  SELECT SYSTIMESTAMP ts1,SYSTIMESTAMP + 6/24 ts2, SYSTIMESTAMP + INTERVAL '6' HOUR ts3
      4  FROM DUAL;
    Materialized view created.
    DOM@DOM11gR1>desc mv1
    Name                                                              Null?    Type
    TS1                                                                        TIMESTAMP(6) WITH TIME ZONE
    TS2                                                                        DATE
    TS3                                                                        TIMESTAMP(9) WITH TIME ZONE
    DOM@DOM11gR1>select ts1, to_char(ts2,'DD/MM/YYYY HH24:MI:SS') ts2, ts3 from mv1
      2  /
    TS1                                      TS2                 TS3
    15-SEP-09 17.50.44.681271 +01:00         15/09/2009 23:50:44 15-SEP-09 23.50.44.681271000 +01:00
    DOM@DOM11gR1>

  • A Security Weakness When Signing without a Timestamp

    Hi Guys,
    I am exploring the need of timestamping PDF documents using Adobe Acrobat wrt security. I see a lot of signatures made without timestamps and I see an issue here mentioned below. If my assumption is valid then Ideally Adobe Acrobat should strongly mandate to use timestamps with revocation information.
    The scenario:
    A user uses a high trust credential to legitimately sign PDF documents but chooses not to use a Timestamp to avoid costs.  These documents have an embedded signature plus the signer’s certificate chain CRLs and/or OCSP responses (but no trusted timestamp).
    At a point in time (let’s say 1 June 2012) the credential and PIN is stolen.   If the theft is before the end of validity period the credential is of course revoked. However if the theft is of an expired credential it can’t be revoked and most people would not notice and perhaps would not even care.  Let us further assume the thief gains access to a number of old signed documents.  Of course in theory this is not a problem, because these documents are signed and therefore protected and can’t be changed. However the thief now has access to a range of valid CRLs and/or OCSP responses that were properly valid from before the theft and can use them to their advantage.  These documents may even be widely published or perhaps received anyway by an insider thief.
    The thief can use the stolen credential and can sign a document at any date/time of their choosing up to 1 June 2012 (by varying their local system date/time) to one that lies within the validity period of any previous OCSP/ CRL data they have captured. Even though the signature covers the validation data this is all done at what seems like a legitimate time. 
    Trust Threat Analysis:
    A stolen credential and PIN can easily be used at a local desktop time (set to anything you like).  With PDF editing software – no problem for a hacker of course – you can embed a CRL that shows the stolen credential as good during any period up to the revocation or expiry.  The hacker just needs to select a signing date/time that is within a CRL validity period for one of the CRLs they have access to.  The selected CRL is then re-used as part of the signing process on a fraudulent document.
    It is now up to the receiving software to make the right trust decision – and a trusted timestamp should always be used to make a trustworthy historic decision.  If there is no embedded trusted timestamp the receiver software could decide to verify the signature at (a) the current time or (b) the (untrusted) time indicated by the signer.  Any software that uses option (b) and trusts the (untrusted) time in the signature rather than defaulting to current time creates a substantial trust issue.  The whole purpose of using and attaching a valid, trusted signature time stamp is to independently confirm the accurate date/time of (potentially untrusted) third party signing events.  The timestamp cannot be re-used since it covers the signature details.  Any substantial variance in time between the signer’s time and the timestamp time is peculiar but systems should always default to trusting the signature timestamp date/time.
    Ideally PDF signing software used by a signer that fails to obtain a timestamp should not allow the document to be signed.  If the policy is to sign with a long-term signature then the timestamp must be present to confirm the time.  Some software products create confusion by allowing the timestamp to be missed if it cannot be obtained.  This means that a document that should have a life of several months or years should actually be seen to have an issue immediately after certificate revocation or expiry (could be in a few days or months).  Using such software, users will not be aware of the issue until the problem has manifested itself.
    Any Comments?
    Regards,
    Wahaj

    The settings for the warning messages have been removed from the user interface (Bug 513166).
    You need to change the related security.warn_* prefs directly on the <b>about:config</b> page.<br />
    Filter: security.warn
    To open the <i>about:config</i> page, type <b>about:config</b> in the location (address) bar and press the "<i>Enter</i>" key, just like you type the url of a website to open a website.<br />
    If you see a warning then you can confirm that you want to access that page.<br />
    *Use the Filter bar at to top of the about:config page to locate a preference more easily.
    *Preferences that have been modified show as bold(user set).
    *Preferences can be reset to the default or changed via the right-click context menu.

  • URGENT HELP NEEDED FOR TimeStamp

    Urgent Millisecond Question....
    I have the Java Code which used to work well in Oracle 8 and Sybase ..
    When I am using it with Oracle 9.2 it creating a problem...
    The code is
    final public JDatetime getJDatetime(int columnIndex) throws SQLException {
         boolean convertb = Util.needConvertTime();
         Timestamp ts=_rs.getTimestamp(columnIndex);
         if(ts==null) return null;
         Date d= new Date(ts.getTime() + (ts.getNanos()/1000000));
         if(convertb) d = Util.ReferenceTZ2Local(d);
         return new JDatetime(d);
    Now in Oracle 8 Say when I insert a
    JDateTime Value as 2003-06-18 16:51:06.89
    and
    When I retrieve is using above getJDatetime
    it get retrieved as
    2003-06-18 16:51:06.0
    Which is ok since Milliseconds are lost....
    Now in Oracle 9
    When I use the convert
    Date d= new Date(ts.getTime() + (ts.getNanos()/1000000));
    It get converted to
    Original Value While Inserting -->TimeStamp in JResultSet->2003-06-18 18:15:56.42
    Date in JResultSet-->Wed Jun 18 18:15:56 GMT 2003
    Date in JResultSet after converting to ReferenceTZ
    Wed Jun 18 18:15:56 GMT 2003
    DateTime in JResultSet after converting to DateTime6/18/03 6:15:56.840 PM
    GMTGETDatetime 6/18/03 6:15:56.840 PM GMT
    so if you see
    Milliseconnd 42 got converted to 840 NanoSeconds
    WHICH IS WRONG
    Can anybody help me with it ??
    Mahesh

    The only Adobe program I know that can edit images is Photoshop.
    If you have troubles with Google software, you need to post in the appropriate Google forum.

  • Loops and system timestamp not synchronized

    Running Labview 8.6.1 on Windows 2000, loops and system timestamp (Windows clock) seem to use different time bases; one second in a loop is not exactly as long as a second in system time. If i run a simple VI as in picture, with a 1-second loop which just prints the system time, the printed timestamp goes faster by about 1ms every 4-5 seconds. The same happens using a Timed loop or a While with a Wait until next ms multiple.
    Why is that? Can i set a loop to match the system time?
    Attachments:
    1sec.png ‏3 KB

    johnsold wrote:
    In the eastern U. S. interconnected power grid the accumulated time is held to within a small fraction of a second when averaged over days.  Over a year the accumulated error is less than parts in 10^12 or better.  The instantaneous frequency can deviate from the nominal 60 Hz by less than 0.1 Hz.
    The system basically uses an integral controller referenced to a NIST atomic clock to force the steady state error to zero.
    Lynn 
    So is that a very technical way of saying "Ben, you are full of Sh#% !"*
    I have not measured the frquency of my AC service in the last three decades or so. I do remember seeing it faster in the summer and slower in the winter. Has it really changed? Silly me thinking that the wide freq input spec I read on wall-warts was there just to handle this variation of freq.
    And to think it has gotten smarter "without a brain".
    Ben
    * I am just trying to catch up what I seem to have missed. The above is all in good humor. No offense intended or taken.
    Message Edited by Ben on 08-03-2009 12:56 PM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Get millisecond values from timestamp column in v$logmnr_contents

    Hello
    How do we get millisecond values from timestamp column in v$logmnr_contents.
    I tried with following query.
    select scn,To_Char(timestamp,'DD-MON-YYYY HH24:MI:SS:FF') from v$logmnr_contents WHERE OPERATION NOT IN('START') and username ='SCOTT' and sql_redo is not null and (seg_owner is null or seg_owner not in('SYS'));
    it says ORA-01821: date format not recognized. I want to find the relation of scn with timestamp. In forums i found, scn is derived from timestamp value. I dont know its correct or not.
    if i query with out FF in time format i get like
    scn timestamp
    808743 27-NOV-2007 00:12:53
    808743 27-NOV-2007 00:12:53
    808743 27-NOV-2007 00:12:53
    808744 27-NOV-2007 00:12:53
    808744 27-NOV-2007 00:12:53
    808744 27-NOV-2007 00:12:53
    if scn is derived from timestamp with milliseconds, each scn should be different right?More help please

    May be there's an easy way solving your problem, I did it like that:
    CREATE TABLE quota_test (test VARCHAR2(50))
    INSERT INTO quota_test
    VALUES ('update "SCOTT"."NEWTAB1" set a="34" and b="45"')
    SELECT test normal, REPLACE(SUBSTR(test,INSTR(test,'"',1),INSTR(test,'.',1)+2),'"','') changed
    FROM quota_test
    Result is :
    NORMAL
    update "SCOTT"."NEWTAB1" set a="34" and b="45"      
    CHANGED
    SCOTT.NEWTAB1
    If you didn't understand, I can explain what I wrote

  • File when copied , is having the current timestamp instead of original time

    Hello,
    I am copying a file file-1(x-date) from server-A to Server-B. when the file-1 is copied to server-b, the size and everything remains fine but the timestamp changes to current timestamp.(Y-DATE)
    my issue : I want to the file when copied to have original time-stamp(X-DATE)
    any idea why this is happening ???
    Thanks

    BigDaddyLoveHandles wrote:
    Skotty wrote:
    You might not think that you could set the last modified date manaully, but alas, you can:
    [http://java.sun.com/j2se/1.4.2/docs/api/java/io/File.html#setLastModified(long)]
    Oh lackaday! Why "alas"?It's suuuuuch a hassle!

  • Problem with timestamp in query

    I have problem with timestamp in JPA query.
    I wonna select all data from database where difference between two timestamps is more than 3 month.
    Database:
    ID timestamp1 timestamp2
    1 20008-11-19 15:02000 20008-08-19 15:02000
    2 20008-11-19 15:02000 20008-11-14 15:02000
    @Column(name = "timestamp1", nullable = false)
    @Temporal(TemporalType.TIMESTAMP)
    public Date timestamp1;
    @Column(name = "timestamp2", nullable = false)
    @Temporal(TemporalType.TIMESTAMP)
    public Date timestamp2;
    sql query works:
    select id from table where
    MONTH( DATE(timestamp1) - DATE(timestamp2) ) > 3
    but how I can write in Java?
    I't doesnt wrk:
    Query query = em.createQuery("SELECT f.id FROM Foo f WHERE MONTH( DATE(f.timestamp1) - DATE(f.timestamp2) ) > 3 ")
    error:
    ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method .
    Exception data: <openjpa-1.0.2-r420667:627158 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: An error occurred while parsing the query filter 'SELECT f.id FROM Foo f WHERE MONTH( DATE(f.timestamp1) - DATE(f.timestamp2) ) > 3'.
    Error message: <openjpa-1.0.2-r420667:627158 nonfatal user error> org.apache.openjpa.kernel.jpql.ParseException: Encountered "MONTH (" at character 438, but expected: ["(", "+", "-", ".", ":", "", "=", "?", "ABS", "ALL", "AND", "ANY", "AS", "ASC", "AVG", "BETWEEN", "BOTH", "BY", "CONCAT", "COUNT", "CURRENT_DATE", "CURRENT_TIME", "CURRENT_TIMESTAMP", "DELETE", "DESC", "DISTINCT", "EMPTY", "ESCAPE", "EXISTS", "FETCH", "FROM", "GROUP", "HAVING", "IN", "INNER", "IS", "JOIN", "LEADING", "LEFT", "LENGTH", "LIKE", "LOCATE", "LOWER", "MAX", "MEMBER", "MIN", "MOD", "NEW", "NOT", "NULL", "OBJECT", "OF", "OR", "ORDER", "OUTER", "SELECT", "SET", "SIZE", "SOME", "SQRT", "SUBSTRING", "SUM", "TRAILING", "TRIM", "UPDATE", "UPPER", "WHERE", <BOOLEAN_LITERAL>, <DECIMAL_LITERAL>, <IDENTIFIER>, <INTEGER_LITERAL>, <STRING_LITERAL>].
    at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.parse(JPQLExpressionBuilder.java:1665)
    at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.<init>(JPQLExpressionBuilder.java:1645)

    The error is indocating improper formatting of your JPQL string. MONTH is not understood. I would recommend using your SQL string in a createNativeQuery(...) call instead.
    Doug

  • FMS 3.5 says 'Bad network data': error in handling RTMP extended timestamps / chunkSize?

    Hello all,
    For a client, I am working on a project where a live RTMP stream is published to an Adobe FMS 3.5.6 server from a java application, using Red5 0.9.1 RTMPClient code.
    This works fine, until the timestamp becomes higher than 0xFFFFFF after 4.6 hours, and the RTMP extended timestamp field starts being used. I have already found: when the extended timestamp was written after the header, the last 4 bytes of the data were being cut off. I have fixed this locally, and now the data being sent seems to me to be conformant to the spec. However, FMS still throws an error message in the core log and then kills the connection from the Red5 client. Here is the error message:
    This is the error message:
    2011-06-03     14:28:02     13060     (e)2611029     Bad network data; terminating connection : chunkstream error:message length 11893407 is longerthan max rtmp packet length     -
    2011-06-03     14:28:02     13060     (e)2631029     Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: _defaultVHost_, IP: 127.0.0.1, App: live/_definst_, Protocol: rtmp, Client: 5290168480216205379, Handle: 2147942405) : 05 FF FF FF 00 13 = 09 01 00 00 00 01 00 01 01 ' 01 00 00 00 00 00 13 4 09 0 00 00 01 ! 9A & L 0F FA F6 12 , B4 A6 CE H 8A AB DC G BB d k 1B 9F ) 13 13 D2 9A E5 t 8 B8 8D 94 ! 8A AE F6 AF } " U 0 D3 Q EF FF ~ 8D 97 D9 FF BE A3 F3 C9 97 o 9D # F9 7F h A4 F7 } / FB & F1 DC 9C BF   BD D3 E7 CA 97 FE E2 B9 E4 F7 9E 1A F6 BA } C9 w FC _ / / w FE n EF D7 P 9C F4 BE 82 8E F7 | BE 97 B4 BB D7 FE ED I / FB D1 93 9A F9 X \ 85 BD DD I E3 4 E8 M 13 D3 " ) BE A9 92 E5 83 D4 B4 12 DE D5 A3 E6 F4 k DE BF Q 3 A0 g r A4 f D9 BD w * } F7 r 8A S 2 . AB BD EE ^ l f AF E1 0B $ AF 9D D7 - BF E8 ! D3 } D3 i E3 B8 F2 M A8 " B1 A5 EF s ] A5 BC 96 E5 u e X q D2 F1 r F9 i 92 b EE Z d F9 * A6 BB FD 17 w 4 DD 3 o u EB ] ] EF FE B5 B1 0A F2 A0 DD FD B2 98 DF E8 e F6 CB FD 96 V % A5 D5 k ] FD w EF AF k v AA E8 ! 9F / w BE FA 9A _ E F2 D3 , ? 17 } AD 7 EC B3   } 07 B5 | z { { A5 = 11 90 CF BF ; 4 FE EF 95 F7 E7 DF B9 , AF z 91 CF C9 BD DE CB { F5 17 } F2 E5 D7 DF z E6 [ 96 > Y m 9F EB AF DD D8 E8 v B9 A8 E9 % A7 | 1 CF 8B D Z k N DF F8 N FA S R FE . ~ CB A 9 E1 ) 8F 8E BB EC c 6 13 F1 AC FD FD FC 8A F7 F3 K B9 FA ^ / A4 FC B9 AA F6 DE C2 [ 1A E c r B3 BF E5 EC B5 x 94 FD . A9 t I Q % EA EC DE | K FE z A4 97 F9 " 1 0F CA FB F5 F5 p 9E 99 3 - ; B8 F4 F1 FF t A3 EC BC # DE AC 91 13 19 o < 06 F5 FD 7F 7 _ $ D B t B5 0D 8A C1 C1 BA 0B FE DB B7 83 _ } BD z F7 CB { FC M A9 8D = D5 B1 < 85 = EF E1 ; BA H y FC BC B4 C A2 D9 ` e E4 94 H 5 13 ' 93 93 8E E C2 1C R 97 9 X B7 FF 10 9F { ) F1 CF AB AC ] EE H A2 DE D3 C5 m F6 K A2 A7 A2 89 D2 z EB DF 97 ^ k 9E 99 BB E7 B6 97 w { ~ + C7 B2 } FE ' C4 | B6 o H DD r A8 9F DC FF F9 Q b l 93 T B6 EE FF 11 j CD s P C F1 3 R I F8 D8 R 9D 93 AA D5 + DE FC BE " B9 E1 ` CB BD 0F F5 C7 AA w CF 8D p 9A F7 g f N FF 84 B7 K Q 93 g E1 - D3 s } w v AE 96 98 ED CF BA E9 2 . f 99 95 97 o 13 CA F7 s e $ F4 B5 15 C4 A8 DE M F7 w \ 8D 00 C6 C2 b D3 / 7 w F2 ' BF CD 89 FF > D7 FB BC A2 S N FB A5 CD AF D3 F9 9D DF AE B5 17 CF 9D B7 , B9 9 ^ 7F [ 93 84 F7 } _ EA DF u \ 99 Z t E CA M EF 7 " AD FE 92 9E n 7F EB D8 C { 99 8B 9E w H BF B1 | g 9F F3 FA E1 - E5 CB BB x CF p 8B D2 w v EF w FA E2 F7 s C5 AC $ FC B4 DB BE G E4 DC F0 A0 96 F3 ! t DC FF % A5 CB A4 ^ AB D2 BD E7 9A E ' 08 + AF U 17 EB 8A w A7 N E4 A5 x 93 12 _ - ; 09 DD DF m 11 BE w \ } BA D3 t BC D9 97 9B C5 7F D8 H F1 D 7 8A ^ FA n F0 B8 W E6 84 5 - 8 B5 h o C4 F7 83 P 88 CB AE m t BB L 95 A9 s 90 A2 Y o DF K _ / l D2 D1 C9 91 ' E4 BD / / D 97 m BB E7 14 93 % C5 ; DD CF D8 : ~ B5 4 F FA U F0 8F w w DC FD 83 FC 13 EF w p DA A5 07 _ * - 1D 14 9D D5 84 F E6 F0 FF E4 15 w n A5 9F DE d AE F5 " - f D2 AE 96 1F # FA F1 x C1 L DF l M 06 8A E4 z DB 17 BA l DA e 15 CD 85 86 1F 09 82 h ] C6 { E7 C5 AF Z C5 B0 83 v D9 03 FC / ~      -
    The message for which the hex dump is displayed, is a video message of size 4925 bytes. Below is the basic logging in my application:
    *** Event sent to RTMP connector: Video - ts: 16777473 length: 4925. Waiting time: -57937, event timestamp: 16777473
    14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.s.consumer.ConnectionConsumer - Message timestamp: 16777473
    14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Channel id: 5
    14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Last ping time for connection: -1
    14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Client buffer duration: 0
    14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Packet timestamp: 16777473; tardiness: -30892; now: 1307104082045; message clock time: 1307104051152, dropLiveFuturefalse
    14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!12b Wrote expanded timestamp field
    14:28:02.046 [NioProcessor-22] DEBUG o.r.server.net.rtmp.BaseRTMPHandler - Message sent
    I have captured the entire frame containing this message with wireshark, and annotated it a bit. You can find it here:
    http://pastebin.com/iVtphPgU
    The video message of 4925 bytes (hex 00 13 3D) is cut up into chunks of 1024 bytes (chunkSize 1024 set by Red5 client and sent to FMS). Indeed, after the 12-byte header and the 4-byte extended timestamp, there are 1024 bytes before the 1-byte header for the next chunk (hex C5). The chunks after that also contain 1024 bytes after the chunk header. This appears correct to me (though please correct me if I'm wrong).
    When we look at the error message in the core log, the hex dump displayed also contains 1024 bytes, but it starts from the beginning of the message header. The last 16 bytes of the message chunk itself are not shown.
    My question is this: is the hex dump in the error message always capped to 1024 bytes, or did FMS really read too little data?
    Something that may be of help, is the reported 'too long' message length 11893407. This corresponds to hex B5 7A 9F, which can also be found in the packet, namely at row 0c60 (I've annotated it as [b5 7a 9f]. This location is exactly 16 bytes after the start of the 4th chunk data, not really a place to look for timestamps.
    My assumptions during this bug hunting session were the following (would be nice if someone could validate these for me):
    - message length, as specified in the RTMP 12 and 8-bit headers, defines the total number of data bytes for the message, NOT including the header of the first message chunk, its extended timestamp field, or the 1-byte headers for subsequent chunks. The behaviour is the same whether or not the message has an extended timestamp.
    - chunk size, as set by the chunkSize message, defines the total number of data bytes for the chunk, not incuding the header or extended timestamp field. The behaviour is the same whether or not the message has an extended timestamp.
    I believe I've chased this problem as far as I can without having access to the FMS 3.5 code, or at least being able to crank up the debug logging to the per-message level. I realize it's a pretty detailed issue and a long shot, but being able to publish a stream continuously 24/7 is critical for the project.
    I would be very grateful if someone could have a look at this hex dump to see if the message itself is correct, and if so, to have a look at how FMS3.5.6 handles this.
    Don't hesitate to ask me for more info if it can help.
    Thanks in advance
    Davy Herben
    Solidity

    Hello,
    It took a bit longer than expected, but I have managed to create a minimal test application that will reproduce the error condition on all machines I've tested on. The application will simply read an H264 file and publish it to an FMS as a live stream. To hit the error condition faster, without having to wait 4.6 hours, the application will add a fixed offset to all timestamps before sending it to the FMS.
    I have created two files:
    http://www.solidity.be/publishtest.jar : Runnable java archive with all libraries built in
    http://www.solidity.be/publishtest.zip : Zip file containing sources and libraries
    You can run the jar as follows:
    java -jar publishtest.jar <inputFile> <server> <port> <application> <stream> <timestampOffset>
    - inputFile: path to an H264 input video file
    - server: hostname or IP of FMS server to publish to
    - port: port number to publish to (1935)
    - application: application to publish to (live)
    - stream: stream to publish to (output)
    - timestampOffset: nr of milliseconds to add to the timestamp of each event, in hexadecimal format. Putting FFFFFF here will cause the server to reject the connection immediately, while FFFF00 or FFF000 will allow the publishing to run for awhile before the FMS kills it
    Example of a complete command line:
    java -jar publishtest.jar /home/myuser/Desktop/movie.mp4 localhost 1935 live output FFF000
    Good luck with the bug hunting. Let me know if there is anything I can help you with.
    Kind regards,
    Davy Herben

  • Pick up Files based on Timestamp???.

    HI All,
    Is it possible to pick up the files in the order of which they are put in a shared folder ?.
    Our client system will put the xml files in a shared folder with timestamps..PI will pick these files one by one..but if the PI server is down.. the files will keep coming in the shared folder from the client system..and when PI come back up they need to be picked in the order in which they have been put according to timestamp.
    I'am using the NFS functionality.
    I dont want to output files from PI based on timestamp added.. I want to pick files up based upon sender timestamp.
    Is this funcationality supported in PI?.
    Thanks.

    HI
    You can write script to do this. Script can copy files based on time stamp from the folder where client system is putting the file to the folder PI is poling based on timestamp.
    With this as Ratan said. If the file creation date for file system is in date and time format(timestamp) File processing sequence by Date can help. It process file starting from oldest file.
    Thanks
    Gaurav

  • How to get the last received notification timestamp when app in background

    Hi All,
    We are developing the app in windows phone Silverlight 8.1.
    We need to show the last received notification time stamp even when the app is in background.
    When the app in foreground, I can get the timestamp.
    Since we cant write the background task for the Silverlight phone 8.1 app, I don't know how to get the time stamp of the last
    notification(toast/livetile/badge) in the app for display.
    Can anyone help on this.
    Thanks,
    Meena

    Yes, continuous background execution is not supported but you can use background tasks. 
    (Continuous background execution in this context refers to the special run state permitted for GPS Navigation apps.)
    For information regarding Background Tasks see: Supporting your app with background tasks -
    http://msdn.microsoft.com/library/windows/apps/hh977046.aspx
    Additional information is available in these topics:
    Guidelines for background tasks
    PushNotificationTrigger
    How to receive raw notifications
    Eric Fleck, Windows Store and Windows Phone Developer Support. If you would like to provide feedback or suggestions for future improvements to the Windows Phone SDK please go to http://wpdev.uservoice.com/ where you can post your suggestions and/or cast
    your votes for existing suggestions.

  • Timestamp Field in ALV Grid

    Hi
    I have a field for timestamp (CHAR 14) in an editable ALV.The Conversion Exit i have used is TSTPS. If I enter a non-numeric character into that field , it gets cleared but no error is generated.However , I want to display an error if the user attempts to do so or do not allow the user to enter those characters at all.
    Thanks
    Shilpa

    Hi
    I have a field for timestamp (CHAR 14) in an editable ALV.The Conversion Exit i have used is TSTPS. If I enter a non-numeric character into that field , it gets cleared but no error is generated.However , I want to display an error if the user attempts to do so or do not allow the user to enter those characters at all.
    Thanks
    Shilpa

  • 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

  • Schedule line timestamp different from Order Create-Date/timestamp

    Scenario: Created an order at 3:30pm CST with the requested delivery date of the material as 7/10/2011. It seems like that when the order is saved, CRM attaches the time-stamp to the requested delivery date. However, the timestamp getting attached to the delivery date is 1 hour less than the order-create time, i.e. delivery-date looks like 7/10/2011  2:30pm CST.
    Please advise what could be causing this and its resolution. FYI, user-profile (or the user creating the order) has the same time-zone setting of CST.
    Thanks!

    Scenario: Created an order at 3:30pm CST with the requested delivery date of the material as 7/10/2011. It seems like that when the order is saved, CRM attaches the time-stamp to the requested delivery date. However, the timestamp getting attached to the delivery date is 1 hour less than the order-create time, i.e. delivery-date looks like 7/10/2011  2:30pm CST.
    Please advise what could be causing this and its resolution. FYI, user-profile (or the user creating the order) has the same time-zone setting of CST.
    Thanks!

Maybe you are looking for