Parallel developments - Version Management issue

Hi all,
My project is going into its enhancement phase and we intend to have a parallel development environment. Dev1 is for maintenance of the Production system, Dev2 for the new enhancement project.
Dev 2 is a client copy of the QA1 environment, as the data there is cleaner than Dev1. Eventually, once the enhancement has gone live, Dev 2 will be the overall Dev system.
My question: Version management is only stored in the source client, that is, Dev 1. How can we sync up the version management histories of Dev 1 and Dev 2. The client is concerned due to audit reasons.
Thanks!

Hi
Here the client doesnt want to use Me9f for output of the message. So the issue is how to get the output done from me21n and get the version updated from Version"0" to Version"1".
for this maintain the Message despatch time as 4 - Send immediately when saving the application Instead of 3 in the message condition record
This will process the message once the PO is relased & saved
Version managemnt is effective only if the existing messages are processed, if the message is not processed then version will not change in the PO.
Thanks & Regards
Kishore

Similar Messages

Version management issue

I am two issues with Version Management in PR and POs:
- New version can only be added onces the PR or PO is release by final authority. Below is the scenario:
I have created a PR and have it release by the two approving authorities. Now I want make changes in the PR. I have it cancelled from the both approving authorities and make the required changes. Now logically the system should allow the initiator to add the new version so that requisition so that the approving authrities must know that the second version of requisition is being released. But the system doez not let the initiator add the version prior to release. Do we have any solution to this?
- second issue is that once the second version is added in the PR and we need to make some more changes and create a thrid version, system doznot let user to revoke the release.

Dear ABC,
For your issue 1, please check if version already set to completed and an message output already sent to vendor.
This is the prerequisites for the new version to be created. A new version will only be created when the information
had sent to vendor.
Regards,
ian, Wong Loke Foong

Issue in PO Version Management

We have recently configured release strategy for PO in SAP.
Now there is issue with Version management.
Consider X and Y are users responsible for Purchasing activities.
Scenario prior to Release Strategy Configuration:
If X has created PO and if it is transferred to Y for some changes, Y used to manually genrate version(Using + button on Version Tab in PO) and used to make changes in PO. i.e. X and Y both were able to genrate version.
Scenario after Release Strategy Configuration:
If X has created PO and if it is transferred to Y for some changes, Y is not able to genrate version as + button on version tab is deactivated but able to make changes in PO. i.e. X is able to genrate version.
Client wants it as per earlier scenario. i.e. Both X and Y shud be able o generate version manually.
Is thare any authorization issue? or it got affetcted because of Release strategy cinfiguaration.....? How to resolve this?

Hi
New Versions of Purchasing Documents
The system always creates a new version when the purchasing document has reached a final state. This means one of the following processing states:
Active
If you do not use the document release functionality
Release completed
If you use the document release functionality
For a new version of a purchasing document to be created, all messages must have also been transmitted.
No new versions are generated for purchase orders that are on hold or not fully released.
Hope it helps
Regards
Prasanna R

Version Management - Active flag issue

Experts,
Here's my issue. When I edit a program, activate it and assign it to a new request, the program shows as active from the editor. But when I go to version management, the active flag (check box) for the current version (with the new request number) is not checked.
I tried checking the check box and do a retrieve. Then it showed an activ flag (checked) and modif flah(unchecked). But when I go to the editor mode and get back to version management, again, the active flag is blank. Is it to do with BASIS or what could be the problem?

solved myself

Version management output type issue

hi,
we have activated version management and all working fine .
but while taking print out through ME9F we have assigned to 3 output types (NEU,ZNEU,ZNIU) for a single PO , until and unless we take print for 3 output tyes we are not able to amend the PO .we are getting the below error .
"No new version created because a message has not yet been transmitted"
is there any option if we take print for one output type(ZNEU )out of 3 output types(NEU,ZNEU,ZNIU) it should allow us to do changes in PO .
please assist we need to close the requirement on priority .
thanks in advance

HI,
is there any option if we take print for one output type(ZNEU )out of 3 output types(NEU,ZNEU,ZNIU) it should allow us to do changes in PO .
No i don't think so system will create new version.
new version is created when you output PO completely
try this create pool request for other two message in Message tab in PO in ME22N and then try PO it will work
Regards
Kailas Ugale

Version Management

Dear Sirs,
We have activated version management for purchase orders.
Purchase Orders are made in the system and printout of the same are being taken from the print preview screen before the release of the PO.
If some changes are made in the PO after the release of the PO, the sytem does not activate the version management. Reason: no messages were issued after the release of PO.
Is it possible that when a print out is taken, the system automatically processes the output message, whether the PO is released or not.
Viral Bhinde

Hi Viral,
I got ur problem.
As you said when you make changes to PO system set new release strategy as well as new version. It is expected that whenever there are changes in PO it should be communicatted to Vendor thru PO print.
In your case ur PO created new version as well as new release strategy. And you tried to take print before PO release. Please first release the PO and take print thru ME9F. That message will disappear.
Plz let us know if there is further problem.
Thanks
Nilesh

Sales Order Version Management

Hello Guys
Who had any experience or document or solution about the Sales Order Version Management just in SAP R3 or ECC6.0?
Thank you so much!
Best Regards
Wang yiwei

Dear Vincent
May be this is related ABAP Issue please check with them because i found same issue
"BAPI_SALESORDER_CREATEFROMDAT2" - getting error while executing in se37.
"Specify either address number or address handle " BAPI_SALESORDER_CREATEFR

Internal Data Transfer to Funds Management - Version Management Error

Hi All,
We are trying to convert the open PO's in our system that were created before FM was implemented, and that are to be converted now before the MIGO stage.
We are using the following steps:
1) Select the document
2) Convert the worklist.
We had done the first step, and faced no issues. During the conversion of the worklist, we face the following error
Message ID - MEPO;Message Number - 813; Version Management of purchase order still faulty.
Message ID - MEDCM; Message Number - 4; Enter short text for version
Message ID - MEDCM; Message Number - 3; Enter reason for change for version
In the Control Data for each of the Document Type, the control data, Version Active and Version 0 OK are activated.
Can someone kindly suggest what could have possibly gone wrong here ?
Regards,
Wy

Hi All,
Just to clarify, I went through note 800784 and found that in our system
1. None of the fields - 'Reason,' 'Description,' 'Req By,' 'Req By Ext' or 'Post Date' - is a required entry in the version management field selection
2. None of the fields - EKPO-ELIKZ or EKPO-EREKZ or EBAKZ - are set as Version-Relevant Fields of Purchase Requisitions.
Cant figure out why I am not able to assign the fund centre and commitment item here, although I am able to perform MIGO and MIRO on that.
Regards,
Wy

Purchase order item text version management is not creating.

Dear sap professionals,
I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number, but in present case instead of creating new version number the data is updating in existed version number.
Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any thing in this process.
Did any one experienced same issue?
With Regards,
Ranganath

ranganath.kakarla wrote:
Dear sap professionals,
>
> I have an issue in item text as per customer need I created item text type as drawing number, the problem is when ever an user change drawing number review in text area system should create new version number, but in present case instead of creating new version number the data is updating in existed version number.
> Same time I am not able to trace field name and table used for this specific drawing number type, do I need to do any new configuration for that or I missed any thing in this process.
> Did any one experienced same issue?
>
> With Regards,
> Ranganath
Hi,
path:mm-purchasing-version management-Set Up Version Management for External Purchasing Documents
Doc.cat will be F means po, Doc type will be NB & p.org of ur client
in control data active both version acrive & version 0 ok.
in field selection reason, shorttext& requestor is required option & save
give the reason for ur inputs
in Set Up Change Displays category willbe f for all doc types
Regards
Raj.

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.

Comparing version management after import for structures

Hi,
I am having issues with transports on ECC 6.40 for table structures. I went to Utilities, Version, Version management, Remote comparison with QAS, and clicked on Delta display, I see that it saids 'Unchanged'. Would this mean that nothing got transported or impotred to QAS?
Is it correct that SAP structures are not transportable? I am actually enhancing SAP standard structures and fields through using a SAP provided standard report.
Would I have to run this report on the target system QAS and eventually PRD to add the SAP fields to the structures? Woudd that also mean that I would have to ask Basis to open the system, run the report, and close it?
Thanks
null

Hi Padmanabha,
in addition, you should replicate the datasource 8<source cube> and reactivate the transfer rules using RS_TRANSTRU_ACTIVATE_ALL.
Hope it helps,
regards
Siggi

MEDIA MANAGER ISSUES?? PLEASE READ BEFORE POSTING

We have created several Media Manager specific threads for your issues that are "stickied" at the top of this board. These are :
Media Manager Installation Issues
Media Manager Design Issues
Media Manager Audio Playback Issues
Media Manager Video Playback Issues
Media Manager General (Other) Issues
Please post your Media Manager issues in the correct corresponding thread so that our FSC employees can identify and begin to resolve some of the problems being experienced by our Media Manager customers.
Thank You!!
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer that solved your issue as the accepted solution.

I can understand your point of view and I respect it in regards to Small Basic being a learning language. None the less, let me make a suggestion that would be more ageeable, I think, to different kinds of people. Why not make different versions
of this new language: version 1 for beginners that I heard would be out by the end of this year,
version 2 for intermediates and version 3 for more advanced programmers. All this would culminate to the Visual Basic language. These 3 versions would smoothe out the gap between SB and Visual Basic. Your new programmers would
evolve at the same time your versions would come out and Microsoft would have a long term policy of loyal programmers.

Color shift (color management) issues in Mavericks

Noticed color management lacking for Safari and Dock icons just after Maverick update, but was unable to check it with recalibration. Today X-Rite issued an update for i1 Display PRO and i was able to recalibrate my display, but the problem unsurprisingly wasn't in the display profile.
Bellow are two screenshots of Safari vs. Chrome and FF vs. Chrome respectively.
Color difference is seen with the naked eye, but gray and blue fields' values are also annotated (Safari is on the left, Chrome is on the right).
These are FF (on the left) and Chrome (on the right) with no color difference, both browsers are color-managed.

Issues here too: 2013 Mac Pro, latest Mavericks/browser versions (OS X 10.9.4), and Dell UP2414Q display (known for good color—not to mention the only retina display money can buy).
Safari seems fine: web sites with no color profiles in the images look very much as I am used to from OS X Lion and Windows on other machines (some variation from screen to screen is just life). CSS colors match image colors when they should.
Firefox is ultra-saturated: web sites the look fine in Firefox--and identical to Safari--under OS X Lion (on a different Mac/display anyway) but on the new Mavericks system, colors are eye-burningly saturated! That's CSS and images alike (without color profiles). CSS and image colors still match—but both are WAY oversaturated.
Note: images dragged from Safari and Firefox to my desktop both look fine when opened in Quick Look or Preview. Both (again, images without profiles) look super-saturated like Firefox when opened in Photoshop CC—despite Photoshop having the same settings I'm used to using (color management Off for RGB, working space set to Monitor) on my old Mac with PS CS6 under Lion. Yet the color values in PS CC do register as correct despite looking so bad (same goes when opening my own RGB source PSDs that generated the web sites to begin with).
Shouldn't Safari and Firefox out of the box look alike, since they do in earlier OS versions? (Even if some workaround is found, "out of the box" a new Mac with default Firefox installation now looks terrible.)
Separate but complicating issues, in case it helps to diagnose this:
a) The Dell display's default calibration looks quite good to me; but if I run Apple's visual calibration steps which I would normally do on a new Mac, everything gets very dark. (So I went back to the default calibration, which is supplied by Apple and called "Dell UP2414Q"; Apple clearly supports this display specifically, since I never installed any Dell software.)
b) When I take an OS X screenshot of Safari, despite it looking "right" everywhere (Preview and Photoshop CC alike), values are way off. (Regardless of whether I strip the color profile or not when importing the screenshot into Photoshop CC.) When I take a screenshot off Firefox, the screenshot looks "right" (no longer oversaturated!) in Preview and Quicklook. When imported into Photoshop CC, Firefox screenshots behave just like drag-saved images from Firefox: they appear super-saturated just like in the browser, BUT the color values at least register correctly.
c) No setting I can find for Photoshop CC will make exported images look right (and match CSS colors) in ANY browser unless I accept them being super-saturated while I work on them (which of course is untenable). I'll deal with that separately: I've abandoned the new Mac Pro for Photoshop work and gone back to my old Mac (and PS CS6)--but this I assume to be Adobe's fault. I mention it only in case it's some kind of clue.
For what it's worth, here's my interpretation: Firefox and Photoshop are using the full gamut of the display, while Safari is not—and Safari looks GOOD not using the full gamut. (And at least with this Dell display, it looks "correct" that way.) Pure primary red #FF0000 (images and CSS alike) which appears normal to me in Safari and Preview and Quicklook turns to eye-burning neon red in Firefox and Photoshop (with management Off and working space set to Monitor). It's kind of amazing that the display can show a red even more brilliant than I have ever seen on a computer before, BUT it doesn't help me design web sites for the rest of the world who has a more ordinary gamut.
Maybe this is just a long-standing Firefox bug, revealed to me now that I have a large-gamut display? (But that wouldn't explain why other people have seen colors MORE saturated in Safari then Firefox.)

Basic Version Management

I would like to see basic version management functionality built into LR. This would allow the user to not only create different versions of an image, but keep track of their relationships and status.
As a fine art nature photographer, I might have an original RAW file, a PSD master file, a series of TIFFs optimized for various print sizes, a JPEG for my web gallery, and maybe a different JPEG for slideshows. I can stack these together, but LR doesn't allow me to relate them as different versions of the same image or keep track of their status (maybe the TIFF for a 16x20 print needs more work, but the 11x14 is done).
Ideally, the Version Management would allow the user to set up a list of version types and statuses. Image versions could be moved from one status to another manually or automatically based on rules. An interactive chart could display the version relationships and allow the user to change statuses quickly.
Different versioning templates would be needed for different types of workflow. One might be used in the above example of a landscape photo that has multiple output types and sizes. A different template would be needed for a panorama built from multiple original images but going to the similar types of output.
Full-featured version management might be best left to a 3rd party module, but the versioning and status information would have to be kept in the LR database.
Brent Gilstrap

Jeff,
First may I say, "Thank You" for the excellent LR video tutorial you did with Michael Reichmann. That got me up and running much faster than I expected!
And thank you for taking the time to reply to my request. Getting back to version management, I must disagree with you that this is a simply an old vs. new workflow issue. This is about letting me work around the limitations of LR.
I don't know about you, but I sharpen somewhat differently for different size prints and for different papers. I also print colored borders on many of my prints - the width of the border varies with the print size (and is well beyond the 20pt maximum stroke border in LR). Also, as I use the ImagePrint RIP and often wish to print borderless on roll paper - at times I must go outside the LR print module to get the print output I want (LR + PTAPP does not support borderless on roll paper yet).
I can't imagine that LR will ever be feature-rich or smart enough to support everything I want from within the Develop and Print Modules. Ok, I CAN imagine it, but I'm not expecting mass-marketed software to meet all of my needs. Once LR has expert sharpening & noise reduction, soft proofing, more flexible print borders, etc... I'll re-evaluate the situation.
For now and the foreseeable future, I will need multiple physical files for print output. I can stack these to group them with the original RAW file - but LR would be so much more useful to me if it could also keep track of the use and status of these different files.
Based on your reply... I'm thinking I'm going to have to develop a Version Management module for LR myself. If only LR had scripting. Doh!
-BG

Version management in Essbase

Hi all - We're looking to do version management with our Essbase objects (outlines, calc scripts, etc) as part of an ITIL implementation. Has anyone had any luck or experience in such an attempt with Essbase in a UNIX environment? The corporate standard will most likely be PVCS (now owned by Serena). Many thanks, charlie 

FYI, we were able to get EAL up and running after adding the following entries into the registry on our servers...
Solution
This timeout issue can be fixed by adding two tcpip registry parameters, but first you must identify which client was communicating with essbase when the timeout occurred so that you know which machine to add the parameters to. If all the EAL and EPM components are installed on a single machine, then that machine would also host the client. If products are installed in a distributed environment you determine the client machine based on how the EAL Essbase Server component is defined.
The APS URL is part of the Analytics Link, Essbase Server definition in EAL.
If the value (APS URL) is "Embedded" this means that the EAL Application Server is communicating via the JAPI directly with the Essbase Server. In this case the EAL AppServer is the client to the Essbase Server. For this case the following tcpip registry parameters need to go on the machine where the EAL Application Server is running.
If the (APS URL) value is http://serverName:13080/aps/JAPI then the EAL Application Server is communicating by way of Hyperion Provider Services (APS). In this case EAL proxies requests to and from the Essbase Server through APS. This means that APS is the client to the Essbase Server and the tcpip registry parameters need to go on the machine where Hyperion Provider Services are running.
Once you have identified which machine is acting as the client to essbase, set the TcpTimedWaitDelay=30 and MaxUserPort=65534 parameters via the windows registry.
1. Open the Windows Registry.
2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters.
3. Add new DWORD Value named "TcpTimedWaitDelay"
- right click and select Modify
- Select "decimal" radio button, type in 30.
4. Add new DWORD Value named MaxUserPort
- right click and select Modify
- Select "decimal" radio button, type in 65534
5. A reboot of the server is necessary.

Parallel developments - Version Management issue

Similar Messages

Maybe you are looking for