Version of sp stacks

hi all ,
i m trying to download the kernel for our sap system .
in system->status , component version is :sap ecc6.0
stack level of sap_basis is 700 (SAPKB70011)
when searching in market place i dont know under which i should download ,
SAP ERP6.0(SAP ERP 2005 ) : SAPK....xx
SAP Netweaver 7.0                 : SAPKB700xx
we have installed only ABAP server .
i dont know which category this system belongs ..
kindly help me

No ECC 6.0 Contain some components which is a part of the Netweaver platform.
So Ecc 6 is not support all the component as netweaver supports but still it supported many components like netweaver.
Java engine is necessary to support some components like SAP ADS, SAP Mobile. But that doesn't means that if java installed in SAP ERP 6.0 then its called netweaver.
Netweaver supports enterprise portal, MDM, BI etc. which is not supported by ECC 6
refer Difference between R/3 4.7, ECC5 & ECC6 anyone?

Similar Messages

  • How do I select one version from multiple stacks and export?

    I have a color copy and B&W copy of 800 images. I want to export the B&W versions only. How do I select just the B&W versions in the stack at one time without having to click on 800 images?

    If you check the filenames, you'll see that the versions have a version name tagged on the end, like "Version 2" when I did a quick monochrome mix of one of my own. Make a smart album with the search term set for text being "Version 2" and you should end up with all the b&w versions. That is, assuming you made them all in the same way and they're all Version 2 versions. Since the initial version would not have the term "Version" attached, you could make the search term "Version" and it would fill with all the 2nd and 3rd et al. versions.
    Just a thought. Give it a try.

  • Since upgrading to Aperture 3.3, when I try to sync photos to my iPhone, I'm getting all versions in a stack loading onto my phone, which makes for some ugly pics, as well as taking up nearly double the space.

    Since upgrading to Aperture 3.3, when I try to sync photos to my iPhone, I'm getting all versions in a stack loading onto my phone, which makes for some ugly pics, as well as taking up nearly double the space.

    Could it be the problem lies with iTunes and not Aperture?  iTunes 10.6.3 was released on the same day as Aperture 3.3 --  June 11.
    If someone has a configuration to test an older version of Aperture with iTunes 10.6.3 to see if the problem exists, that could be helpful.

  • Support Photoshop Elements 5 Stacks and Version Sets

    I would like to see stacks in Lightroom that work the same way as those in the Photoshop Elements 5 Organizer. PSE5 stacks are far more capable than Lightroom ones. (Can stack across multiple folders, can include version sets in stacks, etc.)
    Additionally, I would love to see support for PSE5 Version Sets. These are similar to the "Stack with original" option, but work more smoothly (latest version is always automatically on top, for example).
    Since Adobe has already implemented these in PSE5, you would think it would be pretty simple to also include them in Lightroom.

    Please post Photoshop Elements related queries over at

  • Aperture 3.3 Bug: Syncing Stacks Syncs All Versions, Not Just Pick

    Aperture 3.3 has a pretty significant bug.  Syncing to iOS devices results in all versions in a Stack to be synced to the device, not just the Picks.  This is a HUGE problem as two things happen:
    1) The amount of space consumed by the versions can be increased several fold.
    2) There can be incredible redundancy when viewing photos on iOS devices because of all the extra versions, in many cases the versions may be indistinguishable.
    Does anybody have a work around for this, or know if Apple has acknowledged this bug?

    I've run into the same problem, and it also affects the Apple TV -- my screensaver slideshow started to look pretty strange when all of the extra versions in my various stacks began appearing
    Anyway, I have found what may be an acceptable workaround.  Since iTunes is only using the previews in Aperture, it will exclude any images for which previews do not exist.  So, if you choose the non-pick images in each of your stacks and delete their previews (right-click and choose "Delete Previews") they will be removed from any albums that are syncing to your iOS devices or Apple TV.

  • Modifying Version Set and/or Stack Attributes

    My Photoshop Elements (PSE) 5.0 catalog has many version sets and stacks.
    Contrary to my expectation, I recently learned that that edits to the top photo's attributes (e.g. Date, Caption, Notes, Tags, etc.) did not translate through to the underlying photos of the associated version set or stack. As a consequence, subsequently moving a different photo to the top of a stack or version set can lead to loss (or at least displacement) of these important attributes.
    Is there a way to get PSE to automatically copy attribute changes through to the underlying photos or at least to ask the user if (s)he wants edits to translate through the version set or stack? If this feature is not currently available, I think it would be a significant value-added enhancement to the product.

    Users tend to use software differently and to have differing needs and preferences. Barb's point is valid in that, should Adobe provide the ability to assign attributes 'through' a version set or stack, the feature would warrant a user prompt or preference setting to acomodate user's differing needs and preference.
    Exceptional software, like PSE, anticipates and supports user needs in an efficient and predictable manner. Version sets, almost by definition, can be expected to have the same date, time, tags, captions and notes. Stacks - perhaps to a lesser degree.
    Forcing users to perform tasks in a specified sequence (e.g. adjusting attributes before version sets or stack generation), or to expand stacks or version sets to assign attributes through to underlying photos, seems unnecessarily tedious and inconvenient. For instance, expanding version sets and stacks forces users to aboard current search criteria.
    Anyone who has imported large batches of scanned negatives or slides which contain no meaningful metadata (with PSE set to auto-correct red-eye and to recommend stacks) knows how easy it is to generate version sets and stacks BEFORE the user begins the process of attribute assignment or correction.

  • New Stack Version is available

    Just in case anybody missed it, stack version 5.10.01 is now available from:

    Nothing will happen. I suppose the new version of Bluetooth stack supports new features and options. Thats all.
    On this site you will find more details:

  • Version Automatically on Top of Stack?

    I may be dreaming, but I seem to recall in the early days of Aperture 3 (obviously not long ago), that whenever I created a version, by cropping, adjusting, etc, that new version was automatically placed on top of the stack.
    That was very useful since when I edit a photo, I consider the edited version as my new number 1.
    Now, however, the new versions seem to be placed at the end of the stack, requiring me to move them to the top.
    Anyone have any comments on whether or how new versions can be set to automatically be placed on the top of a stack?

    Gary wrote:
    Gary -- Thanks for the numbers. Numbers are good to have.
    PS I've also been using Stacks for grouping bracketed (and panoramic) sets. But I've also been using them for grouping adjusted versions. It doesn't seem to be quite working out - for me - so I might have to revise that.
    My experience (limited, but aware) has been that, for each of the many grouping or binning functionalities in Aperture, I am always best served by choosing one and only one purpose. Your use of Stacks illustrates the problem: are Stacks for
    . making picks among burst or bracketed shots?
    . grouping panoramas and HDR singles (etc.)?
    . grouping development versions of an image?
    Stacks provide a sophisticated binning functionality (group, rank, collapse/expand) that is applicable to several tasks. Unfortunately, there is one and only one type of Stack, and no (easy) way to distinguish them. (One can easily imagine three kinds of Stacks, one each for the grouping needs listed above.) Am I right in assuming that this is the problem you imply with "+It doesn't seem to be quite working out+"?
    For me, helping to winnow my photographs is the most important function I can assign to Stacks. I stack very similar shots, select the best of the Stack and promote it to the "Pick", and then go through the Project (I use one Project for each shoot) with Stacks collapsed and select the best among the Picks and the non-stacked shots.
    (My "flower bed" is, from subsoil to bloom:
    . Rejects
    . All non-rejects
    . Stack Picks and non-rejects
    . Best of Project ("Selects", which are Project-specific)
    . Selected for printing, export, publication, sale, etc. (Selected Selects -- which I move to Albums)
    That leaves several things to address: how to handle bracketed shots, panorama shots, HDR shots, focus stacking shots, and, not least, Versions.
    Shots bracketed in order to increase the odds of a proper exposure are easy: they get treated just like other Stacks. Stack 'em, pick the best, move on.
    The other groupings I deal with in an "extra-computational" way: I remember that this stack is for a panorama (for instance). Then when I create the panorama I import it and put it in the Stack with the shots which comprise it, and make it the Pick. The "extra-computational" part is, clearly, a kludge, but a livable-with one.
    Version-stacking muddies this tremendously (especially when the version is already in what I might call a "Picking Stack"). *I actually think that Aperture should add a specific and visually identified method of Version-stacking separate from the existing Stacks.* Every image whether inside or outside a user-defined Stack should have it's own Version stack. (Correct me if I'm wrong, but all Version of an image must be in the same Project, no?)
    If I care to Pick two Versions in a Stack (either a Picking Stack or a Versions Stack), I split the Stack.
    What is your Stacks workflow, and how might you revise it?
    I'm also very curious about other's use of color labels. I find them queer, due to the fact that any image can have +one and only one+ color label. There is no set of useful identifiers I can think of which has 8 non-overlapping bins (I assume I am missing something terribly obvious). I tried using colors for different sets of identifiers, but failed at each because there were always images to which I wanted to assign two colored labels. I've ended up using the colors to assign steps along the progression of image development (Develop!, Developing (some adjustments applied but not done), Problem, Developed, Redevelop!, Redeveloped, Abandon, Not yet flagged).
    This works well for me, because I am able to maintain separate identifier sets for development progression and image rating (I use the built-in stars). I can have good images not yet developed, developed images down-rated, images waiting to be rated or developed, and so on. What do you do?
    Need I apologize for the ramble? I really want to set up a workable system that I then won't have to worry about for a couple of years and tens of thousand of images. Thanks for reading and any replies you might make.

  • How can I reorder the stack with the best version on top of the stack?

    when i stack the original appears to be on top. i would like the best version to be on top-
    say for example the one rated with one star. can i do this?

    Yes this is really easy - this is called the stack pick and you can choose it either in the stack menu or using the command-\ short cut. You can also choose a different pick for each and every album the stack is in (say a black and white version or a cropped version) using the stack menu or the shift-command-\ shortcut.
    There are also short cut keys and menu options to promote or demote items within the stack order.
    Also check out stack mode when looking at your images.
    Check this out:
    [Aperture Stack Mode|>
    There is a bunch of other stuff related under Aperture workflow as well.

  • ARW to DNG & JPG: organizer versions/stacks?

    I shot a bunch of photos raw only semi-inadvertantly. (Been looking for an excuse to figure out a raw workflow, guess I found it.)
    So I've figured out how to use PSE Organizer 12/PSE 12 to batch the ARW to DNG then JPG or straight to JPG. Easy enough. (Though someow the first time through I ended up wioth two DNGs for each one. Still not sure exactly how I did that...)
    But that path seems to be complely divorced from the Organizer. I'd like the ancilary products (DNG/JPG) to be saved as Version Sets or Stacks with the original raw files. No Joy. I tagged the ARW and did the whole face recognition thing with the raw files. I'd like that metadata to somehow pass forward to the DNG/JPG. No Joy.
    Am I missing something? Just not supposed to batch this? (Given number of files, sigh.) Not supposed to tag anything at the raw stage? Just not suppsed to use Organizer? Expected to separately import the ancialary products into Organizer and stack them myself?

    Dick W wrote:
    I shot a bunch of photos raw only semi-inadvertantly. (Been looking for an excuse to figure out a raw workflow, guess I found it.)
    So I've figured out how to use PSE Organizer 12/PSE 12 to batch the ARW to DNG then JPG or straight to JPG. Easy enough. (Though someow the first time through I ended up wioth two DNGs for each one. Still not sure exactly how I did that...)
    Can you detail your steps to batch the ARW raw files ? The usual way in the organizer is the 'export' function, and in the editor it's the 'process multiple files' option in the file menu.
    But that path seems to be complely divorced from the Organizer. I'd like the ancilary products (DNG/JPG) to be saved as Version Sets or Stacks with the original raw files. No Joy. I tagged the ARW and did the whole face recognition thing with the raw files. I'd like that metadata to somehow pass forward to the DNG/JPG. No Joy.
    Am I missing something? Just not supposed to batch this? (Given number of files, sigh.) Not supposed to tag anything at the raw stage? Just not suppsed to use Organizer? Expected to separately import the ancialary products into Organizer and stack them myself?
    One important thing about saving to DNG. There is no way to save in version sets with the original raw files. Why do you want to save as DNG ? I don't see a way to batch convert raw files to DNG from the Organizer. You can open several raw files in the ACR dialog of the editor and use the 'save' button to save all selected raw files to DNG. If you save to a 'watched' folder, you'll be prompted to add those DNGs to the catalog. Once in the organizer, you could stack them manually with the originals.
    To batch convert raw files to DNG, I would use the free Adobe DNGconverter software; it's a standalone program which runs outside of Elements.

  • Can customers rebuild an Exadata machine with the latest stack versions?

    There’s a possibility that we’ll be purchase two new Exadata machines (X3) in the near future. I'd be getting very excited if I wasn't already entirely swamped :)
    If it happens, we’ll be asking Oracle to install the latest and greatest of the software stack when they arrive on-site with our new toys. Currently, this means:
    <i>OEL: 5.7 (with latest kernel)
    ESS: (write-back FC, mmmmm!)
    Our current Production database is on a V2 machine and has the following versions of the stack:
    <i>OEL 5.5
    RDBMS/GI BP7</i>
    We are hoping, once the dust settles, that we can re-purpose our existing V2 machine as a Development environment. However, in order for that to be of any use, we need the software stack to match what will be running in Production on the X3s.
    As far as I understand, the upgrade path is as follows (as per 888828.1)
    <i>Upgrade the O/S to OEL 5.7 and the latest kernel on storage cells and comp nodes
    Upgrade the firmware on the IB switch to 1.3.3-2 (which we already have)
    Upgrade the Exadata Storage Server on the storage cells and comp nodes to
    Install the GI and RDBMS binaries
    Upgrade ASM from to
    Install the RDBMS binaries
    Make/move/restore/copy Development onto the newly-upgraded V2 machine.</i>
    I’m wondering whether it’s better for us to upgrade the V2 machine from our current versions of the stack to the latest or whether it’s better to attempt a rebuild?
    As a customer, are we able to rebuild the stack ourselves with the new software or do we have to have Oracle come in and go through their installation process (we are putting a different version of the stack on than we presently have)?

    frits hoogland wrote:
    I don't understand the answers.
    A V2 Exadata system (and up, X2, X3) is full supported up to the newest Exadata software releases, so you just can upgrade. Of course you need to check with MOS 888828.1 what path to take (not all software might be upgradable to the latest release in one go). Need need to puzzle, just upgrade.I'm fairly sure that we would be able to upgrade - in fact, when we weren't entertaining a hardware upgrade earlier in the year, I had planned out a upgrade path from our current versions to what was the current stack before the FlashCache became write-able.
    We didn't have much of a choice at this point because the V2 was planned to be our Production environment for the foreseeable. Our upgrade was possible, but would have been relatively cumbersome as we would have had to upgrade the O/S, the ESS on cells/nodes, the GI and then the RDBMS in chunks to satisfy the various pre-requisites.
    My question was whether it was possible/better/cleaner to simply rebuild the whole box with the latest software stack instead of upgrading now that the V2 environment is likely to be designated for Development if we get the new hardware and there isn't the associated pressure of it being a Production box.
    If you want to change the space ratio between DATA and RECO, the easy path is to delete all the databases, remove the data and reco diskgroups, remove the grid disks on the cells, and create them again, and create the diskgroups on top of it. This also can be done online by dropping the griddisks per cell/storage server in ASM, recreating them with different sizes, and get them in ASM again.I believe that Tycho said he had to choose between upgrading the stack AND change the space ratio between his diskgroups OR just rebuild the system from scratch: and he chose to rebuild.

  • Stacks, versions, links, albums, projects, grief.

    I'm having some confusion. I want two versions, one cropped, one not cropped. I want one album to have all the not cropped versions and another album to have the cropped versions.
    If I stack the versions, then the stack exists in both places. Changing the head of the stack in one album or project changes it in all the others. This would seem to be a bug according the "getting started" pg 76, "the version set pick is specific to the album it's in".
    What I really want to do is take a set of shots, dup'em all, and crop them all to a particular aspect ration. Then do it again for a different aspect. I'm happy with cropping them manually, but I can't figure out how to dup'em all short of doing something dreadfully dreary like copying them one at a time, breaking the version set, manually flagging one of the version set one way and the other another so that I can search sort them into different albums.
    Is there a better way to manage this? Is there any way to get aperture to actually "create new versions when making adjustments"?

    I would do the following (quite straightforward):
    - Take a fist pass at cropping; that will create
    "Version 2" for each image
    No, this simply edits the first version, the one with no "version X" after it.
    - take a second pass at cropping; set "new version
    from master" for that run
    This does the same thing, whether "create new version on adjustment" is set or not. So again, the first version is changed.
    - ... Keep going like that....
    Then run a query where you search in the Query-HUD
    for all versions that end with "version 2" or
    "version 3" etc. Just go ino the HUD, click on "other
    metadata" and set Version ends with..."Version 2" for
    Does that work for you?
    Nope. The only time I've ever seen a "version 2" was when I manually duplicated a version. How else can you create them?

  • Aperture - multiple versions

    Hi all,
    As you might know, Aperture easily gives one the possibility to create multiple versions of a photo, e.g. a B&W version, a color cropped version,... In Aperture these photos are grouped in a stack - but can be considered as independent photos.
    When switching to the Pages (or Keynote) one has the possibility of easily importing images into a document through the media browser - with some reservations to the resolution though - see my other post:
    However: the media browser only shows one version of the stack (the one that is the top one in the Aperture stack) - rather inconvenient at times.
    Until now I only found 2 solutions that work through the media browser: re-order the photos inside the Aperture stack and quit-restart Pages to refresh the media browser; or unstack the images in Aperture such that the media browser (once refreshed) sees them as independent images.
    Another way would be to export the versions one wishes to use as separate images - which at the same time bypasses the resolution issue with the media browser.
    But again: this renders the media browser rather useless...
    Any hints?
    Many thanks in advance,
    15" Powerbook G4 1GHz   Mac OS X (10.4.9)   ...saving for a 17" MacBook Pro

    I am having the same problems, but with only one set of photos (same date only). And, although I love cheerleaders as much as the next guy, I don't need 250 versions!!!
    1. These photos are in a project containing 3800 photos.
    2. The project has .CRW (D60) and .CR2 (1DMkII) files.
    3. The problem files are .CR2 files (only for this date).
    4. All other files from different dates don't create the same problem (.CRW or .CR2).
    5. Aperture Libraray is on internal 300GB SATA drive (not on system drive).
    What I tried:
    1. I removed 3rd Party Ram (Apple blames all my problems on this, but everytime I remove it the problems persist. Another story).
    2. Repaired Permissions.
    3. Rebooted.
    4. I created a new user. Still have the same problems.
    5. Yes, turning off 'Create New Version.....' stops this, but I like having new versions for compare.
    Anyone with similar setups and issues?? Any fixes?? Is Apple still working out a way for us 6600 card owners to upgrade??
    Quad 2.5, 6600, 4GB ram   Mac OS X (10.4.5)  

  • Abap and java stack together gives error message...

    I am trying to install abap stach and java stack together.
    I installed abap was without problem but when I install Java i get the error below.
    I tried SP09 and since it didnt work Sp07 also since I had it with me downloaded before.
    Any help ??? Got stuck
    I need to install together to practice webdynpro...
    INFO 2006-11-30 15:10:12
    An error occured and the user decided to rety the current step: "|NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect".
    ERROR 2006-11-30 15:10:14
    FJS-00003  TypeError: this._name has no properties (in script NW_Java_OneHost|ind|ind|ind|ind, line 8987: ???)
    INFO[E] 2006-11-30 15:10:13
    FSL-02077  File system export (share) saploc does not exist.
    ERROR 2006-11-30 15:10:14
    FCO-00011  The step collect with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect was executed with status ERROR .
    THis error was gone when I used the registry cleaner for removing ABAp stack But now question is How do I install BOTH????
    May be the instance number is the problem....
    In old version of ABap stack we can enter the instance number .But not in SP 9 .Can we change here too?
    This file holds the Key of the errors since it checks for the instance number which is given in the log as details.. May be we can change it....
    In ABap STack install instead of files as in SP 07 they have created an image and may be this si the reason that
    we cannot customize.I have to find a way in order to install it...

    i found soltuion myslef THe lates WAS for abap is preconfigured and so its not suitable for abap-java multiple installation

  • How do I create new versions of a large number of images, and place them in a new location?

    I have been using Aperture for years, and have just one small problem.  There have been many times where I want to have multiple versions of a large number of images.  I like to do a color album and B&W album for example.
    Previously, I would click on all the images at one, and select new version.  The problem is this puts all of the new versions in a stack.  I then have to open all the stacks, and one by one move the new versions to a different album.  Is there any way to streamline this proccess?  When it's only 10 images, it's no problem.  When it's a few hundred (or more) its rather time consuming..
    What I'm hoping for is a way to either automatically have new versions populate a separate album, or for a way to easily select all the new versions I create at one time, and simply move them with as few steps as possible to a new destination.
    Thanks for any help,

    in addition to Kirby's and phosgraphis's excellent suggestions, you may want to use the filters to further restrict your versions to the ones you want to access.
    For example, you mentioned
      I like to do a color album and B&W album for example.
    You could easily separate the color versions from the black-and-white versions by using the filter rule:
    Adjustment includes Black&white
    Adjustment does not include Black&white
    With the above filter setting (Add rule > Adjustment includes Black&White) only the versions with Black&White adjustment are shown in the Browers. You could do similar to separate cropped versions from uncropped ones.

Maybe you are looking for