Version Management activation for RFQ

Dear all,
We have done all the settings for version management activation in RFQ, But it is not working.
Can somebody guide me the steps?
Thanks,
Samir Bhatt

hi
just check the following settings
spro>Materials Management>Purchasing>Version Management>Set Up Change Displays
here check which fields u took in account for version changes

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

Open Item Management activation for GL accounts in ECC 6.00

Hi Experts,
There is an issue about Open item Management activation for GL line items of FBLL03 for VAT GL code. Unexpectdly do not check the open item management in VAT GL account Master record while created the GL master record in 2007. Now we activated Open item Management in GL master record for same GL to nulify the balances with setoff account and same reversed after activation. Now issue is how it is possible to activate Open item Management for previously posted documents ? Is there any standard SAP Program for ECC 6.00 Release SAP _APPL 600.
Please revert.
Best Rgds
SumaMani

Hi PVC,
I got below mentioned message while execute the suggested program in SAP.Please suggest
Do not use the report program to set up open item management for the
account.
Create a new account with the correct account assignment. Post your
items to the new account. If you want to use the original account
number, you must bring the account balance to zero, change the account
assignment, and repost the items. You can remove the old items by
archiving the documents.
Best Rgds
SumaMani

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 Enabling for PO

Dear All,
I want to do Version management for the below scnarios and fieldsm, how to do this, plesae help.
PO - " Version" to be implement while change in PO.(like price,text,payment terms,tax code,addition in line items etc.)& output print should come "Amendment Purchase order".
Please revert can this done.
Also let me know the path ion IMG to achive this.
Regards,
Nagaraj S

Hi Jeyakanthan.
Thanks for your valuable answer.
It is not working, i have enabled the VM as mentioned by you, but it not asking any version change.
As the option given for PR(Version Relevant Fields for Purchase Requisitions) to get version trigger for required fileld why can't we make for Purchase Order.
Please help me out is thr any wayout we can get so we can do this.
Regards,
Nagaraj S

Version management tool for Eclipse Juno / fiori apps

HI All,
We have working with fiori apps. We are using Eclipse Juno. I was wondering what would be the best tool for version management.
THanks for your suggestions,
Gopi

Hi Gopi,
yeah, that's right. When your eclipse recognize a git repository, you can't use the share-functionality of the Team-Provider plugin. But there's a little trick to use it, even if you have a git repo.
Just right-click on your git-project in eclipse, go to "Team" and click on "Disconnect". After that, you can share your project via Team-Provider plugin. The problem with this approach is, that you always have to work with the console or git-bash, when you want to execute git-task.
Sry, i have no experience with NWDI. The only thing i can say is, that it should be no problem to work with multiple people on a project based on git. You can work with a central repo or with a decentralized (beacuse git is a distributed version control system).
Regards
Michael

Version Management for BW queries?

Hi,
Is version management available for queries in BW?
Like an ABAP program, different versions can be generated, allowing an older version to be retrieved and overwrites current version, for the case where heavy changes applied but has to be reverted. And also the function of comparing versions to easily identifying the differences.
Thanks.

There is no version management for queries built into BW. Of course, you can generate new versions of queries each time you change them by doing a "Save As...", but we have found that this is counterproductive for several reasons, including:
1) Extra Query Maintenance - Leads to multiple copies of a query, and eventually confusion over which one(s) are supposed to be used and which one(s) are "obsolete".
2) User Favorites Maintenance - Any favorites that have been created by users will have to be recreated from scratch using the new query and/or workbook.
There are probably others...
Anyway, #2 is the one that finally convinced us to stop creating new versions of queries. Instead, we do considerable testing of any changes on our Dev and QA systems before finally replacing the Prod copy of the query. Of course, "backing out" changes is still a pain this way, but at least you have the original query on Prod to go by. For really major changes, we will also generate "Before" and "After" XLS files with results, both to prove that we are getting the expected results and to serve as a way to go back if the Prod query has been updated before a problem is discovered.
Hope this helps...
Bob

BDC for Me22 Tcode-Version Management

Hi ,
I want to add the version management in for exiting BDC in ME22 Transaction in ECC6.0
How can i go for that.
please help me .
regards,
Ajay
Edited by: Ajay reddy on Sep 16, 2009 3:26 PM
Edited by: Ajay reddy on Sep 16, 2009 3:38 PM

Hi,
Thanks for attempt the Question.
Me22-> Enter Order number-> Go to HEADER> VERSION.
Can I handle the Menu option in recording..... Please help me in this.
regards,
Ajay
Edited by: Ajay reddy on Sep 16, 2009 3:47 PM
Edited by: Ajay reddy on Sep 16, 2009 3:50 PM
Edited by: Ajay reddy on Sep 16, 2009 6:52 PM

Version management(Purchasing)

Hi All,
         please clarify the Use of version management,what&why and when it is required?
         please explain briefly process....like
         set up version management for
        1. PR's and Externanal Purchase documents
        2. define reasons for change,what are the reasons
        3. set up change displays
        4. version relevent fields of PR's, why not for Purchase orders
   thanks in advance
Thanks&regards
Venkate

Hi,
SPRO > MM > Purchasing > Version Management
- Set Up Version Management for Purchase Requisitions
In this step, you set up the Version Management facility for purchase requisitions.
For a combination of document category and document type, you can:
Activate Version Management: - If Version Management is active, the changes made to a purchasing document are managed in versions.
Set up field selection for versions: - For certain fields of the version, you can specify which properties they are to to have: mandatory entry, optional entry, display only, suppressed.
Note: - When a purchase requisition is created externally (e.g. via a BAPI), the system does not check whether these fields have been designated as mandatory-entry fields.
- Set Up Version Management for External Purchasing Documents
In this step, you set up the version management facility for external purchasing documents.
For a combination of purchasing organization, document category, and document type, you can:
Activate version management: - If version management is active, changes to a purchasing document are managed in versions.
Define field selection for versions: - You can specify the attributes certain fields of the version are to have: mandatory entry, optional entry, display only, field suppressed.
- Define Reasons for Change
In this step, you can define the reasons for changes to requisitions and external purchasing documents (e.g. increase in material requirement).
- Set Up Change Displays
In this workstep, you can specify whether and in which change displays (e.g. for version via @II@) a certain field is to be displayed.
- Version-Relevant Fields of Purchase Requisitions
In this step you can specify whether changes to a field are version-relevant. ("Version-relevant" means that a change to a field causes a new version to be created.)

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

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 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

Version management for PO

Hi,
If I create a PO & save, then i will add a freight condition in PO, will it be activated in version managment.
Also can we configure the fields which we want for triggering the Vesrion management.
Pleae suggest.
Thanks
SHP

Hi,
[Version Management| http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/60b43bb7492147e10000000a114084/content.htm]
In the case of procurement transactions extending over a longer period of time (for example, in the procurement of capital goods), you may need to differentiate between various versions of the purchasing document. You may also need to refer to one particular version when corresponding with the vendor.
The Version Management facility enables you to generate and manage versions of purchase requisitions and external purchasing documents such as POs. A version groups together the change documents generated in the course of subsequent processing of the relevant document. A version thus indicates the revision level of a document (version 0 = original document, versions 1 + = revisions) and provides the user with an overview of the various changes that may have been made in the course of time.
Version Management thus represents an extension to the hitherto existing change documentation functionality for internal and external purchasing documents.
Version Management can be used in connection with purchase requisitions (ME51N, ME52N and ME53N only), RFQs, purchase orders, contracts, and scheduling agreements.
The following prerequisites must be satisfied before a version of a purchasing document can be deleted:
The changes made in the version must have been reversed (cancelled, revoked)
All open messages must have been deleted
CONFIGURATION:
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.

Version mgmnt for RFQ and PO

Dear gurus,
pls explain about version management for RFQ and PO
pls explain in detail

SPRO > Material Management > Purchasing -> Version Management .
After activating version management you can see the Version tab in ME53N near to source of supply tab in PR.
http://help.sap.com/saphelp_srm30/helpdata/en/46/882fdd8bfc1743bd5ef8b532f94402/content.htm
SAP Enterprise Buyer provides you with version management for purchasing documents. As a first step, you can display versions of purchase orders and contracts.
The system creates a version in the background if you, as a purchaser, carry out one of the following actions:
· You change a posted purchase order
· You order a posted purchase order again
· You change a contract that has already been released
· You release an already released contract again
In contrast to the change documents that retain a change history, a version displays the status of a document at a specific point in time.
Version management provides a check for you as a purchaser, for example, if you wish to display a purchase order in the form in which you transferred it to the vendor on day X. A version provides clarity, for example, in negotiations on a contract.
Features
You can use versions as follows:
· Display
· Compare and list differences in tabular form. The comparison result has separate areas that can be displayed:
Header data (including organizational data, tax and payment data; partner data and documents)
Item data (including taxes and limits if they exist; partner data, documents; account assignment and conditions)
· Archive, if it relates to transaction data (you can archive versions of purchase orders, but not contract versions)
You cannot change or output versions. This is only possible for the active document.
Also, visit the following thread:

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 activation for RFQ

Similar Messages

Maybe you are looking for