Released Change Requests have changed status to modifiable

Hi all,
something very rare happend some days ago in my development R/3 client. Every released change request appear as modifiable, i mean, all the change requests that have been released before a specific day (eg. 14 Setiembre) now appear as modifiable.
The tasks that these change requests contain maintain the correct status (released) but the father change request appear as modifiable.
SAP says something about avoiding import requests(scc1) when other requests are been released. I didn't got it.
Now we need a secure way to correct the status of these requests. Can you help me please.
REgards,
Christian

From my scant knowledge I would recommend reading about SE03 to verify system settings (not modifiable, etc.) and be looking at SCC4 for checking the changeable status for applicable client. You should be checking STMS and its documentation very carefully.<a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm">Transport Management System</a>
I am sure other Gurus can help, but I remember reading documentation for these transactions as well as SE95 (Modification Assistant).
Please post these kind of questions in the appropriate forum, by the way.
Thanks,
Marilyn

Similar Messages

Change Requests have changed status

Hi all,
something very rare happend some days ago in my development R/3 client. Every released change request appear as modifiable, i mean, all the change requests that have been released before a specific day (eg. 14 Setiembre) now appear as modifiable.
The tasks that these change requests contain maintain the correct status (released) but the father change request appear as modifiable.
SAP says something about avoiding import requests(scc1) when other requests are been released. I didn't got it.
Now we need a secure way to correct the status of these requests. Can you help me please.
REgards,
Christian

From my scant knowledge I would recommend reading about SE03 to verify system settings (not modifiable, etc.) and be looking at SCC4 for checking the changeable status for applicable client. You should be checking STMS and its documentation very carefully.<a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm">Transport Management System</a>
I am sure other Gurus can help, but I remember reading documentation for these transactions as well as SE95 (Modification Assistant).
Please post these kind of questions in the appropriate forum, by the way.
Thanks,
Marilyn

Configuring BW to Report Change Requests and Change Documents

We upgraded to Solution Manager 4.0 on DB2 and need to extract the Change Request and Change Document tables to BW for reporting. We know that there is an internal Transaction Monitor, but we need to also report using BEx Analyzer for users who will not log into Solution Manager.
We found one table CRMD_ORDERADM_H for some Change Request fields, but cannot find the tables for the rest. Does someone know the tables where these fields reside? Thank you.
CHANGE REQUEST
Screen Name Table
Priority
Category
Description CRMD_ORDERADM_H
Sold-to Party
Requester COMT_PARTNER_TO_DISPLAY
Change Manager
Change Advisory Board
Ibase
Product
Subject
External Reference CRMD_SALES
Date
Change Request ID CRMD_ORDERADM_H
Decision Date
Implementation Date
Time of Entry
Change Request Log
Description of Change
Change Request Status
CHANGE DOCUMENT
Screen Name Table
Change Document ID
Status
Description
IT Operator
Implementation Date
Time of Entry
Overview

We upgraded to Solution Manager 4.0 on DB2 and need to extract the Change Request and Change Document tables to BW for reporting. We know that there is an internal Transaction Monitor, but we need to also report using BEx Analyzer for users who will not log into Solution Manager.
We found one table CRMD_ORDERADM_H for some Change Request fields, but cannot find the tables for the rest. Does someone know the tables where these fields reside? Thank you.
CHANGE REQUEST
Screen Name Table
Priority
Category
Description CRMD_ORDERADM_H
Sold-to Party
Requester COMT_PARTNER_TO_DISPLAY
Change Manager
Change Advisory Board
Ibase
Product
Subject
External Reference CRMD_SALES
Date
Change Request ID CRMD_ORDERADM_H
Decision Date
Implementation Date
Time of Entry
Change Request Log
Description of Change
Change Request Status
CHANGE DOCUMENT
Screen Name Table
Change Document ID
Status
Description
IT Operator
Implementation Date
Time of Entry
Overview

Change Request Vs Change Order

Hi,
What is the difference between change request and change orders. When to use Change request and when to use Change order. Both allow impacts on work & financial plans
Thanks
Govind

Change requests are initiated to estimate possible changes to a project. Once approved, a change request can be converted into a change order.
Both can have independent approval work flow.
Also, you can combine multiple change requests into one change order.
For more details, see http://download.oracle.com/docs/cd/E18727_01/doc.121/e13623/T185673T185681.htm
Hope this helps,
Sandeep Gandhi

Report for Support Message, Change Request and Change in one overview?

Is there a report that shows the relation between the support message, change request and the change in one overview? I am already aware of the Change Management Reporting via SOLAR_EVAL, but this does not show the whole document flow in one overview.
The incident message processors want to have a quick overview of the status of the changes that are created on the basis of the support message.
If there is no report, could you point me in the right direction... Do I have to create a query or are you using BW for service desk/charm reporting?

Hi
chk te sap note
[Note 1466131 - ChaRM Reporting: Performance of data update|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1466131]
jansi

Error releasing transport request for change document object

Hi Gurus,
I created a new change document object for a Z-table. When i try to release the transport request in the development system it terminated with a message "Export application-defined objects 17.12.2009 11:07:45 Not yet executed". The transport request continued to be in the "Release started" status and i am not able to release it.
I checked in the co file & data file directory for this request, The co file is available but the data file is not created.
Could you please let me know how to solve this?
Regards,
Immanuel.

It was a problem with some basis settings. Was rectified by the basis team.

ChaRM Change Request and Change Documents if withdraw

Hi groupies,
my problem is this:
we did copy the standard transaction sdcr etc. to zdcr etc.
If I release a zdcr a new transaction zdmi (normal correction) will be created. I switch into the new transaction type zdmi and withdraw the transaction zdmi. Now I go back into the transaction zdcr. In the Standard SDCR you must release the SDCR again. But in my case the status is still "released". What is the problem? Know anyone the problem?
nico

Hi.
Search for customizing section "Make settings for Change Transaction Types"
Select ZDMI and assign the following:
Assign Action: SET_PREDOC for user status "withdrawn" (check table TJ30 or the corresponding status profile via customizing). It's something like "E0xx"
Specify Status Attributes: Fill in the appropriate information, especially user status ("E0xx" - same as above), transaction type (ZDCR), Statusprofile (status profile used for ZDCR, i.e. ZDCRHEAD) and user status which ZDCR should be reset to (i.e. "E0001 to be approved" or "E0003 rejected")
If you just want to be able to create another ZDMI you could also add an action condition to your ZDCR.
(Tx: SPPFCADM -> CRMD_ORDER -> Condition Configuration)
Hope this helps.
/cheers

ChARM - Change Request status issue

We are currently testing our ChaRM processes. The biggest issue we have with the ChARM system is that transports associated with a Change Request are being imported into subsequent systems regardless of the status of the change request.
For instance...
If I have 5 transports (each having their own change request) in which all 5 have been released from development and have been imported into the quality system. It seems that from this point on, if 3 of the 5 change requests have their status changed to "testing completed", the production import should only import 3 of the 5 tranports. We assumed that if the other two did not have a status of testing completed, they would not be allowed to be imported into production. This causes an issue because all 5 tranports will move to quality and subsequently move to production regardless of the status of the change request. All 5 of these tranports are also on the same maintenance cycle.
Is this the way the system is supposed to work? If so, how do we utilize ChARM in a continuous maintenance production environment?
Your response is appreciated, Thank You for your help.

Thanks for the update.
So, I guess my next question would be if Change requests and their associated tranports can be moved from one maintenance cycle to another after they have been submitted and released from Dev. My concern is that in our normal production release environment has tranports that pass testing requirements at different times.
For example, Lets say that we release transports into our production system, or "set to go live" for a scheduled import on Tuesday and Thursdays at 5PM.
On Monday, I have 5 transports from 5 different Change Requests that I develop and release the DEV environment. On Tuesday, 3 of the 5 transports have been successfully tested and are cleared to go to Production, however 2 of the Change Requests did not have testing completed.
Is it possible to move the 2 transports to a subsequent maintenance cycle so that the first 3 that successfully passed testing can proceed to go live and import on Tuesday at 5PM?
My concern is that we do not always know upon development release when the Change Request and associated transport will be permitted to go to production.
Thanks much for your help.

OSS note - change request - correction instruction

Hi Gurus,
when you apply an OSS note SAP creates automatically a change request containing the objects you modify.
Among these objects I can also see a list of "Correction Instructions", what is the meaning of this list?
What information it contains?
Suppose I have implemented 2 OSS notes obtaining a similar CR:
CR_number_XXX
--- Report source code:
code1
code2
Correction instructions:
1
2
3
4
Now I want to transport only modifications about, for example, code1. Is it enough to delete code2 from the CR?
Or should I delete also the unuseful instructions?
Thanks
TD

Hello,
Correction instructions sometimes differ for different SAP Release. Hence you can see several corrections in a note.You should select the appropriate instruction for (check your SAP release) and carry out the changes required.
You must transport all the objects under a particular instruction.
Regards,
Ajith

Change Request & Task Issue

Hi Experts,
 Please help me out for following concern.
 Changes done(In Z program) for some testing purpose, are saved in test CR.
 Now i want to save changes doin again in New CR, for further transport.But whenever i am goin to change it ,its taking either the same test CR or creating new Task in same CR. But not askin for new CR.
Some1 concerned that i have to release that CR ,then only i can do that,but i cant do it ,as it is test CR.
Please suggest solution.
Thanks in advance.
Thanks and Regards
Deepak

A Change request that is not released consists of an abject list that has details of the objects (programs, etc) that are to be transported in the request. While it is not released, it does not contain any of the details of the objects, just their object keys. These details are in individual tasks by user id.
When you release the change request, the system takes a copy of the current version of all the objects and writes it to two files in the transport directory of the SAP server - one control file and one data file. These files are named based on the request number.
If you make further changes to a program before releasing the request, those changes will be included in that request when it is released.
If you have made changes to a program that have been put into a change request that is not to be transported you need to manually move the relevant object list entries to the new transport request. You cannot simply delete them from the first request and then save changes to the program again as the object list entries may not be the same. Releasing the change request is not a solution as this may have the same result - the entries added to the new request may be incomplete.
For example, if you create a program it is added to a request as R3TR PROG containing program, texts, gui etc, but if you later change it and save it is added to request as LIMU REPS for program or LIMU REPT for texts or LIMU CUAD for gui.
To move manually, copy/paste values from SU10 object list of the task to a new request/task. Once 100% sure it is OK in new request, delete line from old task then lock object in new request (select line and use padlock icon). For customising there may be object keys associated with the line that you also need to copy. Take care to ensure all relevant objects are in the new transport.
Andrew

Change Request Management without Transport Management

Hello Change Request Management Experts!
I have understood that It is possible to take change request managment in use without transport management. So I could handle Change Request with different statuses without automatic funtions behind these statuies. We like to see how to handle changes between different roles of people and implement the functions after that.
I suppose that I should take only Change Request (approvals) and not Change Documents (execution) from Change Request Management.
Have any of you tried to do that?
Best Regards, Leena Nissilä

Hi Andy,
Thank you for your answer. I have tried to do that also but I where is still some configuration missing because I get error message in: No maintenance cycle is open for the current system. I have also tried to to that maintenance cycle but I thought that it needs CTS activation in some project.
I also like to know what is minimun configuration for change management that I could use SDAD with Service Desk.
I looking forward to you reply,
Br Leena
Edited by: Leena Nissilä on Sep 17, 2008 1:24 PM

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

Requires Reapproval - Od Change Request

We have several POs that are in the status of "Requires Reapproval" but we cannot approve because there are pending change requests from 2-3 years ago. The workflows for the change requests have been purged and the system will not allow us to just change the quantity back to the original amount.
have you run into this? at this point, we don't want to approve the PO since it is so old. We would prefer to just cancel it.
Thanks in advance -
Rob

We have run into this earlier and found that datafix is the only solution for these POs.
Thanks,
PS.

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

InfoCube Error Message: Choose a change request with target system BWQ

Hi experts,
I have a problem when I want to edit an InfoCube created by other developer. The error message received is as follow:
"Choose a change request with target system BWQ".
When I click on the Documentation (F9) button, the detailed message is:
"Message no. TK511
Diagnosis
The selected change request BWDK901086 has target system .
However, the objects you edit can only be recorded in change requests with the target system BWQ.
The correct target system is determined from the package and transport layer to which the object concerned belongs.
System response
The selected change request BWDK901086 is not used to record the objects.
Procedure
Either choose a different change request or change the target system of the change request BWDK901086.
From the prompt window for change requests, you can display all requests you can use by choosing Own requests.
Alternatively, you can create a new request by choosing Create request.
For more information, see the SAP Library under BC - Basis Components -> Change and Transport System ."
Can someone helps me to solve this problem?
Thanks!

hi Fullham,
try se09/10 and find request BWDK901086 (use binocular icon) or se03. then double click that request, go to tab 'properties', hope you will see 'Target System' system there, click 'edit'/pencil icon and change it to BWQ.
you may need to change the owner (which may not authorized), ask basis help if necessary.
hope this helps

Released Change Requests have changed status to modifiable

Similar Messages

Maybe you are looking for