Realization phase in Template/Implementation project

Hello!
We have completed our blueprinting in SM40 on a project which was created as a template project. Now to kick-off realization phase, should we create a new implementation project out of the template..or ..just configure the project as a template itself...
What are the pros and cons? What is the right way of doing it..
Appreciate any advise/inputs.
Thanks.
Mike

Hi Mike,
in the template project every customizing element has the attribute global / harmonized / local.
Even if a rollout directly with the template project is possible (never heard of that), you would loose one of the greatest advantages of the global rollout functionality:
When copying the template project into an implementation project, all customizing elements set as global are "locked" and can not be changed by the local support teams. The ones with attribute "local" can (details see attribute specification). Thus you ensure that local settings can be applied and global processes remain as defined.
Next step is to centrally develop a new version of the template for roll-out, while your maintenance teams can work with the implementation project(s).
Another decision is to use one Implementation project for all roll-out candidates (pro: all relevant documentation in one project; con: documents need to be well arranged for not to loose track) or several Implemenation projects for each roll-out candidate (con: scattered documentation; pro: easy overview per roll-out candiate).
Hope this clarifies a bit...
Regards
Christoph

Similar Messages

How to transport Implementation project template changes?

Hello All,
I have made changes to the project template (added doc types, assigned status schemas) for Implementation projects in my dev system by going to SOLAR_PROJECT_ADMIN > Goto > Project Template > Implementation projects. I want these values to be the standard values whenever I start a new Implementation project.
When I save my changes, I am not prompted for a transport request, nor can I find any transport option in the menu. Do these project templates need to be manually configured in my test and production systems, or is there another way of assigning the changes to a transport that I cannot figure out?
Thanks in advance,
Michele

Hi,
Just enable the GLOBAL field for the values which you want to be available for all the implementation projects.
e.g
You created a documentation type which is having global field tick so it will be available for all
Hope it helps
Regards
Prakhar

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

SAP CRM Implementation Project - Phases/Stages

Hi all
I am very new to this Area !
I would like to know different Phases/Stages in the SAP CRM Implementation Project !
Regards
RJ

Remo,
I believe every SAP CRM Implementation project would follow the ASAP methodology which is as follows:
Phase1: Project Preparation
The system landscape is set up, consultants are assigned. Project charter is created etc.
Phase2: Business Blueprint
The implementation consultants do a study of the clients business and learn how the processes/ cycles involved thru discussions, workshops etc
This is documented as an AS-IS document.
The clients business processes are then mapped on to SAP by the consultants.
This is documented as the TO-BE document
Gap Analysis is performed to identify any gaps between the AS-IS and TO-BE documents. i.e. something that the client wants but cannot be met thru SAP CRM. Then enhancements etc come into picture.
Phase3: Realization
The system is configured as per the TO-BE document. And the client is given for testing.
Phase4: Preparation for Go-LIve
Once the client confirms all the unit and integration tests, the master data needs to be uploaded. Other system checks by basis and SAP itself are performed.
Phase5: Go live and support
The project goes live and the consultants give a month's of hypercare or support.
Hope this is wat you were expecting.
Regards,
Julius
P.S: Reward if it helps.

How to connect Template project and Implementation project

Hi Experts,
     I would like to know how to connect Template project and Implementation project
    in Solution maneger.   Please help.
Best regards,
   Gaito

Hey Gaito,
great. Now that you have a template project, you need to create one or more templates within the project template.
Go to tab Templates (of your Templ Proj) and activate 'Global Rollout Functionnality' to be able to use the templates.
Create a new template thanks to button create. Visibility will be set to red 'private'. You ll have to set it to visible so it becomes visible from your implementation project.
You ll see when trying to do that next message 'No scenarios/configuration structures assigned to the template XXXX'. That means that in SOLAR01 you did not define a scenario that ll be used in template you re trying to create
In order to do that go to SOLAR01 for template project, select/create scenarios in tab structure and set in column template value of your template (the one you re creating in SOLAR_PROJECT_ADMIN) and in Global Attribute set value t Global
You l definitely find more info on this in sap document SMI310 (course). I don t know if you can find it on internet
Hope this helps
Regards
Khalil

Copy teammembers and keywords from template to implementation project

Hello All,
When adding structure elements (business scenarios, etc) from a template project to an implementation project, the data on the administration tab is not copied with it.
When selecting a specific scenario from the template we need to be able to also copy the keywords and team members to the implementation project.
1) Is this possible without custom development
2) If we use custom development. How can I link a structure element to its Administration tab data (keywords and team members) in ABAP?
Thanks
Jurjen

If you copy the entire project using SOLAR_PROJECT_ADMIN, and then delete out of scope scenarios using SOLAR01, then the administration data can be copied over. Note, however, that this only works for the initial project copy. Subsequent changes to the information on the Administration tab in the Repository cannot be carried over to the projects using SA_PROJECT_UPGRADE. Another restriction is that you can't copy a template project to an implementation project. Also, if you want to use further template functions such as the Global Attributes, then you have to bring scenarios in using the template functions, where this data is not copied over.

Template project reference in Implementation Project

Hi,
I have defined Template Project & created Business Blueprint hierarchy for the same.
Now I need to refer the Template Project in Implementation Project.
1) How to refer Template Project in Implementaion Project ?
2) Can I get the Template Project reference in Implementation Project automatically in Scope OR do I need to do some settings ? Currently I am not able to see the Template Project in Scope.
Regards
P Kumar

Hi Kumar,
Refer below links. Should be useful and also I am assuming that you have created master template and you want to refer master in local implementation project.
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-i
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-ii
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/05/21/template-management-part-iii
Master template should be visible in local implementation project under scope automatically.
Thanks
Sateesh.

Template Project Usage in Implementation Project

hi,
I have defined the Template project in Solar_project_admin. Now how I can use this template project in Implementation project.
What are the steps of copying the template project into implemenation project.
Regards
PK

Hi Aditya,
Many Thanks. I am new to this feature ( Template project & roll out). My requirement is like, I need to define one template project & same has to be rolled out in other contries implementation projects. This is in a broder sense.
Now what are the steps to go about. How to proceed.
Will there be only one Solution Manager or different countries will have sepearte Solman. Will one Solman will do all rollouts.
Can you give me some useful stuff as a biginner, how the project management is used ( especially Template project & roll out )
Regards
PK

Regarding Testing phase in Implementation project

Hi FI/CO gurus
I would like to know about the testing phase in implementation project like
1. What are the different types of testing done by a SAP FI/CO consultant after configuring the relavent objects in implementation project, pls provide with one example of your experience?
2. what is the difference between SAP version 4.7 and ECC 6.0 in FI/CO point of view?
3. Please tell me what are the main responsibilities of a SAP FI/CO consultant apart from configuring objects in implementation project?
hopes for the positive reply. Thanks in advance.
Regards
Sree

Hi FI/CO gurus
I would like to know about the testing phase in implementation project like
1. What are the different types of testing done by a SAP FI/CO consultant after configuring the relavent objects in implementation project, pls provide with one example of your experience?
2. what is the difference between SAP version 4.7 and ECC 6.0 in FI/CO point of view?
3. Please tell me what are the main responsibilities of a SAP FI/CO consultant apart from configuring objects in implementation project?
hopes for the positive reply. Thanks in advance.
Regards
Sree

How to map business scenarios from implementation project to template project

Hi
We have a template project and in this we have maintained few business scenarios. And also some specific scenarions are configured in the implementation project. Now we need to make template project as Global Template and for this we need map all existing scenarios in implementation project to template project.
Please suggest how we can map from implementation project to template project.
Thank you

Hello,
Along with Sandeep recommendation, you can do it by several ways.It all depends on how are the current projects organized.
Did you create the template project and then rolled out the templates to the impl. project?
In case you want to update these scenarios in the Template project based on the changes you performed in te Impl. Project, you can use the Compare & Adjust functionality.
You can Copy Scenarios from one project into another by using the right click/context menu directly in the node in solar01.
If you just want to copy the structure, you could export the Impl. project structure in solar_project_admin by using the "fill business blueprint" functionality, then adjust the structure similarly for the template project and upload.
and so on..
regards,
Fabricius

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.

Implementation project in bw

hello gurus,
                  can anyone let me know the full details of one lifecycle implementation project in bw?
                   i know it has been posted so many times and i tried to dig as well but coudnt get quiet all
                  that..i need all the details of a project like tech.spec and functional spec..responsibility and
                  involvement of bw consultant in each phase of asap methodology....
                 please help me
                 thanks in advance
regards,
anshu

Hi,
BI Implemenation Project- Phases(ASAP)
1.Project Preparation / Requirement Gathering
2 Business Blueprint
3 Realization
4 Final Preparation
5 GO Live & Support
1.Project Preparation / Requirement Gathering
Collect requirement thru interviews with Business teams /Core users / Information Leaders .
Study & analyze KPI 's (key figures) of Business process .
Identify the measurement criteria's (Characteristics).
Understand the Drill down requirements if any.
Understand the Business process data flow if any .
Identify the needs for data staging layers in BW u2013 (i.e need for ODS if any)
Understand the system landscape .
Prepare Final Requirements Documents in the form of Functional Specifications containing :
Report Owners,
Data flow ,
KPIu2019s ,
measurement criteriau2019s,
Report format along with drilldown requirements .
2 Business Blueprint
Check Business content against the requirements
Check for appropriate
Info Objects - Key figures & Characters
Check for Info cubes / ODS
Check for data sources & identify fields in source system
Identify Master data
document all the information in a file u2013 follow standard templates
Prepare final solution
Identify differences (Gaps) between Business Content & Functional
specification. propose new solutions/Developments & changes if required at different levels such as Info Objects ,Info cube , Data source etc . Document the gaps & respective solutions proposedu2013 follow standard templates
Design & Documentation
Design the ERD & MDM diagrams for each cube & related objects
Design the primary keys/data fields for intermediate Storage in ODS
Design the Data flow charts right from data source up to Cube .
Consider the performance parameters while designing data models
Prepare High level / Low level design documents for each data model.--- follow standard templates
Identify the Roles & Authorizations required and Document it u2013 follow standard templates
final review of design with core BW users .
Sign off the BBP documents
3 Realization
Check & Apply Latest Patches/Packages ...in BW & R/3 systems.
Activate/Build & enhance the cubes/ODS as per data model designs...maintain the version documents .
Identify & activate Info objects / Master data info sources / attributes ,prepare update rules
Assign data sources .prepare transfer rules , prepare multi providers . prepare Info packages .
perform the unit testing for data loadsu2026.both for master data & transaction data .
develop & test the end user queries .
Design the process chains ,schedule & test
create authorizations / Roles u2026assign to users ..and test
Apply necessary patches & Notes if any .
freeze & release the final objects to quality systems
perform quality tests .
Re design if required . (document changes, maintain versions)
4 Final Preparation
Prepare the final check list of objects to be released .identify the dependencies & sequence of release
perform Go Live checks as recommended by SAP in production system
keep up to date Patch Levels in Production system
Test for production scenarios in a pre-production system which is a replica of production system .
Do not Encourage the changes at this stage .
freeze the objects .
5 GO Live & Support
keep up to date Patch Levels
Release the objects to production system
Run the set ups in R/3 source system & Initialize Loads in BW
Schedule Batch jobs in R/3 system (Delta loads)
schedule the process chains in BW .
Performance tuning u2013 on going activity
Enhancements - if any
Regards
CSM Reddy

What is Developers role in Implementation project

Hi All,
Can any body tell me the Role of Developer in Implementation project
Plz reply back me to [email protected]
Regards,
Kiran

Hi kiran,
Developer will develop the objects, means If a client is located at other place senior consultrants like, functional or Techno functional consultants will gather the requirement and they will try to convert it into technical specification the the developer will start developing the objects.
Developer will do the developmnent and unit testing ..
Generally Developers will come into picture from the realization phase fo the project.
Hope iam clear.
Apparao

Re: Roles of ABAPER in implementation project

HI experts,
What s the Roles of ABAPER in implementation project?and responsibilities in support project?

IMPLEMENTATION :This is project in which we implement sap for a company from scratch right from creating tables and data for the first time..writing code for the first time etc.
SUPPORT : this is the kind of project where SAP has been already implemented but due to some additional business requirement or any thing like small problems in general they hire a team who work for them to solve the small issues.its also called issue based project.
It depends on the Volume of the company and how many company codes and Plants it have and for how many it has to be implemented
There are different types of Projects in SAP:
1. Implementation
Customer wants to install SAP/Include different modules of SAP viz. MM/SD/FI/CO/PP etc for the first time.Previously he might be using some legacy system in his orgn. This is implementation project. Here one needs to integrate several modules, migrate data from Legacy system to SAP system. Need to prepare interfaces/RFC's to interact with 3rd party systems.
Most of the company's follow ASAP methodology for the Implementation projects
there are 5 stages in the ASAP methodology
they are
1. Project Initial Preparation
2.Business Blueprint
3.Realization
4/ Final Preparation
5.Golive And Support
ABAP work mostly starts in the Blue print ending stage or in the realization stage
2. Support
Customer has already installed SAP & wants to give the work of maintaining those systems. This is support project
There is no phases in it. Just receive the tickets, solve and send back to client.
3. Upgrade
Customer has SAP Version 4.6b and wants to update his version i.e. wants to go to Version 4.7. This is upgrade project
4. Rollouts
Customer has upgraded his version & wants to rollout country specific changes.
This is rollout project
Say a company is having branches in 3 to 4 countries.
In One country they have already implemented SAP
IF they wants to implement the same SAP in other countries of their branches they will simply follow the same SAP implementation policy (Rollout) how they have done for the first country just by changing the country specific settings and configurations.
Regards,
Pavan

Authorization Role Practice in Implementation Project

Gurus,
Okay, I've been implementing SAP R/3 for around 5 implementation cycles, before realizing my method for creating role may be outdated. I need your advice regarding this.
Here's my common scenario on every implementation project in realization phase:
1) Functional Consultants hand over their authorization matrix to me
The matrix will be the role name to created, along with its transaction code and authorization object.
There's also user assignment to each role.
2) I created the role in PFCG.
Reference, single, composite role. Anything you can build in it.
3) Map the SAP user to appropriate role
Now here's the interesting part.
Users will then be given their own SAP User on UAT phase.
When they try to do transactions, almost every time, every one of them'll stumble upon "No authorization" error.
What I do is, check their SU53 object, add corresponding object, then let them test again whether it fixes the error.
The authorization matrix given by consultants will not have every needed auth. objects.
It can't be helped. You can't also just put the Full Authorization (*) to object you don't familiar with.
How do you usually do this?
Any helpful tools?
Thanks for help.
Regards,

Hi,
Generally role matrxi should contains every info what eve they needed to create the Role for the functional folks.
in you case there is some missing things that is interrupting you so better you can focus on Standard SAP roles and study that roles properly before you creating any Customizatio roles.
so that you will get an idea what are all the objects you have to use to create MM roles and also what are all the objects you have to use to create SD roles etc etc....
so please try to read the Standard role first before creating the custmoiztion roles.
-Srini

Realization phase in Template/Implementation project

Similar Messages

Maybe you are looking for