Quickly retrieve Exif metadata

I've got a script for Photoshop CC 2014 that makes some exposure value (EV) calculations based on Exif metadata in camera raw files and then adjusts the image exposure to the target EV.  I know that this information is quickly available in Bridge, but when I try to get the metadata in Photoshop, I have to use the Document.open() command, and that opens the file (which takes a long time) instead of just grabbing the Exif metadata.  I can get it quickly in a Bridge script, but I'm having a hard time embedding that stuff in a Photoshop-targeted script (the BridgeTalk stuff is a bit confusing to me, or it isn't working on my computer).
I've also attempted to use "bridge.executeScript()", but the bridge object apparently is not available to scripts targeting Photoshop (or else something is messed up with my installation).  Bridge is available in bridge-targeted scripts only.
Here's how it's working in Photoshop scripting (I include only the relevant part).
for (var nfile = nstart; nfile < nstop; nfile++){
var Name = File(testListing[nfile]).name.replace(/\.[^\.]+$/, '');
var file = File(testListing[nfile].path + "/" + Name + ".JPG");
if (file.exists){
app.open(file);
else{
app.open(testListing[nfile]);
var DocInfo = app.activeDocument.info;
var docRef = app.activeDocument
EV[nfile] = CalcEV (DocInfo, BaseISO);
app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);
(FYI, I use the jpeg file if it's there because Photoshop reads the exif from that file more quickly than it does from the raw file)
Here's how it's working in Bridge scripting:
firstfile = '7A7A5842.CR2';
lastfile = '7A7A5843.CR2';
var ExifProperty = 'exif:DateTimeOriginal';
var ExifNamespace = 'http://ns.adobe.com/exif/1.0/';
app.document.deselectAll();
app.document.selectAll();
var myThumbs = app.document.getSelection("cr2");
var fstart = -999;
var fend = -999;
for (var n = 0; n < myThumbs.length; n++){
    if (myThumbs[n].name == firstfile) fstart = n;
    if (myThumbs[n].name == lastfile) fend = n;
var NumFiles = myThumbs.length;
var fileThumbs = myThumbs.slice(fstart,fend);
flen = fend-fstart+1;
var EVarray = new Array(flen);
for (var n = 0; n < fileThumbs.length; n++){
    var md = fileThumbs[n].metadata;
    ISO = md.read(ExifNamespace,'exif:ISOSpeedRatings');
    SS_string = md.read(ExifNamespace,'exif:ExposureTime');
    var test = SS_string.split("/");
    ShutterSpeed = test[0]/test[1];
    var Aperture_string = md.read(ExifNamespace,'exif:FNumber');
    if (Aperture_string == '') {
        var Aperture = Number(1.4); // assume Samyang set at f1.4
    else {
        var test = Aperture_string.split("/");
        Aperture = test[0]/test[1];
    var ISOadjust = Number(1.);
    EVarray[n] = Math.log(Math.pow(Aperture,2)/(ShutterSpeed*ISOadjust))/Math.LN2;
    $.writeln('ISO ',ISO,' SS ',SS,' Av ',Aperture, ' EV=',EVarray[n]);
app.document.deselectAll();
"Done...";

Hi Bob, if Bridge was closed then no info would be returned, so make sure Bridge is running.
Here is the script with slight modifications showing how to process the data in the main function.
#target photoshop;
main();
function main(){
var bt = new BridgeTalk();
cameraRawData = new Object();
bt.target = "bridge";
bt.body = "var ftn = " + getInfoFromBridge.toSource() + "; ftn();";
bt.onResult = function( returnedData ) {  cameraRawData = eval( returnedData.body );}
bt.onError = function( sumatWentWrong ) {  alert(sumatWentWrong.body);}
bt.send(10);
//If you get here all should be well and you can process the data
for(var a = 0; a< cameraRawData.Name.length; a++){
$.writeln(cameraRawData.Name[a] + " - " + cameraRawData.FNumber[a]);
function getInfoFromBridge(){
/* all comments in this function must be in this format ! */
Info = {}; /* new Object, can be written as var Info = new Object(); */
/* create new arrays within the object */
Info.Name = new Array();
Info.FNumber = new Array();
/* change folder to */
app.document.thumbnail = Folder("~/desktop/test");
app.document.deselectAll();
/*get  a list of all cr2 documents */
var thumbs = app.document.getSelection("cr2");
for(var a in thumbs){
var t = new Thumbnail(thumbs[a]);   
var md = t.synchronousMetadata;
/*populate the arrays */
Info.Name.push(thumbs[a].name);
Info.FNumber.push(md.read( "http://ns.adobe.com/exif/1.0/","exif:FNumber"));
return Info.toSource();

Similar Messages

  • Index of EXIF-metadata from jpeg files by TREX

    Hello,
    I have the following scenario:
    We have a central fileserver with a lot of marketing pictures. Our marketing people are looking for a solution to search pictures by data stored in the EXIF-metadata of the jpeg-files.
    So I like to integrate this fileserver as a repository in KM, set up an index and let TREX do the search (as of note 663630 TREX can search the EXIF-Data of JPEG-Files).
    As goodie I want to give the marketing people the possibility to browse through the pictures in an image gallery. This gallery should be consisting of a query-based taxonomy where all the pictures are sorted by special EXIF-data (e.g. name of the photographer).
    Until now I have integrated the fileserver (as a FS-Repository) and create an index.
    Before index creation I added the mime-type “image/jpeg” to the TREXValidMimeTypes.ini and restarted TREX.
    After indexing the pictures could be found by it’s name, but the EXIF-data is not indexed.
    Now my question:
    Why TREX doesn’t index the EXIF-metadata?
    And how can I use the EXIF-data in an taxonomy?
    System:
    EP6.0 on WebAS 6.40 SPS16
    TREX SPS16 Patch 2
    KMC SPS16 Patch 2
    Greetings from Berlin, Germany
    Jens

    Greetings to Berlin,
    when triggered by KM, TREX will only index metadata that is known to KM as KM propertis.
    I do not know in detail and am not at all sure, but you could try to create custom properties in KM that are called exactly like your EXIF-metadata, set them to "indexable", <b>not</b> fill them with values on KM side and then try again.
    You may want to try this for just one of the EXIF-metadata as a test.
    Even if that works somehow, the maximum result is:
    - Property <b>name</b> existent in KM
    - Property thus searchable an classifiable
    - BUT property <b>values</b> will not show up in KM, as they will remain known only to TREX
    Regards, Karsten

  • IPhoto and EXIF Metadata

    Is there any way to set iPhoto 6 so that it will preserve all metadata in an image, even if the image is modified in iPhoto? It seems like the EXIF metadata is preserved in my photos upon import into iPhoto, but if I adjust an image using iPhoto all my EXIF metadata (shutter speed, aperture, etc.) is overwritten or lost.
    This is very annoying. Why does iPhoto behave this way? It has no business overwriting this metadata that should, by all logical accounts in my mind, remain with the image.

    Jim:
    How are you checking the metadata? I find that when I edit, like a crop, the modified jpg contains all of the EXIF data that the original has. I've verified that with other applications that read all the metadata.
    The only metadata that is not saved for use by other applications are the comments and keywords. Those are kept in the iPhoto database file.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Problem with EXIF metadata reading

    Hi everyone
    I'm trying to read EXIF metadata information. Here is my code snippet:
    uchar* exifData;
    Handle exifDataHandle = filterRecord->handleProcs->newProc(100);
    propSuite->getPropertyProc('8BIM', propEXIFData, 0, nil, &exifDataHandle);
    exifData = (uchar*)(*exifDataHandle);
    filterRecord->handleProcs->disposeProc(exifDataHandle);
    After this code executed I have exifData size only 4 bytes, but as I now minimum valid EXIF data should be 6 bytes. Maybe I did something wrong?
    Thanks for help.
    Regards

    Dennis Knutson wrote:
    The old serpdrv was eliminated with 7.0 unless you manually copied the VIs and driver from an older version.
    Well perhaps it was I who converted in labview 5.1. I remember that the old system was quite clumsy written. It was very slow. But with a few trick it could be speeded up. Just by using refnums like in files and a simple C program for baud rate setting. I could use stable 115200 tranfer rates back in labview 3.1 
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Cannot retrieve table metadata - Table does not exist: ODP source 0WRKCNT_CATG_TEXT does not exist

    Hi, when i able to import the 0WRKCNT_CATG_TEXT extractor into source system i am getting the above bug Cannot retrieve table metadata - Table does not exist: ODP source <0WRKCNT_CATG_TEXT> does not exist, i have been checked in RSA5 T code to check the object is active or not, its active and its available in ROOSATTR table with enabled mode,but still its showing the error, can anyone help on this ..

    Hi Airings,
    'ORA-00942: table or view does not exist'
    According to the error message, it seems that the migrating table or view does not exist in the database, or SSMA does not have access to it. To troubleshoot the issue, please check the following things.
     1. Verify that if the spelling of the table or view name is correct.
     2. If the table or view exists but is in a different schema from the current schema where the SQL is executing (in other word, the table doesn’t own by you, but owned by other user), the ORA-00942 error will return too. Resolve this by
    explicitly reference the table or view by specifying the schema name (schema_name.table_name).
    3. SSMA queries some additional catalog tables that you may not have permission to, please make sure that you grant the account permission to
     read sys.mlog$. For more details, please review this similar thread:
    Bug in SSMA For Oracle 6.0 for non-dba Oracle user.
    Reference:
    ORA-00942 Table or View Does Not Exist Oracle Error
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Can I change exif metadata with AIR?

    Hi.
    I am autor of a simple application that changes exif information in scanned images. I am looking for a way of re-implementing the application in a more cross platform way than it is today and found AIR interresting.
    However, I can not find any API for accessing image metadata in the documentation..
    Is altering the exif metadata possible with AIR (without having to implement all the "libexif-like" suff myself?)
    Thanks
    /sverrir

    There is nothing built in to AIR - but you may wish to look at
    http://code.google.com/p/as3corelib/
    which is an opensource AS3 library which includes some image metadata manipulation routines.
    You may also wish to make a feature request here
    http://ideas.adobe.com/air
    so that we will consider this addition in a future addition of the AIR runtime.
    Hope that helps.
    Chris Thilgen
    AIR Engineering

  • IPhoto geotags not save in EXIF metadata

    Why if I geotag a picture using iPhoto, that geotag won't be saved into the EXIF metadata? Exporting for example that picture in, say, Adobe Lightroom, or uploading it to Flickr won't show the location I picked in iPhoto, simply because that information is not stored in the EXIF metadata.
    Is it this behaviour what iPhoto is supposed to do? Or is it a bug? Conversely, if I geotag a picture in Lightroom, that geotag will be saved in the EXIF metadata, and correctly read by any other application

    iPhoto stores the location data in the edited version and does not write it into the original image file. To create a geocoded image file, export the edited version with the location data included:

  • Lightroom Import: How to load Exif metadata description

    Exif schema contains a description tag, which I would like to populate as part of the process of importing images from camera. Would you please show me how that can be done. I cannot locate rhe correct property in the import dialog.

    Are you referring to the EXIF:ImageDescription field or the EXIF:UserComment field?  When LR imports an image, those fields get automatically imported into the LR catalog.  They appear in the Metadata panel on the right.   EXIF:ImageDescription will be displayed as "Caption" under the Default metadata set, and EXIF:UserComment will be displayed as "User Comment" under the EXIF metadata set.

  • Photoshop Bug? GPS exif metadata stripped out

    We recently discovered that ANY changes made in Photoshop CS4 stripped out our GPS exif metadata.  We also tried it in CS3 - same thing!  And by changes, this includes anything - changing IPTC, adjusting levels, etc.  It even happened when just opening, re- saving and closing the file in Photoshop.
    FYI:  We tested it with images exported from both Adobe Camera RAW (Canon files) and Phocus(Hasselblad), and the problem occurred with both.  We've also tried it with files from different cameras, which used different GPS brands altogether, therefore we can rule out:  the GPS units, camera (Canon 1Ds Mark II, Hasselblad H3D-39), and software used to convert RAWS (Phocus, Adobe Camera RAW, Lightroom).  We also tried different computers to make sure no preferences were corrupt on an individual machine, to rule that out.
    To make things even more complicated, we just discovered that even though we can no longer see the GPS info in Photoshop CS4, Adobe Bridge DOES see the GPS info!  But - none of our other softwares which normally recognize GPS can see the info (iView, Cumulus).
    Very, very frustrating.......HELP!
    Mac OS 10.5.6, PowerMac 2 x 2.66 GHz Dual-Core Intel Xenon, Photoshop CS4, Files exported to Prophoto RGB 16-bit TIFF) using both Lightroom and Phocus

    Addendum: Does anyone know how to add EXIF back into a file?  
    I assume this would be difficult, as EXIF is hard to remove, much less put back.
    Many of these files have already been worked on extensively, and re-importing and re-working is not a good option.
    We have already tried the following (did NOT work):
    1)  Exporting the XMP from the file BEFORE any changes are made (with GPS info still intact), and importing XMP to finished file (tried all 3 option settings)
    2)  Copy and pasting the finished file on top of the original (GPS intact file) and flattening, so that the finished file would take on the properties of the old, un-retouched file.  What's odd about this is that after flattening the file, saving, and looking at File Info - it appeared it had WORKED.  But when you close the file, and re-open, the GPS is gone again.

  • Export exif / metadata

    Hi,
    how can i export all exif / metadata from an image to a txt/csv file?
    I'm missing the copy & paste function for the metadata. If i edit an image with an external app, some of the exif data gets lost...
    Cheers

    *missing the edit button*
    I want to extract all the exif data (ISO, Aperture, Exposure, ...) I see inside Aperture.
    And is there a way to write the exif (ISO, Aperture, Exposure, ..., NOT ONLY the subject, description, ...) from one image to a new image?

  • How to make Canon specific EXIF metadata visible in LR?

    Hi
    I love LR but it excludes some fields of EXIF metadata that are provided by Canon's propietary raw converter. I am sure that there must be a way to make these visible inside LR so one can filter and create smart collections based on these metadata.
    What is the best way to achieve this? A plug-in? Any additional info?
    Thanks,
    Juan Dent

    One possibility is to use Exiftool that can read Canon tags and transform it to keywords or captions that LR can understand. Check out this list from http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Canon.html:
    Canon CameraSettings Tags
    Index
    Tag Name
    Writable
    Values / Notes
    1
    MacroMode
    int16s
    1 = Macro
    2 = Normal
    2
    SelfTimer
    int16s
    3
    Quality
    int16s
    1 = Economy
    2 = Normal
    3 = Fine
    4 = RAW
    5 = Superfine
    130 = Normal Movie
    4
    CanonFlashMode
    int16s
    0 = Off
    1 = Auto
    2 = On
    3 = Red-eye reduction
    4 = Slow-sync
    5 = Red-eye reduction (Auto)
    6 = Red-eye reduction (On)
    16 = External flash
    5
    ContinuousDrive
    int16s
    0 = Single
    1 = Continuous
    2 = Movie
    3 = Continuous, Speed Priority
    4 = Continuous, Low
    5 = Continuous, High
    7
    FocusMode
    int16s
    0 = One-shot AF
    1 = AI Servo AF
    2 = AI Focus AF
    3 = Manual Focus (3)
    4 = Single
    5 = Continuous
    6 = Manual Focus (6)
    16 = Pan Focus
    9
    RecordMode
    int16s
    1 = JPEG
    2 = CRW+THM
    3 = AVI+THM
    4 = TIF
    5 = TIF+JPEG
    6 = CR2
    7 = CR2+JPEG
    10
    CanonImageSize
    int16s
    0 = Large
    1 = Medium
    2 = Small
    5 = Medium 1
    6 = Medium 2
    7 = Medium 3
    8 = Postcard
    9 = Widescreen
    129 = Medium Movie
    130 = Small Movie
    11
    EasyMode
    int16s
    0 = Full auto
    1 = Manual
    2 = Landscape
    3 = Fast shutter
    4 = Slow shutter
    5 = Night
    6 = Gray Scale
    7 = Sepia
    8 = Portrait
    9 = Sports
    10 = Macro
    11 = Black & White
    12 = Pan focus
    13 = Vivid
    14 = Neutral
    15 = Flash Off
    16 = Long Shutter
    17 = Super Macro
    18 = Foliage
    19 = Indoor
    20 = Fireworks
    21 = Beach
    22 = Underwater
    23 = Snow
    24 = Kids & Pets
    25 = Night Snapshot
    26 = Digital Macro
    27 = My Colors
    28 = Still Image
    30 = Color Accent
    31 = Color Swap
    32 = Aquarium
    33 = ISO 3200
    38 = Creative Auto
    261 = Sunset
    12
    DigitalZoom
    int16s
    0 = None
    1 = 2x
    2 = 4x
    3 = Other
    13
    Contrast
    int16s
    0 = Normal
    14
    Saturation
    int16s
    0 = Normal
    15
    Sharpness
    int16s
    (some models use a range of -2 to +2 where 0 is normal sharpening, and others use a range of 0 to 7 where 0 is no sharpening)
    16
    CameraISO
    int16s
    17
    MeteringMode
    int16s
    0 = Default
    1 = Spot
    2 = Average
    3 = Evaluative
    4 = Partial
    5 = Center-weighted average
    18
    FocusRange
    int16s
    0 = Manual
    1 = Auto
    2 = Not Known
    3 = Macro
    4 = Very Close
    5 = Close
    6 = Middle Range
    7 = Far Range
    8 = Pan Focus
    9 = Super Macro
    10 = Infinity
    19
    AFPoint
    int16s
    0x2005 = Manual AF point selection
    0x3000 = None (MF)
    0x3001 = Auto AF point selection
    0x3002 = Right
    0x3003 = Center
    0x3004 = Left
    0x4001 = Auto AF point selection
    0x4006 = Face Detect
    20
    CanonExposureMode
    int16s
    0 = Easy
    1 = Program AE
    2 = Shutter speed priority AE
    3 = Aperture-priority AE
    4 = Manual
    5 = Depth-of-field AE
    6 = M-Dep
    7 = Bulb
    22
    LensType
    int16s
    --> Canon LensType Values
    (this value is incorrect for EOS 7D images with lenses of type 256 or greater)
    23
    LongFocal
    int16u
    24
    ShortFocal
    int16u
    25
    FocalUnits
    int16s
    26
    MaxAperture
    int16s
    27
    MinAperture
    int16s
    28
    FlashActivity
    int16s
    29
    FlashBits
    int16s
    Bit 0 = Manual
    Bit 1 = TTL
    Bit 2 = A-TTL
    Bit 3 = E-TTL
    Bit 4 = FP sync enabled
    Bit 7 = 2nd-curtain sync used
    Bit 11 = FP sync used
    Bit 13 = Built-in
    Bit 14 = External
    32
    FocusContinuous
    int16s
    0 = Single
    1 = Continuous
    8 = Manual
    33
    AESetting
    int16s
    0 = Normal AE
    1 = Exposure Compensation
    2 = AE Lock
    3 = AE Lock + Exposure Comp.
    4 = No AE
    34
    ImageStabilization
    int16s
    0 = Off
    1 = On
    2 = On, Shot Only
    3 = On, Panning
    35
    DisplayAperture
    int16s
    36
    ZoomSourceWidth
    int16s
    37
    ZoomTargetWidth
    int16s
    39
    SpotMeteringMode
    int16s
    0 = Center
    1 = AF Point
    40
    PhotoEffect
    int16s
    0 = Off
    1 = Vivid
    2 = Neutral
    3 = Smooth
    4 = Sepia
    5 = B&W
    6 = Custom
    100 = My Color Data
    41
    ManualFlashOutput
    int16s
    0x0 = n/a
    0x500 = Full
    0x502 = Medium
    0x504 = Low
    0x7fff = n/a
    42
    ColorTone
    int16s
    0 = Normal
    46
    SRAWQuality
    int16s
    0 = n/a
    1 = sRAW1 (mRAW)
    2 = sRAW2 (sRAW)

  • Lens Exif metadata worked for KM but no more for Sony cams

    Playing with the metadata panel in Aperture 2.1, I was surprised to see the information for the lens manufacturer/model for some shots I did with my old Konica-Minolta 5D DSLR.
    Sony took over the Konica-Minolta DSLR system about 2 years ago and as many others I have since moved to a Sony A100 body and recently to an A700 body.
    Using the very same lenses, that give me detailed lens Exif metadata with the old Konica-Minolta 5D, the metadata field is empty with Sony A100 and A700 files.
    A bit annoying, that the 4 years old Konica-Minolta 5D is supported in Aperture, while the follow up models from Sony are not.
    Hope this will be fixed in the next update.
    Peter

    Steve,
    you are probably right, that Sony is encoding the lens data in a somewhat non standard way.
    But as far as I know, in the EXIF of the Konica-Minolta files, this was done as well in a non standard way, by storing a binary lens code (at least I don't find any plaintext lens data in the image file, when I peek into it with a low level file-editor like Hexedit). As the lens information is displayed in clear text for the Konica-Minolta files within Aperture, Apple must have already integrated a lens database holding data for Konica-Minolta and Sony lenses. Interestingly even new Sony lenses like the Carl-Zeiss 16-80 lens show up, when used on an old Konica-Minolta DSLR.
    For me it looks like Sony might store the same lens-code now in a different proprietary EXIF field but Aperture is still looking into the old Konica-Minolta EXIF field, which is non existent or empty.
    So yes, Sony probably broke it, but there was enough time for Apple to fix it, especially as they have updated the lens database all the time. It is weired to add all recent Sony lenses to Aperture's lens database, but make the data only available, if you use the lenses on a 5 years old Konica-Minolta body.
    So I repeat my request for Apple to fix this in Aperture soon.
    Peter

  • How do i remove the exif metadata from my jpg file produced with a digital camera photo?

    How do i remove the exif metadata from my jpg file produced with a digital camera photo?

    The excellent and free utility Irfanview has the option to remove the EXIF data.
    Simply open and the file and do a Save, or Save As with the original name.
    Surprisingly, the default is to not keep the original EXIF data.

  • Updating EXIF metadata

    My new imports into Aperture 2 show some metadata which was not present in in 1.5. Specifically, the new version identifies lenses specifically and records camera serial numbers.
    I would like to get my imported library to show these metadata items too. The info must be in the raw file, but doesn't show in the Aperture 2 metadata. I assume this means that the metadata is parsed at import and then not touched again.
    Does anyone know a way of forcing Aperture to update the metadata from raw files to take advantage of software improvements?

    I am disappointed to see that a bunch of EXIF metadata is still not imported correctly from my EOS 1D Mk 3 - ie metering mode, exposure mode and white balance are still only represented by numbers and not their actual selection title.
    Is this my error are there any other EOS1D Mk3 users out there experiencing the same issue?
    Dingah

  • Error: Cannot retrieve repository metadata (repomd.xml) for repository: ol6_UEK_latest. Please verify its path and try again

    i am trying to executing command
    "yum update"
    and i am facing error during this
    [Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
    Trying other mirror.
    Error: Cannot retrieve repository metadata (repomd.xml) for repository: ol6_UEK_latest. Please verify its path and try again

    here i found the "ol6_UEK_latest" in public-yumo.l6.repo.
    and here is URL corresponding to this:
    name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
    baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
    gpgcheck=1
    enabled=1
    plz help me is something wrong with URL or what i do ?

Maybe you are looking for

  • Help me fix my 8900 PLEASE! Desperate now

    Hi A month ago, I was using my phone - had like a 20-30 minutes call, it was quite hot, so I was a little sweaty through the call (relevance will come later). Anyway, 5-10 minutes after call, my keypad stopped functioning completely. Read around, the

  • Help, my ipod is in safe mode

    i connected my ipod to my computer and it turned on in safe mode and now itunes is telling me i must restore my settings...is there any way to fix this problem without loosing all my songs?? i have about 1400 and it has taken me two months to get all

  • Excise(serious issue)

    hi friends..         when excise was changed from 10% to 8%, i changed the conditions records for all tax code with JMOP conditions type from 10% to 8% directly in t-code FV12 and saved.       My issue is before changing BED was calculating properly

  • BAPI for POST INVOICE

    Hi all,     Which is the BAPI used to Post an Invoice after the delivery has been made. Thanks, Madhan.

  • Xsl fo doubt

    Anyone can help me out.. I am having an order by date(date TYPE) in Purchase order xsl style sheet.The client want to add a Number variable to come to another date... Something like this: Nov 30 2009+7=Dec 7 2009 How to do this in XSL-FO?? thanks kp