Doubt in implementation phase

hi
can u plz tell me in implementation phase where does the coding part comes is it in realization phase or in fit gap analasys.
wht do we do in customization phase

Customization is used to fit GAPs.
Thats where ABAP comes in picture.
check the links -
Implementation
Implementation
implementation scenario
Regards,
Amit
Reward all helpful replies.

Similar Messages

Oracle EBS R12 Pre - Implementations phase question air

Oracle EBS R12 Pre - Implementations phase question air
Posted: Jun 30, 2009 10:22 AM Edit Reply
Dear all Gurus,
We are going to implement Oracle EBS r12, for industrial concern, we have following quires if any peer may suggest.
1) we heard the oracle R12 has build new release with 11g db , is it been practical for choosing it for corporate ???
2) Linux Read hat which version is more stable like 5 releases is compatible with R12 new release?
3) We are also thinking for 64 bit architecture rather than 32 bit, could any one figure out the practical pros and cons for this.
4) We are also wondering about the server machine brand and its configurations like HP DL380 G6, DELL 2850? could any one share abut his experience about the same.
5) What sort of Server configurations (Processor , 2way -4way , RAM , HD and other accessories ) for r12 Multi node setup for 150 clients (DB Server , Apps Server , Test Prod )
6) What should be backup strategies like tap backup and how much space requirements we must have provisioned for retaining almost 2~3 month backup.
7) Application implementations methodologies?
8)
I know to address our queries would be time consuming for you bust peoples , but I would really oblige for being shared your journey this would defiantly the PATH way for other like mentoring for others.
looking forward your valuable instructions ASAP.
Thanks & Best Regards
Muhammad Waseem
Manager IT
Neee-Has Textiles Divisions
31-Q Gulberg II Lahore
Pakistan
92-0333-4240949

Duplicate post.
Oracle EBS R12 Pre - Implementations phase question air
Oracle EBS R12 Pre - Implementations phase question air

GAP's in the Implementation Phase

Hi !
What would be the general gap's we will be facing in the implementation phase and how they are going to fix it.
Please answer this question. It's urgent and necessary.
Regards,
Ben

Hi
GAP can not be generalised. It is Vary business to buiness and depending upon consultant that how that consultant give the solution for Business Process
Mann

Project duration as per implementation phases

Divide project duration as per implementation phases?

Dear Gopala Rao,
It actually depends on various factors, such as :
1. how many modules they want to implement.
2. Team Size.
3. Organizational Structure (Volume of data)
4. Legacy System
5. Business Complexity etc.
There is no hard and fast rule that every project should be completed in a particular duration of time. Depending on the above factors, it may vary any where from 6 months to 18 months or so. (Approximately, it may be less than 6 months or more than 18 months in some exceptional cases).
Usually it is divided into phases:
1. Project Preparation : Project team, infrastructure, Software, Steering committe etc will be identified in this phase.
2. Business Blue Print : Re-engineering of Business process and BBP sign off.
3. Realization : Analysing Gap and Realization of possible customization and development effort
4. Final Preparation and Go Live : Development and Configuration
5. Post Go Live support : Support after go live
You would allot specific time periods for each of these phases and will set milestones accordingly.
or it could even be like :
Project Start
Analysis
Design
Design Freeze / Client Sign-off
Construction
Testing
Implementation
Project End
Project Management Framework
Post Close Review
Training
Change Management
Refer following links for more info:
http://en.wikipedia.org/wiki/SAP_Implementation
http://www.sapfans.com/sapfans/asap/be_01_e.htm
There are different flavors of project implementations.
1. Template implementation - without much customization - based on a predefined rollout template
2. CUstom rollout
3. Ramp up rollout
4. Enhancements to an existing implementation
5. project recovery
The project life cycle consists of [1] Project Charter,[2]Scope,[3] planning,[4]Execution,[5]Control and [6] closure.
Charter tells you the purpose of the project,for example,to eliminate an expensive Transmission process by implementing EDI.
Scope tells what all you will be doing in the project.In SAP,this is Blue printing.
planning:Here you plan the capital Expenditure - capital budgeting,Expenses,Revenue,Resources and other elements that go in to the project.
projectExecution : Actual execution of the planned activities
Control:Here you steer the project towards the intended goals-variance analysis,cost Reduction,Value engineering,budget,standards,fast tracking,crashing,Resource allocation etc etc ,....all find a role here.Here Time,Cost and the other resources are controlled so as to complete the project in time and within the cost baselines.
Testing also comes here-unit test,integration test,UAT........
Closure:The project sign off takes place here.
In the support Environment the "project" will cover a]incident management,b] problem management,c]change management,d]configuration management e] Release management and f] help desk.
Reward points if it is helpful.
Thanks and Regards,
Naveen.

CHARM during implementation phase possible?

Hi Gurus
I would like to know the constraints of implementing CHARM during the implementation phase of the project.
I am aware that, charm functionality is best suitable for post go live change tracking tool and it is not recommended during the implementation phase. But I would like to know the reasons behind not recommending CHARM during implementation phase.
Please provide your valuable inputs.
Thanks.

Hi,
The following may not be the detailed reasons behind not recommending CHARM during implementation phase.
Implementation Project u2013 A project to implement SAP solution as a part of regular implementation or a roll out. This is considered for single-site implementations. Predefined scenarios can be selected from template projects.
Change Request Management (ChaRM) is an SAP tool to manage all those activities performed between the design of a change and the final promotion to a productive system
ChaRM can:
o Improve efficiency and transparency of change management processes
o Minimize business disruptions
o Store documentation of implemented changes
o Track and monitor changes
o Improve audit process
o Reduce risk of correction and project failures
ChaRM benefits are:
o Allow the Organization to control and manage changes in the SAP system effectively
o Guarantee that any change to the SAP system follows the standard process flow and procedures with mandatory controls and documented steps
o Effectively adheres to requirements for SOX compliance
Please also go through [this|http://www.sap.com/community/webcast/2009_06_worldtour_fr/2009_06_Worldtour_SOL1_SAP_fr.pdf] document.
Hope it helps.
Cheers,
Satish

Implementation Phases in ASAP Method

Hi Gurus,
Can anybody explain me the following.
a) Implementation phases in ASAP method
b) Detailed activities in each phase.
Please forward me documentation, if any.
Regards,
Santosh

When you open ASAP it will show you all phases and activities you have to do.
You can follow the method ASAP or only use some part out it.
The phases are the same as all project methods only the names are different
ASAP is now replaced by solution manager. When you don't have ASAP it is better to use solution manager

Bw implementation phases

Hi gurus,
In a bw implementation project 5 phases are there.
As a bw consultant in that five phases what is our responcibilities.
points will be assigned.
Thanku

Hi Chinnu,
Phase 1: Upgrade Project Preparation -
The purpose of this phase is to provide initial planning and preparation for your R/3 upgrade project. Although each upgrade project has unique objectives, scope and priorities, the steps in Phase 1 help identify and plan the primary topics that must be considered.
Phase 2: Business Blueprint -
The purpose of this phase is to establish a common understanding in your company about how the new R/3 release will handle your current business processes after the R/3 upgrade.
Phase 3: Realization of DEV and QAS -
The purpose of this phase is to perform the upgrade of all non-production R/3 Systems, which normally include development (DEV) and quality assurance (QAS) systems, and to ensure the quality of this upgrade process by comprehensive testing. You need to upgrade your DEV and QAS systems before performing the upgrade for your production system (PRD). Furthermore, you will develop your end user documentation and training in this phase.
Phase 4: Realization of Production -
The purpose of this phase is to complete the final preparation for the upgrade of the production R/3 System, and end user training, if necessary. On the successful completion of this phase, you are ready to run your business in your upgraded production R/3 System.
Phase 5: Go Live and Support -
The purpose of this phase is the transition from your previous R/3 System to a newly upgraded and improved R/3 System. Be aware that you must set up an ongoing support organization to service your R/3 users, both during the first few days of your upgraded production operations, and on an ongoing basis.
For Roles & Resposibilities:
check these links:
http://help.sap.com/bp_biv335/BI_EN/documentation/BW_ROLES_SKILLS.doc
/people/mary.huang/blog/2005/06/01/bw-project-management-as-a-jigsaw-puzzle
/people/marc.bernard/blog/2005/02/08/follow-me-into-the-world-of-business-intelligence
/people/arunkumar.sampathkumar/blog/2006/09/08/configuring-ep-for-connecting-to-bw
Also check:
http://help.sap.com/bp_biv135/html/index.htm
Go through these links:
http://csc-studentweb.lrc.edu/swp/Berg/articles/Managing%20SAP%20BW%20projects%20part-1%20v7.ppt
http://csc-studentweb.lrc.edu/swp/Berg/articles/Managing%20SAP%20BW%20projects%20part-2%20v15.ppt
Standard business content queries, cubes etc. depending on application you can find here:
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
Responsibilities of an implementation project...
For ex, Lets say If its a fresh implementation of BI or for that matter you are implementing SAP...
First and foremost will be your requirements gathering from the client. Depending upon the requirements you will creat a business blueprint of the project which is the entire process from the start to the end of an implementation...
After the blue print phase sign off we start off with the realization phase where the actual development happens... In our example after installing the necessary softwares, patches for BI we need to discuss with the end users who are going to use the system for inputs like how they want a report to look like and what are the Key Performance Indicators(KPI) for the reports etc., basically its a question and answer session with the business users... After collecting those informations the development happens in the development servers...
After the development comes to an end the same objects are tested in quality servers for any bugs, errors etc., When all the tests are done we move all the objects to the production environment and test it again whether everything works fine...
The Go-Live of the project happens where the actually postings happen from the users and reports are generated based on those inputs which will be available as an analytical report for the management to take decisions...
The responsibilites vary depending on the requirement... Initially the business analyst will interact with the end users/managers etc., then on the requirements the software consultants do the development, testers do the testing and finally the go-live happens...
BW Data Architect
Description
The BW Data Architect is responsible for the overall data design of the BW project. This includes the design of the:
» BW InfoCubes (Basic Cubes, Multi-cubes, Remote cubes, and Aggregates)
» BW ODS Objects
» BW Datamarts
» Logical Models
» BW Process Models
» BW Enterprise Models
The BW Data Architect plays a critical role in the BW project and is the link between the end users business requirements and the data architecture solution that will satisfy these requirements. All other activities in the BW project are contingent upon the data design being sound and flexible enough to satisfy evolving business requirements.
Time Commitment
the time which must be committed to this Role to ensure the project requirements are met
Project Complexity Time Commitment
Low If the BW project utilizes standard BW content and InfoCubes, this role can be satisfied by the BW Application Consultant.
Medium If the BW project requires enhancements to the standard BW content and InfoCubes and/or requires the integration of non-SAP data, this role may require a committed resource.
High If the BW project requires significant modification and enhancement to standard BW content and InfoCubes, it is highly recommended that an experienced resource be committed full-time to the project.
Key Attributes
The BW Data Architect must have:
» An understanding of the BW data architecture
» An understanding of multidimensional modeling
» An understanding of the differences between operational systems data modeling and data warehouse data modeling
» An understanding of the end users data
» An understanding of the integration points of the data (e.g., customer number, invoice number)
» Excellent troubleshooting and analytical skills
» Excellent communication skills
» Technical competency in data modeling
» Multi-language skills, if an international implementation
» Working knowledge of the BW and R/3 application(s)
» Experience with Data Modeling application software (i.e., ERWIN, Oracle Designer, S-Designer, etc.)
Key Tasks
The BW Data Architect is responsible for capturing the business requirements for the BW project. This effort includes:
» Planning the business requirements gathering sessions and process
» Coordinating all business requirements gathering efforts with the BW Project Manager
» Facilitating the business requirements gathering sessions
» Capturing the information and producing the deliverables from the business requirements gathering sessions
» Understanding and documenting business definitions of data
» Developing the data model
» Ensuring integration of data from both SAP and non-SAP sources
» Fielding questions concerning the data content, definition and structure
This role should also address other critical data design issues such as:
» Granularity of data and the potential for multiple levels of granularity
» Use of degenerate dimensions
» InfoCube partitioning
» Need for aggregation at multiple levels
» Need for storing derived BW data
» Ensuring overall integrity of all BW Models
» Providing Data Administration development standards for business requirements analysis and BW enterprise modeling
» Provide strategic planning for data management
» Impact analysis of data change requirements
As stated above, the BW Data Architect is responsible for the overall data design of the BW project. This includes the design of the:
» BW InfoCubes (Basic Cubes, Multi-cubes, Remote cubes, and Aggregates)
» BW ODS Objects
» BW Datamarts
» Logical Models
» BW Process Models
» BW Enterprise Models
BW Project Implementation and Rollout
Global IDs uses a modified version of the ASAP methodology to ensure a robust BW environment is implemented, tested, and delivered. The project milestones include the following:
Blueprinting
Realization
Roll Out
Post-Implementation Support
Organizational Change Management
BW Maintenance
Once the BW environment is implemented, tested, and delivered, we can perform the maintenance using both onsite and offsite resources. Our maintenance contracts ensure that the customer can depend on us for:
Troubleshooting and Error Correction
Creation of New Infocubes
Customization of reports
Archiving and Storage
Data Maintenance
Focus
Also Check the below Links:
Check this link for GAP Analysis:
Hope this helps
Regards,
Ravikanth

Implementation Phases - Which is toughest of all?

Out of 5 phases of ASAP Methodology, which phase is considered as the most Challenging phase in SAP-HR Implementation?

Hi,
Although all five phases have their own difficulties, I do attach the greatest importance to business blueprint phase in my projects. This is because, in this phase you determine the backbone of your system and all subsequent phases are built upon this backbone structure. Any error in the backbone would require a great deal of re-work.
Best regards,
Dilek

Regarding Implementation phases

What are the phases in SAP Implementation and in which phase data migration takes place?

hi
Following are the steps involved in SAP implementation using ASAP methodology
Phase 1- Project preparation: initial planning and preparation.
Phase 2 - Business Blueprint: documentation of the business process requirements of the company.
Phase 3 - Realization: implement all business and process requirements based upon the business blueprint.
Phase 4 - Final Preparation: complete testing, user training, system management and cut-over activities.
Phase 5 - Go-Live & Support: transition from implementation to production.
Care to be taken at mapping the current business scenario into SAP system during Busines Blue Print Phase .Business users should have understanding of SAP system prior to Implementation.
These are some of the details you can look for:
Business Goals
Know how your project will benefit the business, and make sure you communicate those benefits to the employees who will use the technology. Poorly defined goals doom a technology project; well-defined goals help keep all project personnel working together. The system with unclear business benefits is one better left unsponsored and undone.
User Involvement
Getting user buy-in requires more than just communicating benefits. It also helps dramatically to enlist users' collaboration in designing or selecting the system.
To convince business line managers to lend their workers to the front end of a project, executives recommend talking to their wallets.
Risk Management
Every I.T. project faces risk, whether it is technical (caused by unproven technology or integration problems) or business risk. Veterans say project sponsors should not only understand the risks but also demand that contingency plans be put in place before the first nail is hammered. But even though risk management is a project management basic, it is easy for executives with little technical knowledge to ignore it because they are intimidated by the technology. Fortunately, they also say technical risk is easier to manage than business risk. If the project hinges on a relatively new technology, it makes sense to build and test a prototype before going whole hog.
Scope Management
Keeping requests for new features from derailing or slowing down a project is a step that should be handled by the project manager, but occasionally the executive sponsor has the clout to say no to a request the IT leaders can't refuse. Besides inflating costs, scope creep can deflate user enthusiasm as the project's benefits are pushed off. Getting the project done quickly is a good goal for the executive sponsor to champion; bells and whistles can be added later, after the initial rollout. "Vanilla is a very good flavor"
Appropriate Accountability
No accountability, no progress--that's no surprise. The challenge in IT projects is to hold the right people accountable for the right deliverables. The IS department's job is to hand over the specified level of system functionality by the due date. After that, it's up to the business workers to get the specified business benefits out of the system. And the executive sponsor should make sure accountability is in place to enforce that division of labor.
Non-IT execs have a tendency to exaggerate the role IS workers will play after a system is rolled out. As a result, it is common to point the finger for system failure at IS. That gives the other employees less incentive to make the new system work.
IS and business line workers develop a lot more synergy when both feel an equal burden of responsibility.
Helpful Hype
Amidst all the spreadsheets, numbers, risk analyses and so forth, remember to add a spoonful of sugar for those who will actually have to use the technology.
verify the following links
http://en.wikipedia.org/wiki/SAP_Implementation
hope it will help you
regards
sreelatha gullapalli

ChaRM: switch back project implementation phase

Dear All,
is it possible for an implementation project to switch back the phase (for example from test to development or from golive to Emergency Correction)? Which are the contraindications?
Regards,
Bob

Hi Bob,
- technically nothing is blocking you from that
- functionally: you should just pay attention to what have been done in last phase before switching. As long as transport requests sequence is respected during import (meaning you use ChaRM for imports) there should nt be any contraindication
be aware that by checking table /tmwflow/tpphmac for phase model 'devrl' (that corresponds to implementation project) you ll know what is exactely allowed in each phase of your project type.
SAP Would not recommend changing values in this table though
Regards
Khalil
Edited by: Khalil SERRHINI on Sep 7, 2010 11:01 AM

ECC 6.0 and BI Authorizations in Project Implementation Phase for Dev only

I ) ECC 6.0 Authorizations for Project Team
     I have browsed through SDN and gone through several documents and perhaps trying to post our senario as clearly as possible for better answers
Aim : 1) To give appropriate authorizations to
      a) Functional Consultants
      b) ABAP developers
      c) BI consultants
      in Development environment only on Customizing client,
      sandbox client and unit testing client
There is no inhouse security consultant in house at this time.
Type of Oragnization : Midsize
project Life cycle phase : Bluprint-Realization
Question1:
     What role and profile should I assign to functional consultants by preparing a role from the SAP standard role and what is the best way to restrict functional consultants from sensitive areas.
eg: Modifying SAP_ALL option and assigning it to functional consultants.
II.
BI 7.0 Authorizations for BI consultants in Development environment
Aim: 1) To give authorizations to BI 7.0 consultants (using only ABAP          stack)
Question: I have read through some forum and wiki answers in sdn and many explain that give SAP_ALL and SAP_NEW to BI consultants and in addition give 0bi_all, SAP_BW_DEVELOPER and much more.
    Can some body list what are the needed Roles for this kind of users ?
I know in theory many talk, do not assign SAP_ALL, but the person who advice this never explained the best alternative, and none of them I know have practially told that they have not assigned SAP_ALL.
Please explain . I think asnwering my question will bury many questions in this fourm .

Hi Nick,
Did you get the answer? I'm lookinf for the same information about profiles.
Thanks!!

Doubts on implementation of SEM BCS in version 6.0

Someone possessing the implementation model of SEM BCS in version 6.0?
tks regards

<div class="jive-quote">which notes to be applied initially</div>
- OSS notes are used just to correct some errors found in the system. The system may have a different core (SAP R/3, ERP, ECC etc), patch levels, service packages installed, components installed, their release/versions, EhP functionality (if any) and so on. Everything is very individual.
<div class="jive-quote">which is not setting standarts</div>
<div class="jive-quote">if there is an implementation model step by step</div>
- None that i'm aware of.

Doubts in Implementation project

Hi,
can somebody guide me for the following terms in implementation porject?
1. Function specification 2. Business blueprint 3. Functional design document
4.Technical design documnet 5. FD & Td's
can u explain me what is the sequence of documents in Imp project?.
Thanks in advance
VSM

Hi Subbu,
Functional Specification
Detailed information about our Report requirements,Sources Of data,Detail explanation from the key user of that particular area, About tables and fields .....This JOB is gennerally done by FUNCTIONAL people
Business Blueprint
Information Requirements Analysis
Multidimensional Data Modeling
Templates Business Blueprint
Sizing, Hardware Sizing
review BW System Lanscape & Transport
Authorizations
Functional design document
data flow about...Fuctionality
Technical Specification
Using FUNCTIONAL SPECIFICATION we r going to prepare an Design document of what are the objects you are going to use in the system and what type of Data Sources your are using and Targets etc.. This is nothing but an Technical Specification... and this also contains what type of the load is it...
For ASAP Methodology see the following link :
ASAP
Scenario bases doc:
http://help.sap.com/bp_biv335/BI_EN/documentation/SolutionScope_EN.doc
check in the following thread
SAP BI/BW Technical Documents
http://help.sap.com/bp_biv335/BI_EN/html/Business_Blueprint.htm
Hope it clarifies......U
Regards
chandra sekhar

Doubt in implementing OWSM policy in osb 11g

Hi,
Can anybody tell me how to implement basic username-token policy in wsdl based paroxy service in osb 11 G.
I am able to select service policy configuartion from the policies tab of proxy service in sb console,but after that i can not find any OWSM policy there to add.Pls assist me

have you run rcu to create mds storage for the policies?
and after that you run the configuration wizard to expand your domain with "Oracle Service Bus OWSM Extension" ?

Doubt in Implementing BAdI CRM_BWA_MFLOW

Dear ABAPers,
I have to implement the BAdI "CRM_BWA_MFLOW".I want to know in Which transaction code it is called and What is the Purpose of this BAdI.
Thanks & Regards,
Ashok.

Hi Ashok,
CRM_BWA_MFLOW is used to extract data from CRM System.
Please check the below post its almost similar to your post and has good information on the BAdI "CRM_BWA_MFLOW".
Hope this helps you.
Re: CRM Enhancement
Cheers!!
VEnk@
Edited by: Venkat Reddy on Oct 29, 2008 3:37 PM
Edited by: Venkat Reddy on Oct 29, 2008 3:57 PM

Doubt in implementation phase

Similar Messages

Maybe you are looking for