Change Management Issue

Dears,
I am configuring CHARM in solman 7.0,I have performed configuration activities but after creating change management ticket by DSWP->Change management->Change request management I go to ticket and make it in change mode I get in option tab:
There are no actions in the worklist.
Please suggest what could be the possible reason of this error.
Shivam Mittal

Are there any error in the ticket......check the button ....
You have authorization.
Is Ibase properly filled and the solman project activated the CHARMS properly..
.the maintenace cycle is active.
Regards
Prakhar

Similar Messages

Drop Ship SO, Change Management Issue in 11.5.9

Hi,
Currently Client is using Oracle Apps Release 11.5.9
Requirement :
While updating Drop Ship Sales Order, corresponding requisition and Drop Ship Purchase order needs to be updated automatically
Problem:
This functionality is available in 11.5.10 which automatically updates requisition and PO but not in 11.5.9
I couldn't find the package API which they had used in 11.5.10 for implementing this solution.
Hence Please help me in providing the package(API) which is used in 11.5.10 for auto update of requisition and drop ship PO when drop ship SO is changed. So that i can try to implement the same logic in 11.5.9 for client.
Thanks,
Selvan

marist89 wrote:
In anticipation of an impending maelstrom of regulatory changes, I want to upgrade my 11.5.9 EBS environment to 11.5.10 and at least have a hope of being supported. Upgrading to R12 is just not an option at this point, my users are overwhelmed by it. I know that's the best way to go, but it's not going to happen.
I have an 11.5.9 environment on Solaris running on two tiers. The middle-tier serves Web & Forms. The DB Tier serves DB (10.2), CCM, and Reports.
At the same time I upgrade, I want to move my EBS to Linux. I also want to change my configuration so that I am running Web/Forms/CCM/Reports all on the same tier and isolate the DB to it's own node.
My general thought process was:
1. Move the db from Solaris (10.2) to Linux (11.2) using a combination of (362205.1) and (557738.1).
2. Install 11.5.10 on a new node (Linux) and just run the appropriate driver for the 11.5.10 patch against the db on Linux.
Does this seem like a reasonable approach?No, as it is not supported -- You may log a SR to confirm with Oracle Support.
You need to upgrade 11.5.9 to 11.5.10 (or 11.5.10.2) then migrate the database using export/import and the application tier node. Or, migrate the database then upgrade to 11.5.10/11.5.10.2 then migrate the application tier node.
Oracle Applications Release 11.5.10.2 Maintenance Pack Installation Instructions [ID 316365.1]
Upgrade Path Recommendations for E-Business Suite 11i [ID 364623.1]
Release 11.5.10 Maintenance Pack Installation Instructions [ID 259484.1]
Migrating to Linux with Oracle Applications Release 11i [ID 238276.1]
Debugging Platform Migration Issues in Oracle Applications 11i [ID 567703.1]
Oracle Applications Release Notes, Release 11i (11.5.10.2) [ID 316803.1]
Recommendations To Install Oracle Applications 11i [ID 294932.1]
Thanks,
Hussein

What is the relationship between Change management and Issue tracking?

What is in general change management and what is issue tracking in a SAP point of view?

Hi
See this thread
Re: SAP APO
Additional inputs :
APO refers Advanced planned and optimizer
APO is similar to BW in the sense it is also a OLAP processor intended for reporting needs
Supply chain management
http://help.sap.com/saphelp_nw2004s/helpdata/en/25/79eb3cad744026e10000000a11405a/frameset.htm

The Ultimate Guide to Resolving Profile and Device Manager Issues

The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
Hello,
I have been plagued with Profile Manager and Device Manager issues since day one.
I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
(Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile and Device Manager may need a Code Signing Certificate.
The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
I shall outline a sensible strategy:
1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
2. Start the server fom the clone and shut down ALL services.
3. It may be sensible to set up a root user access.
4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
Erase database:
sudo /usr/share/devicemgr/backend/wipeDB.sh
7. Note your Directory (diradmin) password for later if you want to re-use it.
8. Open Open Server Admin and demote OD Master to Standalone Directory.
9. In Terminal delete the old Certificate Authority
sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
This step is crucial because else re-building you OD Master will fail.
9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
11. Go back to Workgroup Manager and re-import users and groups.
NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
If the home directory has not been defined you cannot login from a network account.
13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
sudo serveradmin stop devicemgr
sudo serveradmin start postgres
sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
sudo serveradmin start devicemgr
14. You can now switch back on your services, including Profile Manager.
In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
16. Check that Apple Push Notifications are set.(you easily check if they are working later)
17. You may want to re-boot OS Server from the clone now.
18. After re-boot open Server App and check that your server is running well.
19. Delete all profiles in System Preferences -> Profiles.
19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name should read "Trust Profile for...) and underneath in green font "Verified".
21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
Now enjoy Profile and Device Manager !
Regards,
Twistan

HI
1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
also make sure that u have the message processing role
Hope it clarifies ur doubt and resolve ur prob
Regards
Prakhar

Power Mac G5 DP1.8GHz - Bad Logic Board or Power Management Issue?

I have a Power Mac G5 DP1.8GHz/1.5GB/80GB which I bought non-working. It has not yet been disassembled or examined by a certified tech. This is it's issue (which replicates): the computer powers on. It makes a single warning tone, then the LED flashed at least 15 times (too fast to count). Then the posting chord is heard. Hard drive spins up. Then nothing (no video). Won’t boot from any disk. I have changed the RAM and tested the RAM banks with known-to-be-good RAM from another DP1.8GHz G5. The warning tone stopped once or twice after this switch, but then it didn’t chime. I changed the PRAM battery, but not with as new one. However, after installing the used one and then resetting the PMU, it displayed video briefly for the first time. While installed in the other 1.8GHz G5, the hard drive was formatted, given a clean install of OS X 10.4.11, and then moved into this computer where is never mounts. The computer is not accessible through TDM.
Do I have a bad logic board? Bad CPUs? A power managment issue? A RAM issue?

Through my own trial and error troubleshooting, I have found the CPUs to be in good working order and the logic board passes the Apple Service Diagnostic every time. Despite the installation of numerous pairs of modules that worked in another DP1.8GHz, the computer has a RAM issue-it gives the "no good RAM" tone most of the time when it powers up (after a PMU reset it does not). Also the computer boots from disk or into Open Firmware but the disk utility can't see either hard drive so I may have a bad SATA controller.

Grid Control : Change Management Across Non-Prod and Prod

All,
I had some questions with regards to Grid Control Implementation Architechture on Prod and Non-Prod Env's
The best practice is to configure a production Grid Control (GC) environment to monitor only production targets. This prevents nonproduction targets from adversely impacting a production environment.Another issue could be the compliance policy where in the production systems are to be isolated from Non-Production Environments.
If this is the case then we have to have 2 GC environments , 1 for Prod and 1 for Non-Prod. In such a scenario how well can we do change management (Version control ) across the Non-Prod and Prod Environments ?
To be more specific
How is version control managed for Oracle builds if we have separate GC for Prod and Non-PROD? (Change Management pack / Configuration Management Packs are there but what is the real depth of these? )
Change management for the Oracle Environments from DEV -> Test -> Pre-Production-> Production? We aim to have consist build across the environments can we achieve this if the GC is managed by Different OMS/OMR and if we have 2 separate environments how do we sync the GC environments managing PROD/NON-PROD after a change?

This is feature is not there in 10.2
This situation can be avoid by chagning the 9i port to 1522
or install the GC on diffrent box

Tracking Change Management in P6

caveat: We don't use Contract Manager / Expedition 
We do use Timesheets for time entry and
status of activities
Ok, in P6 we
are trying to track change management. Maybe not the full
workflow that passes from individual to individual. We are
looking at two ways to track that the Project Manager is
doing his job.
First, we may use
steps. The project control specialist would get
communication from the PM and the PCS would then enter a
step with info provided by the PM. At completion the PM
would acknowledge that the change management process has
been completed via timesheets (check it complete) 
Or we may use Issues. Same idea as above
but I believe with issues we could take advantage of the
"discuss" button in the client and track history. Pitfall
- MyPrimavera does not show the history. 
Anyone else trying to track a
Plan-Do-Check-Act type of event?
 Thanks,
Patrick

Hi Cherry,
what about your TMS configuration. Did you switched to extended transport control and modified your transport landscape to transport groups?
Please check your project with: /n/tmwflow/charmchk. The result could be helpful for error analysis concerning wrong tms configuration.
kind regards
Rayko

BOM Validity - Using Engineering Change Management

Hello All,
We are currently reviewing the ECM functionality to assistn in BOM validity maintenance. I have made the necessary changes in SPRO to activate this functionality. My initial testing utilizing the Change Master and associating it with the BOM works fine. However, the question I had was more around having to make retroactive changes. I noticed that the system using the Entered or Created date from the transaction to determine the BOM validity. Is there anyway to influence the BOM validiy to look at document dateof the transaction instead of entered date? Has anyone run into this type of issue before?
Thanks for your help.
Gus

Hi Krishna,
You can use change numbers to change independent (recipe) formula in the PLM-Recipe Management.
The object formula is assigned to the object type specification (type 60 of the change management).
For the object type specification the use of the object management record is not supported in the SAP standard.
Only the change documents are available.
Best regards,
Roland Freudenberg

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

Charm - how manage issues after go live phase

Hi all,
ny customer use Charm Implementation project for managing roll-outs of new countries in his SAP ECC Landscape.
Now Test Phase is going to end and he asks himself: "how can I manage issues after go live in Charm?"
If I have to create additional TRs for bug fixing in the weeks after go-live can I manager them in Charm?
I know there is the function for create TR direct in Talsk List, is this the correct way?
In other words, do I manage issues after go-live out of Change Documents using Task list?
As you know, Is there any best practices from SAP od from elsewhere?
Thanks o lot
Giovanni Lippolis

Hi Miguel, Bob and Jansi,
thanks for you contributions.But I realize I didn't explained myself completly.
My situation is similar to what Bob described,
I'm not in an ideal world (do you remember Clint Eastwood and Kevin Costner), and I think neither you.
But, in my case there are not open TR to be recovered in project, but I suppose I'll have to open some TR (I hope a few) for fixing bug that will happen in production in the days post roll-out.
So I wouldn't like to manage there fix in a maintenance project, because the reason of these bugs is in TR imported in roll-out.
What I would like to do is to regress project to the Test phase (I don't need new CR and NC!) and open few Test Messages for fixing bugs.
I'suppost It should be possilble.In your opinion?
Ideas?
Thnks a lot.
Giovanni
So what

Order Change Management and direct manufacturing technique (SOBSL 52)

Dear all,
there is a statement in our SAP development team, that I can hardly believe:
Order Change Management and direct manufacturing technique are not fully supported in SAP standard (ECC6.0).
Can any body help me with this issue?
Kind Regards
Bernd

Dear Bernd,
please see SAP note 436928, which descriped the restrictions from OCM.
Regards,
Sabine

Adding users as contributors in change management

Hi everyone,
I am facing some issues in adding some users as contributors in change management.
The users have almost all the required privileges like
REPO.MODIFY_FOREIGN_CONTRIBUTION.
REPO.MODIFY_OWN_CONTRIBUTION.
REPO.MODIFY_CHANGE
When I click NEW CONTRIBUTOR , I am unable to see the User in the list.
Is there any other special privileges that are required. I have gone through the developer guide also to resolve the issue but couldn't find any missing privileges.

Hey:
Sorry,I don't have a document or deliverable written up to do that. But I have found a few weblogs on related subject matter on this forum. I would suggest you search for this.
However, I will write up a high level process for this here:
Log into your Primary Domain Controller (Non Solution Manager)
So, if your trying to modify the routes in ECC, log into the Domain Controller of ECC
Transaction: STMS
Overview - Transport Routes (Shift + F7)
Go into Change Mode (Pencil and Glasses Icon)
You now need to modify the Transport Group for example: /QASGRP/ or /CUSGRP/
All transport groups begin and end with the "/"
You will see two or three groups in the consolidation route (Between DEV and QAS)
You need to be careful and modify the Customizing Group.
Once completed, you will save and activate changes.
Let me know if you have any other questions
Imran

Maintenance Optimizer - Under Change Management in solman_workcenter

Hello,
If I go to transaction solution_manager and navigate to the Maintenance Optimizer in our solman system, I see dozens of lines of maintenance requests. Furthermore, I go start a new transaction and I will be shown the appropriate logical components which are assigned to the solution landscape that I chose when entering solution_manager/dswp.
However, when I use solman_workcenter instead (which is the direction that we want to go), and then go to the change management tab, and click on maintenance optimizer, I am not shown any maintenance requests. Furthermore, when I try to start a new transaction, the logical components are not displayed and I cannot choose the system for which I want to the transaction for.
Am I missing some configuration or setup within SOLMAN_WORKCENTER which is preventing me from being placed into the appropriate Solution Landscape?
Thank you.

John,
Looks like this is an authorization issue.
Please check the user has these following roles.
SAP_SMWORK_ADMINISTRATOR_COMP
SAP_SMWORK_BASIC
SAP_SMWORK_BPM
SAP_SMWORK_CHANGE_MAN
SAP_SMWORK_DIAG
SAP_SMWORK_INCIDENT_MAN
SAP_SMWORK_JOB_MAN
SAP_SMWORK_LANDSCAPE_MAN
SAP_SMWORK_SETUP
SAP_SMWORK_SYS_ADMIN
SAP_SMWORK_SYS_MON
It's working fine for us.
Our user has these above said roles.
Regards,
Sanjai

Order Change Managment

I have a peculiar type of issue. The production order has the status CGFB- Confirm./goods mvmnt forbidden Which has been activated for the production order through Order change Management. But once this is being activated i am not able to do the delivery and order is blocked. So how should i deactivate this status in the production order. I have checked for the Material in the Work Scheduling view but no Overall profile is being usef for the Material. So i can i deactivate the Status CGFB in the production order set by the Order Change Managment.

REPORT ZPPSFC179 has been runned for the production order and the problem is not being solved
Message was edited by:
kumar jagadish
Message was edited by:
kumar jagadish

WARNING: Canon Pro Printers and CS4 – Serious Colour Management Issue

Over the last four days (and over fifty prints) I have undertaken extensive and meticulous tests to identify the cause of a problem; namely that targets for profiling a new printer (a Canon Pro9000), printed with ‘no colour management’, were printing far too dark and with what appeared to be a colour cast.
I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3.
Furthermore, colour managed prints (using the same accurate profile made in CS2), printed in CS2 and CS4, show subtle differences. This may not be an issue except in the most critical applications.
It is likely that the problem will not be confined to the two Canon printers above since many other Canon printers share the same driver architecture.
Reading posts and discussions on other websites would seem to indicate that this problem is also manifest with some Epson printers and may also effect Mac OSX 10.5.
I have to conclude, therefore, that Photoshop CS4 cannot be replied upon to print targets of sufficient accuracy to produce reliable profiles for a colour managed workflow.
The fact that this is only just being reported can be attributed to four factors:
That many CS4 users are continuing to use profiles made under older versions of Photoshop and have yet to make new profiles using CS4.
Some users may not immediately notice a problem, or may ascribe it to other causes.
Some users may take the line of least resistance and use a previous version of Photoshop to work around the problem.
Some users are still using the older versions of Photoshop not effected.
Eric Chan (of Adobe) has stated on another website that CS4 implemented some new APIs for printing and that this has given rise to some "minor glitches". If Eric Chan is correct, and Adobe changed the APIs in Photoshop CS4, this begs question of whether Adobe sufficiently tested CS4 before release ? If Adobe did not test their software, and therefore failed to identify this critical problem, this would suggest negligence on Adobe’s part. If Adobe identified the problem but then did not inform users that a potentially serious colour management issue existed this would suggest wilful or gross negligence.
It is not good enough to say that Adobe simply followed the ‘conventional’ path and ‘followed the rules’ regarding API implementation. The experience of end users does not correspond to a “minor glitch” and, in my case, has been extremely costly in terms of time (over five days in all), lost revenues, and materials. Furthermore, why should Adobe's customers be forced to use their valuable time diagnosing problems clearly of Adobe's creation – and actually admitted.
In UK law providers of goods and services (and this includes software) have to supply them as “fit for purpose”. Clearly, in terms of colour management, CS4 is not fit for purpose. Neither can Adobe hide behind its labyrinthine licensing terms since any exclusions would be ruled unlawful under the UK’s ‘Unfair Contract Terms’ Act.
My strong and unequivocal recommendation is that representatives from Adobe, Apple, and the printer manufacturers meet together – with the utmost urgency – and provide a rapid and complete solution. It is simply not good enough to pass this ‘over the wall’ saying “it’s not our problem”. It is. Adobe's, Apple's, and the printer manufacturers'. Please solve it. And quickly.
Identify the problem clearly, make it and the solution/s public; and publicise it widely and thoroughly.

Dear DYP.
Thank you for your concern.
"What fixes have you tried?"
If I may quote from my post above:
"I have conclusively eliminated the printer, the printer drivers, the Mac OS, corrupted preference files, corrupted user accounts, incorrect Photoshop settings, incorrect printer driver settings, the ‘sticky settings' issue, and user error as possible causes of the problem.
I can say with 95% certainty that my tests, conducted using Mac OSX 10.4.11, have proved the following:
That, printing to a Canon Pro9000 or iP4500, Photoshop CS4 does not print accurate targets suitable for producing profiles. This applies to both the No Colour Management (NCM) and the Printer Manages Colour (PMC) settings.
Photoshop CS and CS2 are not effected.
I did not test CS3"
These tests took place over three weeks and involved over five days of work and the replacement of the printer on Canon's recommendation (although the printer is clearly not at fault).
Please note that I am using Mac OSX 10.4.11.
"What driver versions are you using?"
Pixma iP4500 6.9.3 (also 6.9.1, 6.9.2 and the driver supplied on the CD).
Pro 9000 4.8.7 (also 4.7.3, 4.8.4 and the driver supplied on the CD).
"Yes it is frustrating but in a lot of cases it is fixable as I and others have clear reported, on this and the LR forums."
I have not found any fix on any website referring to Canon printers, despite exhaustive searches (this includes Canon's European and US websites which are mute on the issue).
The ReadMe file supplied with the installation disc of CS4 refers to problems with "some Canon printers" when printing with the 'Printer Manages Color' but does not identify using 'No Color Management' nor Epson printers as having issues.
I hope this post answers your questions.
Clearly all users of CS4 need to be warned of this problem which is likely to effect other printers. I believe that I am assisting others by issuing this warning. It is done, not to cause mischief, but in the spirit of a public service. CS4 users can then treat their printing results from CS4 with caution, and then conduct their own tests. I have presented a workaround which is to use a prior version of CS4.

Change Management Issue

Similar Messages

Maybe you are looking for