System should not creates new version when value of PO increased..

Hi Experts,
Need your help to solve this problem. When i increase value of PO it should retrigger Release strategy but it creates version first, then i have to tick completion indicator and check then only release strategy retriggers..
It should not create new version when change po
Please check below screenshot
Please help

Hi
Please reveiw the following points in note
   - 493900 FAQ: Release Strategy
      4.  Why is the release strategy not determined?
     "If you use version management, the determination of the release
      strategy starts when the version is completed.
      You complete a version by setting the "version completed"
      indicator in the version tab."
   - 662993 Resetting an already occurred release
     You edit a purchasing document with release strategy.
     You change the quantity or the price. In spite of that, the
     already set release is not reset.
The release strategy works the same with or without version management
active - the only difference in case - version management is active -
is that if release is to be reset, it will be reset only on version
I hope this helsp to clarify this issue
Kind regards,
Lorraine

Similar Messages

  • Create new versions when making adjustments?

    Hi,
    What does anyone suggest this setting should be set to? It's on the Advanced Tab in Preferences.
    I think it was un checked when I installed the Trial Version.
    The help file stated the following:-
    +Create new versions when making adjustments” checkbox: Select this checkbox to have Aperture automatically create a new version when you adjust a selected image. The adjustment is applied to the original version and the new one is left untouched.+
    So when I edit an image the the software makes a copy and the original is altered? What happens if it's left un checked?
    Any help on the whole editing thing would be gratefully received.

    This is just a way to automatically create a new version when you make an adjustment. The new version is stacked with an unaltered version, allowing you to quickly see them side by side. What you have to remember is that the *original file is never altered*. This is all virtual. What is called original in this case is in fact an original version, not the actual file. The actual file is called the Master. Very important to understand the distinction.
    I personally leave this off. I never use RAW files without adjustments so there's no point in keeping an unaltered version around, plus it tends to quickly multiply versions and just creates clutter. If I want to see the original file I just hit M (this is the default command key for Show Master). Hit M again and I'm back to my version. If I've created a version and want to do a new different looking one starting from scratch, I can select New Version From Master: presto a new "original"!
    If I've worked on a picture and want to create a BW version, chances are I want to keep the work I've already done as a starting point. In that case I select Duplicate Version and do my BW on the new version. Again, I'm never actually duplicating files and I'm never actually altering pixels, original or otherwise. This is all a set of xml instructions that Aperture applies when it displays the files.
    Helping?
    Message was edited by: Jade Leary

  • Preference to "Create New Versions when making adjustments"

    Isnt the option in Preferences "create new version when making adjustments" seem irrelevant when Ap doesnt touch the original (master) anyway? How is this option intended to be used? Most of the imags for me would be slight tweeks so I wouldnt necessarily want every one of those showing as a 'full new version'.

    yeh, that would seem logical wouldn't it - to create a new version for each session... but that's not what happens.
    i mostly use the HUD and don't close between adjustments but i do sometimes use the side panel which i also don't hide/close between adjustments. i can't remember whether making adjustments via the side panel creates new versions for every adjustment, certainly this behaviour happens when i use the HUD and i'm fairly sure i would have tried the side panel to avoid this annoying behaviour but i can't say for sure and will have to test the side panel behaviour next week if i get time.
    even with the preference for 'create new versions' turned off, there seem to be certain images that always create a new version when i make an adjustment - whether using the HUD or side panel. I haven't figured out an exact pattern to this but it seems to be something to do with those files that have been 'sent to external editor'. subsequent adjustments within aperture always create a new version - haven't a clue why...
    just as an aside, sometimes when i make adjustments (particularly sharpening or noise reduction) i get single pixel wide horizontal lines of noise appearing across my images, which are there when i print or export too, not just screen artifacts due to a badly processed preview...hmmm...anyone else noticed this or has found a post about ways to avoid this?
    all that said, aperture is a godsend for my workflow
    MacBook 2.0 White   Mac OS X (10.4.8)  

  • "Create new versions when making adjustments" - Lion, Aperture 3.1.3

    I recently upgraded to Lion, and then shortly thereafter to Aperture 3.1.3.
    While I don't seem to share everybody else's issues with Lion nor with Aperture, I do have one of my own.
    In Preferences -> Advanced, I have a box titled "Create new versiont when making adjustment."  It is checked.
    My expectation, (and the way things have always worked under Snow Leopard) is that if I select a master image and begin to make adjustments to it from _any_ feature int he adjustments pallette, that I new version will be created, stacked next to the original, and that the changes I am making will be made to the new version.  This is _not_ what is happening.
    Instead, the changes are applied directly to the master image.  This is annoying, and will probably be fixed in an update...    I thought the work around would be to manually create the version for the time being, until Apple sorts this out.  That didn't work either.
    If I manually create a version, and then proceed to make adjustments to the version, Aperture dows what I would have expected in the first place.  It creates a new version and applies the changes to that.
    For example, I right click on a master image and select "New Version form Master"  A new version, titled "... - Version 2" is created.  When I begin to modify Version 2, a new version is created titled "... - Version 3" and my changes are applied to this version... leaving me with the master and Version 2 which are now duplicates of each other.
    Even more interesting is this:
    Images that were imported into Aperture prior to the Lion upgrade, and the 3.1.3 patch behave as expected, in that a new version is created when adjustments are applied to a master image.
    Images that were imported into Aperture _after_ the upgrade to Lion and the 3.1.3 patch act as describd above, in that no new version is created when adjustments are applied to a master image.
    So...  Here are the questions:
    1. Is anybody else experiencing this?
    2. Does anybody know how to restore the correct behavior?

    Alright,   I have solved the problem.
    Some time ago, I thought it might be neat to import pictures with the Auto Exposure adjustment in place.  What I didn't realize was that if the master image is in the library with adjustments on it, it downs't create a new version when you add additional adjustments.
    As soon as I disabled that, and imported some new imges the probelm went away.
    Also... I went back to the six or seven project that I had imported while use Auto Exposure and removed that adjustment from those images...  
    All is resolved.

  • ORA-27142: could not create new process/ when i am duplicating DB

    I am trying to duplicated DB on new server and getting this error
    Need suggestions to solve this ?
    RMAN-03002: failure of Duplicate Db command at 10/03/2006 16:58:58
    RMAN-03015: error occurred in stored script Memory Script
    ORA-27142: could not create new process

    check the availability of disk space where netbackup writes log files.
    if its is all set,
    open the netbackup log file and look for any recent relevant messages.
    look closely in rmanlogs and netbackup logs for any messages ralating to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE

  • Aperture not creating new version of raw image when editing in external editor

    I have my export settings set up in Aperture 3.5.1 as editing int Photoshope Elements 12 as Tiff files.  When I right click on a raw photo in aperture and say to edit in PSE, it will open it in the program, but only in camera raw. 
    This happens even when I have made edits to that particular file, such as exposure.  This is causing problems with saving back to aperture.  I have troubleshot this with Elements and the problem seems to be that Aperture is not creating a new version  on export.
    Can you tell me what I need to do?
    Thanks so much for any insight.

    What you have described is not how it is meant to work so it sounds like there is an issue on your system.
    Try running the first two first aid procedures (repair permissions and repair database) as described here:
    http://support.apple.com/kb/HT3805
    I think this should fix the issue, but let us know if it doesn't.
    PS: When you drag the image from Aperture to PSE on the task bar, you are sending the JPEG preview to PSE, so that's an unrelated process.
    Andy

  • "Create new versions when making adjustments" checkbox - do I check it??

    I have been using Aperture for many months. I'm not sure why, but I looked at my prefs the other day and the checkbox above was unchecked. Two important questions:
    1. Which way should this be set??
    2. Is Aperture still keeping the original separate from any edits I am making? PLEASE tell me that my originals have been kept separately!!! : )
    Thanks in advance,
    Erik

    1. It's a Preference. It should be set the way you prefer.
    2. Aperture never adjusts the master.
    When you look at an unadjusted image in Aperture, you are seeing +Version 1+. You can adjust Version 1, or you can create a new version and adjust that. Or you can set the preference, and when you make adjustments, a new version will be created automatically. This can cause unwanted versions to accumulate. Or maybe they are not unwanted.
    The Master is never affected, just the versions.

  • Mail dock icon does not create new message when a file is dragged onto it

    After installing Snow Leopard, dragging a file to the the Mail icon in the dock no longer creates a new message with the file attached. Mail is brought forward as the active application, just no new message window.
    This was the behavior in earlier versions of mail.
    Is there a preference, or any other change, that can be changed to allow drag-and-drop of a file to create a new message with an attachment?
    --James

    There are some issues with drag and drop. I was having the same issue with Mail with SL, but I didn't check after 10.6.1. However, I just installed a new hard drive, and migrated. Mail works for me, now.
    It didn't work with my 10.6 which had been upgraded with multiple builds in the beta. I assumed it was related to the other drag and drop issues. Now that I check it again, I don't think so.

  • The system could not create any outputs for mv type 561

    Hi,
    I tried to print out a goods receipt others in MIGO and i received "The system could not create any outputs" when i tick on output control. I tried to follow the steps in How to print the material document in MB1C movement 561 I stuck at step 4 where i cannot find MvT 561. Please help
    Chk your setting as below to get GR print out.
    . Maintain the Printer Name in MM->Inv Mgmt and Phy Inv->Print Control-> Gen Settings-> Printer Setting Enter the local printer where you want to print your Goods posting document
    2. Ensure that in MM->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
    3. In MM->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
    4. In MM->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for Goods Receipt/GI/Transfer Posting Documents
    Here for Particular mvt type 101,201,121,311,313,501,521,561 etcu2026 Maintain the Print item as 1--Material document printout
    5. In MM->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the following--
    Select the particular Output type then goto Details
    a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Transmission medium is 1
    b. Print Parameter is 7
    6. In MM->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc , Maintain the Output device for all your Plants
    7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
    Now the settings are ready for Printing Material doc
    8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
    9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.

    issue is resolved

  • Aperture creating new version of image for each adjustment applied!

    To anyone out there who can sort this one out, I will be forever grateful!
    Here's the problem. I'll be jamming away in Aperture, adjusting photos like a madman. After adjusting a random number of photos (it usually varies between 5-30 photos or so after starting Aperture each time), the adjustments panel will no longer update when I click on a new image (i.e. it holds the info from the last image I adjusted and will continue to apply new adjustments to that last image even if another image is highlighted). If I switch to the metadata panel and then back to adjustments it will refresh itself and recognize the currently selected image (although I have to do this for EACH image I want to adjust once it starts acting up like this). The BIG problem is that even if I get the adjustments panel to recognize the selected image at this point, for EACH adjustment I apply it makes a new version of the image. For example, if I first change the contrast, it will make Version 2 of the image and select it (which is what it's supposed to do for the first adjustment, because I have "create new versions when making adjustments" checked in my preferences), but if I then make another adjustment like changing the saturation, it makes Version 3 of the image (from the master, so that only the saturation adjustment is applied and not the contrast adjustment). As you can imagine, this utterly destroys my once incredibly efficient Aperture workflow and makes it pretty much impossible to use Aperture for adjustments unless I turn off "create new versions when making adjustments" in the preferences, at which point it does seem to work again (although I've only tried it on a few images, so not 100% sure it will work properly even then). If I restart Aperture (or my computer), it will work normally again for a few pictures and then will start acting up again with the same problem.
    Originally I was running into this problem on my PowerBook G4, and so I figured it was just because Aperture didn't like my wussy G4 processor and was acting up when the load got too heavy (after all, the adjustments would work fine for up to 30 images or so). However I recently purchased a sexy iMac 24" 2.8 GHz and maxed out the RAM to 4GB, but I'm still getting the same darned problem with Aperture on my iMac. Yes, I'm using the same library of photos I was using on my PowerBook G4.
    This problem has been plaguing me for about 3 months now (everything else in Aperture works fine so I'm still using it to import and organize my photos, I just haven't been able to make adjustments on large groups of pictures for a while), and I've searched and searched these forums countless times to see if anyone has run into similar problems, but I've not seen a single mention of it. I've also tried EVERYTHING mentioned for similar problems (rebuilding library, vacuuming database, erasing com.apple.aperture.plist preference file, repairing permissions, reinstalling Aperture, making burnt offerings to Steve Jobs), and NOTHING is working. ARRGH!!
    For those who might have some words of wisdom to offer this delighted-***-miserably frustrated Aperture user, here are a few more details about my setup:
    I have a library of about 37,000 photos, the vast majority of them being RAW .CRW files from a Canon 10D. The 25GB library file is stored on my internal hard drive, and all photos are referenced from an external LaCie 500GB FireWire 400 hard drive. I have a LOT of export plug-ins installed in Aperture, but no image adjustment plugins. I have generated previews turned off for all projects. I've had the same problem on both my PowerBook G4 and new iMac 24" 2.8 GHz. One other thing worth mentioning is that instead of upgrading from 2.1 (which was already giving me this problem) to 2.1.2, I downloaded the full version of 2.1.2 and installed it. I noticed that my 2.1 Aperture.app file was less than 100MB, whereas the 2.1.2 Aperture.app file is over 300MB. Don't know if that's normal or not.
    The only other thing I can think of to try at this point is to load a new library into Aperture and import a large group of pictures and make adjustments to them to potentially see if my problem is being caused by Aperture or by the library. Will probably try that tomorrow.
    I would appreciate any advice or feedback anyone can offer about this nasty little problem, as it's giving me a serious hormonal imbalance.
    THANKS!

    Thanks for the reply RB, but my current workflow depends on me creating new versions when I make adjustments. I suppose as a temporary solution I will probably have to either turn this preference off or just be willing to constantly restart Aperture. At least I finally found another thread with the same problem, so finally I don't feel completely alone in the far reaches of the Aperture universe. For anyone who is interested, here is the link to that thread:
    http://discussions.apple.com/thread.jspa?messageID=8555067
    It appears this problem is closely related to the ubiquitous black viewer problem that seems to be plaguing far more users than my issue (although I've run into the black viewer problem a few times myself), as both problems force Aperture to output the following message to Console:
    Main Thread Exception in Aperture: * -NSCFArray objectAtIndex:: index (1) beyond bounds (1)
    It seems that both of these problems existed in Aperture 1 and 1.5 up until the 1.5.6 upgrade which seems to have fixed it, but then with Aperture 2 the problem seems to have returned. At least that's the gist of what I've been reading on a number of threads. Whatever the case, I hope Apple gets this sorted out in their next update!
    As it appears there is no proper answer to this problem at the moment, I'm gonna go ahead and mark this thread answered (and since you were kind enough to at least take the time to reply RB, you can be credited with the answer... thanks!).

  • No new version when modifying a TIFF?

    I exported CR2 to PS, returned the TIFF to Aperture. But when I make a change in the TIFF, it produces another version.
    "Create new versions when making adjustments" is NOT checked.
    Is there anyway to modify such a TIFF without having another version created?
    Thanks

    Hi,
    Not wishing to be pedantic but helpful here. The version is not a ghost in one important sense: it is a collection of edit instructions to apply to the underlying master. Hence it is mere kb in size vs the TIF or RAW or even JPG master.
    It also explains some of the lag between clicking on a version thumbnail and seeing the resulting image fully rendered and available for further editing. The more complex edit instructions and the more of them (spot/patch, straighten especially) will give rise to a slower rendering of the image .... which is where Previews come in useful to give a better feel for the image while all the instructions are being applied in the background.
    That said, the Aperture engine is still slow for spot/patch and straighten edits especially, but this must be balanced against the disk I/O time that would be consumed reading multi-Mb RAW or TIF files. Oh for instant disk access and read time with infinite processing capacity!

  • Create new version, checkout, checkin workflow not correct via abap

    Hey,
    I wrote an abap programm with the following workflow:
    - I create a new version of the document CVAPI_DOC_CREATE_NEW_VERSION
    - I check out the new version with CVAPI_DOC_CHECKOUTMODIFY
    - I check in the file with the new content CVAPI_DOC_CHECKIN
    And now there are 2 files in DMS with the same version. But there should be only one document with version 01.
    The method CREATE_NEW_VERSION creates an dms document. But also the CVAPI_DOC_CHECKIN method creates an document in dms. But the checkin method should override the new version.
    Thanks for your support.
    BR,
    Christoph

    Hi Christoph,
    unfortunately it is very hard to suggest a detailed solution for your individual program. Personally I would recommend you to
    use the following sequence:
    - I create a new version of the document CVAPI_DOC_CREATE_NEW_VERSION
    - BAPI_DOCUMENT_GETDETAIL2 to read out the current document data
    - I check out the new version with CVAPI_DOC_CHECKOUTMODIFY
    - BAPI_DOCUMENT_GETDETAIL2 to read out the current document data
    - I check in the file with the new content API_DOCUMENT_MAINTAIN2 or BAPI_DOCUMENT_CHANGE2.
    If you enter the storage category in the table DOCUMENTFILES of the mentioned function modules the file should be
    checked in again. For further information on the DMS BAPI behavior please see the attached documentation to SAP note 766277.
    Best regards,
    Christoph

  • During PO creation system should not allow to save if it cross the PR value

    Hi,
    As I said in above subject line while creating the PO system should not allow to create more than the PR value and Quantity.
    Always system should allow the person to create the  Po with in PR value as well quantity in order to set up please let me know the configuration settings.
    thanks in advance.

    Hi,
    Please search the forum first for your queries for existance and then post queries., coz, the same question has been answered so many times before.

  • System should not allow to do the changes in PO once the ID created.

    Hi All,
    Once the Inbound Delivery is Created based on the Purchse Order, System should not allow to do the changes in the Purchase Order like Deletion of Item, etc..
    Any Configuration Changes is avaliable. ?
    Regards,
    Sudhakar

    Dear,
    Please check the staus in order
    Current order status xxxx does not allow goods receipt (Message no. C6009)? is this the message?
    This will not allow you to do GR for production order when you activate status profile "SAT1" in the production order. After that when you confirm order it will automatically assign next user status i.e. "SAT2" (if not assign it manually in CO02) it will allow you to do GR for that production order.
    Regards,
    R.Brahmankar

  • In pages(not the New version) footer is over to the left, so when i put the page numbers in they don't sit right. How do i move the footer

    In pages(not the New version) footer is over to the left, so when i put the page numbers in they don't sit right. How do i move the footer

    The footer is not only to the left. To get the page number to the right you can use Format > Align right. That will make all page numbers move to the right. Is that what you want?

Maybe you are looking for