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

Similar Messages

SNP Life Cycle Process

Hi 2all SAP Ppl
Could please any one explain what the complete process of SNP i mean right from getting Forecast
in to SNP .what processes will carry out in SNP up to end of SNP cycle.
Please help me out your help will be greatful,anticipation for u experts help.
Thanking u
Ronald
Edited by: ronald.wens on Jul 26, 2009 1:51 PM
Edited by: ronald.wens on Jul 26, 2009 1:52 PM
Edited by: ronald.wens on Jul 26, 2009 3:56 PM

Hi Ronald,
As required, more details and explanations as below.
1) SNP is a rought cut planning cycle
2) It involves 3 engines heuristic, ctm and optimiser
3) It basically plans for infinite planning and in some cases finite too
4) It has engines capable of producing optimised results with huge
constraints taken into account
5) It works based on master data like resource, product, location,
quota, transportation lane, costs etc.,
6) SNP plans based on DP output as forecast
7) Using forecast, it plans for production, procurement and distributes
its planning results
8) The SNP planning outputs are in the form of purchase requisitions
and planned orders
9) The outputs are again (optional) sent to PPDS for further detailed
planning (depends on the scenario)
10) Capacity levelling is part of SNP life cycle process to level the
bucket outputs
11) Optimiser basically considers costs into account for planning
12) Transportation lanes are basically maintained for Deployment
and TLB generations
13) In SNP, system tries to compensate between demand Vs
supplies.
Hope it is more clear to you now.
Please confirm
Regards
R. Senthil Mareeswaran.

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

1 life cycle implementation

hi Frnds,
i want to know abt the process in implementation phase & wht is 1 life cycle implementation?
any doc reg this mail me <u>[email protected]</u>
points will be awarded

Have a look at this:
/thread/172255 [original link is broken]
Regards

Life cycle of a web dynpro callable object

What is the life cycle of a web dynpro callable object.
Means when that Web dynpro callble object is used in a GP process which method of that component called first and what is the sequence of the method execution in that.
Can anyone please explain me.

Sorry ritu there was one mistake in the above two replies.
The actual execution of the methods when a callable objects is get executed is as following
1.component controller's init() method
2. interface's init() method
3.view's init() method.
4.interface's execute() method
5.view's wDoModifyView() method.
If you want to change anything on your view according to the change in the interfac's execute method.
Then you have to do that coding in view's wDoModifyView() method.
with regards
shanto aloor.

Request for information on Contract Life Cycle in SRM 4.0

Hi SRM Experts,
I am implementing Contarct Process in SRM 4.0.
How I can create PO (or cntract release order) with reference to contract (created with process contracts).
Could you please provide SRM 4.0 contract Life Cycle.
Thanks,
Sudarsan

none

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.

Servlet life cycle/Singleton pattern/synchronized

I have some questions about the life cycle of a servlet and the use of synchronozed.
We have a main controller class that is extended from HTTPServlet and accepts all HTTP requests. It in turn instantiates another class to do the work. That class eventually returns control to the main controller and the request is forwarded. It is a typical MVC.
1. Once the helper class is instantiated how long will it live? We never destroy the class. I can debug the class using JBuilder and see variables set from the previous access.
2. While the class is in memory, if two or more requests are requiring the use of it, is a copy of the class created and used by each request. These particular classes are not instantiated as 'private static' instances.
3. If no copy is made, will the requests wait for the other to finish its processing before it gains control of the class. If no, I am assuming that proper use of synchronized will eliminate any issues.
4. Anyone have advice on where and when to synchronize or do you know of any good articles on this topic.
Thanks in advance for any advice you can give.

Hello,
Many of your question depends on where you declare the helper class, so here it goes:
1) The helper class will stay in memory as long as it's scope lasts. Ie: If you declare it as an instance member of the servlet it will stay alive until the servlet is unloaded by the application engine.
2) In short, local and parameter members, yes. Instance members no.
3) Most servlet configurations servers multiple requests on the same servlet. So if your helper class is an instance member it can be accessed be multipe threads at the same time. You can also declare that your servlet is not thread safe and the application engine will create multiple copies of it instead.
4) Er... Have a look around. I'm sure there are several examples and tutotrials on this site alone.
Yours
- Lars J. Nilsson

SAP HCM Life Cycle

Hi Expert,
Can anyone help me with the life cycle stages of SAP HCM.
I have a student who asked me what is the concept of SAP HCM, I explained about where was it started, what is the architecture, why is SAP preferred against other applications, modules covered, logic of integration... I would like to know if I am missing on anything as far as Concept is concerned.
Thank you in Advance.
Sejal

Hi,
There is nothing as such called lifecycle of SAP HCM.
It is similar to an ERP application, and basically your organization first decides which of the ERP module they are going to implement, once they have decided to go for HCM, they wil opt for it.
Again in HCM it depens on customer which module he is going to implement and HCM is vast it inlcudes PA, OM, TIME, PAYROLL, BENFITS, TRAVEL MANAGEMENT, LSO, Performance management, HR Forms and Processes etc.
This implmentation has a life cycle - like
Requirement gathering, Blue printing, Realization, implementatin (Configuration and coding), Custom implemenation, Integration if required, Testing (includes, UT, SIT and User acceptance testing), Documentation and hence Go Live.
This is a huge process and requires domain / business / technical/ functional / Quality / Knowledge experts.
Hope it helps you.
Thanks & Regards, Swapnil Mishra

MM Life Cycle

Hello All,
Can any one give me life cycle of MM
I want to create PO for material and do whole process so that it will do the stock filling for me for that material.
Because this material i need to use in SD and it is not delivered by Third party.
so i have to complete the life cycle in order to proceed further.
Thanks
Sundu

hi,
by using t.code me21n we can create purchase order- no accounting document will be generate
by using t.code migo we can create goods receipt-
inventory raw material a/c-dr
to
gr/ir clearing account
t.code miro is used for invoice verification
gr/ir clearing account-dr
to
vendor acount

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.

Can more than 1 full life cycle implementations be done for a company?

Hi there,
Can anybody please tell me if its possible to do more than 1 full life cycle implementation for a company with multiple company codes? From my understanding, SAP life cycle is ASAP methodology, starting from project preparation to go-live. So if I'm implementing sap for 1 company code, I'll be completing 1 full life cycle implementaion. Now if i do the same for another company code, for the same parent company, will that be considered as 2 full life cycle implementation? Kindly help. I'm not so clear about this full life cycle implementation concept.
Would really appreciate your gekp.
Awaiting response,
Fieona

HI,
Well I think It is possible but there are two cases.
If the implementation is in some company code having same business as the company in which initially SAP was implemented and all the business processed are same then in that case it would be called Rollout. In rollout you would only create the Organizational data that is enter prise structure and master data for that company but there will be no new process configuration as all the running process are already there.
How ever if you talk about the group lets say has two three completely different business for ex AUto mobile and Power and you implemented it initially in Automobile. Now you want to implement in Power generation sector then definately it would be a fresh implementation. In this case the most important is that you will prepare new BBP as all the business process are different. A complete new documentations, new master data , org elements and a different realization phase and testing phase would be there.
Please correct If I am wrong.

Servlet Life Cycle. .can anybody say whether this is correct or not

Hello everyone
Servlet Life Cycle.This is what i understood .can anybody say whether this is correct or not
According to sevlet specification,servlet life cycle has 4 stages
1)Loading and instantiation
2)Initialization
3)service the request
4)destroy
When we start webcontainer, webcontainer looks for deployed web applications and reads deployment descriptor of each web application.In the process of reading web.xml webcontainer container creates servletcontext object for holding context parameters and servletconfig object for holding servlet init-parameters after finding the servlet classes of the web application.
After finding the servlet classes webcontainer loads the servlet classes.
Loading can be done in 2 ways
1)When Webcontainer starts(loads) the webaplication by using load on startup in web.xml.
or
2)when first request comes for the webapplication
Say webcontainer starts the webaplication by using load on startup in web.xml ,Webcontainer creates an instance of servlet class and call init method of GenericServlet class by passing ServletConfig as parameter to init method i.e init(ServletConfig config).The code that is part of this init method initilize the ServletConfig variable of GenericServlet class and call init() method of GenericServlet class.
So when a request comes,webcontainer creates HttpServletRequest object,
HttpServletResponse object ,identifies the servlet class based onthe URL and
allocates a thread for the request and calls
service(ServletRequest req,ServletResponse resp) of HttpServlet class by
passing HttpServletRequest object, HttpServletResponse object as arguments.
Since req,resp are of type ServletRequest,ServletResponse they are type
casted to HttpServletRequest , HttpServletResponse and calls
service(HttpServletRequest req,HttpServletResponse resp) of HttpServletand
here request method is determined and either doGet()/doPost() methods are executed.
And finally when desroy method is called.

Mostly, but a servlet that has been initialized may service any number of 0 or more requests before being destroyed. So the life cycle might be:
1) Load
2) Initialize
3) Service a Request
4) Destroy
or
1) Load
2) Initialize
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
4) Destroy
or
1) Load
2) Initialize
4) Destroy
For any given <servlet> definition, you might have a combination of all:
1) Load (instance 1)
2) Initialize
4) Destroy
1) Load (instance 2)
2) Initialize
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
3) Service a Request
4) Destroy
1) Load (instance 3)
2) Initialize
3) Service a Request
4) Destroy
And for some Servlets with special configurations you might get:
1) Load (instance 1)
2) Initialize
1) Load (instance 2)
2) Initialize
1) Load (instance 3)
2) Initialize
3) Service a Request (instance 1)
3) Service a Request (instance 2)
3) Service a Request (instance 3)
3) Service a Request (instance 2)
3) Service a Request (instance 2)
3) Service a Request (instance 2)
3) Service a Request (instance 1)
3) Service a Request (instance 2)
3) Service a Request (instance 2)
3) Service a Request (instance 3)
3) Service a Request (instance 1)
4) Destroy (instance 1)
3) Service a Request (instance 2)
4) Destroy (instance 3)
4) Destroy (instance 2)
Finally, if you have multiple <servlet> entries in the web.xml (maybe with different servlet names and mappings) then you could have multiple parallel chains of this sort of life-cycle.
The key concept you have is correct. But once you understand that it is important to know that you really have no control over the lifecycle of the Servlet and that you should not assume anything about it.

MM process life Cycle

Similar Messages

Maybe you are looking for