Version Management - Automatic creation on vew version

hi experts,
I have activated in customizing a version management for Purchase Order, but I have the following problem:
the system doesn't generate a new version of PO when I change the address. I have already defined this field like a print-relevant in Customizing for Purchasing under Messages ® Fields Relevant to Printouts of Changes.
At the moment a can only see this change in a version display in the current version.
tkanks a lot
Mario

Hi Mario,
1) Go to SPRO-MM-Purchasing-Version Mgmt-Setup Version Mgmt for External Documents
Activate Version Mgmt against your Doc type and Double click on that Doc type NB then in next screen in Control data tab mark all the fields and in Field Selection set all the Fields as Required entry Except Posting Date and save.
2) go to SPRO-MM-Purchasing-Version Mgmt-Define Reasons for change
Create one New Reason Called Xyz something and give text and save.
3) Go to SPRO-MM-Purchasing-Version Mgmt-Set up change Displays
Here Select Doc type say NB and Give Table name say EKPO for PO and EBAN for PR, Give Field name say MENGE for qty and save.
Now try once.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/60b43bb7492147e10000000a114084/content.htm
Reg,
Ashok

Similar Messages

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

Fields triggering Version management in POs

I see in the following path in SPRO
MM-> Purchasing ->Version Management -> Set up version management for external purchasing document:
Version Management is active for doc cat 'F ' , doc type EC , and Purchasing Org FR01. But still when I changed the price of a PO (type EC and pur org FR01 ) and set the delivery indicator in the PO , the version management was not triggered.
What is the reason for this? Is it that VM will be triggered only for a specific fields in the PO?Where are these fields set?
I have seen in the same path there is an option "Version-relevant Fields of Purchase Requisitions" , but there is nothing for PO

hi,
Check your settings properly...
You can't set the fields for the PO as you do for PR...
The whole document will be taken in to consideration for version change and if setttings done properly
then the version compleated indicator must be set before releasing the PO and then check...
Regards
Priyanka.P

Automate version management in PO

Dear experts,
is there anyway to automate version management in PO without having to add it manually ..

hi johannes ,
can u explain in brief what do u mean by automate version management in PO ..
just explain the scenario .
regards,
vijay.

After automaticly updated to the version 7 the extensions page in the Add-ons Manager went blank and give this sentence "you don't have any add-ons of this type installed" but all the add-ons still working in the program

All the add-ons I had installed for the version 3+++ still working at the version 7, but the problem is that the extensions page in the add-ons manager is blank except a sentence that says "You don't have any add-ons of this type installed"

https://support.mozilla.com/en-US/questions/826729 has a solution for the problem

Can JWS be used as a multiple Java version management tool?

WinNT4 WKS with JRE 1.3.1 - 1.4.2 loaded on it using IExplorer or Netscape.
We don't have a need for the JWS download features because our clients (and their applications) remain static for the most part. However, we do require multiple JRE version support because our customers have written class/objet "fixes" (mostly for text rendering) and these fixes break if you try and run the application on a different version of Java from which it was written. Basically, we can't have a default JRE on each machine and hope that it will work with all customer applications. So we will load all necessary Java components on our workstations (in this case JRE versions 1.3.1 - 1.4.2). I know that browsers can be forced to load with a specific Plug-in version (providing it exists on the machine) through Object & Embed tags in the HTML and that standalone apps can be directed to the correct Java directory path. My question is, can JWS automatically identify the Java requirements of our customers applications and act simply as a multi-version management tool to provide the right JRE/Plug-In for either standalone or browser applications? Keeping in mind that all the JREs will be loaded on the workstions and it won't need to download any components from some site.
I've noticed that JWS identifies all JREs loaded on a machine in the Java tab so I'm wondering if it can "switch" the environment as needed for each application.
Does anyone know if I can use JWS in the scenario I described above? Thanks!

JWS can manage the multiple JREs installed if you run the application through a .jnlp. This can not "switch" the default JRE. It runs the application specified in the .jnlp using the requested version specified in the .jnlp.
JWS does not apply to applets. You should use the object tags as you mentioned below.
...can JWS automatically identify the Java requirements of our customers applications
No. You must determine this and setup the .jnlp appropriately.

How do I configure Firefox to automatically open the latest version of a web site instead of a cache version

I can not work out how to set Firefox to automatically load the latest version of a web site. I have web sites in my bookmarks and it does not look on the internet for the latest version and furthermore using F5 does not work . I need to be able to find a way to have it auto set to look for the latest version live on the internet.

Hi,
This could help you: [https://support.mozilla.org/en-US/kb/Managing%20file%20types#w_changing-download-actions Changing download actions]

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

Version management for Purchase order

Dear Friends,
I am implimenting version management for Purchase orders.
Under version management(IMG) ,set up change dispalys node--
following fields are available.
Ex:
Doc type-- ZCO,NB
For item view fields:
Field nameEMATN(material),TableMEPO1211--material field in Item over view
Field nameMENGE(Quantity),TableMEPO1211
For Header level fields:
Field nameZTERM(payment terms field),,TableMEPO1226
Category--A or B for selection of change documents
No out put--if i tick it concern field will not included in change doc
Version--what is the purpose
Please suggest me
1) we need enter the all the field names in the item over view and item details and Header level fields as given above ,is it correct.
2) And with regard to Table, do i enter for Header level fields-EKKO or MEPO1226 which is available in F1 under techinical information,
for item level fields,shall i enter table name-EKPO or MEPO1211as dispalyed in the F1 under techinical information.
3) I need to enter all the fields existing in the purchase order
4) All these fields and data is to be entered for every document type NB and ZCO.
5) After changes are made in Purchase order,first time on saving the PO,version is creating automatically,
second time,if we do changes, version is not creating on saving the purchase order,what configuration needs to be done.
Please suggest.
Regards,
Magana

Also tell me the use of *Display of change documents in PO*.
It will display changes made both in item & header.It will help you to audit all changes made in p.o after it is raised.
In version management not all changes can be ameneded as seperate versions
only critical changes like price revision,quantity revision.

Version management in RFQ not working

i have configured the version management for RFQ. When i create a RFQ, version 0 is not completed. even though i can maintain quotation and as well as create a Purchase order. system does not throw any message that purchasing document version is in process as we have in PO. Kindly guide me.
Johi Kapoor

No i dont want version 0 to be automatically ticked as completed. client want to manuals tick the version. client requirement is verion 0 is not ok, why the system is allowing to maintain that quotation or allowing to create a po with reference to that rfq.
need any settings for this.
Edited by: Johi Kapoor on May 19, 2011 6:21 AM

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

NO Version Management in SAP BPC-is it in SAP BPC7.0 NW AND/OR SAP BPC70 MS

All,
As far as I know SAP BPC doest not have versions management. How you guys out there handle version management for SAP BPC. Do we have VM on SAP BPC 7.0 NW?
Why there is no VM in BPC. Come on convince me : - )
Thanks,
SK

Guys,
What is the verdict on Version Management being there in BPC? Can you (Saquib or others) give an example as to what Version Management functionality you might be looking for?
From the little I know, when you are doing software development through lifecycle (in SAP it would be called Transport strategy) management, you promote different changes in the target system and hence SAP has an implicit version management. I am assuming that BPC 7.0 NW version would have that automatically since it is promoted through transport strategy only. Are you referring to the same thing as version management or is it something else? But I also read somewhere that only appset is promoted through transport and not sure if each and every component is part of that.
Please enlighten with your insighs.
Thanks.

BI 4.1 Version Management - Change copy of version name

Dear Experts
I wondered if there is a possibility to change the "get copy of version" name of a Web Intelligence report.
When there is the need of changing a report I make the changes and I click on "Checkin" to ensure that the latest version of the cms is under version control. Now often the newest report is not the report currently used by the customer because the newest version has not been tested yet for example.
Therefore it is necessary sometimes to promote an old version of this specific report. I then click on history and choose the desired revision number and finally click on "Get copy of version". This action provides a report out of version control which can then be promoted accross the systems. The problem now is that the filename ends with a string containing something like "<reportname>(Copy of Version 2 @ 2014/06/11 11:41:24)".
Is it possible to change this string which is beeing automatically added to the filename? For example to "<reportname>_<revisionnumber>". Or even better: Are there any other ideas to handle the version management in interaction with promotion management?
Thank you
Lars

At this time you cannot change the name automatically. You can suggest an idea in idea place.

Manual selection production version during order creation

hello!
i have setup production orders that during order creation the production version has to be selected manually. this works fine in CO01 and CO40. but in CO41 the production version is determined automatically - where would i change that setting?
best regards,
matthias

Dear Matthias,
In my understanding it is not possible in standard SAP.
If you have manual selection of production version and if you have set the BOM selection method as 2 in
MRP 4 view of the material master then,
1.If you create a production order manually then the system displays the pop up to select a production
version.
2.If you are converting the planned order into a production order then it picks up the one which is
present in the planned order.So obviously if 2 production versions are there with same lot size and
validity dates,then the system picksup the first one only during MRP run.
Even if it picks up the first prod.version in planned order,but while converting click on master data and
change the production version if required.
3.Otherwise what you can do is set the production version in MD61 itself ,so that its going to be
considered during MRP run and same will be included in the planned order.
Check and revert back.
Regards
Mangalraj.S

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 - Automatic creation on vew version

Similar Messages

Maybe you are looking for