Design,Build CRM Implementation Project

Hi Friends,
                I have been involved in Project Realization stage.Now we have a
              requirement where in we need to design,build(IMPLEMENTATION)
              project.Please send me any documents and what to know before
              stating a project.My mail ID is <b>[email protected]</b>
Jayapal Reddy.

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.
P.S: Reward if it helps.

Similar Messages

  • What are the roles in CRM implementation Project(all generic extractions)

    Hi Gurus,
    Now I am placed from a support project from BW (CRM) implementation project(all are generic extractions).
    & I am also new to implementation project.
    what are the neccessary steps to be taken when we are implementing BW for CRM.
    Gurus please clarify my doubts.
    1. what are the steps in implementation project in detail(as a developer).
    2. what are the sizes of the cubes,ODS & How to decide them.
    3. what are the neccessary steps for Master data & Transaction data.
    4.How to make the functional specifications for Infoobjects,cubes,ODS,Remote cubes,Multiproviders.
    5.can we change to delta loads to full loads if yes what happens to existing data.
    6.How flat file extraction used in the case of crm& how to do ascii format.
    7.What are the steps to be taken when we are creating Queries & Reports in BW CRM.
    It's very urgent.
    thanks = points.

    1. what are the steps in implementation project in detail(as a developer).
    U have to basically to the techinal design after understnading the functional designs and implemnet the same( creating infoobjects, datatargets, datasources, queries etc.). Then u have to load data and do the unit testing on the same.
    2. what are the sizes of the cubes,ODS & How to decide them.
    Completely the business reqmnet and the data that the client wants to load.
    3. what are the neccessary steps for Master data & Transaction data.
    U have to understand ur master data and transaction data on the basis of whch u have create ur infoobjects and load data in them and finally in the datatarget.
    4. can we change to delta loads to full loads if yes what happens to existing data.
    Sure u can do that by choosing Full update in the infopkg. It will just load the complete data instead of changed records.
    *Hope it helps.

  • 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 !

    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.
    P.S: Reward if it helps.

  • Crm implemention projects in india

    hi experts,
    can any one of u will help me to get information about the sap crm projects( client , implementation partner, sap crm version and time duration)

    Hi Srinivas,
    It is better to go for the implementation partner site and check for case studies and customer success stories, so that u can get some information abt the projects, but it is very difficult to get the exact information abt that,
    any how u can go this site u can get no of clients
    hope it will help u
    reward points if helpful to u
    all the best

  • Standard authorization role for CRM implementation team member

    We are starting SAP CRM implementation project (7.0) and I would like to avoid giving sap_all authorizations to functional consultants in development environment. Unfortunetly I can't find standard customizer profiles like the ones in ERP system exists.
    So the objective is to have quite broad role or profile with no restrictions in customization and functional area. However it's important not to have Basis authorizations in this role/profile. Hope that someone can give me a hint in this direction.
    Thnak you,

    as soon as the implementation team member should also do developments my experience is that without SAP_ALL you will have much trouble. Therefore in our dev-system each consultant will have SAP_ALL authorization. Of course only in the DEV-System.
    Kind regards


    Hi BI Experts,
    We have got a BI Implementation Project, wherein we have to implement CRM.
    I would appreciate if somebody sends me useful information or data for CRM Implementation Project at your earliest.
    My Email ID is [email protected]
    Please do the needful.

    Iam sorry i mean to say that CRM is one of the area for BI Implementation.
    Please send the necessary help on my mail ID [email protected]

  • Lot of build errors in project created for debug CRM 5.0

    Hi SDN!
    I want to setup java debugging for CRM 5.0 modified application. According to note 1154496 I created project "crm_b2b".
    I took file from
    server\usr\sap\<system name>\<instance>\j2ee\cluster\<server number>\apps\\crmb2b at first try and from
    server\usr\sap\<system name>\<instance>\j2ee\cluster\<server number>\apps\\crmcrb2b at second try. After import NWDS performed building for my project and shows lot of build errors (more than 12 thousands for 1-st try and near 2 thousands for 2-nd try). I reduced some of error by adding jar files from crm war file to build path. But I don't know how to resolve errors like "The method hasPermissions(Permission[]) in the type UserBase is not applicable for the arguments(EserviceHierarchyPermission[])" (error in, line 186). Also some of errors concerned with requierd libraries in build path.
    My NWDS is 7.0.14
    CRM 5.0 SP 11
    Regards, Lev
    Edited by: Lev Kulaev on Jul 3, 2008 2:03 PM

    Here are my doings:
    1) set breakpoint in standart code
    2) run my debug configuartion
    3) run CRM 5.0
    4) NWDS stopped execution on breakpoint
    5) I right-click on variable, choose "Watch"
    6) NWDS shows me "error during evaluation" in "Expression" tab for selected variable
    I'm confusing since it was possible to use "Watch" for variables in CRM 4.0.
    Yes, you right, I can view all variabe values on "Variables" tab. I wanted to use "Expression" tab because it's more comfortable for me but it seems that I can use only "Variables" tab.
    So, thanks for help! My question is answered, but if you can give me more information about subject, you're welcome.
    Regards, Lev

  • SAP crm implementation business scenario for crm  marketing project

    Dear guru's
    Can any body will help me to know about one sap CRM  marketing implantation project business scenario.
    Like one full process of marketing project and the integration of the other modules like r/3,
    Like what end users do if we implanted the marketing project for one company,
    Any industry but please give me detailed with the documentation if possible.
    I practice with the best practice but iam not able to the comparison to the business process of the company.
    No need to tell about company details I want  to know only the process.
    Like which type of company it is suet or which type of company it is not sute.
    If there is any document like this type of company sauté for the marketing and like this type of company suites for the service modules like that.
    this  is sivaanjith this is my  please help me to come out of this confusion.
    siva anjith

    well talking about the implementation project in CRM
    let us assume we are implementing it in BANKING industry
    here the requirement is in improvement in the field processing and all the effeciency of the sales or feet on street
    so we implement the CRM marketing with CIC
    what it will do that we start with first the readiness document that what all are the requirement of the bank and how the company can cope it with the help of CRM
    then we prepare the BLUEPRINT to state that the data to be processed will be strucutured in CRM in how many phases or the timely schedule of the roll over of CRM in bank
    next up we start with the configuration ,like we have to start campaigns and generate leads for the banks which may get converted into the opportunities
    so have to do all the configuration of CRM according to the requirements being given
    one thin g i forgot which is very imp is that we do requirement gathering,its pretty imp part of entire process
    after getting these only we can do whatever we want with CRm
    so after that we realise the configuration in realisation phase then we do those UATs and SITs
    this way we phase out the CRM in any sector
    just a gist of everything
    hope i cleared some air
    best regards

  • Info on activities involved in various stages in Implementation Project

    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,

    Based on ASAP methodlogy.
    1)Project Preparation
    2)Business Blue print preparation
    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
    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
    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
    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.
    Ravi Shankar.

  • 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?*

    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

  • Need urgent help in listing out checklist from DBA prespective for BI Implementation Project

    Hello Guys,
    We are in Designing phase Data Modeling of PDW/APS Implementation Project.
    I need urgent help in making a checklist from a DBA perspective.
    Like what are things ill be needing at a time of implementation/Deployment.
    Your expert comments and help will be highly appreciated.
    Thank you,

    You can get good summary of checklist from this article about
    DBA checklist for data warehousing.
    Which highlights on below pointers:
    New system or old. (I.e. Up-gradation vs starting from scratch)
    Complexity of SQL Server architecture 
    SQL Server storage
    Determining SQL Server processing power
    SQL Server installation consideration 
    SQL Server configuration parameter
    SQL Server security
    SQL Server Database property
    SQL Server jobs and automation
    Protecting SQL Server data
    SQL Server health monitoring and check ups
    SQL Server ownership and control 
    based on my real time experience, I will suggest you to keep an eye on 
    Load performance (It will be useful when your database(Warehouse) will have huge amount of data)
    System availability (Check for Windows update and up time configuration) 
    Deployment methodology should be planned in advance. Development of packages and respective objects should be done systematically.
    Source control mechanism 
    Disk space and memory usage
    You might or might not have full rights on production environment, so be prepared to analyze production environment via Select statements [I guess you got my point]
    Proper implementation of Landing , Staging and Mart tables.
    Column size (this can drastically decrease your database size)
    Usage of indexes (Index are good, but at what cost?)
    I hope this will assist you in building your check list.

  • 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. (
    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. (
    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 (
    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. (
    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. (
    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. (
    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 (
    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. (
    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.

  • 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

    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 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
    CSM Reddy

  • Solution Manager for Implementation project

    I want to know how we should use solution manager for an implementation project. I am aware about the ASAP methods and the transactions in solman system for each phase. I have starting trouble like how to and where to start with? My ECC systems are not yet installed. Still we can go ahead with Blueprint creation and definition of roadmaps etc. Currently, it is done on paper.  If anybody has done an implementation project through solution manager, could you please give me some hints how to start ? I repeat I am aware of the transactions but dont know what to add there in solar01/02 when the process are not defined/system not installed. Please guide me.

    Hi Rajeev,
    You're correct; you can start building the Business Blueprint without SMSY having all the systems that are 'to-be'. As long as you enter logical components in the project landscape with the correct product versions, you can replace those with the actual components once they have been installed. The BPR needs those product versions in the blueprint when you load the relevant scenario's. Once loaded, you can start documenting the scenario's, place the processes and process steps not used out of scope or delete them entirely and define custom scenario's, processes and process steps.
    When the Blueprint has been completed with relevant design documentation, the Configuration transaction can be used to document how you actually configure the systems and, of course, to configure them from Solution Manager. The system landscape officially has to be definitive at the end of the Blueprint phase, unless you won't be configuring the systems centrally from Solution Manager.
    The Solution is actually not necessary for a clean implementation; the Project will eventually lead to the solution. Once the systems are all configured and documented in SSM, you create the Solution and upload the project documentation into it in the Solution Directory.
    Let us know how you get on!
    Kind regards,

  • Charm in implementation project

    Hi All,
    Iam currently configuring charm in implementation project. We do not have QA and PRD systems build yet.
    I have created transport routes DEV>VQA>VPR ie with QA and PRD as virtual systems.
    Now how do I add this as virtual systems in logical component. If I create entry in SMSY manually, tomorrow when my QA and PRD systems are available, how do I change it?

    For demo system you can create three additional clients say 100>dev, 100> QA, 300> PRD and 500> solution manager ( that will be your original client).
    you can create logical component for the same in SMSY and also you need to set up the transport route accordingly.
    you can test the entire charm functionality this way.
    When you would be having your actual systems you can create another logical component and project for the real scenario in solution manager and adjust the transport routes and you can still keep the demo system active alongwith real system scenario in case you want that.

Maybe you are looking for