Process of implementation project

hi friends
i am deva
what are the steps invloved in implementation of a project?

ASAP methodology
ASAP METHODOLOGY:
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/frameset.htm
http://www.sapfans.com/sapfans/asap/be_01_e.htm
http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf
ASAP Roadmap (SAP Help)
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
ASAP Methodology & ASAP Roadmap (SAP Service Marketplace) - Requires OSS Login
http://service.sap.com/asap & http://service.sap.com/roadmaps

Similar Messages

Charms Process in Implementation Project

Hello Gurus,
I am part of an implementation project for where we are implementing various functionalities of Solution manager.
Here we are in the process of implementing CHARMS in the Implementation Phase.
So I have created a project of type 'Implementation' and has already activated Charms.
Here the task list is already created and active
Following are the issues which i am facing while creating a change request.
1: If I create a change request of type 'SDCR' and authorize the change request, a normal correction of type 'SDMI' gets created automatically. But system throws an error 'No Maintenance cycle is open for the current system'
I believe for a project of type 'Implementation' ,maintenance cycle doesnt get created, instead an implementation cycle gets created.
So Let me know if i have missed out any configuration. or if possible can u suggest me if there is any workaround for this?
Regards,
Anubhav

Hi Raquel,
Thanks for the reply.
I have only activated BC Set 'SOLMAN40_CHARM_BASICFUNC_001' prior to activating CHARMS.
After Activation Charms A project cycle of type 'SDDV' also got created along with the task list.
But when I try to create a change request of type 'SDCR', it is automatically creating Correction of type 'SDMI'
Also I had selected the correct Subject option 'Development (Implementation)' in Transaction SDCR
Am I suppose to activate any other BC set?
But why is it giving me error related to Maintenance cycle?
Regards,
Anubhav

Can any one explain about the SAP Testing process in Implementation Project

Can any one explain about the SAP Testing process to be carried out by BW Consultant in an Implementation Project which is in Testing Phase..

hi bharat,
Two types of testing is possible in bw
unit testing
integration testing
Integration testing - It is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.
Integration testing takes as its input modules that have been checked out by unit testing, groups them in larger aggregates, applies tests defined in an Integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
Unit testing - One part or the whole part of transfer rules , update rules, etc..
Integration testing - The whole data flow cycle to be tested
This link will give u detailed description
http://en.wikipedia.org/wiki/Software_testing
Stress testing in BI..
/people/mike.curl/blog/2006/12/05/how-to-stress-test-bw-the-easy-way
REFER THIS REG CATT
http://help.sap.com/saphelp_erp2005/helpdata/en/d7/e21221408e11d1896b0000e8322d00/frameset.htm
Check this doc on Unit Testing
unit testing
Look at the threads below :
Testing Methods in BW
Unit Testing in BW
How to do testing in BW
Hi...BW testing
Re: Hi...BW testing
Hi...BW testing
Pls refer following links...
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e210c8408e11d1896b0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3c/aba235413911d1893d0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e2123b408e11d1896b0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e2123b408e11d1896b0000e8322d00/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/721d6a73-0901-0010-47b3-9756a0a7ff51
https://service.sap.com/upgrade-bw
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7dc0cc90-0201-0010-4fa7-d557f2bd65ef .
https://websmp204.sap-ag.de/~sapdownload/011000358700009385902004E
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/67acb63d-0401-0010-b685-b1b87dd78892
Hope it helps you!
****Assign Points If Helpful****
Regards,
yunus

Steps or process of implementation project

hi friends
i am deva
what are the steps are involved in sap project implmentation in a orgn?

hi,
The ASAP methodology is recommended by SAP for implementation planning and system implementation. It has the following phases.
Project Preparation - The primary focus of Phase 1 is getting the project started, identifying team members and developing a high-level plan.
Business Blueprint - The primary focus of Phase 2 is to understand the business goals of the company and to determine the business requirements needed to support those goals.
Realization - The purpose of this phase is to implement all the business and process requirements based on the Business Blueprint. You customize the system step by step in two work packages, Baseline and Final configuration.
Final Preparation - The purpose of this phase is to complete testing, end-user training, system management and cut over activities. Critical open issues are resolved. Upon the successful completion of this phase, you will be ready to run your business in your productive R/3 system.
Go Live and Support - Transition from a project oriented, pre-productive environment to a successful and live productive operation.
Def:The Accelarated SAP is the implementation solution provided by SAPwhich integrates several components that works in conjunction to support the rapid and efficient implementation of the PROJECT.
PHASES IN ASAP METHODOLOGY
1.Project Preparation
2.Business Blue Print
3.Realization
4.Final Preparation
5.Go-Live and Support.
1.PROJECT PREPARATION WE HAVE 8 STEPS.
1A.SCOPE OF PROJECT
1B.PHASES INVOLVED
1C.SYSTEM LANDSCAPE
1D.TEAM FORMATION
1E.DEADLINES OF THE PROJECT
1F.BUSINESS PROCESS DOCUMENTS (OR) BUSINESS REQUIREMENT
SPECIFICATIONS
IN 1F AGAIN WE HAVE 5 STEPS....Pls dont get confused.
1F ->A1-REQUIREMENTS OR EXPECTATIONS
A2-GENERAL EXPLANATIONS
A3-SPECIAL ORGANIZATIONAL CONSIDERATIONS
A4-CHANGES TO EXISTING ORGANIZATION
A5-DESCRIPTION OF IMPROVEMENTS
1G-TECHNICAL REQUIREMENTS
1H-KICK-OFF MEETING
2 BUSINESS BLUE PRINT . IN THIS WE HAVE 8 STEPS
2A.ORGANIZATIONAL STRUCTURE
2B.DATA COLLECTION SHEETS
2C.DATA CONVERSION STRATEGY
2D.BUSINESS BLUE PRINT DOCUMENTATION
2E.CUSTOMIZATION
2F.ESTIMATION OF DEVELOPERS
2G.COMMUNICATION STRATEGY PLAN
2H.DEVELOP THE SYSTEM ENVIRONMENT
2I.USER ROLES AND AUTHORIZATIONS.
3. REALIZATION . HERE WE HAVE 7 STEPS.
3A.ORGANIZATIONAL CHANGE MANAGEMENT
3B.BASELINE CONFIGURATION & CONFIRMATION
3C.UNIT TESTING
3D.FINAL CONFIGURATION AND CONFIRMATION
3E.FUNCTIONAL SPECIFICATIONS.IN 3E , WE HAVE 3 STEPS AGAIN...
3E1.SOLUTION INFORMATION
3E2.OBJECT INFORMATION
3E3.REVISION HISTORY....WE HAVE 12 STEPS HERE .....
3E3A.DESCRIPTION AND PURPOSE
3E3B.BUSINESS PROCESS DETAILS
3E3C.CURRENT FUNCTIONALITY
3E3D.EXPECTED FUCNTIONALITY
3E3E.SAP SITUATIONAL ANALYSIS
3E3F.ADDITIONAL INFORMATION
3E3G.FORMS
3E3H.REPORTS
3E3I.INTERFACE
3E3J.DATA MAPPING
3E3K.APPROVAL AND MODIFICATION HISTORY
3E3L.ADDITIONAL ATTACHMENTS.
3F.TESTING THE PROGRAMS
3G.PREPARING THE ENDUSER DOCUMENTATION
4.FINAL PREPARATION
WE HAVE 4 STEPS.....
4A.UPLOADING THE STIMULATED DATA
4B.INTEGRATION TESTING
4C.CUTOVER ACTIVITIES
4D.PRE GO-LIVE END USER TRAINING
5.GO-LIVE AND SUPPORT
SIGN-OFF MEETING
CHAN

Solution Directory - How to lock a business process for a implement project

We have Solution Directory assigned to a maintenance project and I understand the checkout/checkin process and how it locks the business process in the Solution. What is the best practice when you are starting a new IMPLEMENTATION project that will impact existing business processes that are in the Solution? I know that I can copy from the solution to build the new project, but it doesnu2019t lock the BP from the solution.
I have a new Implementation project, that i want to checkout/pull existing business processes for the Solution Directory.
*How can these Business Processes be "locked" in Solution Directory as they are with a Maintenance project?*

Kelly,
You would use the maintenance project to make daily modifications.
Consider the case of a O2C business scenario. You need to almost make daily configs etc, which get pushed through, such things will go into a maintenance project.
But if you plan to enhance O2C with a CRM front end or include a better planning solution or TPM or something, then you are looking at an implementation project.
Rule of thumb. Short Scale changes : Maintenance Project, Long term/major enhancements : Implementation Projects.
Also In this case to speak about the lock down. Well the Solution Directory kind of takes care of that for you.
I am assuming that you have a solution populated with business processes. So now if you want to enhance it with a new functionality, you would use an implementation project. So when you define the implementation project, and then navigate to Solar01, and try to add business scenarios , ensure that on the Structure tab you select the Solution as the source. This ensures you are copying content from your current, updated, productive solution. Once you do that, the implementation continues on its track, whilst daily support processes are managed with the check-in / check-out functionality of the Solution and the Maintenance Project.
You technically do not need to lock the business processes down, since the Compare and Adjust functionality of a solution will help you identify the deltas between the Solution and the implementation project and you can always make those adjustments post go-live and thus just update the Solution at one shot. Also remember that with SolMan 7.1 the Compare and Adjust functions can be used with Template, Implementation and Solutions in any permutation-combination.
Hope this helps.
Plz let me know if you need any additional information
Cheers!!

Collect business process requirements in sd implementation project?

how to collect business process requirements in sd implementation project?

how to collect business process requirements in sd implementation project?

Study business process requirements in sd implementation project?

how to study business process requirements in sd implementation project?

Hi chandu,
I will suggest you first go through the document given below
SAP Implementation is the whole of processes that defines a complete method to implement SAP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. 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.
Concept Definition
CHANGE MANAGEMENT ***Activities involved in (1) defining and installing new values, attitudes, norms, and behaviors within an organization that support new ways of doing work and overcome resistance to change; (2) building consensus among customers and stakeholders on specific changes designed to better meet their needs; and (3) planning, testing, and implementing all aspects of the transition from one organizational structure or business process to another. (www.gao.gov)
CHANGE MANAGEMENT DOCUMENTATION All documentation that is required and being delivered whilst performing change management, e.g. the functional test cases and all the other documents a new end-user of SAP requires and the various tools and approaches used to manage change by the TSO. (Anderson, 2003)
COST OF OWNERSHIP ANALYSIS Determination of where and when the costs are inquired within the context of the SAP solution stack and ongoing operations. The analysis addresses all internal and external costs, both one-time as well as recurring (Anderson, 2003)
CUTOVER The process of transitioning from one system to a new one (Anderson, 2003)
CUTOVER PLAN All documentation related to planning, preparing and executing cutover, describing how to lock down the system from a technical change management perspective, preparing the TSO for its new role and rolling out the SAP graphical user interface to all future end users. (Anderson, 2003)
DATA CENTER A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment. (www.wikipedia.org)
DATA CENTER REQUIREMENT A requirement for the SAP data center, i.e. a physical requirement like power requirements, a rack requirement, a network infrastructure requirement or a requirement to the network server. (Anderson, 2003)
DISASTER RECOVERY (DR) REQUIREMENT Requirement that focuses on downtime that lasts many hours to days or even weeks (Anderson, 2003)
FUNCTIONAL TEST CASE A set of conditions or variables under which a tester will determine if a certain business process works (www.wikipedia.org)
HIGH AVAILABILITY (HA) REQUIREMENT Requirements that describes the amount of time that the system needs to be available to satisfy the needs of the users. (Anderson, 2003)
INSTALLATION DOCUMENTATION All documentation related to the installation of an end-to-end SAP solution (Anderson, 2003)
OPERATIONS MANUAL The collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents. (Anderson, 2003)
SAP SAP AG is the name of the biggest European software company. The head office is in Walldorf, Germany. SAP was founded in 1972 as Systemanalyse und Programmentwicklung ("Systems Analysis and Product") by five former IBM employees in Mannheim, Germany. (www.wikipedia.org)
SAP IMPLEMENTATION PROJECT PLAN A comprehensive project plan that contains all products that are delivered whilst performing an SAP implementation project (Anderson, 2003)
SOLUTION STACK Set of software subsystems or components needed to deliver a fully functional solution, e.g. a product or service. (www.wikipedia.org)
SOLUTION STACK PARTNERS LIST A list of all vendors that deliver the products that make up the SAP solution stack (Anderson, 2003)
SOLUTION VISION A vision of the future-state of the SAP solution (Anderson, 2003)
STRESS TEST PLAN A test plan that is focused at determining the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. (www.wikipedia.org)
TEST PLAN A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. (IEEE 829)
TRAINING The acquisition of knowledge, skills, and attitudes as a result of the teaching of vocational or practical skills and knowledge that relates to specific useful skills (www.wikipedia.org)
TRAINING PLAN Consisting of training units, a training plan is the result of hierarchical decompositions of a training goal, tailored according to the learning preferences and prior knowledge of the trainee. A plan is the means by which the trainee satisfies the goal. (www.ece.eps.hw.ac.uk/)
TSO Technical Support Organization. The people that are committed to implementation and management of SAP. (Anderson, 2003)
TSO CHART A chart that depicts the structure of the TSO. (Anderson, 2003)
Activity Sub-Activity Description
Project preparation Craft solution vision Refine and communicate a SOLUTION VISION of the future-state of the SAP solution, to sketch a design that meets both business and financial requirements. The focus should be on the companyu2019s core business and how the SAP solution will better enable that core business to be successful.
Design and initially staff the SAP TSO Design and staff the key positions of the SAP Technical Support Organization (TSO), the organization that is charged with addressing, designing, implementing and supporting the SAP solution.
Sizing and blueprinting Perform cost of ownership analysis Perform a COST OF OWNERSHIP ANALYSIS to determine how to get the best business solution for the least money i.e. to determine where and when the costs are incurred within the context of the SAP solution stack.
Identify high availability and disaster recovery requirements Determine all HIGH AVAILABILITY and DISASTER RECOVERY REQUIREMENTS, to plan what to do with later downtime of the SAP system
Engage SAP solution stack vendors Select the best SAP hardware and software technology partners for all layers and components of the SAP SOLUTION STACK, based on a side-by-side sizing comparison
Staff TSO Staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin installation/implementation of the SAP data center.
Execute training Train the various members of the SAP TSO, like data center specialists, high availability specialist and network specialists and train the end-users to give all the required SAP knowledge and skills
Setup SAP DATA CENTER Build a new SAP DATA CENTER facility or transform the current data center into a foundation capable of supporting the SAP SOLUTION STACK
Perform installations Install the (My)SAP components and technological foundations like a web application server or enterprise portal.
Round out support for SAP Identify and staff the remaining TSO roles, e.g. roles that relate to help desk work and other such support providing work.
SAP functional development Address Change Management Develop a planned approach to the changes in the organization. The objective is to maximize the collective efforts of all people involved in the change and minimize the risk of failure of implementing the changes related to the SAP implementation.
Address SAP systems and operations management Create a foundation for the SAP systems management and SAP computer operations, by creating a SAP OPERATIONS MANUAL and by evaluating SAP management applications.
Perform functional, integration and regression tests Test the SAP business processes, by executing functional tests to ensure that business processes work, integration tests to ensure that the organizationu2019s business processes work together with other business processes and regression tests to prove that a specific set of data and processes yield consistent and repeatable results.
Final Preparation Perform systems and stress tests Plan, script, execute and monitor SAP STRESS TESTS, to see if the expectations of the end users, defined in service level agreements, will be met.
Prepare for cutover Plan, prepare and execute the CUTOVER, by creating a CUTOVER PLAN that describes all cutover tasks that have to be performed before the actual go-live
Go Live Turn on the SAP system for the end-users
Hope this will help.
Reward Point if helpful.
Thanks,
Raja

Change Request Management in Implementation projects or not?

Hello guys,
We are starting a Change Request Management project at a customer. We discuss in the blueprint phase whether we should be using it only for maintenance activities, and not for implementation projects. We have some people that can be working both in maintenance and also in projects at the same time.
We want to understand whether that scenario is possible and also whether is advisable. We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
What are the drawback, difficulties, considerations you may consider in making that decision? Is it logic to work that way or is it better just to implement it for the whole installation, including implementation projects?
Esteban Hartzstein
Edited by: Esteban Hartzstein on Jan 20, 2010 3:37 PM
Edited by: Esteban Hartzstein on Jan 20, 2010 3:39 PM

We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
this you can do either via SE03 / Display/Change Request Attributes / SAP_TMWFLOW Request created using Change Manager X X / Defaul for all client = Mandatory
or
you can achieve this by just activating the CHaRM in SolMan ( solar_project_admin / system landscape / CHARM)
Nesimi

How to represent and document BI, SBOJ in an implementation project

Hello
We are working in an implementation project modeling all the scenarios, proceses and process steps. We want to represent as well all the BI, SBOJ and BPC information. We are thinking of creating specific scenario for those. We would like to get inputs about best practices regarding representation of BI and so on in Solution Manager, how to prepare the blueprint, what type of "functional" documentation, technical one, etc.. Then, how to manage the different objects in SOLAR02, what is available in config tab, development tab, only documents or we can have access from SOLAR02 to the different objects, and then navigate? I would like to have your view on this subject.
Regards
Esteban Hartzstein

You might get better help asking on [email protected]

Mapping of SD process in University Project.

Hello Experts,
For University process I need to consider the standard sd process which can be considered for implementation project.
Here the main issue is, I wont be using IS - HER.
So, I need guideline for the std. SD scenario which can be considerd for mapping in SAP IDES.
Thanks,
Rasik
Edited by: rasikmahajan on Jul 22, 2011 8:21 AM

Hi,
Consider students are your customer
Also select the main factor is base on year wise
for payment process
Full payment at time of admission
Installment payment manage with bill plan
Kapil

CTS Mgmt in SolMan for an Implementation Project?

Hi,
In an Implementation Project, if we need to use Solution Manager for CTS, is there any pre-requisites?
To be more clear, the project is still in the development stage and has not gone-live. The SolMan project type will be "Implementation" project(not a maintenance project). In this scenario, how the development/customization request will be moved across the landscape?
What are the steps to be followed?
Any inputs in this regard will be greatly appreciated.
Thanks a lot in advance.
best regds,
Alagammai.

Hi Avinash,
Again thanks a lot for your timely help.
So, all transports relating to an implementation project can be moved using the CHARM feature of SolMan. Nice )
(ii) Whenever I create Implementation or Maintenace project in my SolMan system, I am not finding this "Change Request" tab under "System Landscape" tab. What could be the problem? Is that becos CHARM is not configured in my system?
(iii) As you told while we create the transport route in the satellite systems, do we do it in the regular way? Or is there any modifications need to be done as we have to use it with CHARM? (sorry, might seem to be a silly question... but, as I am not aware of it...)
(iv) Also, you have listed a number of steps to be done. Are these steps to be done in the SolMan system?
(v) Is there any link or document describing this process? Do you have any document of your own? If so, can you pls send the same to my email id [email protected]?
Thanks & Best regds,
Alagammai.

Linking solution manager projects with CHARM implementation project

Hi Guys,
Currently i am working in CHARM implementation project, i have created one CHARM implementation project with urgent correction and i am able to create the Transport request and release the transport request succesfully and i am able to move it to quality system successfully. But my customer is asking to link the solution manager project to CHARM implementation project.
Earlier before implementing CHARM they have implemented project managent in solution manager, during that project they have created so many projects which are currently running, now they want those projects to be linked CHARM implementation project.
When ever they create a transport request through CHARM they want the TP to be saved under a respective project which they are using currently. but according to my knowledge the TP can be saved under CHARM implementation project only.
Now i want to know whether the projects created in SOLAR_PROJECT_ADMIN can be linked to CHARM implementation project. Pls give ur valuable inputs as it is very urgent.
Thanks&Regards
Raju

Hello,
We have implemented this with two systems landscape where in we have in place a Solution Manager Dev system and Solution manager Production system both are SOLMAN 4.0 with SP12. So the path for us to move the changes is from Development Systems to Production system.
We have ChaRM between the Dev and production. We reapplied the satellite system concept. For us the Solution manager Prod is a satellite systems all the changes that we move from Development system to Production systems is tracked with necessary documentation in the ChaRM process.
Yes, I agree with you that this is not any big magic. Working with two SOLMAN implementation, I strongly feel that SAP needs to have well rounded ChaRm processes. We have robust Change Management Process, but when we moved to ChaRM we were limited functionality of the ChaRM processes.
I had approached and did some research on how other companies are implementing the same process. Most of them have almost the same process for tracking SOLMAN changes. I am still look out for improved process to manage SOLMA changes.
Hope this helps!!! Thanks
Vish

ChaRM activation in implementation project??

HI
I am quite new to solution manager , i want to ask that if we have created an Implementation Project in Solution Manager What is the pupose of activating ChaRM in it?? when i can do configuration directly from "Configuration" in Solution Manager itself and directly transport it to landscape by the transport option in "SPLAR_PROJECT_ADMIN"??
Please guide
Thanks

Hi Sindra,
When we have a normal correction we would normally use the Transport of Copies function to move developments into the QA system so we can check that we get the desired result. If we need to change our development we can change the development and assign the changed development to a new task in the Transport Order. When we want to transfer the development we can then release the task, create a new TOC and import the TOC. This can be completed as many times as required, the important point to remember is that we never release the Transport Order until we have completed the development.
If during the project cycle we need to perform a correction to the development when we are in the test phase we can use Test Messages (SDTM) to control the creation of a new transport and the import process.
If during the correction process you are finding that the status of the document is changing to a previous status then there could be a problem and you should have a warning or error message displayed in the ticket.
Hope this helps,
Rich Labib

Info on activities involved in various stages in Implementation Project

Hi,
I need some detailed information on activities involved in various stages in a SAP Implementation.
I have seen the earlier threads in the forum on this Topic,but they are very brief.
It will be very helpful for me if someone can provide some detailed document on practically what is done in those stages.
Thanks in advance,
Ashish

Hi,
Based on ASAP methodlogy.
1)Project Preparation
2)Business Blue print preparation
3)Realization
4)Final preparation
5)Post go-live support.
Project Preparation:Phase 1 initiates with a retrieval of information and resources. It is an important
time to assemble the necessary components for the implementation. Some
important milestones that need to be accomplished for phase 1 include
u2022        Obtaining senior-level management/stakeholder support
u2022        identifying clear project objectives
u2022        architect an efficient decision-making process
u2022        creating an environment suitable for change and re-engineering
u2022        building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement
and cooperation of the important company decision-makers - key stake holders
and others. Their backing and support is crucial for a successful implementation.
Clear project objectives:
be concise in defining what your objectives and expectations are for this venture.
Vague or unclear notions of what you hope to obtain with SAP will handicap the
implementation process. Also make sure that your expectations are reasonable
considering your company's resources. It is essential to have clearly defined
ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision-
making process. Before embarking on this venture, individuals need to be clearly
identified. Decide now who is responsible for different decisions along the way.
From day one, the implementation decision makers and project leaders from
each area must be aware of the onus placed on them to return good decisions
quickly.
Environment suitable for change and re engineering:Your team must be willing to
accept that, along with new SAP software, things are going to change, the
business will change, and information technology enabling the business will
change as well. By implementing SAP, you will essentially redesign your current
practices to model more efficient or predefined best business practices as
espoused by SAP. Resistance to this change will impede the progress of your
implementation.
Business Blue Print Preparation:SAP has defined a business blueprint phase to help extract pertinent information
about your company that is necessary for implementation. These blueprints are in
the form of questionnaires that are designed to probe for information that
uncovers how your company does business. As such, they also serve to
document the implementation. Each business blueprint document essentially
outlines your future business processes and business requirements. The kinds
of questions asked are germane to the particular business function, as seen in
the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool
designed to facilitate the creation and maintenance of your business blueprint.
This database stores the questions and the answers and serves as the heart of
your blue print. Customers are provided with a customer input template for each
application that collects the data. The question and answer format is standard
across applications to facilitate easier use by the project team.
Issues database:
Another tool used in the blueprinting phase is the issues database. This
database stores any open concerns and pending issues that relate to the
implementation. Centrally storing this information assists in gathering and then
managing issues to resolution, so that important matters do not fall through the
cracks. You can then track the issues in database, assign them to team
members, and update the database accordingly.
Realization:With the completion of the business in phase 2, "functional" experts are now ready
to begin configuring SAP. The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the
baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your
business and process requirements as part of the fine tuning configuration.
The initial configuration completed during the base line configuration is based on
the information that you provided in your blueprint document. The remaining
approximately 20% of your configuration that was not tackled during the baseline
configuration is completed during the fine tuning configuration. Fine tuning usually
deals with the exceptions that are not covered in baseline configuration. This final
bit of tweaking represents the work necessary to fit your special needs.
Configuration Testing:
With the help of your SAP consulting team, you segregate your business
processes into cycles of related business flows. The cycles serve as independent
units that enable you to test specific parts of the business process. You can also
work through configuring the SAP implementation guide (IMG). A tool used to
assist you in configuring your SAP system in a step by step manner.
Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the
Project team to be self-sufficient in their knowledge of the configuration of your
SAP system. Knowledge transfer to the configuration team tasked with system
maintenance (that is, maintenance of the business processes after Go-live)
needs to be completed at this time.
In addition, the end users tasked with actually using the system for day-to-day
business purposes must be trained.
Final Preparation:As phase 3 merges into phase 4, you should find yourselves not only in the midst
of SAP training, but also in the midst of rigorous functional and stress testing.
Phase 4 also concentrates on the fine tuning of your configuration before Go-live
and more importantly, the migration of data from your old system or systems to
SAP.
Workload testing (including peak volume, daily load, and other forms of stress
testing), and integration or functional testing are conducted to ensure the accuracy
of your data and the stability of your SAP system. Because you should have begun
testing back in phase 2, you do not have too far to go until Go-live. Now is an
important time to perform preventative maintenance checks to ensure optimal
performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy.
Preparation for Go-live means preparing for your end-users questions as they
start actively working on the new SAP system.
Post Go-live Support:The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live
is another matter altogether. Preparation is the key, including attention to what-if
scenarios related not only to the individual business processes deployed but also
to the functioning of technology underpinning these business processes and
preparation for ongoing support, including maintenance contracts and
documented processes and procedures are essential.
Regards
Ravi Shankar.

Adjust changes in Implementation Project back to Template Project

Hello All,
Please can you help with transaction SA_PROJECT_UPGRADE, the case is as follow:
STEP 1
- Template project is created including process structure and documents, template is activated
- Implementation project: is created derived from template project.
- In Template project: Change in pocess node made: added an new process node
- Run SA_PROJECT_UPGRADE with checked box "New Version of Original" and chosen project: Implementation project
- Implementation project: the yellow boxes appears on the appropriate place and button "adjust to original" is used.
So far, so good
STEP 2
- Implementation project: a new process node is added, project is saved
- Run SA_PROJECT_UPGRADE with checked box "'Current Version in Project" and chosen project: Implementation project
- Template project: no changes are visible in SOLAR01 or SOLAR02
- In SOLAR01: settings -> User specific -> box checked "Dislay changes made in project"
So far, NOT good.
Resume:
- using transaction SA_PROJECT_UPGRADE from Template -> Implementation Project works according documentation
- using transaction SA_PROJECT_UPGRADE from Implementation Project -> Templates does not work according documentation
Does anybody recognise this?
Or do I oversee something?
System: SSM 4.0 updated to SP13
Thanks in advance
Rutger Koppelaar

Hi Rutger (& all others watching this thread),
I would like to make certain corrections to one of the points posted by me:
2) Within a Template Project, any actual changes to the document does not offer itself as a 'change' while doing comparison on Implementation Project. In other words, after a given Scenario and all its associated documentation are copied into an Implementation project, if a given document at a given node needs to be edited, it's better to create a new document and upload it in Template Project than to open & change the same document. If the same document is edited, the Compare and Adjust cannot see that as 'difference'.
On the above point, I have now see better/different results with my recent work; not sure if this is version/ support package specific.
Environment:
SolMan 4.0
SAP_BASIS - Release 700 Level 0013
SAP_ABA - Release 700 Level 0013
ST - Release 400 Level 0014
Assumption: Both the Template and Implementation Projects are in the same SolMan instance and not a case where the Template is being transported into another instance!
Findings (please bear with this verbose description; one day I intend creating a Blog instead, to list all these points):
(1) In General Documentation Tab of Template Project, any changes made is instantly visible in General Documentation Tab of the Implementation project - not even dependent on running SA_PROJECT_UPGRADE transaction
If you indeed run this transaction - in foreground or background, and later check the Implementation Project, it would not highlight that node as having undergone any change. However, if you double click the document itself, you'd be pleasantly surprosed that it opens the most updated version you maintained in the Template Project. No need for 'Compare and Adjust'.
(2) In Test Cases Tab - any change you make to Test Document in Template Project is again instantly available for the Implementation Project that had inherited the document, provided no manual changes were done to that document in the Implementaiton Project directly. Again, no need to run SA_PROJECT_UPGRADE transaction or the subsequent 'Compare and Adjust' function
2a) If, however, the Test Document was altered in Implementation Project subsequently, the chain gets broken (in my understanding so far), and any subsequent changes made in Template Project does not become 'instantly' visible in Implementation Project - the two behave as though they are different documents
In such a case, if you desire to 'restore' the supremacy of Template Project's contents, run SA_PROJECT_UPGRADE transaction, and after the background job finishes, visit Implementation Project concerned. The node where the Documents differ is not highlighted (unfortunately). However, if you are aware of that node, and hit 'Compare and Adjust' button the ensuing Window does tell you with a # sign on the right hand panel that the Document has indeed changed in the original. You can 'adjust' that and save.
Once this is done, and also you vow to not change the document in Implementation Project directly, the link between the two is kind of re-established. Any subsequent alterations you make in the Test Case at Template Project would be instantly visible from Implementation Project, as before !
I have tried to explain precisely what I experiemented and found. I hope this works consistently
The ways in which Document linkages are established and pointers to KW object IDs work is rather inscrutable for me, without ABAP support.
I'll update any further findings here.
Please keep a watch.
Thanks and regards,
Srini

Process of implementation project

Similar Messages

Maybe you are looking for