Confirmation of Support notification and Change request.

Hi Guru's,
In my clinets landscape we are using ChaRM for Change requests and Urgent correction. We have two situation here to handle.
1. I (Change Manager) should only be able to confirm a support notification if all the dependent/subsequent change requests have been confirmed
2. I (Change Manger) should only be able to confirm a change request if all the dependent/subsequent urgent corrections have been confirmed.
Request your help.
Vinod

Hi,
you can customize that your change request will automatically get a new status if the linked urgent correction reached a specific satus.
You can then do the same with support message and change request. This will lead to a chain where your support message is confirmed automatically if your urgent correction is confirmed.
Check SPRO - Make Setting for Change Transaction Types - Assign Actions "SET_PREDOC"
Best Regards
Daniel

Similar Messages

Support message and change requests only for production system

Hi guys,
I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
Kind regards
Rayko

Hi Rayko,
We do not have this option.
Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
Best Regards,
Fernando

Difference between task request and change request

What is the difference between task request and change request during sap implementation. In general how many tasks will generate during a normal company inmplementation by any functional consultant?

Hi,
Change request and task request are same.But generally change request is generated during newly created objects or reports that are transported and task request is used when u regenerate the change request by modifying that object again and transporting it in new change request.
A particular change request may contain multiple number of task request but that number depends upon number of objects u transfer during generation and transportation.
Pls do reward points if ans is useful.
Regards,
Suhas.

Service Desk and Change Request Config document

Hi SolMan Experts,
Could you please help in getting Service Desk and Change Request Management Configuration document please !!!
Thanks in advance.
- Ignacio.

Hi,
Please get the stuff from the following sites.
1. http://help.sap.com/ -> SAP NetWeaver -> SAP Solution Manager
2. http://service.sap.com/solutionmanager
3. use tcode SPRO--> search for service desk and follow the steps.
4. use tcode SPRO--> search for Change Request management and follow the steps
Regards,
Srini Nookala

What is meant by change pointer and change request

hi,
what is meant by change pointer and change request in sap r3
plz can u any one notes or link on this , or if possible briefly tell about this..
i am looking for clear idea on this..
thanks
Ruban

With respect to Dictionary Change pointers means all the changes done to dictionary objects.
All the change logs with respect to tables are stored in CDHDR and CDPOS table
Change Pointers in broad sense are used with respect to IDOC
Change Pointers & Reduction of IDOCs.
Applications, which write change documents, will also try to write change
pointers for ALE operations. These are log entries to remember all modified
data records relevant for ALE.
Following Steps must be followed in case of Change Pointer.
1) Goto Transaction BD60.
Note down the Details of the Message Type for which change pointer has to activate. Details like Function Module, Classification Object, ALE object Type etc.
E.g. ZDEBP3
2) Next step is goto transaction BD53
Click on change button.
First select the segment for which the fields has to modified (either remove or
add ).
It will show the fields in a pop-up window where the user can select, deselect the respective fields.
Save the settings for the Message type. Dont forget to activate the change pointers by clicking Activate Change pointers button on the main screen.
3) Once the activation is done system will reset the settings for the Message type in Change pointers (BD60). Maintained the old settings for the Message type.
Check this FAQ
. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can deactivate change pointers for this messages type.
You can deactivate change pointers for the message type
and reactivate them again.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
3. Are there still too many change pointers to be processed?
The change pointers are analyzed with the transaction BD21 or the report RBDMIDOC in ALE and flagged as processed. If the change pointers are created periodically, this report should also run periodically.
4. Are no longer required change pointers reorganized in time?
The report RBDCPCLR (transaction BD22) to reorganize the change pointer should run periodically. Depending on how many change pointers are created or processed, you can schedule the background job hourly, daily or weekly. You should delete all obsolete and processed change pointers. You can also use this report for specified message types.
We come across change pointer technique while dealing with master data distribution thru ALE/IDOCs
When we want to reflect changes made to master data(i.e customer master, vendor master, material master ...) visible to other clients listed in customer distribution model, we follow change pointer technique.
What is customer distribution model?
A customer model depicts various messages (master data, transactional data) exchanged between the systems and establishes a sender and receiver of data
A customer model is always maintained on any system for the entire distributed network of SAP systems, so it must be distributed to various systems in the distributed network.
These r some details regarding change pointer technique which u may find it usefull.............
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master, vendor master & sales orders. changes made to a document are recorded in the change document header table CHDHR, and additional change pointers are written in the BDCP table for changes relevant to ALE. BDCPS table stores the status of changed documents processed or not.
The process for distributing master data using change pointers involves the following steps.
The application writes change documents. SAP maintains change documents for
several objects in the system, such as materials, customers, invoices, and bank data, to provide an audit trail for changes made to an object. A change document object represents a set of tables for which changes are recorded. For example, the change document for the material master is named MATERIAL and it contains the various tables of the material master object, such as MARA and MARC.
When an application transaction makes changes to an object, the application writes change documents, which are stored in the CDHDR and CDPOS tables for each change made to an object.
Tip
Execute transaction SCDO to see a list of change document objects and
their tables.
The SMD (Shared Master Data) tool writes change pointers. When changes are made to an object, the SMD tool checks the ALE settings and consults the ALE distribution model to determine whether a receiver is interested in the object that was changed. If the system finds an appropriate receiver, the system creates change pointers in the BDCP table that point to change documents in the CDHDR table.
The ALE programs analyze change pointers and generate IDocs. SAP provides
standard function modules that read the change pointer table and generate IDocs for the objects that were changed. These programs are designed to ignore multiple changes and create only one IDoc. For example, if a material is changed four times before the function module is invoked, only one IDoc with the latest data from the material master data is created. The function modules are invoked by a standard report, RBDMIDOC. The selection parameters of this report allow you to specify the message type for which change pointers are to be analyzed. Configuration
you must carry out the following configuration steps to enable master data
distribution based on changes to the object.
Step 1: Enable Change Pointers Globally
Transaction: BD61
This option enables the change pointer process globally. Make sure that the flag is checked.
Step 2 :Enable Change Pointers for a Message Type
Transaction: BD50
This setting is required for activating change pointers for a specific message type.
make sure that the Active flag is checked for your message type.
Step 3 :Specify the Fields for Which Change Pointers Are to Be Written
Transaction: BD52
For standard master data objects such as the material, customer, and vendor objects, SAP already provides a list of fields for which change pointers are written. If you are satisfied with the standard set of fields, you can skip this step. If you want to add new fields, you must add entries for the required fields. If you are not interested in IDocs being generated for changes to a particular field, you can remove it from the list. For example, if you do not want to distribute the
material master for changes made to the Catalog Profile (RBNRM) field, you can delete this entry from the table.
Step 4: Changing a Field in the Master Data
Change a field in the master data object for which the change pointer is enabled. For example, if you change the net weight of a material in the material master data, a change pointer is written.
Tip : You can verify a change document and change pointer by viewing entries in
tables CDHDR and BDCP, respectively.
Step 5 :Executing Program RBDMIDOC to Process Change Pointers
Execute program RBDMIDOC to initiate the process of generating an IDoc. On the selection screen, specify the message type. For example, you can specify MATMAS. After you execute the process, it displays the number of entries processed.
Note :
Normally, you schedule this program to run frequently and start IDoc
generation for different message types.
Step 6 : View the idocs in WE02/05

How to give authorisation to create and change request?

How to give authorisation to create and change request? Which T Code is needed to create request and change request?
Rajkumar.

Hi,
For creating/changing/displaying change requests, you need to give access for SE01, SE09/SE10.
You needn't give access to transaction SE03 to all users, only super users should have that access from security point of view.
Regards,
Sarita

Diffenence between task and change request

What is the difference between task and change request? Is it possible to release a change request without releasing a task?

Tasks are a level under the change request. You can have multiple tasks under each change request. You can release a task without releasing the change request, but not vice versa.
Regards,
Rich Heilman

Difference between Customazation and Change request

Hi All,
Can anyone please describe the difference between Customazation and Change request?
Please provide with 2-3 examples with scenarios.
Edited by: 994943 on 20-Mar-2013 19:14

Hi All,
Can anyone please describe the difference between Customazation and Change request?
Please provide with 2-3 examples with scenarios.
Edited by: 994943 on 20-Mar-2013 19:14

What is the difference between task and change request?

Hi all
What is the difference between task and change request?
thanks all

Dear Ispit,
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/19/3f5bf8a4b011d285090000e8a57770/content.htm">Request Types and Task Types</a>
<a href="http://help.sap.com/saphelp_sm32/helpdata/en/dd/cc86a571464559a2685a404397065b/content.htm">Change Transactions in Change Request Management</a>
For more information about the SAP Change and Transport System (CTS), visit the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
Transport Request is generated in following scenarios:
1. Customizing Request - When doing or changing some customization.
2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.
Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.
Benefit of Transport Request:
SAP Landscape normally has 3- Tier system:
Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)
Quality Server - Mainly useful for testing.
Production Server Actual / Live server, where the real transactions are created & posted.
Procedure to Release & Transport Request:
1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter
2. In the next screen, you will see list of transport request created.
Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.
3. Expand the main request & you will be able to view the sub requests attached to main request.
4. First release the sub requests.
Note: To release the request, select the request ni & click on release request individually (Do not select release all request)
5. Next release main request.
6. Once the request is released sucessfully, imform the basis person to import the request to QA server.
or
If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.
Reward points if this is helpful.
Regards,
Naveen.

What's the difference between transport request and change request

Hi, I am reading TMS part of TADM12-1 now, and confused about two terms mentioned in this book, transport request and change request.
Is there any difference with them? Please advise. Thanks
James

In the context of course tadm12 transport request = change request

SCSM 2012 R2 Portal - Publishing Service Request and Change Request.

Dears,
Sorry for this questions, it is very basic.
I want links on how to create below things:
Create Cataloge about Services we provide such: Create VM, Delete VM, Create User and Mailbox, Add user to group
How to publish this request to Portal
Create Change request approval flow such: approve creating user and mailbox
How to publish above change request
Thanks

In addition to Thomas and regarding your assumption "I am not sure if the books help on this points":
In the
Microsoft System Center 2012 Cookbook in the chapter 5 starting on page 148 the detailed steps "how to create a request offering for a new user request" are described.
Each recipe in this chapter describes how to setup a request offering with all related components to get this done.
The recipes you need in this chapter are:
Creating Service Request templates, page 148
Creating Service Request activities, page 151
Creating Service Offering categories, page 157
Creating Service Catalog Request offerings, page 159
Creating Service Catalog Service offerings, page 167
Publishing Service offerings and Request offerings, page 176
Working with Service Requests in the portal, page 183
Creating Service Request notifications, page 187
There is only one minor mistake in this chapter on page 153:
"Unanimous (only one reviewer
needs to approve)" -> it must be "Unanimous
(all reviewers
must approve)"
I am pretty sure the recipes will work because I wrote the chapter. And sorry for the mistake on page 153! ;-)
Andreas Baumgarten | H&D International Group

E-Mail notification in Change Request by approval

Hello out there,
I'm trying for days to set up an automatic e-mail notfication for my change request transaction by workflow.
My aim is to trigger an email notification by saving after setting the approved activity.
I tried it with following workflow conditions:
E.g. by setting schedule condition on status "validation - E0014" and start condition on status "release for approval - E0012" everything works fine.
So I think the problem is the status "approved - E0004" ... maybe 'cause it isn't set by actions like the other statuses?
Any ideas?
Thanks,
Martin Kläser
P.S.: Solution Manager CHARM is driving me to insanity ...

Problem is solved.
The conditions were alright ... the problem was that change manager and requester (both test users) got the same e-mail address so nothing happened.
After changing requester's mail everything works fine.

Transports and Change Request

Hi Gurus-
Can some one tell me a simple scenario including following terms. I needed this as I am unable to picture everything together when I read documentation about these.
1. Transports
2. Change Request
3. Task
4. Package (Transportable)
5. Creating a Change Request (who will do this normally, as a developer how do I get this)
6. Releasing Change Request
7. Collecting Objects
Plese take a simple scenario like adding KF to a infoCube or changing a report.
Thanks in advace, points will be awarded.
Message was edited by:
PUNZU

Please see my comments below.
1. Transports
Generally used to transport changes from development to QA to Production. Direct changes in Production is not advisable. Hence we make use of this tool.
2. Change Request
A change request/transport request stores all the objects you are changing and assigning them to this request. Any further changes to these objects will automatically be captured in this request.
3. Task
Generally, when a second user changes the same object which is captured in a request, a task is created under that request. However, when you release request, the final change gets transported. You need to release task before releasing a request.
4. Package (Transportable)
You define a group of objects as package just for identification purpose. For example, for workbench objects like cubes, I/O, ODS, you define workbench package. Whenever you are using transport connection from rsa1, and capture the objects in a request, you must assign each and every object to a particular package. There is no hard and fast rule of define packages. It is just for identification purpose.
5. Creating a Change Request (who will do this normally, as a developer how do I get this)
Generally, you as a developer should do this. Whenever you are making some change to an object and activating it, it will ask for a transport request. Otherwise, you can also drag and drop individual objects and select them and transport using transport connection tab in RSA1.
You can see the transport requests that you have created in transaction se09 or se10.
6. Releasing Change Request
Right click the request in se10 and click release.
7. Collecting Objects
You need to collect in target server. Generally, in most of the places, this process is automized with a workflow. you don't need to take care of this.
Hope this helps(something different from the things available in documentation).
Regards,
anup

Parallel Activities and Change Requests

We are beginning to play around with using parallel activities in CRs, but have noticed that when we create CR with parallel activities our workflows fall behind. After around 3 - 5 hours the workflow will process and notifications and status changes will
occur. Could this be because parallel activities appear to be designed with Release Management in mind and so there are not solid relationships between Release Management and CRs without linking a Release to a CR?

You may have an issue with a particular workflow, that could be slowing down the execution of other workflows. I would suggest taking a look at the link I pasted below. It is a great blog post by Travis Wright on how to troubleshoot workflow performance
issues in SCSM.
http://blogs.technet.com/b/servicemanager/archive/2009/12/21/troubleshooting-workflows-in-service-manager.aspx
Matthew Dowst |
Blog | Twitter

Table for Created and Changed Requests...

Dear all,
I need a program to fetch the created date and changed date for given
1. Tcodes
2. tables
3. structures
4. domains
5. bapi
6. badi
7. smartforms
8. scripts
etc.
Can you plz suggest me from which table i could get all these details.
I tried TRDIR and i have got the dates for reports.
Regards
Sivaprasad...
best suggestions will be rewarded with points.
Edited by: Sivaprasad ML on Aug 4, 2008 2:20 PM

Hi,
Check this out
RSRREPDIR                Directory of all reports
TADIR                          Directory of Repository Objects
TCDIR                          Control Directory
TDDIR                          Active field exits for data elements
TFDIR                          Function Module
Thanks,
Muthu

Confirmation of Support notification and Change request.

Similar Messages

Maybe you are looking for