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.

Similar Messages

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

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

Steps for configuration of version management

Dear Experts,
Kindly tell me what is meant by version management and under which situation this will be used and how its impact in MM after configuring this. Kindly let me know the configuration steps for version management.
Regards,
Prasath

You make the settings here for activating the version management:
SPRO --> MM --> Purchasing --> Version management --> Set up version management for PR -->here make the settings and tick on the activate indicator...
Now define the relevent fields which shd go under version change:
SPRO --> MM --> Purchasing --> Version management --> Version relevent fields of PR's
If you wanna set up change displays and its output, then make settings here:
SPRO --> MM --> Purchasing --> Version management --> Set up change displays...
NOTE: You can only release this PR fully if you tick the version completed indicator in the PR document...
Similrly you can activate for Purchase order
spro-mm-purchasing-version management-purchase order

Unable to change gl account in purchasing document rows of item type(8.8 ve

Hi all,
In previous sap b1 version ,in purchase document rows of item type -- system allows to change the gl account in rows.
But in current 8.8 it is missing ,can any one know how to activate this or is there any logical reason to lock this.
Regards,
Naresh K

Hi Chandra,
In some older version this was possible. This was changed as this is the stock account to avoid usage of incorrect account and valuation report issues.
If you want a specific stock account for the item change you can define that on the item master data. Set it to Item Level and then change the GL account.
Hope it helps,
Jesper

Solution for printing of Purchasing Documents in SAP with version managemen

Hi experts,
We found that the standard solution does not meet the following requirements for purchasing document
1)     The print for the latest version of the document does not contain items unaffected by change. It requires printing of whole document with all items, but with version number and highlighted changes.
2)     The standard solution cannot highlight some of the changes which are not captured by version management like text changes, target value and Contact (Purchasing Group) in header, text changes at item level, etc.
3)     The standard solution can be used to reprint the whole PO without version management but that cannot highlight the changes specific to the version for which it is printed.
If any solution which can meet the requirements specified above, please let us know <removed by moderator>.
Thanks in advance.
Edited by: Thomas Zloch on Mar 30, 2011 9:39 AM

Ok.
I have already done with SPRO configuration.
MM->Purchasing->Version management->
It has implemented ECC 6.0. The version management has been activated for Purchasing documents. The standard printing solution for printing of these documents (PO, Outline Agreements and RFQ) print these documents with changes made in the latest version. Any item which is not changed in the latest version does not get printed.

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

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

Hi Experts,
We have activated Version Management for Scheduling Agreement - LP. When we create a Scheduling Agreement, it is generating zero version but 'Net Order Value' is showing as zero in versions tab. We have also addressed fields 'NETPR' and 'NETWR' for document type - LP, in Set up Change displays.
Can any one please suggest a solution for this.
Thanks in advance.
Regards,
Sree

Hi Experts,
Any advise on this isuue?
Regards,
Sree

SRM Manager to Display/Edit Purchasing Document

Hi All,
We have configured SAP SRM 7.0 with PPS so that an end-to-end process starting from creating Shopping-Cart until Invoice can be performed successfully.
We have user called: BUYER, and MANAGER. Each of them able to perform end-to-end scenarios.
But until now, we cannot make MANAGER to display/edit any purchasing document such as Shopping-Cart, PO, Contract that is created by BUYER.
We have tried to put all available PFCG roles & portal roles to MANAGER which make MANAGER a super-user. But still, MANAGER cannot see BUYER's document.
We refer to the following URL for PFCG roles & portal roles:
http://help.sap.com/saphelp_srm70/helpdata/en/d7/4b8a5e1b324584a4aa16281f071a0a/frameset.htm
Does anybody have solution for this?
Thanks before.

Hi! About SC's, the only roles that are able to access SC from other users are:
Approver: only when the SC is awating approval;
Admin: through the monitor.
I hope this clarifies.
Best regards,
Christian Zeuch

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.

Free Goods Purchasing in contracts (agreements)?

Hello Gurus,
I've seen that a Free Goods configuration is possible using Info Record fields (Info record category,...).
Is it possible to use these conditions in the contracts (ME33K)??
Thanks!
Marc

Hello Ramesh,
Again, many thanks for this. I think I'm close to understand the solution.
However, I have still few questions please:
1.- If I select the PB00 as you say, then I go to 'Extras/Free Goods the system guides me to the condition record change (TC MBN2). Is this correct?
2.- Where will I be able to see the NR00? Will it be directly in the Purchase Order?
3.- If the NR00 condition can not be seen in the contract (ME33k) conditions, where can I see that the Free Goods is correctly set up for a concrete contract?
4.- Is it necessary to link the Group for Calculation Schema (Purchasing Organization) to the Procedure for discount in kind determination (NR0001) in the customizing? IMG/Material Management/Purchasing/Discount in Kind/Define and Assign Discount-in-Kind Schema/Determine Free Goods Schema
Thanks!!
Marc

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 (purchasing document pr,po, contract,agreement)

Similar Messages

Maybe you are looking for