on 10-16-2007 12:29 PM
Set up change request plz wht is the meaning of that try to give me somme ideas and examples.
thanks in advance
Hello,
Change requests are used to transport objects across the clients in a system landscape.
That is when you carry out any customisation in SPRO or do any ABAP task a change request is generated in the Golden client which is moved to Quality Systems first and then to Production system.
Once a customising/workbench task is completed, you release the change request using transaction code SE01.
and then the Basis guys transport the same to Quality and to the Production systems.
<b>REWARD POINTS IF HELPFUL</b>
Regards
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could anyone explain m how to design and customize a change request ? When the request is already sent, how can we modify it or how can we get it back for correction?
What r the steps?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could anyone explain m how to design and customize a change request ? When the request is already sent, how can we modify it or how can we get it back for correction?
What r the steps?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ngassom
Please go through some of the following links
http://help.sap.com/saphelp_47x200/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4b/b155e40c3e11d3959a00a0c930dcc1/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/57/38dea84eb711d182bf0000e829fbfe/frameset.htm
Thanks
G. Lakshmipathi
Hi Ngassom
The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.
Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.
The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.
Thanks
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A change request is a document containing a call for an adjustment of a system; it is of great importance in the change management process.
Reasons for a doing a config change might be that there is config mistake or the client requests for an enhancement ie., what is not already there or an additional functionality which the client needs.
A change request is declarative, i.e. it states what needs to be accomplished, but leaves out how the change should be carried out. Important elements of a change request are an ID, the customer (ID), the deadline (if applicable), an indication whether the change is required or optional, the change type (often chosen from a domain-specific ontology) and a change abstract, which is a piece of narrative (Keller, 2005).
Change requests typically originate from one of five sources: problem reports that identify bugs that must be fixed, which forms the most common source, (ii) system enhancement requests from users, (iii) events in the development of other systems, (iv) changes in underlying structure and or standards (e.g. in software development this could be a new operating system) and (v) demands from senior management (Dennis, Wixom & Tegarden, 2002).
Message was edited by:
sam masker
Message was edited by:
sam masker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.