Documents used / prepared in an implementation project

Hi experts,
I would like to know what are the main / imp documents we prepare in an implementation project viz. BPML, etc
Could someone send me the list and functionality of the docs ?
Regards
Mahesh.

Hi
Could anybody help me on this?
Mahesh

Similar Messages

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]

Use Change management in implementation project

Hello SolMan Experts,
I have a requirement that I need to do an implementation through solution manager. I want to develop objects in my R/3 systems using solution manager. I have seen a thread where someone told that Change request is not possible in implementation but we have an option to create a change request with development(Implementation).
Should I create a change request development(Implementation) for each development happening for the project?
Please help.
Thanks in advance
Farzan

Hi Farzan,
While I am not able to give you further technical know-how on your specific question, I would like to share a word of caution though.
In my experience, activating ChaRM within an active Implementation Project poses problems if you have to change the 'System Landscape' of the project midway.
For instance, if you had 3 Logical Components listed in the tab Sys. Landscape of the Implementation Project, activated ChaRM, and later, you decide to add one more Logical Component, it does reset the CTS counters to '0' and you have to do a few steps manually, to restore it to what it should be.
I am not sure if this is due to a bug or if this is a known constraint. I for one, can't foresee any Implementation Project which can effectively freeze the Sys. Landscape scope by end of Blueprint phase. In long projects, due to afterthoughts and various pressures, one may end up tampering with a few Logical Components well into Realisation phase.
You may like to check with SAP over OSS and ask them for recommended approach.
As a recap, yes it is possible to activate ChaRM in Implementation project technically. However, if it is indeed a recommended approach, I am not so sure.
Regards,
Srini

Not able to see General Documentation in Implementation Project

Hi All,
I've created one Template Project and one Implementation Project. Now I've added some documents to Template Project - General Documentation Tab. Ideally this newly added documents should be appeared in Implementation Project - General Tab. But in my case I am not able to see this newly added documents. Is there any reason behind this? What should I do to make them visible in Implementation Proj - General Documentation tab?
Another question is, If a document from Project Documentation tab is deleted by pressing 'Delete Row' button (not actual 'Delete' button), how can I retrieve that document? How can I see the list of all deleted documents?
Thanks in advance!
Shaun
Edited by: shaun99 on Feb 16, 2012 4:28 PM

Hi Shaun,
For the implementation project, please read the session "USING THE TEMPLATES" in the wiki page for template projects, where it explains how to update your project with the changes made in the template project.
-http://wiki.sdn.sap.com/wiki/x/gRkMDg
regarding the download, I'm not aware of any easy way to do mass download of the documents. Maybe in SI80 you could do such thing but I believe you would only be able to filter by the folder where the documents are phisically stored and as you're using a template project, all the documents are stored in the folder SOLAR00, shared along with solutions and etc..
more info about this in the wiki page for documents in solar01 and solar02:
-http://wiki.sdn.sap.com/wiki/x/rBoMDg
Kind regards, Fabricius

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

ChaRM on implementation Projects

Hello
I have a conceptual question regarding the use of ChaRM on Implementation projects.
We are using ChaRM and have ensured that CTS is driven from Solution Manager i.e transport requests can only be created from corrections (SDMI). To date all SDMI's have been created as follow on documents to Change Transactions (SDCR). Going forward we would like to differentiate genuine changes (Changes to scope after blueprint sign off) from implementation activities driven from blueprinted requirements.
Whilst we see benefit from approval workflows for genuine changes, it is quite a chore to create SDCR's for all regular implementation work which is implicitly approved by signed off blueprint.
It is also difficult for us to then differentiate Changes from Implementation SDCR's.
Can anyone see a problem with all implementation tasks being generated directly as SDMI's with no preceding SDCR whilst leaving genuine changes as SDCR generated corrections?
The only one I can think of so far is that there is workflow that sets the status on an SDCR when the SDMI has been through it's lifecycle although I'm not sure how the system would behave if there is no SDCR.
Thanks
Mark

Hello,
for the first please use SDMJ. SDMI is old.
You can create SDMJ directly without SDCR and his approval workflow. There is no problem.
It is not really clear how to work with Implementation projects and "changes".
There are two known scenarios:
Implementation project (phase of the application management life cycle is "Implementation"):
If you have an really Implementation project for an Implementation of for example an new SAP product you should use an "Implementation project". It is not a change request!
Here you work with the known IMG-projects, blueprint, project phases.....
The transport process is realized via bc-sets. It means you create all you "changes" in bc-sets.
Implementation project (phase of the application management life cycle is "Optimization"):
Here you can use also the "Implementation project"
You can create SDMJ directly without SDCR and his approval workflow. There is no problem.
The transport process is realized via transport requests.
I guess the different between this two scenarios is the transport process.
Hope this is helpful.
Best regards
Thomas

Deleting document from general documentation tab in implementation project

Hello,
We tried to delete a document from gen. documentation tab in an implementation project, since the gen. documenation tab is greyed out, we couldn't do so. The document is a link from a template project, we tried to delete it (by using the trash can icon) from there first, but the system says "the document is still in use".
Does anyone of you know how to delete a document which has been linked to implementation projects based on a template project?
Regards, Li

Hi Li,
Here's a solution you can try for your problem.
Go to your template project in SOLAR01and mark the line of the document you want to delete and press the remove button (red minus icon).
Then go to your implementation project and go to the same place where that linked document is. Click on the <b>Adjust to Original</b> icon (looks like two little boxes with two arrows pointing down.) when you click on this icon, you will get a pop-up window where on the left hand side is your template (original) and the right your implementation (current). On the left, you will see a blank line with the red minus icon and on the left you will see the document you are trying to remove. select that line and click on "Adjust selected entries" icon that's in the middle of the screen.
Notice both lines became blank, once that's done, click on complete icon at the bottom.
You're document has been removed from your implementation project.
Note: This is the only way that I have found for this issue. This does not mean that the document was completely deleted from Solution Manager....just the link to your project. If ever in the future you want to link it back, you can still find it with SOLAR_EVAL.
Please let me know if this worked for you.
Regards,
Salpi

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.

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

Work in implementation projects

HI,
Am searching job in SAP-BW.Can anyone tell me the roles and responsibilities in implementation projects for a person who has 2years of ex.Pls kindly help me.
thanks
surya.

Hi,,
A BW consultant, role may vary depending on the type, of the project.
For Migration project
u2022 Designing mapping documents in order to check the need of creation in BW.
u2022 Developing various objects like Cubes, ODS, Info Sources, InfoObjects etc.
u2022 Designing Transfer Rules and update rules including start routines, update routines and Transfer routines as per the requirement.
u2022 Scheduling Info Packages to carry out the data loading process. Involved in data loading from SAP R/3 to Source layer ODSs into BW. Loaded data using Data mart, as the Business layer and Report layer ODSs get loaded from source layer ODSs using data mart functionality of BW.
u2022 Involve in the backfilling of historical data from present sys to SAP BW .
u2022 Developing the Master/Transactional data process chains considering the dependency among the BW objects and automated the triggering and monitoring of the same on daily, weekly and monthly basis.
u2022 Transportation of various BW components.
u2022 Performing unit testing and data validation of newly developed and enhanced objects in Quality BW system in terms of providing an efficient solution.
u2022 Responsible for overseeing the Quality procedures related to the project.
u2022 Responsible to deliver (Transport into Prod) the object as per the scheduled deadlines; with accuracy of deliverables by considering the quality norms.
u2022 Involving in the Client/Onsite communication for any client side clarifications, for assignment of work, for discussing on project status related issues, etc.
For Support project
Data Load Monitoring:
1.Carried out data load on a daily, weekly and monthly basis using Process chains from both SAP Source systems as well as Non-SAP Source systems such as Informatica.
2.Resolving Data load error such as Invalid characters, Time period conversion, Currency conversion, Duplicate records, etc
3.Ensuring the availability of the updated data in the datatarget on time.
4.Spooling out data through Infospoke from SAP BW to systems like Trillium, Ariba (Reporting Tool)
Ticket Resolution:
1.Process chain modification: Working on u201COptimizing Process chainu201D by creating new process chain considering the load dependencies.
2.Reloading of R/3 data from different clusters u2013 Reconciliation issues
3.Enhancements as per Business requirement.
Additional responsibilities:
u2022Preparing design documents from the Business Requirement docs and identified the relevant data targets for satisfying the customer requirements.
u2022Creation of Operational manual: BW Run & Maintain Support.
u2022Process Chain Detail Documentation (Sequencing & Dependency within Local Chains).
u2022Monitoring checklist Document (From Process Chain Perspective)
u2022BW Doc checklist preparation
u2022Table space activity with basis team.
u2022Data load analysis taking into account the CPU utilization.
u2022Applying Support packs and performing ORT.
Refer.
Roles & Responsibilities for Junior & Senior consultants(Technical)
Periodic Jobs and Tasks in SAP BW
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/08f1b622-0c01-0010-618c-cb41e12c72be
Production and Implementation
production support
Re: In production Support , how i can acquire the knowledge
Re: How to resolve tickets its urgent
Assing points for this if helped.
Thanks

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

Advantages of using BPR in an SAP project

Hi
Could anyone tell me what are the advantages and significance of using the Business Process Respository (BPR) while starting an implementation Project (or template project). Lets say as opposed to NOT using the BPR. What are the pros and cons of the two approaches? And how reliable are these BPR contents?
Appreciate your answers
Drake

Hi Drake,
BPR comes from SAP and delivered via Software Component ST-ICO. Periodically, SAP keeps upgrading this component and in my view, one of the best enablers of Solution Manager.
From a Project point of view, if you use BPR provided content, at Scenario, Process level, it inherits all 'associated' assignments, like Transaction Codes, IMG nodes relevant for a given Process Step. Also, it loads any other accelerator documents from SAP in General Documentation Tab.
These contents are helpful for Business Process Monitoring (BPM) too when you want to 'inherit' the Processes and Process Steps defined in Project into Solution. There are standard metrics that SAP provides for process steps in BPM that would be more easily compatible if a project had got the same terminology.
BPR, however, isn't as comprehensive as we may like it to be. It's rich on some areas and frugal on certain others.
In terms of 'reliability', well there is no specific aspersions that could be cast on it
If it's rich, it's visible and useful; where it's not good enough, we can always add some content and still make some good use of it.
Another advantage of using BPR is that when a new version of BPR is downloaded and applied, using SA_PROJECT_UPGRADE transaction, the system will offer a chance to see areas which are impacted by a change and those can accepted in SOLAR01/02.
So, BPR-led content can always be kept up-to-date.
In my personal experience, I have realised that 2 consultants can easily have 4 opinions! On ever fluid concepts like Scenario, Processes etc. to attain a convergence of thoughts and minds is a difficult proposition. BPR allows for a project to close the gap and adopt SAP ways of definition and helps jump-start the project. The time saved is better used in value added areas or in rigorous testing and training !
The only firms/ projects which may want to shy from BPR could be those:
- who have a fairly well established vocabulory of defining their day to day processes and where retrofitting SAP definitions can be counter productive
- who have traditionally used advanced platforms like ARIS or other tools
- who work in industries inadequately represented by SAP
Best regards,
Srini

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

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.

Link between implementation project configuration (SOLAR02) and ChaRM?

Dears;
We want to benefit from listing all IMG Objects and developments in an implementation project (SOLAR02) to control our transports as we have ChaRM activated on the affected systems.
But there seems to be no link/control which has several consequences:
*Status of "changes" in ChaRM and related developments in the implementation project have to be tracked seperately
*There is no link between the development in the project (SOLAR02) and the created TR.
*There is no limitation/control in the content of the TR if it concerns items not listed in your project => how to check if the project is up-to-date?
Are my assumptions correct? Or am I forgetting something?
What is the experience in maintaining changes (transports) for implementation project? On what level? Linked with the structure in Solar02 or completely independant?
I have done quite some reading around the topics but documentation around project management via SolMan and ChaRM via SolMan seems never to be really connected? (only the overall status of the project and the activation of charm via SOLAR_PROJECT_ADMIN)

>
Jett Jiang wrote:
> 1. Active Change Request Management. the inter-connect is in SOLAR_PROJECT_ADMIN.
> 2. Use normal correction to control the TRs and updates the documents at the same time.
Thank you for the reply. Concerning these points:
1) This is done... No questions there
2) The "and" in your sentence means that I myself have to do both things? So there is no link?
So this does mean that (what my understanding was) I have to create a normal change via ChaRM but under the project for example a certain business scenario. That developers work on all topics related and should "remember" that if they put something under that transport they should verify if this is documented in the SOLAR02?
If then the change is put to testing they should manually update the status of everything related to this transport in the SOLAR02...

Documents used / prepared in an implementation project

Similar Messages

Maybe you are looking for