BW project life cycle document

Dear BW experts,
Couple of days back I had finished SAP BW course and now reading BW documents. I would appreciate if some one could send the BW project life cycle document. Could any one send the responsibilities of BW technical consultant and I think it would differ in (Implementation and maintenance project). My id is [email protected]
Regards,
Bhaskar

Hi Gula,
Hope you would be interested to know on ASAP methodology!Go through : http://www.sapfans.com/sapfans/repos/sapfile.pdf
Regards,
Happy Tony

Similar Messages

Life cycle and desing patterns

Hi Friends,
I am new to SAP BI/BW and learned extract and Reports
Now i am getting some doubts like what sdlc and design patterns are used to SAP BI/BW
Please could you suggest , whether we are have to use in BI/BW
thanks
Babu

Hi Babu,
SAP BI/BW project also has got the standard project life cycle steps. Whenever you are working on a SAP BI/BW implementation project it starts from
Requirement Gathering -
> Blueprinting -
> High level and detailed design -
> Implementation -
> Unit Testing -
> Integration Testing -
> Go live.
Regards,
Durgesh.

What is step by step in real time project i.e. end-to-end life cycle?

what is step by step in real time project i.e. end-to-end life cycle?

Hi Vamsi,
The below explanation gives you an idea of what is going to come after what in a software development.
These below stages are know as Software Development Life Cycle/Waterfall Model.
1. System/Information Engineering and Modeling
As software is always of a large system (or business), work begins by establishing the requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when the software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up. Once the ideal system is engineered or tuned, the development team studies the software requirement for the system.
2. Software Requirement Analysis
This process is also known as feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, target dates etc.... The requirement gathering process is intensified and focussed specially on software. To understand the nature of the program(s) to be built, the system engineer or "Analyst" must understand the information domain for the software, as well as required function, behavior, performance and interfacing. The essential purpose of this phase is to find the need and to define the problem that needs to be solved .
3. System Analysis and Design
In this phase, the software development process, the software's overall structure and its nuances are defined. In terms of the client/server technology, the number of tiers needed for the package architecture, the database design, the data structure design etc... are all defined in this phase. A software development model is thus created. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.
4. Code Generation
The design must be translated into a machine-readable form. The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like compilers, interpreters, debuggers etc... are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.
5. Testing
Once the code is generated, the software program testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases. Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations.
6. Maintenance
The software will definitely undergo change once it is delivered to the customer. There can be many reasons for this change to occur. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.
Reward if helpful.
Thankyou,
Regards.

Needing specifics for full life cycle SD project.

Hello Gurus,
will you please tell me the whole process and steps for a full life cycle SD project? I need detail and specific information about that. please don't provide those general or overview info for that. highly appreciate in advance.
Many thanks.

Hi Vansanth
To know Pharma processes and associated configuration (do not think WM is there), this is the best link:
http://help.sap.com/bp_bblibrary/600/BBlibrary_start.htm
Best regards
Ramki

What is the total life cycle involved in any project

Hi ,
Can n e body help me in knowing the complete life cycle of any project.
Starting from the point customer wants to implement SAP for their business to implementation and support.
thanks in advance,
sastry

Dear Sastry,
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 : Development and Configuration
5. Go Live and Post Go Live support : Going Live and 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
Reward points if it is helpful.
Thanks and Regards,
Naveen.

Need projects functional setups documents

Any body have any documents (or link for documents) which explain complete life cycle of project functional setups and its explanation with screen shots.
I am new to this module i need to learn from basic.
Regards ,
azamtulla khan.
[email protected]

Hello
To get overview and basic concepts you may need to review Oracle Projects Foundementals.
For setup instructions and explanation I suggest you follow Oracle Projects Implementation Guide.
Both documents are available if you search METALINK Knowledge tab, or go directly to the following site:
[http://www.oracle.com/technology/documentation/applications.html]
Dina

Regarding Life cycle

Hi
this is santosh
What is life cycle implementation? generally some companies ask the person have at least one life cycle implementation what does it mean?

hi,
life cycle implementation means we can develope project from scrach onwards.
life cycle implementation contains genarally 5 phases, these are
Five Phases of ASAP methodlogy.
Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project.
Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System.
Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).
Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.
Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.
regards,
Ashok Reddy

Accounting entries for OTC life cycle

Hi Guys,
I was wondering if anyone of u can explain me the complete accounting entries that get credited and debited....right from booking an order till reconcilation (the whole OTC life cycle).
Thanks & Regards,
Ravi.

All looks good but there can be exceptions if you introduce two variables:
1. Invoicing Rules and Acconting Rules. These will affect your accouting in AR (Invoicing Rule will affect your Receivables and Accounting rule will affect the revenue accounting).
2. If you are on R12, there is Customer acceptance process that will change the accounting on both COGS and Revenue accounting a little bit but the final entry remains the same as you mentioned.
Forgot to mention: In someones blog on in Metalink's section where customer's documents are uploaded in knowledge base, I found a decent document that can help you with some more information.
Thanks
Nagamohan
Edited by: Nagamohan on Oct 2, 2008 6:11 PM

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD?

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD in any company?

Anand,
let me start with saying that the question you ask may not help you to determine the duration of your project. As Ryan and others stated the duration of the project is highly dependent on the scope of the solution you are implementing, geographical scope, amount of modifications/enhancements, number of languages, number of users that need to be trained, amount of standard processes customer is able to re-use in the implementation and many other factors (like quality of implementation contractor you will chose and availability of customer and implementors resources). I can probably go on for another couple lines, but I guess you get the idea.
With that out of the way let's talk about some example implementations that will give you an idea - Ryan did great job outlining what I would call traditional approach above. I have couple examples where customers leveraged innovative deployment strategies that are available today. In particular the project teams leveraged pre-packaged services like RDS, World Template or Best Practices as their baseline solution and they built from there. Second acceleration technique customers now leverage is the deployment in the SAP HANA Enterprise Cloud to accelerate the time to initial setup of the system and thus move from traditional blueprinting to scope validation exercise that further shortens the time. There are other acceleration techniques we see applied in some cases like use of iterative implementation of the delta requirements on top of the baseline solution.
Let me offer few examples to illustrate what I explained above:
ERP implementation at Schaidt Innovations with 3 months long deployment of ERP solution using ERP RDS as a baseline (you can view their testimonial here - Schaidt Innovations: SAP ERP on HANA in the cloud - YouTube)
Customer in Asia with global template deployment that leveraged SAP ERP for Manufacturing with deployment to cloud and 9 countries rollout (Japan, Korea, China, Taiwan, Hong Kong, UK, Germany and US). The initial deployment took 4 months for first country and 2 months for rollout into the additional 8 countries - so total of 6 months. The original plan using traditional approach with full blueprint and heavy configuration was estimated to be more than double of the actual deployment time.
There are many other examples where customers follow the assemble-to-order delivery model for their project and gain significant benefits doing so. I suggest you to review some of the recordings we did in 2013 about this approach and if you are member of ASUG review the Agile ASAP sessions we did for ASUG PM SIG.
Link to webinars: SAP A2O Webinar Series Schedule
Let me know if you have any questions.
Jan

MM process life Cycle

Hi
Can anyone provide me with the MM process life cycle . please forward me the documents on [email protected]
Thanks and Regards
Naval

Hi Kishore,
Are you working with prospecta software...are u working for australia client...how z u r colleques Hari and all....The following are MM life cycles...
Purchase requisition
request for quotation
quoatation
purchase order
Goods receipt
Invoice verification.....
hope its enough...
regards
Dinesh. A

Custom code life cycle management (CCLM)

Hi Gurus ,
At this moment i'm working on Custom code life cycle management concept in Solution Manager.
If any one worked on this one previously can you please send me complete document.
It's Urgent Plssssss
Thanks in Advance...
Vijay R.

Hi Vijay,
Check below links for CCLM
how to guide
https://service.sap.com/~sapidb/011000358700000426872012E
1547234 - Technical configuration of Custom Code Lifecycle Management
SAP Solution Manager WIKI - Custom Code Management - Solution Manager - SCN Wiki
https://websmp206.sap-ag.de/~sapidb/011000358700000426872012E
hope this helps
Thanks
Prakhar

Life Cycle Management BODI

Hi folks,
can anyone give me some hints how life cycle management is done in BODI?
I want to connect a DB2 database via BODI with a BI. BI comes in 3 tier layer. Would you install 3 BODI server? And if so how do I "transport" the changes from one repository (Development) to another one (Production)?
What is best practice for that?
Unfortunately I didn't find any documents so far.
Your help is very welcome.
Best regards
Michael

This is what I have: https://wiki.sdn.sap.com:443/wiki/pages/viewpage.action?pageId=49414406

Re: Life cycle in SAP BW

Hi gurus,
I am actually a newbie in looking for a job in SAP BW. Am more bent to put a 2-21/2 yrs experience since there's not place for freshers in UK industry, but most of the offers come saying either i should have a experience in full life cycle..could somebody explain how i could come over it
Regards
Sri

Hi ,
When they refer to the full life cycle its the ASAP methodology which SAP recommends to follow for all its projects.
1.Project peparation.
2.Business Blueprint.
3.Realization.
4.Fit-Gap Analysis
5.Go-Live Phase.
Normally in the first phase all the management guys will sit with in a discussion .
In the second phase u will get a functional spec n basing on that u will have a technical spec.
In the third phase u will actually inplement the project and finally u after testing u will deploy it for production i.e. Go-live .
U might fall under and get involved in the realization phase .
If its a supporting project u will come into picture only after successful deployment.
let us know if any queries .......
Regards --- Kumar Sarvepalli ........ Honor points

Using page life cycle (OnPageLoadBackingBeanB)class to update page controls

I used the onPageLoadbackingBeanbase class that exists in SRDemo to handle the page life cycle for my project ADF faces pages but found that the controls is null in all phases of the page
How can i use the page life cycle for dealing with the page controls like
filling selectOneChoice in the isPostback once not in every action or refresh
thanks

I sent this post 1 week ago and no response
please help
Message was edited by:
user560167

Role of DBA in DW life cycle

Hi friends,
Wouldu pls tell me what are the basic jobs to be done by a dba in a complete dataware life cycle?
Thanks in advance,
Pragati.

I would refer to the various books by Ralph Kimball for more information on this as he covers all the various roles within a data warehouse project. The Oracle Database 2 Day DBA 10g Release 2 (10.2) provides a comprehensive overview of DBA type tasks, most of which apply to any type of application (OLTP or data warehousing).
In addition DBAs might also be asked to manage design repositories such as those required by Oracle Warehouse Builder and other ETL tools and ensure these are configured and backed up correctly.
Much will depend on the size of the data warehouse team, the size of the project and the required roles and responsibilities. In some customers where I have worked there have been different DBAs covering development, testing, QA, prooduction environments. At other customers I have seen DBAs cover just about everything including writing deployment scripts. So there is no standard approach in my opinion.
Hope this helps,
Keith
Product Management
Oracle Warehouse Builder

BW project life cycle document

Similar Messages

Maybe you are looking for