Change documents cannot be generated

When trying to approve an admin charm we are getting warning : change documents cannot be generated
Diagnosis
Change Documents cannot be generated.
System Response
The status is reset, the action is canceled.
Procedure
Your Change Request Document contains data which cannot be used for the generation of the follow-on change documents.
Please check the following possible errors:
The chosen project in project field of the 'Details' assignment block is a project without a maintenance cycle or the assigned maintenance cycle is in a status where the generation of Change Documents are not allowed. The generation of projects is for example not allowed if the project is in a final status.
If possible, change the project or choose a phase in the maintenance cycle which allows the generation of Change Documents. If this is not possible, this project cannot be used.
The 'Scope' assignment block contains scope items for with a chosen IBase which is not the IBase of the productive system in the one (or more) logical components assigned in the chosen project. This is only relevant for the change category 'Urgent Correction', 'Normal Correction' and 'Administrative Change'.
Choose the right IBase for the change category scope item.
If a change is not possible because the Change Request was approved and the fields are not edit able, set the Change Request to 'Validation'. Then the data can be changed and the Change Request can be approved again.
Can someone help why this happens

Hi,
Have you checked all the possible errors stated as in your error?
1. Do you have proper auth to create, proper system assigned with the dev role and ibase created?
2. is it new CR or you are trying to extend the scope? if this case, what is the status of CR? check out
ChaRM: RfC process stuck at "Being Implemented"
3. whether your project has the valid maintenance cycle assigned? you can check in solar_project_admin maintenance cycle is open ?
4. what is the phase status of maintenance cycle and project cycle. check this allows to create CD, with the status as development with release ?
Phases in the Project and Maintenance Cycle - SAP Documentation
please check
Thanks
Jansi

Similar Messages

Change documents for customer Z table - serious help wanted

Hi all,
I am no beginner and I don't expect any comments from beginners.
Situation: My customer wants to replace the material valuation transactions MRN1 MRN2 MRN3 due to bad performance and locking problems with own developed programs.
The valuation results will be stored in a customer Z-Table on a monthly base. For auditing and transparency purposes, this Z-table has to get a change object and the update routines will have to write change documents.
Due to the expected size of the new Z-table, it is not advisable to simply switsch on table logging.
In this huge project (and in none I participated!) nobody ever implemented the change document process for a Z-table. <b>BUT EVERYBODY CAN TELL YOU THI IS NO PROBLEM AT ALL.</b>
I read some documentation at SAP and serached for threads or blogs here. I could not find anything desribing that in depth.
So before I start, I'd be happy to get some hints from people who created own change documents and implemented the process. Links to documentation and other helpful pages are also welcome.
If I can keep the process simple, I'd like to create a BLOG on this - because I think, in the future it will get more and more difficult to pass the auditing process with undocumented features and uncontrolled table changes.
TIA.
Regards,
Clemens

Hi,
Please check this thread.
http://www.sapdevelopment.co.uk/tips/changedoc/cd_createch.htm
Once you create your change document object using generate update pgm option then please check the WRITE document fm.
I have done this long back i am updating CDHDR and CDPOS for 2 table YATT and YATTPLANTS. Here YATT have single record (header table) and YATTPLANTS have multiple records (item table)
function yatt_write_document           .
call function 'CHANGEDOCUMENT_OPEN'
    exporting
      objectclass             = 'YATT           '
      objectid                = objectid
      planned_change_number   = planned_change_number
      planned_or_real_changes = planned_or_real_changes
    exceptions
      sequence_invalid        = 1
      others                  = 2.
case sy-subrc.
    when 0.                                   "ok.
    when 1. message a600 with 'SEQUENCE INVALID'.
    when 2. message a600 with 'OPEN ERROR'.
endcase.
if upd_yctc                           ne space.
   call function 'CHANGEDOCUMENT_SINGLE_CASE'
     exporting
       tablename              = 'YATT                          '
       workarea_old           = o_yatt
       workarea_new           = n_yatt
        change_indicator       = upd_yattc
        docu_delete            = 'X'
     exceptions
       nametab_error          = 1
       open_missing           = 2
       position_insert_failed = 3
       others                 = 4.
    case sy-subrc.
      when 0.                                "ok.
      when 1. message a600 with 'NAMETAB-ERROR'.
      when 2. message a600 with 'OPEN MISSING'.
      when 3. message a600 with 'INSERT ERROR'.
      when 4. message a600 with 'SINGLE ERROR'.
    endcase.
endif.
if upd_yctcauthplnts                  ne space.
    call function 'CHANGEDOCUMENT_MULTIPLE_CASE'
      exporting
        tablename              = 'YATTPLANTS                 '
        change_indicator       = upd_yattplants
        docu_delete            = 'X'
      tables
        table_old              = yyattplants
        table_new              = xyattplants
     exceptions
       nametab_error          = 1
       open_missing           = 2
       position_insert_failed = 3
       others                 = 4.
    case sy-subrc.
      when 0.                                "ok.
      when 1. message a600 with 'NAMETAB-ERROR'.
      when 2. message a600 with 'OPEN MISSING'.
      when 3. message a600 with 'INSERT ERROR'.
      when 4. message a600 with 'MULTIPLE ERROR'.
    endcase.
endif.
call function 'CHANGEDOCUMENT_CLOSE'
    exporting
      objectclass             = 'YATT           '
      objectid                = objectid
      date_of_change          = udate
      time_of_change          = utime
      tcode                   = tcode
      username                = username
      object_change_indicator = object_change_indicator
      no_change_pointers      = no_change_pointers
    exceptions
      header_insert_failed    = 1
      object_invalid          = 2
      open_missing            = 3
      no_position_inserted    = 4
      others                  = 5.
case sy-subrc.
    when 0.                                   "ok.
    when 1. message a600 with 'INSERT HEADER FAILED'.
    when 2. message a600 with 'OBJECT INVALID'.
    when 3. message a600 with 'OPEN MISSING'.
*    WHEN 4. MESSAGE A600 WITH 'NO_POSITION_INSERTED'.
* do not abort, if positions are not inserted!!!
    when 5. message a600 with 'CLOSE ERROR'.
endcase.
endfunction.
a®

Change document

I learn the procedure for change document from sap hlep:
1.Define change document object
2.Set change document flag
3.Generate update and INCLUDE objects
4.Integrating the functionality into the program
5.Writing the fields in the program
I'm confuse about step 4 & 5. Can any guys tell me how to achieve them?
Thanks a lot
--Alex Miao

Hi Alex,
The entries into the table CDHDR and CDPOS are not made just because of making the change document active in the data element of the corresponding field.
We need to first create a change document object using the transaction SCDO for the corresponding fields and tables. Now upon generation, you would get a couple of includes and a function module.
Now, in your program, if you want to have entries in CDHDR and CDPOS for the database changes you make, you need to include the programs generated in SCDO and call the function module after every INSERT,MODIFY or DELETE. Without which the entries will not be made in CDHDR and CDPOS.
Souce: http://www.****************

Regd. change documents

Hi,
I have to link a business object event to a change document object. I have also to create this change document object. It's a custom object. I have created the change document object and generated the update program. What else do I need to do for this.... Do I have to do some coding for this.
Regards,
Vijay

Hi Vijay!
Yes, there is some coding to be done.
Change documents are only created, when called in transactions explicitly. Take the includes, which where created with the change document object, and add the to all programs, which update your tables. Use the pre-defined form routines.
Have a look at implementation of any standard object, when you like to have some example coding.
Regards,
Christian

Problem while generating Update progam for a Change Document Object

Hi,
I'm trying to deal with Change Document concept in a R/3 4.6C environment and to establish new Change Document object for my (Z)-table. I haven't using any namespace and created object with name ZTEST. Following the online documentation I came to the point, where I have to generate include program. I made all the nessesary inputs (using Z prefix) but faced
"Function module name is reserved for SAP"
Creating everything similarily using some of our registered namespaces (/somenamespace/) I succeed to generate the Update program and to integrate it in my Z-programs as well.
My question is: is it possible to use Change Document Object-names without predefined namespace - being a regular customer developer, but not an SAP developer - means, if I am allowed to manage programs in the customer namespace (Z,Y, X) only. If yes, how to do this?
Further (I decided not to open a new thread) - generated Update program uses
CALL FUNCTION 'xxxxx' IN UPDATE TASK
for creation of Change Numbers for generated Change Document Object. This CALL doesn't work when I implemented it in my Z-program, but when changed (IN UPDATE TASK was commented) - everything goes well and the system creates records in CDHDR/CDPOS tables for my object class and table.
Why is that? According to the documentation I shoud only fill appropriate variables for the Change Document Object (class, tr.code, etc.) and call generated FM, nothing is pointed out about any possible problems? Am I doing something wrong?
Well, to be precise, I think I have to give a sample:
1. I have a sample Z-table with few fields (their data elements are marked as Change-Document relevant).
2. Using own z-progam I created a new record for this z-table. Also fill all the nessesary variables included in the interface of generated FM for Change Document Object (for example - FM-mane CD_CALL_my_object).
3. I call the CDO FM.
4. Check what is happening (directly in both tables CDHDR/CDPOS or using FM CHANGEDOCUMENT_READ).
Further, I perfom the steps from 1 to 4 updating the created in previous loop record in my Z-table.
In both cases if the FM 'CD_CALL_my_object' is called IN UPDATE TASK nothing happens, but in case of direct call (without addition IN UPDATE TASK) the system behaves as expected. Well, obliously I can change the generated code for our production needs, but it doesn't seems to be the correct decision - in case of next possible modification of the Change Document Object definition, respectively in need of re-generation of the code.
Any hints are wellcome.
Thanks in advance.
Ivaylo Mutafchiev
Edited by: Ivaylo Mutafchiev on Jan 24, 2008 10:24 AM

"IN UPDATE TASK" resolved by myself. The one should explicitly call 'COMMIT WORK' from Z-program after CALL FUNCTION '...' IN UPDATE TASK in order to get changes in the CDHDR/CDPOS commited. The key in this issue for me was to check the documentation of CALL FUNCTION :-).
Regards,
Ivo

Shortcut to generate change documents for multiple user id access in ecc 6

hi.
i need to generate a report with changes to user ids within the last month. i dont have access to sap notes. thanks

apart from SUIM, you can also refer to below reports
RSUSR100                                   Change Documents for Users
RSUSR100N                                  Change Documents for Users
RSUSR101                                   Change Documents for Profiles
RSUSR102                                   Change Documents for Authorizations
regards,
Surpreet

SOLAR02 The document cannot be changed

Hello,
I have developed a program that uploads files massively to Solution Manager, and the upload process works fine.
But when i try to edit a document that i uploaded using this program, the systems shows me this popup message.
The document cannot be changed.
Because:
it was copied from a template.
it was copied from the Business Process
Repository.
it is saved in a different context.
The document is flagged for copying, e.g.
because you are in a copied project.
<ZH>It has been copied.</>
The reference to the original document is
replaced by a reference to the copy.
Has anybody seen this before or why is this message being showed.
Kind regards
Jon
Edited by: Jon Azkorra on Dec 17, 2011 2:09 PM
Edited by: Jon Azkorra on Dec 17, 2011 2:15 PM
Edited by: Jon Azkorra on Dec 17, 2011 4:30 PM

Hi Rajat,
Sorry for the delay, I was out of office.
If you really wish to switch off this protection you can use report SM_FOLDER_NO_REFCOPY. Please see note 1236369 for details
In your case you would need to add the 'Technical Folder Name' SOLAR00 using the report Start report SM_FOLDER_NO_REFCOPY At 'Technical Folder Name' enter SOLAR00 and press the add button this inserts a new entry in table IWBSETTING. You should find in this table afterwards and entry with NAME = SM_FOLDER_NO_REFCOPY and VALUE = SOLAR00
Afterwards when you try to change the documents (or their attributes) from within the implementaion project the document should not be copied anymore
But please ba aware of the fact when using this that as of then the original document in the template can be changed from within every project type.
bets regards,
Fabrcius

Change B2B error message: "Error in R/3 system: document cannot be sent"

Hi experts!!
I had the requirement the B2B user not to be able to change orders from the past days.
I wrote some ABAP code in MV45AFZZ user exit and the functionality works fine! I even receive my custom error message in the B2B but before my message i also get "Error in R/3 system: document cannot be sent. Call our hotline.."
Is there anyway i can change this standard message in JAVA side???
Thank you in advance!!

In the ABAP side, set break point in BAPI_SALESORDER_SIMULATE and check the BAPIRETURN table.. Depending upon the stage and action on the order, the other RFCs you might focus on are SD_SALESDOCUMENT_CREATE or SD_SALESDOCUMENT_CHANGE. The return structure is BAPIRET2 for this set of RFC.
You might remove the "unwanted messages here.. or let them flow into the Java layer and tackle them there. That will require you to extend different xxxxStrategyR3 classes and overwrite certain methods in certain classes. The development is NOT streamlined here.
Read the classes CreateStrategyR3 - there is a method performCustExitAfterR3SimulateCall
in ReadStrategyR3 - there is a method called replaceR3MessageTexts and in change..
in ChangeStrategyR3 - there is a method called performCustExitAfterR3Call
In all these places you have to read the appropriate table that contains the message and remove it. See ReadStrategyR3~replaceR3MessageTexts for some idea..

How can I stop Firefox 4 from displaying "The document cannot change while Printing or in Print Preview" from appearing every time I click on File/Page Preview?

Clicking on File/Page Preview in Firefox 4 brings up a warning dialog "The document cannot change while Printing or in Print Preview" every time. How can I stop this from happening? It is very annoying, and it is necessary to click "OK" on this dialog twice before it will go away. Thank you.

Does it behave that way in [[Safe Mode]] ?
If it doesn't, then one of your add-ons in the culprit.

Generate change documents for characteristic value changes in material master

Hello,
I am currently using material class (class type: 001) and assign some characteristics to material master. I am going to create a query/custom report to track all changes in the characteristic values in that material master. However, I could not find any change document in CDHDR table.
I have activated "Change Docs" parameter in class type 001 customizing as described in SAP note: 65124 Classification Change Documents as follow:
Is it possible to generate change documents for characteristic values in material master?
Regards,
Julian

Hi Rajen,
Thanks for your reply. It seems that I missed one more step in the customizing. Once the multiple object is activated, I need to activate the change document parameter for each assigned object.
Thread closed.
Regards,
Julian

Cannot cancel Urgent Change document in Solman 7.1

Hi all,
After we upgraded to Solman 7.1, we found that the Urgent Change documents in CHARM are not allowed to be withdrawn/cancelled when tranports have already been imported to QA system.
In previous Solman 7.0, we were able to cancel/withdraw Urgent Correction documents using report CRM_SOCM_SERVICE_REPORT even when transports has already been moved to QA.
Any idea how we can cancel Urgent Change documents in Solman 7.1?
Thanks,
Tess

The question is how to do it? the end-user when open a CR will not do it and the receiver (service desk) can not waste his tiem doing it
Its a consulting issue.....not technical...who shd do is more like a process....so you know better in your current case.
Yes, but ths stnadard tool allow to do it or a Z programm is needed? Which type of inconsistences could appear?*
there is a standard report
CRM_SOCM_SERVICE_REPORT
but remember handle with care.
hope it resolves
regards
prakhar

SOLAR_MIGRATION of multiple projects & Change documents

Hi,
We are in the process off migrating solution manager projects to a new server using solar_migration. The idea is to migrate project by project since the projects are rather large.
Now I get the idea that the generated transport contains all the change documents, also those of of other projects not yet migrated, even though I have only selected one project for the migration. The reason I get this idea is that the size of the transport files of empty migration test projects runs into several GB, so they must contains documents that do not belong to it.
This could be a problem if for instance in 2 weeks time we migrate the second project which also contains all the change documents. This second migration could then overwrite the possibly updated documents in the project we migrated first.
Is the assumption correct that you cannot limit the migration of a project to only contain the change documents of that specific project?
If it is could we for the second project select the change documents based on a date range? And will the documents of the second project that have a change stamp before this date range authomatically become visible once the second project is migrated?
Thanks for any clarification
Tom

Hi Tom,
there is no risk to overwrite any documents, documents are identified by a unique ID, and each change generates a new version.
If there are objects (=documents) in the transpotr request, that should not be in there (you should verify from the transport objects), you should open a call to SAP asking for clarification there.
Kind regards,
Carl

Article Change Documents for Custom Fields

Hi,
We have lot of custom fields defined in the article master. When the custom fields are changed through the online transaction, the changes are recorded in the change document tables (CDHDR / CDPOS). If the changes are made through the "BAPI_MATERIAL_MAINTAINDATA_RT" the changes are not getting recorded in the change document tables and hence they cannot be viewed under "Environment -> Display Changes". Lately, this is causing big issues as users are using the custom attributes more seriously now..and we're having issues tracing back the changes...Users do not use online transactions to make the changes..The changes are submitted through the portal which are then submitted through the ARTMAS IDOC which in turn calls the BAPI....
We want to activate the change document functionality through IDOCs/BAPI....Is it configurable or has to be coded somewhere in the BAPI where it generates the custom segments for the custom fields....
Any help would be greatly appreciated
Thanks,
Sri

Hi,
You can use txn BD51 in which you can specify "BAPI_MATERIAL_MAINTAINDATA_RT" and use "o" as Input without checking the Dialog allowed option.
I assume that you have already done the relevant settings for the change pointers for message type ARTMAS( BD50) and activate change poiinter for relevant document changes (in Txn BD52 by maintaining the relevant Object - MAT_FULL,Table name - MARA and ZZ fields)
Hope this helps,
Best Regards,
Aram.

CUA: User & Role Master Data Change Document

Hi Team,
I would like to know is there any way to find out CUA user master & role assignment change document data from CUA Central System & All Targets Systems.
I am looking for user friendly tool similar to SUIM.
I have looked into other methods of CUA change document tips and tools but it is not so fruitful to convenes my Audit team.
FYI. System Users (CUA_ADMIN) is not the user which i want to see in my change document window, i want to know actual security consultant ids within that.
Kindly get back to me.
Appreciate, for your response.
Regards,
Asif

HI Matt: Your understanding is correct for CUA Tier2 Setup.
FYI.
We have successfully configured trusted relationships between SAP Systems with the help of my BASIS & UNIX team.
To do this: We have performed following actions:
u2022     Trusted System trust relationships for the RFC Connection has been maintained from the Central to the Child System and from All Child to Central System via transaction code SMT1.
u2022     UNIX Database level trusted relationship entries has also been added with the help of UNIX Team
u2022     RFC Destinations has been reconfigured with Current user option (SM59).
u2022     For Security Administrator special authorizations has been provided in order to get trusted relationship RFC authorizations.
Note:
I have added Full Authorizations under these new special objects S_RFC, S_ICF, S_RFCACL, & S_RFCADM and same was assigned to all our Security Administrators. Remote Logon & Trusted Connectivity is working fine for all of us.
We are 4 Security Administrator here, And for All of us this new concept of Trusted RFC for CUA is working fine.
New Authorizations updated on both CUA and the Child System.
Our ids are replicating as a log in the last change by field of SU01 and change document of SUIM. Happy to see this. 
But unfortunately there are strange ABAP dumps are started generating from CUA (SolMan) System soon after this Implementation.
When we look into ST22, runtime errors CALL_FUNCTION_SINGLE_LOGIN_REJ & CALL_FUNCTION_SYSCALL_ONLY are keep generating.
Following are the example of dump logs and all the dump are with similar fashion but with different user-ids within that.:
Short text: No authorization to logon as trusted system (Trusted RC=0).
What happened? : Error in the ABAP Application Program The current ABAP program "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error analysis: An RFC call (Remote Function Call) was sent with the invalid user ID "(End user user-ids)". Or the calling system is not registered as trusted system in the target system.
How to correct the error: The error code of the trusted system was 0.
Meaning: 0    Correct logon as trusted system mode
1 No trusted system entry for the calling system "BIP " (like other child System) or the security key entry for the system "BIP " is invalid
2 User "111552 " (Type of End user) does not have RFC authorization (authorization object
     (S_RFCACL) for user "End User id " witl client 100.
3    The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 6. (6    No external user check)
My Point: I think All these End users are trying to connect CUA Trusted RFC connections through individual different child Systems..
Why they need to Connect to CUA and for what reason they need special Trusted RFCu2019s authorization???
Pls help me to fix this problem.
I have gone through the old SDN posts related to the same topic and few SAP notes and help link but it wont help.
Note 1579570 - Problem with trust relationship after using HMAC
Note 128447 - Trusted/trusting systems
Note 131387 - No authorization to log on as a trusted system
Note 986707 - No authorization to log on as a trusted system (RC=1)
Few More SAP Notes: 986707, 333441, 1151790 & 128447
http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/frameset.htm
We donu2019t see any logs under SCUL, BD87 & ST01.
Please anyone can assist me on this.
Regards,
Asif

Issue in generation of Change Document - ChaRM

Dear All,
We are implementing ChaRM, I have copied the standard transaction type to z.
I am able to create request for change with transaction type zmcr but when the normal change or urgent change document are created they have standard transaction type.
I have made the changes in SPRO (Defining copy control of transaction type) but still document are getting generated with standard transaction type.
Please attached document of copying control.
Thanks in advance
Regards
Sushant

I have removed zmcr - smmj but now the change document is not getting generated. Please see the screen shot attached.
Regards
Sushant

Change documents cannot be generated

Similar Messages

Maybe you are looking for