Version management in release procudeure

can anyone help me throwing some lights on version management in release procedure of PR/PO??
regards
Prakash

Hi,
When you activate version mgmt it will ask only when the value changes for the PO and not when the PO is released.
Ex:
If I want to change the PO price or Qty now new version would get trigger. You need to check and save the PO. Until and otherwise if you are not tick on the 'new version completed' you can't release the PO, It would be in Open state.
regards,
Dhanush.

Similar Messages

In ME38 can we add Version Management , Release Strategy

Hi,
Is there any way to add Version Management and Release strategy in ME38.
Thanks & Regards
Sudhansu

Hello ,
Please check the settings
Here Activate (Tick) for LPA .
please check and revert back.

Version Management active for Release Purchase Orders

Hi Friends
We activated Version Management for Purchasing documents. Version 0
activates automatically when we create PO / contract. After final
release version will be closed automatically.
When ever new version is active we could able to make release orders.
When we make message no.MEDCM014 to error, we could not to do. But we
want release orders should be make up to old value.
Can we do with some user exit or BADI for this purpose.
Regards,
Sai Krishna

Hi,
I think there is no std. way to solve this
Regards,
Sai Krishna

Version Management on PR with Release Strategy

We are using Release Strategies on PR, along them Version Management activation is also required. All configuration have been done, Versions are automatically triggering in PR's without release, however in PR with release new version is not reflecting, every change is going in Version 0.
Suggestion is required...
Full points will be awarded.

Refer the note 664928
You change a purchase requisition. Why does the system not generate a new version?
Answer:
The system always creates a new version when the purchase requisition reaches a final processing state. These are the following processing states:
Active, if no release is used
Release completed, if the release is used
Only the following changes to a purchase requisition lead to a new version:
All version-relevant changes (defined in purchasing Customizing under -> Version Management -> Version-Relevant Fields of Purchase Requisition)
Changes to the document assignment

How to manage the Release versions of webdnpro applications

Hi All,
We are building some applications using webdypro . These applications may need to be rollout for different countries like V1.0 and V1.5 ....ect.
How i need to manage this versions like when completed my V1.0 version when i start working on 1.5 version changes. If want to implement for V1.0 to some client. What is the version management i need to follow. What is the procedure for this.
Regards
vijay

Vijay,
google for some version control mechanisms like CVS,VSS
Thanks
Bala Duvvuri

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

Skin Customization in Oracle Identity Manager 11g Release 2 (11.1.2)

I was recently tasked with branding an OIM instance to match pretty stringent branding standards. To accomplish this task, I extended the fusion theme which is provided out of the box into a new custom skin. In the example below, I took the design as far as I could, which required decently advanced css knowledge; however, even a novice web designer could easily make simple updates to the backgrounds and fonts which would also greatly enhance the user experience.
Utilizing FireBug for Firefox, I inspected elements of the OIM interface to see which div's I needed to modify in the css file. You can edit as little or as many elements as you'd like in your custom skin; however, I'd recommend preserving the primary elements original placements to avoid confusion for users that are already used to an out of the box version of OIM.
This is the Oracle doc I used when creating the custom skin: http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/uicust.htm#BABJIJIA
Notes regarding the Oracle tutorial mentioned above:
Be sure and remove the temp directory, shut down your OIM server, upload your files, then restart your OIM server with each css modification.
30.3.1 - Configuring Skins: 1. After you create the skin in the trinidad-skins.xml file, make a copy of the trinidad-skins.xml from the /iam-consoles-faces.war/WEB-INF/ directory to the
oracle.iam.console.identity.sysadmin.ear/WEB-INF/ directory AND the
oracle.iam.console.identity.self-service.ear/WEB-INF directory.
(The doc references admin.ear: the fully qualified name of the ear is: oracle.iam.console.identity.sysadmin.ear)
30.3.1 - Configuring Skins: Make all of your changes in the /oracle.iam.console.identity.sysadmin.ear/WEB-INF/trinidad-skins.xml file, /oracle.iam.console.identity.self-service.ear/WEB-INF/trinidad-skins.xml file, and the /iam-consoles-faces.war/WEB-INF/trinidad-skins.xml file.
(The doc doesn't mention making your css edits in the oracle.iam.console.identity.self-service.ear directory which is required)
Here is a link to my blog post with screenshots: http://www.idmworks.com/blog/entry/skin-customization-in-oracle-identity-manager-11g-release-2-11-1-2

I was recently tasked with branding an OIM instance to match pretty stringent branding standards. To accomplish this task, I extended the fusion theme which is provided out of the box into a new custom skin. In the example below, I took the design as far as I could, which required decently advanced css knowledge; however, even a novice web designer could easily make simple updates to the backgrounds and fonts which would also greatly enhance the user experience.
Utilizing FireBug for Firefox, I inspected elements of the OIM interface to see which div's I needed to modify in the css file. You can edit as little or as many elements as you'd like in your custom skin; however, I'd recommend preserving the primary elements original placements to avoid confusion for users that are already used to an out of the box version of OIM.
This is the Oracle doc I used when creating the custom skin: http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/uicust.htm#BABJIJIA
Notes regarding the Oracle tutorial mentioned above:
Be sure and remove the temp directory, shut down your OIM server, upload your files, then restart your OIM server with each css modification.
30.3.1 - Configuring Skins: 1. After you create the skin in the trinidad-skins.xml file, make a copy of the trinidad-skins.xml from the /iam-consoles-faces.war/WEB-INF/ directory to the
oracle.iam.console.identity.sysadmin.ear/WEB-INF/ directory AND the
oracle.iam.console.identity.self-service.ear/WEB-INF directory.
(The doc references admin.ear: the fully qualified name of the ear is: oracle.iam.console.identity.sysadmin.ear)
30.3.1 - Configuring Skins: Make all of your changes in the /oracle.iam.console.identity.sysadmin.ear/WEB-INF/trinidad-skins.xml file, /oracle.iam.console.identity.self-service.ear/WEB-INF/trinidad-skins.xml file, and the /iam-consoles-faces.war/WEB-INF/trinidad-skins.xml file.
(The doc doesn't mention making your css edits in the oracle.iam.console.identity.self-service.ear directory which is required)
Here is a link to my blog post with screenshots: http://www.idmworks.com/blog/entry/skin-customization-in-oracle-identity-manager-11g-release-2-11-1-2

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

Problem in Purchase order version management

Dear Guru,
My Friend i have some problem in version management in Purchase order, when my user changed PO new version created, then user fill the data like reason, text, requested by but he forget about the tick mark on completed field so that PO not require new release.
can u suggest how i can mandetory this completed field
Regards
Kashyap Kumar

Hello,
In version management..the tick is mandatory.... and remaining fields are not manadatory.......
Mahesh

Version management for POs

Dear friends,
Iam implimenting Version management for purchase orders.I have got doubts like;
1)---In IMG side ,under setup change displays node, we need to enter all the field names of purchase order document type wise, ..i.e.
we have got three doc.types of POs,NB,ZCP,ZCO,then Header and item details fields of PO shall be entered against each doc.type in this node.
like -NB-EKPO---MATNR
NB-EKKO-field
We need to enter tables as EKKO and EKPO and
all the fileds are to be entered for all the doc.types.
we need to enter all the fields including header fields and item fields ,
2)----For header fields,if i change the data,version is not creating,
3)--At item details ,after release of the PO,if i change the data,if i save the document,it is saving without automatically closing the version.We need to manually close the version.
I have given error category E for application MEDCM for 14,19,22,eventhough system is not giving error.
Atleast provision should be there to give error if user doesnot close the version manually.
Please suggest for my doubts.
Regards,
Magana

Hi
For a combination of purchasing organization, document category, and document type, you can:
<b>Activate version management</b>
If version management is active, changes to a purchasing document are managed in versions.
<b>Define field selection for versions</b>
You can specify the attributes certain fields of the version are to have: mandatory entry, optional entry, display only, field suppressed.
Set the message ststus as follows
MEDCM     014     Purchasing document &, version & in process     W
MEDCM     019     Purchasing document &, version 0, still in process     E
MEDCM     021     Not all version-relevant changes were cancelled (&1)     W
MEDCM     023     No unprocessed message exists                         W
System will allow to manually close the version .Version 0 will be set automatically .After that system will allow to manually close the version.
I dont think you will face probelm.
Regards
Sunny

JDeveloper integration with Serena PVCS Version Manager

I have seen that Oracle JDeveloper 10.1.3 now supports Serena Dimensions for versioning. What about Serena PVCS Version Manager 8.1? Are there any plans to integrate JDeveloper with the PVCS Version Manager?

Hi all,
Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
not yet developed an extension for JDeveloper to enable users to work with PVCS Version
Manager, which I believe is a specific product, rather than an interface.
This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
first posting above for more details.
Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
to build your own extensions for using JDeveloper with other source code control tools than those
we support.
In an ideal world, we would have been able to offer support for every source code control tool on
the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
we still plan and are currently looking into supporting more tools going forward and as many tools as
possible in the long term.
Unfortunately, we only have limited time available for each release and based on the feedback we
received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
that the market for source code control tools is quite fragmented and that customers use a wide range
ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
and ClearCase support, in order to help users build their own extensions in a similar way to ours.
Hope this helps,
Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

Activate Version Management in Purchase Order

Dear All Expert,
Current Condition, Version Management will be activated once the PO has been full released (using t-code ME29N) and then printed (using t-code ME9F).
Problem:
Condition in our client that they only need particular document that will be printed, so not all PO will be printed.
Based on this condition our client tends to activate Version Management once PO is approved/released (using t-code ME29N) without need to be printed.
Hope anyone could help me to solve this problem.
Thanks,
Franz.

Is there anyone who can help my problem, about Version Management

Version Management on SAP Script Forms

Hello,
Is there a version management for SAP Script forms
like what we have in ABAP programs?
I need to revert back the old version of my SAP scrip form like what I used to do in an ordinary ABAP program.
Is this possible?
Need your views on this.
Thank you very much,
Jeffrey A. Prado

Hello Jeffrey,
as far as I know there are just two versions stored in the system, the active one and the one you work on. As long as you do not activate your work, you should be able to track your changes. The other way (which I use) is to save the original version with another name and simply load it back when needed. Since we are working with an old Release I do not how it looks in the "new world".
Greetings,
Sebastian

Looking at version management of a Program report

Hi gurus,
can you please explain, why does the older version is active and flagged than the current version?
Points will be given later.

At the top of the version management screen you always see the active version. The date behind that version is the date that version was activated.
e.g. 10.Dec.2007
Now you decide a week later to release and transport your request. Once you release the request the (at that point newest version) is 'closed'.
e.g. You started doing changes in the program on 5.Dec.2007 which created a new version 00005.
You released the request on 17.Dec.2007 which closed the version 00005.
The display is as follows:
active version: xxxxxxxxx 10.dec.2007
00005 yyyyyyyyy 17.Dec.2007
00004 ........
In this case the active version is older than the current version.
Hope that explains it,
Michael

Version management in release procudeure

Similar Messages

Maybe you are looking for