Incorrect dates in Elements 9

I am running this in 64 bit Windows 7. When photos are imported the date is often wrongly set and the year is out by 1 year. For example, Windows explorer reads the tag information correctly (year=2007) but elements is 1 year out. See below:

Thanks for the reply. Under "Camera Data" both "Date Time" and "Date Time Digitised" are incorrect. However, this is not true of all files.
Dr Chris Wooff mailto:[email protected]
Deputy Director,
Computing Services Department,
University of Liverpool.

Similar Messages

  • Incorrect data in ODS

    Hi All,
    we are loading data  from one ODS to another with delta processes.The second ODS got some incorrect data Populated.After that I did a full repair load selectively for one record only from first ODS to another and it went fine.But when I am loading by full repair load the records for entire company code,one particular key figure is getting doubled for most of the records.I've checked there is no problem with the start routine.
    Please  let me know if I am missing anything in full repair load.
    Thanks in advance.

    Hi,
    In sequence to this post,now i am getting a differnt and strange error.
    the data gets loaded from ODS1(0FIA_DS11) to ODS2(0FIA_DS12).
    But for some asset main nos the CACQ_VL_YR and TACQ_VL_YR does not get populated.
    WE have a start routine in between.The start routine poplualtes the CACQ_VL_YR .TACQ_VL_YR is polulated with ACQ_VAL_TR.
    the routine is as follows:
    DATA: lt_trans LIKE table of DATA_PACKAGE,
             wa_trans LIKE LINE OF lt_trans.
      LOOP AT DATA_PACKAGE.
        CLEAR wa_trans.
    Nicht-Werfelder 1:1 übernehmen
        MOVE: DATA_PACKAGE-currency   TO wa_trans-currency ,
              DATA_PACKAGE-comp_code  TO wa_trans-comp_code ,
              DATA_PACKAGE-/BIC/ZASS_MAIN TO wa_trans-/BIC/ZASS_MAIN ,
              DATA_PACKAGE-/BIC/Zdep_area TO wa_trans-/BIC/Zdep_area ,
              DATA_PACKAGE-fiscyear   TO wa_trans-fiscyear,
              DATA_PACKAGE-fiscvarnt  TO wa_trans-fiscvarnt.
    Wertfelder mit identischer Übertragungslogik bei PLN und ***
        MOVE:
        DATA_PACKAGE-vaw_odp_tr TO wa_trans-vaw_odp_tr,
        DATA_PACKAGE-vaw_sdp_tr TO wa_trans-vaw_sdp_tr,
        DATA_PACKAGE-vaw_udp_tr TO wa_trans-vaw_udp_tr,
        DATA_PACKAGE-vaw_avr_tr TO wa_trans-vaw_avr_tr,
        DATA_PACKAGE-va_rapc_tr TO wa_trans-va_rapc_tr,
        DATA_PACKAGE-va_rodp_tr TO wa_trans-va_rodp_tr,
        DATA_PACKAGE-va_invs_tr TO wa_trans-va_invs_tr.
        CASE DATA_PACKAGE-transtype.
          WHEN '***'.
        Wertfelder kumuliert
            MOVE:
            DATA_PACKAGE-acq_val_tr TO wa_trans-cacq_vl_yr,
            DATA_PACKAGE-inv_sup_tr TO wa_trans-cinv_gr_yr,
            DATA_PACKAGE-ord_dep_tr TO wa_trans-cor_dep_yr,
            DATA_PACKAGE-spc_dep_tr TO wa_trans-csp_dep_yr,
            DATA_PACKAGE-upl_dep_tr TO wa_trans-cup_dep_yr,
            DATA_PACKAGE-res_trf_tr TO wa_trans-cres_tr_yr,
            DATA_PACKAGE-interst_tr TO wa_trans-cinter_yr,
            DATA_PACKAGE-reval_tr   TO wa_trans-crev_rv_yr,
            DATA_PACKAGE-rev_odp_tr TO wa_trans-crev_od_yr.
            COLLECT wa_trans INTO lt_trans.
        Wertfelder geplant
          WHEN 'PLN'.
            MOVE:
            DATA_PACKAGE-acq_val_tr TO wa_trans-acq_val_tr,
            DATA_PACKAGE-inv_sup_tr TO wa_trans-inv_sup_tr,
            DATA_PACKAGE-ord_dep_tr TO wa_trans-plo_dep_yr,
            DATA_PACKAGE-spc_dep_tr TO wa_trans-pls_dep_yr,
            DATA_PACKAGE-upl_dep_tr TO wa_trans-upl_dep_yr,
            DATA_PACKAGE-res_trf_tr TO wa_trans-pln_avr_yr,
            DATA_PACKAGE-interst_tr TO wa_trans-pln_int_yr,
            DATA_PACKAGE-reval_tr   TO wa_trans-prev_rv_yr,
            DATA_PACKAGE-rev_odp_tr TO wa_trans-prev_aodyr.
            COLLECT wa_trans INTO lt_trans.
       'echte' Bewegungen ignorieren.
          WHEN OTHERS.
        ENDCASE.
      ENDLOOP.
      DATA_PACKAGE[] = lt_trans[].
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    Can anyone throw some light on this?
    Regards,
    Dhanya.

  • Getting error when trying to end date the element links

    When i am trying to end date the element link and i am getting a error message as ORA-01403: no data found if i click on the details button the following message is displayed:
    ORA-01403: no data found
    FRM-40735: ON-DELETE trigger raised unhandled exception ORA-01403.
    If i click on Ok button it bringgs another popup message that reads as follows:
    An Unexpected Error- 1403 has occured.An alert has been sent to the system administrator.
    ORA-01403: no data found
    I am really not getting why my link is not end dating.
    Could anyone advice me on how i can end date my element links.
    NB:the date track i am using is 01-DEC-2009 and no prayroll or quick pay has been processed as of this date

    Pl see if enabling an Forms Runtime Diagnostics (FRD) trace can help identify the cause
    MOS Doc 373548.1 - How To Collect And Use Forms Trace (FRD) in Oracle Applications Release 12
    MOS Doc 167635.1 - How To Perform Forms Runtime Diagnostics (FRD) Tracing in Applications 11i
    HTH
    Srini

  • Find Sales Order Item Basic Data by Elements query fails

    I am trying to consume Find Sales Order Item Basic Data by Elements in .NET 3.0.
    Every thing appears to be working fine -- I could query by PO number, Creation time, SalesOrganisationID etc.
    However, the most basic query is mysteriously failing. I just want to query by Sales order number, and have given a valid sales order number 6718 that exists in SAP.
    It fails giving the following errors:
    (in Log.LogItem.Note variable):
    <b>"Conversion failed: Invalid input format"</b>
    (in Log.LogItem.TypeID variable):
    <b>"701(SFB)"</b>
    Code is pretty simple, and I am just trying to query Saler Order number 6718. Of course there is nothing wrong with its format.
    From the ESOA site, all I could get was:
    <i>----
    QUOTE -
    The following values are optional selection criteria for restricting the search result:
    SelectionByID – Document number range
    INCLUSION_EXCLUSION_CODE
    INTERVAL_BOUNDARY_TYPE_CODE
    LOWER_BOUNDARY_ID
    Value
    UPPER_BOUNDARY_ID Value
    Value
    UNQUOTE -
    </i>
    I could not even have any  documentation on what to put in InclusionExclusionCode, and IntervalBoundaryTypeCode. They apper to be some Global Data Types for which I couldn't find any documentation. By sifting through Wiki, I just guessed a couple of values praying that it may work. I am a bit new to ESOA, but have expertise in .NET 3.0. Would someone guide me where to find the documentation for that, where are the error codes listed, so that I make the queries with little better preparation.
                querydata.SelectionByID = new SalesOrderERPItemBasicDataByElementsQueryMessage_syncSalesOrderERPItemBasicDataSelectionByElementsSelectionByID[1];//Single element array is good enough
                querydata.SelectionByID[0] = new SalesOrderERPItemBasicDataByElementsQueryMessage_syncSalesOrderERPItemBasicDataSelectionByElementsSelectionByID();
                querydata.SelectionByID[0].InclusionExclusionCode = "E";
                querydata.SelectionByID[0].IntervalBoundaryTypeCode = "6";
                querydata.SelectionByID[0].LowerBoundaryID = new SalesOrderID();
                querydata.SelectionByID[0].LowerBoundaryID.Value = "6718";
                querydata.SelectionByID[0].UpperBoundaryID = new SalesOrderID();
                querydata.SelectionByID[0].UpperBoundaryID.Value = "6718";

    How do you test with a SOAP Client  - I am trying to use same dataset as provided?
    I did with WSDL Test - SAP, SOAP Client and got the following error:
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
       <soap-env:Body>
          <nr1:SalesOrderERPBasicDataByElementsResponse_sync xmlns:nr1="http://sap.com/xi/APPL/Global2">
             <Log>
                <MaximumLogItemSeverityCode>1</MaximumLogItemSeverityCode>
                <Item>
                   <TypeID>701(SFB)</TypeID>
                   <SeverityCode>1</SeverityCode>
                   <Note>Conversion failed: Invalid input format</Note>
                </Item>
                <Item>
                   <TypeID>701(SFB)</TypeID>
                   <SeverityCode>1</SeverityCode>
                   <Note>Conversion failed: Invalid input format</Note>
                </Item>
                <Item>
                   <TypeID>701(SFB)</TypeID>
                   <SeverityCode>1</SeverityCode>
                   <Note>Conversion failed: Invalid input format</Note>
                </Item>
                <Item>
                   <TypeID>701(SFB)</TypeID>
                   <SeverityCode>1</SeverityCode>
                   <Note>Conversion failed: Invalid input format</Note>
                </Item>
                <Item>
                   <TypeID>701(SFB)</TypeID>
                   <SeverityCode>1</SeverityCode>
                   <Note>Conversion failed: Invalid input format</Note>
                </Item>
             </Log>
          </nr1:SalesOrderERPBasicDataByElementsResponse_sync>
       </soap-env:Body>
    </soap-env:Envelope>
    Thanks..
    Vikas

  • Unable to stop incorrect date exports

    How do we set up a form in Adobe Acrobat XI that allows dates to be formatted a certain way (mmm/dd/yyyy) and exported in the same way to Excel and always be recognized as a "proper" date in Excel?
    Currently the following does not work (Attempt #1):
    Set up a field; Set the format category as date; Set up a Custom format of "mmm/dd/yyyy"
    Create a distribution file
    When users fill out the form if they type in an incorrect date, eg., "August 27 2013", the form automagically shows the date on the PDF as "Aug/27/13" - Great!
    When the users submit the form and it's brought into the response file the dates are shown in a default date format of mm/dd/yyyy - Fine, once the form owners understand this
    When the form owners export the information the data exported is the same as the original users entered it, not as it was automagically formatted to. For instance, if submitters originally entered "August 27, 2013" then that's what goes across to Excel. And some of these formats Excel doesn't know how to convert. - Understandably frustrating for form owners
    Attempt #2: As a workaround we set up special formatting that has a mask of "AAA/99/9999". This at least provides forces the users to use the same formatting, but is confusing the submitters when they need to enter dates from 1-9 and we've also found that the conversion of this format to a date in Excel doesn't work, but at least it's consistent! Javascript was also added to force users to use specific month abbreviations.
    d = new Date(event.value.replace(/-/g, " "));
    if (!Date.parse(d)){app.alert("Please enter in a proper date.\n\nThe month abbreviations are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec");}
    Attempt #3: The last attempt was to continue to use the set up as Attempt #1, but to also use the javascript from Attempt #2. The theory being that if a user entered in "August 27 2013" the javascript would complain. Alas, the javascript appears to run after Adobe automagically does its date format conversion.
    Does anyone know how to get around this or have any other ideas to either enforce a usable date format or have Adobe export the dates as they've been automatically formatted to? We've tried to find a way to turn off the automatic date conversion that Adobe's running, but haven't found a way yet. Another option seemed to be to allow a masking that allowed for optional characters (so that the "0" wouldn't be needed for the dates 1-9) but there doesn't seem to be one.
    Thanks in advance!

    Since there was no clear way to ensure that the date formatting was correct prior to exporting, we're going to get the respondants to use drop downs to ensure the formatting is correct. Not the most convenient for the users though as they're accustomed to being able to type in the values to select it (e.g., for the date of 23 they would expect to enter 2 then 3 for 23) based on other applications, but the Adobe pull downs don't "group" what's been entered (e.g., 2 then 3 will select 30, not 23) and so it will take them a bit to get used to it. I still can't believe that Adobe wouldn't simply export what it's been formatted to though... after all that's what we set the form up for.

  • Calendar Tile on Windows 8.1 displaying incorrect date for icloud calendar but date icon displays correct date on iPhone 5 and iPad Air

    Calendar Tile on Windows 8.1 displaying incorrect date for icloud calendar but date icon displays correct date on iPhone 5 and iPad Air.  Date on Windows 8.1 is correct.  Thank you.

    Try doing  a reset on your phone. Sounds like your carrier's time set is not getting through to your device. If the reset doesn't do it, then go to Settings>General>Reset>Reset Network Settings. That should do it.

  • IDoc with incorrect data is expected to fail but it  does not

    Hi All,
    The Job CQM_CR_O_IF103_IN_INOVIS_ORDER3 got cancelled as result of a short dump. In the initial investigation we found that the IDoc 0000000012089824 had an incorrect information i.e. it had a material which did not
    exist. The IDoc is expected to fail and give an error message but has not done so.
    We also observed the IDoc does not fail when the incorrect materialhappens to be the last material in the IDoc.
    The workaround was to fail the IDoc manually and then the subsequent jobs runs successfully.
    Would like to know why the IDoc is not failing when it has incorrect
    data.
    Thanks & Regards,

    Hello,
    the idoc fails only if there is a hard error in the segment, means i.e. if there is a wrong transaction type or missing ... But I think that the system behavior is correct, because the idoc cannot fail because a product is "just" wrong. This is no hard error, you should then get an error in the transaction that i.e. the product does not exists. You can try to use badi CRMXIF_ORDER_MAP to check the products, but then please make sure that note 1644057 is implemented.
    BR
    Rene

  • IDoc with incorrect data is expected to fail but does not

    Hi All,
    The Job CQM_CR_O_IF103_IN_INOVIS_ORDER3 got cancelled as result of a short dump. In the initial investigation we found that the IDoc 0000000012089824 had an incorrect information i.e. it had a material which did not
    exist. The IDoc is expected to fail and give an error message but has not done so.
    We also observed the IDoc does not fail when the incorrect materialhappens to be the last material in the IDoc.
    The workaround was to fail the IDoc manually and then the subsequent jobs runs successfully.
    Would like to know why the IDoc is not failing when it has incorrect
    data.
    Thanks & Regards,

    Hello,
    the idoc fails only if there is a hard error in the segment, means i.e. if there is a wrong transaction type or missing ... But I think that the system behavior is correct, because the idoc cannot fail because a product is "just" wrong. This is no hard error, you should then get an error in the transaction that i.e. the product does not exists. You can try to use badi CRMXIF_ORDER_MAP to check the products, but then please make sure that note 1644057 is implemented.
    BR
    Rene

  • Incorrect dates on iPhoto video when accessed by iMovie '09??

    Hi,
    I have a few videos in iPhoto. All have the correct time and date.
    iMovie '09 has access to these, but is showing the incorrect date on some of them (even though iPhoto is showing the correct date). The date is the same - 31 December 1903.
    It has been like this since I first used iMovie '09.
    Can anybody help?
    Cheers.
    BTW, how do I contact Apple support about something like this? I can't find any e-mail support.
    Message was edited by: NeddySeagoon

    NeddySeagoon - wondering if you found the answer to this?
    I too have iPhoto videos showing up in iMovie fine, but the dates are wrong in iMovie (correct in iPhoto).
    Also, I have updated video titles in iPhoto, but those titles are not showing up consistently in iMovie. Perhaps related issue, I'm not sure.
    Any idea if this could be a permissions issue? (Video is stored on an external drive). Or something else?
    Thanks!

  • Reserved fields in the catalog record have incorrect data???

    I inserted the orginal installation disk for the Mac mini. I ran the verify disk. Then nine of these messages in red showed - "Reserved fields in the catalog record have incorrect data." I then did repair disk and now it shows that 1 volume could not be repaired. I have the MiniStack as well. I am assuming that the Hard Drive is the one needing repair. Not the MiniStack which also has OS installed along with Classic. How can I fix the disk? How important is the message in red?

    You have directory damage.
    Use Disk Warrior to repair the drive: http://www.alsoft.com
    Explanation of what directory damage is and what causes it: http://alsoft.com/DiskWarrior/details4.html
    The other option is to wipe your drive and re-install everything.

  • VISA Read gets incorrect data from serial connection

    I am having difficulty using the VISA functions in LabVIEW to read data from a virtual COM port. Data is being sent from a serial to USB chip via a USB connection using OpenSDA drivers. I have a python program written to read from this chip as well, and it never has an issue. However, when trying to achieve the same read in LabVIEW I am running into the problem of getting incorrect data in the read buffer using the VISA Read function.
    I have a VISA Configure Serial Port function set up with a control to select the COM port that the device is plugged into. Baud rate is default at 9600. Termination char of my data is a newline, which is also default. Enable termination char is set to true. A VISA Open function follows this configuration, and then feeds the VISA Resource Name Out into a while loop where a VISA Read function displays the data in read buffer. Byte count for the VISA Read is set to 20 so I can read more of the erroneous datat, however actual data will only be 6-12 bytes. The while loop has a wait function, and no matter how much I slow down the readings I still get incorrect data (I have tried 20ms thru 1000ms). 
    The data I expect to receive in the read buffer from VISA Read is in the form of "0-255,0-255,0-255\n", like the following:
    51,93,31\n
    or
    51,193,128\n
    And occasionally I receive this data correctly, however I intermittently (sometimes every couple reads, sometimes a couple times in a row) get incorrect readings like this:
    51,1\n
    51,193739\n
    \n
    51,1933,191\n
    51,,193,196\n
    51,1933,252 
    51,203,116203,186\n
    Where it seems like the read data is truncated, missing characters, or has additional characters. Looking at these values, however, it seems like the read was done incorrectly because the bytes seem partially correct (51 is the first number even in incorrect reads).
    I have search but haven't found a similar issue and I am not sure what to try from here on. Any help is appreciated. Thanks!
    Attachments:
    Serial_Read_debugging.vi ‏13 KB

    The first thing is that none of the error clusters are connected so you could be getting errors that you are not seeing. Are you sure about the comm parameters? Finally, I have never had a lot of luck looking for termination characters. You might want to just capture data and append each read into one long string just to see if you are still seeing this strangeness.
    What sort of device is returning the data? How often does it spit out the data? How much distance is there between it and your computer? Can you configure it append something like a checksum or crc to the data?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Crystal report showing Incorrect data against Bex Query

    I have created Crystal report on top of Bex Query, I have not done any calculations in the report, just dragging structure and key figure in the report, ran for one month, when I compare with Bex Query with same period, it is showing incorrect data.
    I don't know what can be wrong here?
    We are Business Objects 3.1 SP3.
    Thanks,
    Ravi

    HI,
    I would suggest you trace the workflow in Web INtelligence according to these notes:
    Tracing:
    Unix : Note 1235111
    Windows : Note 1260004
    and then post a link for downloading the trace files here.
    regards
    Ingo

  • BOXIR2 FP4.6 -WebI report with merged dimensions: Incorrect data

    Issue: BOXIR2 FP 4.6 -WebI report with merged dimensions: Max value of an object from second query is displayed in the report even when the formula is based on the object from the first Query.
    Data displays properly on BOXIR2 SP2.
    Steps to reproduce.
    1.Use u2018Island Resort Marketingu2019 Universe to create a WebI report.
    2. Create a Query with objects u2018Reservation Dateu2019 and u2018Future guestsu2019 and apply a query filter where the u2018Reservation Dateu2019 is between 1/1/2001 and 31/1/2001 an Run the query.
    3. Add a second Query with the same objects i.e. u2018Reservation Dateu2019 and u2018Future guestsu2019 and apply a query filter where the u2018Reservation Dateu2019 is between 1/1/2001 and 31/12/2001.
    4. Create a report variable MaxDate using the syntax "=Max([Query 1].[Reservation Date]) In Report"
    5. Use the objects u2018Reservation Date Query 2u2019, u2018Future guests Query 2u2019 and u2018MaxDateu2019 variable to create a table in the report.
    You will find the Maxdate column displays Max date values of u2018Reservation Date Query 2u2019 instead of u2018Reservation Date Query 1u2019.
    Could you please advice me on this issue.

    Hi Hiteshwar,
    MaxDate variable returns a maximum of Reservation date  from Query 1 i.e. 1/15/01 which is correct. If you put that variable separately it will display that date correctly but you are grouping it along with objects from the query2 thatu2019s why it is displaying correct value for Query 2 where it finds 1/15/01, but for other values WEBI canu2019t group this value as it refers its formula which contains Query 1 reservation date.
    Hence we canu2019t say it is displaying values from Query 2 it is taking values from Query1 itself  for 1/15/2001 and for remaining values it is taking non matching values from Query 2 with which it is grouping.
    If you put that variable with objects from Query1 it wonu2019t display 1/15/01 but all values reservation date from query 1 contains because it is grouping based on reservation date though it is single max value.
    Even when you write "=Max(Query 2.Reservation Date) formula and use it with objects from query 1 though it contains so many values it matches (Groups) only the values from reservation date from Query 1.and displays only those values i.e. 1/1/2001 and 1/15/01.
    MaxDate returns 1/15/01 as Maximum Date value from Query 1 but Query 2 contains value far more greater than 1/15/01 hense that will be more incorrect data if WEBI displays maxdate as 1/15/01 along with Query 2 objects.
    Here we can avoid this behavior by Custom SQL but MaxDate is a report level variable hence we canu2019t edit SQL.
    If your data contains some duplicate values WEBI will repeat MaxDate value like
    Reservation date     Restaurant           Future_Guests    Total Guests 
    1/1/01                          ABC                         3                   3     
    1/15/01                       XYZ                          4                   8    
    1/16/01                       XYZ                          4                   8  
    By default, WEBI Groups Total Guests based on the Restaurant and Reservation Date, but if we want we can group those values based only on Restaurant which will duplicate Total Guest values for Restaurant XYZ. But you report contains only one dimension with all unique Values we canu2019t group those.
    I hope this is clear.
    Thanksu2026
    Pratik

  • How to Disable/End Date an Element Link/Element in HR 11.5.7(Fam.Pack G)

    We want to disable some element links that are no longer valid. These element links are assigned (element entries) to certain employees based on the eligibility criteria set (e.g. Organization/Job/Grade/etc). However we want to disable these elements from a specific date onward as they are no longer valid. I tried to end date either the element entry or the element link but I got the message "Field is protected against update".
    From help the only thing I found regarding deleting an element is to delete all element entries linked to that element link and then delete all element links linked to that element to be able to delete or end date the element.
    But what we need to do is only to disable the element links and not to delete them all together and lose any historical records related to these element entries.
    If anyone has any idea on how to deal with this issue will be highly appreciated.
    Thanking you in advance.
    Elena

    Hi again,
    I made a search regarding elements/links and managed to find an old document (2002) regarding links and following the suggestion there I managed to end date the element links in request.
    In order to end date the Element Link since it does not allow
    you to make any updates you have to try to DELETE it and then select END DATE instead of PURGE.
    Thank you!
    Best regards,
    Elena

  • Incorrect date getting determined

    Hi,
    I not sure what is happening. I written the below code. The begda and endda is between 11.06.2012 and 24.06.2012 but the begda for the particular pernr is 14.05.2012. gt_pa0008 has the correct values but its very strange gs_pa0008 is fetching an incorrect date but the other fields are correct
    PROVIDE FIELDS * FROM gt_pa0001 INTO gs_pa0001 VALID flag1
               BOUNDS begda AND endda
               FIELDS * FROM gt_pa0008 INTO gs_pa0008 VALID flag2
               BOUNDS begda AND endda
               FIELDS * FROM gt_pa0007 INTO gs_pa0007 VALID flag3
               BOUNDS  begda AND endda
        where begda <= lv_date AND endda >= wa_t549q-begda
         BETWEEN pn-begda AND pn-endda.
    Thank you.
    Regards,
    Narayani

    This relates to an incorrect FX Rate determination when a specific condition record is used.
    Under normal circumstances, this should not occur, but it looks like, if the ZHIV condition record is set up in EUR, rather than, (in this case) HRK, the values in the sales order / invoice and subsequently finance are converted back to front, (i.e 1 EUR = 7 HRK, rather than 7HRK = 1 EUR).

Maybe you are looking for