Document Version management

Hi ,
can any body suggest me , how we saved different version of document in document management (Enterprise Portal).where it will saved.
Its urgent. please help ..
Thanks

Hi Rashmi,
If you would like to look at versions.Please go to details-Settings-Versions.
You would be able to see the versions only if you have enabled the version control feature.
Furthermore,if you would like to look at the versions in the backend go to KM-Content-Documents-systems-Versions.
Hope this helps.
Regards
Ajey

Similar Messages

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

Version management (purchasing document pr,po, contract,agreement)

dear mm gurus,
as per as i know all the changes made in the purchasing document can be tracked through display document> environment> item/header changes.
So whats the advantage of implementing Version Management?
Is it capture some changes which is not captured environment--> item/header changes.?
Please help me in this regards.
regards,
atanu dinda

Refer to this thread
Version Management
Rammohan.

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

Purchase order version management

Dear All.
             I have configured the purchase order version management.
but at the time of change ppurchase order i have changed the text field for that also new version is triggered. i want to control this if only qty and price and payment terms change only version management should trigger. is it possible through standard please tell me the config steps.
Regards
Kumar.

Data output category
    Indicates the data output category to which the relevant field belongs.
Use
    You can assign a character to related fields. You can then use this
    character to select the fields in the application.
    Note
    SAP recommends you use only the folloiwng characters: a-z, A-Z, 0-9.
Example
    You wish to obtain a quick and straightforward overview of changes
    involving the material, order quantity, and price. This information is
    particularly important to you. You therefore assign the character A to
    these fields.
Indicator: no output
    Indicates whether the field is included in the display of changes.
Use
    If this indicator is selected, the corresponding field is not included
    in the display of change documents.
Example
    You have selected the indicator for the Requester field. The content of
    this field is then changed in the purchase requisition.
    Result
    The changed field is not included among the changes that are displayed.
Indicator: No output in case of versions and buyer approval
    Specifies whether or not the field is to be included in the display of
    changes for a version.
Use
    If this indicator is selected, the relevant field will not be included
    in the display of changes that you can invoke via @II@ on the Versions
    tab page.

Document versions in external repositories

If Im using an external document repository liked with the portal (DMS, File System, etc), can I still use document versioning control? Where are the versions stored (in KM or in the external system)?

Hi Guest,
I am quite sure that if you use an external document repository you can only use the features provided by the external repository. If the external repository provides document versioning and the repository manager used to integrate the repository in the KM repository framework does implement the functionality then you may be able to use document versioning.Otherwise, not.
Hope I could help!
Best regards,
Martin

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

Activate PO Document Approval Manager

Cold anyone please tell me how to activate "PO Document Approval Manager" in OAM in 11i as i just received this request from my functional guy?
Thanks
J

Pl post details of OS, database and EBS versions.
Using the System Administrator responsibility, navigate to Concurrent --> Manager --> Define, query up "PO Document Approval Manager", then click the "Work Shifts" button and set the "Processes" field to an appropriate value, and save.
In R12, the functionality of this manager has been changed significantly.
How To Plan The Number Of Processes Required By PO Document Approval Manager After R12 (Doc ID 735474.1)
HTH
Srini

PO version management - view history version

Hi expert,
I'm using PO version management together with change PO output.
1. Is there a way to pre-view or re-print a certain history version of the PO output? currently only the last version can be previewed and I got error message when I try to reprint hisotory version (no printed relevant changes).
2. When I change the PO, a new version is not created until I save the PO. I have to come to the change mode again to mark it "complete". Is there a way to have the new version available before save, so I can make my changes and mark it completed right way.
3. Is there a standard SAP report shows incompleted PO versions? I need to run it to remind me of the PO's that I still need to work on or to mark completed.
Thanks a lot for your kind help!
Regards,
Jully

Hi Jully,
You can try the following link :
http://www.sap-img.com/mm001.htm
It is an ABAP program contributed by one of the SAP members, which reports all the changes made in PO and list out the details per document.
Take the help of your ABAP consultant to run for you.
See if it helps.
Best regards
Amit Bakshi

Version Management for PO Fields

Hi,
Curently System is capturing the Version
Management for PO with Fields, Incoterms, Total Net Order Value, Value Changes, Currency, Deletion indicator in purchasing document & Purchase order quantity.
But the Requirement is to capture(display) only the Incoterms, Deletion indicator in purchasing document & Purchase order quantity.
How to filter the other PO Fields in Version Management- Total Net Order Value, Value Changes & Currency.

Thank for ur smart reply...
Here the Requirement is in Purchase Order to capture(display) only the Incoterms, Deletion indicator in purchasing document & Purchase order quantity.
And to filter the other PO Fields in Version Management- Total Net Order Value, Value Changes & Currency.
But you had given the suggestion for PR. psl guide me how to do this process for PO process.

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 management for DMS

Dear all;
I have attached one document say Drawing with REV 0 in DIR ,Now I want to replace the Old drawing with latest revision say REV R1 at same time I dont want to replace the old REV 0 .How to solve this problem with version management In DMS in application as well as in SPRO.
Thanking You;
Regards;
Joydeep Mukherjee

Hi Joydeep,
Trust you are looking at versioning of the originals/documents in a DIR.If yes,then 'content version' feature must be enabled in DC 30 transaction.Path is SPRO > CA components > DMS > General Data > Define Workstation Application. Herein,select the required workstation application and check the 'content version' field.
To test,check out a original/document in a DIR and check in with changes as a new version.You will have the previous as well as the current version original/document available.
Regards,
Pradeepkumar Haragoldavar

Version management for external purchasing

Hi.
We activated the version management for scheduling agreement. But the problem is when we save the document it took the netpr ( Value) Zero. and also when we create new version i.e ammedment of price the it create one new version with zero value,
Can any budy suggest me why it took the zero value?
Thanks
Prashant

Got it

Version Management for SD

Hello All,
I need to maintain Version Management for SD. My client's requirement is whenever they change Quotation or Sales order they get version number.
E.G
Quotation Created -
> 10
Change Quotation -
> 10.1
Change quotation again -
> 10.2
just to remember the purpose of changing Quotation . Is it possible to do in SAP SD.
Regards
SD1000

Query 1. Working with quotation version
Generally, version for sales order is used for SAP Mill Products.
So to have that functionality for your quotation.
Configuration
- Copy Standard sales doc type for VSH1 for sales version doc to create version doc for Quote, say, ZVQT.
- and all coresponding configuration which is requiored for introducing a new sales doc like allowing sales doc for desired sales area, number range, Item catergory determination similar to that of Quotation item category determination, pricing, copying control from QT to ZVQT and vice versa.
- Configure Sales Order Versions
To do this follow following path in SPRO
IMG - SD - Sales - Sales Doc - Sales Order Version - Configure Sales Order Versions
Here, you assign Sales Doc QT to the version sales Doc ZVQT
Process
1. In sales order (VA02), in menubar go to Edit - Additional Functions - Version Data - Transfer
2. This will create a new document for ZVQT as a new version with reference to our original Quotation (QT) with item data.
3. We can make changes in our version document (ZVQT).
4. Once we confirm the changes, we can copy the version to our original Quotation.
5. Further multiple verisions of the quotation can be created and compare the same.
Query 2. Bill of Material - LUMF
I hope your item cat determination for LUMK is
Sales Order
- Item Cat Group
- Higher Item Cat
- Def Item Cat
OR
LUMF
TAP
OR
LUMF
TAP
TAN
So, if you are using TAP as higher Item Cat.
Then you need not worry on pricing at the higher level,
As, Item Cat TAP is not relevant for pricing.
Thus, that item has Statistical relevance.
Regards
JP

Document Version management

Similar Messages

Maybe you are looking for