Difference between implementation, support & upgradation projects

Hello Friends,
                I am new to SAP. Can anyone tell me what are implementation, support & upgradation projects..what are the differences between those projects? what is role of ABAP developer in these projects?
Regards,

Hi,
SAP Implementation: SAP Implementation is the whole of processes that defines a complete method to
implement SAP software in an organization. It is based on best practices and case studies from various
literature sources and presents a collection of processes and products that make up a complete
implementation method to allow any organization to plan and execute the implementation of SAP (ERP)
software.The SAP implementation process is made up out of four main phases, i.e. the project preparation
where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase
where the solution stack is created and training is being performed, a functional development phase and
finally a final preparation phase, when the last tests are being performed before the actual go live.
ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given
by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases.
Sometimes ABAPer may be asked to do a technical research for an optimal solution.
SAP Support: After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application.Ticket is like a request for changes/bug fixing or a request for a new
ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
SAP Upgrade: SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one.Some times might need to work on SAP notes too.
Hope this helps.
Thanks,
Srinivas

Similar Messages

  • Difference between HR support packs and EHP.

    Can anyone tell me the difference between HR support packs and EHP

    Hi Harish,
    Enhancement Packages-  SAP enhancement packages for SAP ERP are optionally installed software innovations for SAP ERP 6.0. They include functional enhancements, industry specific functionality, and simplifications u2013 for example, to the user interface. With enhancement packages, you can easily adopt ongoing SAP innovations at a lower cost than full upgrades. In addition, enterprise services are delivered with enhancement packages.
    Support Pack  - If the same or similar bug is reported by multiple clients or end users, then SAP recognizes such bug corrects them and collects all these corrections in one place and adds some enhancements to the earlier version of SAP and then calls this as a SUPPORT PACK. In simple words collection of  SAP NOTES is a SUPPORT PACK.
    Enhancement packages are not support packages: Support Packages contain corrections and legal changes, SAP enhancement packages new functionality.
    Do let me know if I helped you.
    Thanks,
    Padmaja.

  • In the shared variable properties box, when enabling aliasing, what is the difference between binding to a project variable vs. to a psp url

    In the shared variable properties box, specifically with regard to a the target being an rt target, when enabling aliasing, what is the difference between binding to a project variable vs. to a psp url?

    The difference is in the type of variable you are binding it to.  A project variable is a variable that lives within the specific project in which it was created.  A PSP URL is an address using the Publish-Subscribe Protocol (PSP).  You can learn more about PSP URLs here: http://zone.ni.com/reference/en-XX/help/371361G-01/lvconcepts/using_datasocket_technology/#Specifyin...
    PSP URLs will enable it to communicate between different machines and also between projects which may or may not be open.  The project variable will exist within the project.
    Julian R.
    Applications Engineer
    National Instruments

  • Difference between implements and extends

    Hi all,
    what is the difference between implements and extends. i am sorry to ask this silly question, but i am new to JAVA.
    Thanks
    Balaji

    when you extend a class, your class that you are coding inherits every method and field from the extending class. For example:
    public class CustomFrame extends JFrame {
    //Your class's methods will be in here, but so will all of JFrame's methods.
    }You can override (most) methods from extended classes if you want them to do different things than they normally do. The most commonly overriden methods when using swing are stuff like paint(Graphics g). It needs to be overriden to repaint all of the components.
    When you imlpement something, you have to specify an interface. Interfaces have methods in them with no code. If you implement an interface, all methods in in must be defined. If not, the code will not compile. Some interfaces like ActionListener extend other classes to perform stuff. The actionPerformed(ActionEvent e) method will perform an action when a button is pressed, etc.

  • Difference between Implement and Extend

    what is the difference between implements and extends and why do we use them
    thanks,

    classes extend one other class and implement as many
    interfaces as they wish.
    interfaces extend as many interfaces as they wish.But for all that, they both just mean "inherits."
    There wouldn't even have to be two different words, since you never have a choice between X extends Y and X implements Y. For a given X and Y, only one of the two will be legal.

  • Whats the difference between implements and extends!??

    Can an interface be extended or not??
    If it can whats the difference between implements and extends??
    Thank you!

    Code Sample:
    interface a implements aa{This is illegal. An interface cannot implement another interface. It can only extend another interface.
    interface a extends aa{That's the way to do it. As already said above:
    An interface can only extend another interface.
    A class can extend another class.
    A class can implement zero or more interfaces.
    So, "implements" is only used for classes that implement interfaces. For the rest, "extends" is used.

  • Difference Between A Support User and Super User in CRM

    Hi All,
    May I know what is the difference between a support user and a super user in CRM?
    Please advice, thank

    HI Plaban
    not sure if you answered your own question here?
    Change User - by itself would allow update of address data, user parameters, defaults, etc
    Assign Object - as you mentioned roles and profiles.
    However, if assigning, I think you need to have both actions: change and assign
    I recall (ages ago) that change was only the user details and not the role or profiles. As a result, there were a few threads where people had to update the action for the request type of provisioning would not occur.
    This is something you could test
    Regards
    Colleen

  • Difference between implementation guide and user guide.

    Hi All,
    I am a recent graduate, just wanted to know what is teh Difference between implementation guide and user guide.
    Sorry the question may sound to simple but I am not aware of the aswer.
    Regards,

    Hi,
    The implementation guide is the reference that you need to use to do the functional setup while the user guide covers how the navigation of the module/application and tells you how to use it.
    Thanks,
    Hussein

  • Difference between SAP Reference IMG & Project IMG...

    Hi SAP Gurus,
              Can anyone explain me about the difference between
              SAP Reference IMG & Project IMG...
    Thanks in advance,
    Praveen.

    Hi !
    The SAP Reference IMG contains alle the customizing functionallity of SAP.
    Within a Project IMG you can restrict the availible customizing function.
    Thinking about having an MM project. When you create an "MM" Project IMG you will only "see" MM relevant customizing functions in your project IMG.
    Regards
    Rainer
    Some points would be nice if that helped.

  • Difference between a Solution Manager project, and IMG project.

    Hello,
    We are in process of installing and thereby configuring scenarios for Solman 4.
    While reading about it on help.sap.com, I came across following:
    <b>
    "<i>The Change Tracking function of Change Request Management allows you to track everything that relates to changes within the context of a Solution Manager project, or an IMG project."</i></b>
    Please help me here by clarifying difference between two.
    regards, Shantanu

    Hi Shantanu,
    Let us assume you have captured everything w.r.to an SAP Implementation project in Solution Manager and this project has gone live. Here all details relating to an SAP Project are captured in a Solution Manager Project. Solution Manager project acts as a container to hold all the details relating to the SAP Project.
    Now when this SAP Project comes in the support/maintenance phase, whenever a small change needs to be done to this SAP Solution, it will be raised as a Change Request. This change request will be captured in Solution Manager (starting from the point when the request was raised from an end user as a support message, which eventually might have evolved as a Change Request). All details about this change request, its approval workflow, task control being transferred to different roles(people), movement of the request along the transport path, everything is captured and controlled in the Solution Manager Project.
    So, we are clear about Solution Manager Project now.
    What is an IMG Project?
    For each and every component involved in this SAP project, an IMG project will be created with the same name as the Solution Manager Project in the component systems. These IMG projects in the Satellite systems are the same as the normal Project IMGs which we use in any SAP Project to hold all details relating to an SAP Project w.r.to that component.
    In the context specified by you, it has been told that any changes w.r.to a Solution Manager project or an IMG project can be tracked in CHARM. It is because any change that is requested w.r.to any component(say SRM or ECC) will result in a change in the details captured in Solution Manager project about that SAP Project, and also will result in a change in the details captured in the appropriate Project IMG (say SRM or ECC).
    Hope it is clear.
    Dont forget to reward points for useful answers.
    best regds,
    Alagammai.

  • Difference between a folder, a project and an album?

    I've been using Aperture a lot and feel like I have a good handle on the way it works and looks at the world. One question I come back to is what are the exact differences between Folders, Projects and Albums?
    Check these assumptions/beliefs/misconceptions:
    - an album can contain versions
    - a project can contain albums
    - a folder can contain projects and albums and other folders
    - a project can contain a folder
    - if I 'move' (drag and drop) a version from one album to another, then it in fact disappears from the first one and appears in the second one
    - but other combinations, like from an album to a project, etc. produce other results
    - if a folder contains two albums, and I brows the folder I see all the versions in both albums
    ... I am not sure what the differences are and why I couldn't do all of it just with folders.
    ... I also don't see the rhyme or reason to how each works
    Any pointer, link or explanation would be greatly appreciated!!
    Thanks,
    Pito

    I'm partial to that one, too.  .  The formatting got busted when Discussions were upgraded.  Anything between plus signs should be in italics.
    Here it is correctly formatted:
    The Well-trod Path. Walk it unless you have a map for a different route.
    The Library is your image database. It contains all the information Aperture has about your images: where they are stored on your computer/drives/network, how you have them organized within Aperture, what adjustments you have made to them, all the pre-Aperture metadata (EXIF, IPTC, keywords, etc.) they had before you imported them into Aperture, and all the Aperture metadata (Version names, ratings, color labels, Stacks, additional keywords, etc.) you assign to them from within Aperture. The Library also contains small copies of each image (in effect, thumbnails, but in Aperture larger than actual thumbnails and called "Previews").
    The image is the core record in your Aperture database. The database is a giant list of images with a whole bunch of information assigned to each image.
    Within Aperture you can view individual images and any grouping of images. You can create a group based on any of the information you have about your images.
    The Project is your primary image holder. It has a unique, privileged relationship with your images: Every image must be in a Project; No image can be in more than one Project. You should make a Project from every actual, out-in-the-world photo shoot that you do. Shoot=Project. Stick to this (the mis-naming of "Project" is one of the worst interface decisions made in Aperture).
    You will regularly want to view your images in groups other than the Project in which they reside. Aperture provides several specific containers for this (as well as superb tools for creating ad hoc groupings). As a family, those containers are Albums. Aperture includes (regular) Albums, Smart Albums, and the following albums dedicated to special tasks: Book, Light Table, Slide Show, Web Journal, Web Page. Any image can be in any album, and can be in as many albums as you want.
    As your Aperture database grows, you will want to organize your Projects and Albums. Aperture provides Folders to aid you. Folders hold groups of Projects, Albums, and other Folders. Folders cannot contain images which are not in a Project or Album: You do not put images in Folders; you put containers in Folders.
    The organization of your image database is entirely for you to customize for your needs.
    There are two additional pieces of the Aperture puzzle every new user needs to understand in order to make good use of it.
    In additional to what I listed above, your Library may or may not contain your original image files. Each image in Aperture has an original. Aperture is non-destructive -- your original image files are never altered. If the original image file is contained within your Library, it is called a Managed Master (Aperture's pointer to this file, and the file itself, are both inside the Library). If the original image file is not contained within your Library, it is called a Referenced Master (the pointer in your Aperture Library points to a file outside your Aperture Library). Referenced Masters bring some important advantages -- but the new user of Aperture can rely on Managed Masters until the need for Referenced Masters arises. Aperture makes is easy to convert your original image files back and forth from Managed to Referenced.
    A Version is the name given to the variants and copies you make of you original image within Aperture. You use Aperture's tools to make Adjustments to images. Each group of adjustments you make to one image is saved as a Version. You can (and should) create as many Versions as you need. Versions appear as images, but are simply text instructions which tell Aperture what Adjustments to make to the original image file. Aperture presents these to you on-the-fly. This is brilliant. It means that Versions are minuscule compared to Masters. The gain in storage and computational efficiency is enormous.
    This also means that your images in Aperture do not exist as image format files. In order to create an image format file, you must export the image from within Aperture. There is no reason to do this until you need an image format file outside of Aperture.
    Aperture, then, is best understood as a workspace for
    storing
    organizing
    adjusting
    preparing for publication, and
    publishing
    digital photographs.
    Your workflow is
    shoot
    import as Project(s)
    add image-specific metadata
    organize into Albums, organize Albums and Projects with Folders
    make adjustments to images (crop, rotate, change exposure, etc. etc. etc)
    prepare for publication
    publish.
    HTH.
    Thanks for posting the link.

  • Difference between implements thread and ex

    what is the difference between extending the thread and implements the runnable interface..?

    Not much. One reason to prefer implementing the Runnable interface as oppossed to extending Thread is to allow your class to extend a diifferent base class if you choose to do so. Since Java supports single implementation inheritance it is always a good idea to implement Runnable as oppossed to extending Thread in case you want to extend some other class, besides Thread, now or in the future.
    Some OO purists may also claim that unless your class (that extends Thread) "is a" specialized Thread that extending Thread breaks the OO sematics of the "is a" relationship that inheritance is suppossed to represent. For instance a widget class that draws a pixel randomly on the screen that needs to be run in it's own Thread really isn't a specialized Thread class.

  • Difference between contract creation and project creation

    I am new to Oracle Projects. In Oracle Project Contracts I can see that we create a new contract. Also in Oracle Projects we can create a new Project.
    Can anyone please let me know what is the difference between creating a contract and creating a project in Oracle Projects.
    Can we create a project based on an already created contract?
    Regards

    Hi Dina,
    thanks for your reply. We are currently implementing Oracle Projects in our company where our main business is construction works.
    As you have said that a contract is a commercial agreement between the customer and the contractor. We get a Bill of Quantities(BOQ) along with the contract documents. In the BOQ all the different types of works for the project is defined along with the quantities which are known as BOQ Items. We have to quote our rates for the BOQ items. We generally perform an operation called Rate Analysis of these BOQ Items by assigning various quantities of resources that shall be required to execute each of the BOQ items. Thus we arrive at the cost of each BOQ items. Once the work gets executed, this BOQ happens to be the basis for invoicing or application to the client. So we create our budget based on the BOQ itself. We make our Business plan based on the items of this BOQ itself and also book the expenditure on these BOQ items.
    Although we create Project plan using Primavera, there is no one-to-one correspondence between activities of the project plan and the BOQ items. So we cannot really create our budget based on the project plan.
    So if we manage everything only on the basis of the BOQ items, we loose important project management related information like earned value management etc. And if we depent only on the Project plan we loose important cost related information.
    So we need to plan in such a way so that both these are fused together.
    Can you kindly advice me about how to proceed ahead with our implementationso that we can use Oracle Projects optimally for our business.
    Thanks & Regards

  • Functionality differences between Principal Toolbox & Ms Projects 2010

    Hi there,
    I'm looking for some advise about the functionality differences between Principle Toolbox (planning module) & MS Projects 2010.
    Currently I'm working at an IT company where my project managers use MS Projects 2010 to plan their activities for their projects. 
    My management wants to know what the differences in functionality are between the two programs. I'm not looking for answers like "different GUI", but (for example) I would like to know what functionalities can you use with MS Projects and can not
    use with the Pincipal toolbox. 
    I hope someone, who has experience with both programs, can give me some good advise.
    Thanks in advance

    Hi,
    I've never worked with Principle Toolbox but here are 2 interesting comparisons which you might already know:
    http://project-management-software.findthebest-sw.com/compare/3-21/Microsoft-Project-vs-Principal-Toolbox
    http://www.itqlick.com/index.php?module=Products&pname=internalcompare&prod1=112&prod2=2395
    I think the main concern should be that Principle toolbox doesn't offer a cloud solution.
    Hope this helps,
    Guillaume Rouyre, MBA, MVP, P-Seller |

  • Differences between 1st Gen + upgrade and 2nd Gen?

    Hi all. I was looking into purchasing a new iPod touch, but before I do so, I was wondering if there is any difference between getting an iPod touch 1st generation and purchasing the software upgrade and simply purchasing a 2nd generation? Reason being that I can get a 1st gen much cheaper than the $10 that it would cost to get the software upgrades, so if I can do that it would be great.
    So is it a seamless upgrade or will there be some small differences between the two? Thanks in advance for the replies!

    Updating a 1st gen Touch to 2.1 is the way to go if you don't care too much about the primary differences, where the 2nd gen Touch has the speaker, external volume control, and slimmer at the edges. I've had both and am glad that I have updated to the 2nd gen Touch.
    Note that the 2nd gen Touch does not have the same charging circuit as previous iPod models, so if you have 3rd party chargers that rely on the 12V (firewire) pin on the iPod's dock connector, those won't work. For the 2nd gen Touch you need to have "Made for iPod" designated charging accessories which use the 5V (USB) pin of the connector. Chargers don't specify which pin of the connector they use, so if you go with a 2nd gen Touch be sure that any accessories you buy for it are designated specificatly for the 2nd gen.

Maybe you are looking for