Purchase Requisition - Version Management

Hi,
I have activated version management, on any chnage in releaseed status in PR lead to new version update.
Once you complete the version system retriggers the relese strategy.
My question is do we have any standard message which will ask us to complete version on amy change and then allow to save the chnages.
Loking forward your quicjk reply.
Thanks,
Charu

Hi ,
But even if i make the fiels for reason mandatory, completion indicator is not required.
My requirement is for completion indicator.
Thanks
charu

Similar Messages

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.

Purchase Requisition version

Dear all,
could you help me on this question?
i want to keep the PR date & Requirement date fixed under all activities in project builder, but whenever i do the scheduling or in thing like addition of new activity & then go to save project builder system shows some networks having costing error.
When i checked PR under that particular network in ME53N some of them shows new version created.
but the fact is these dates will change unexpectedly.
when i want to save the dates of all activities, i create the Purchase Requisition version. could you explain it in details?
Please do the needful as soon as possible.
thanks a lot.
Rakesh

Hi,
I think you creating network activities... you have scheduled the project...... materials you have attached to activity..... you have created material POs with Network account assigned (consumption)
or PR through Projects directly.
in this scenario requirement date of materail may be copied from start ( eirliest/ latest) or finished ( eirliest or latst), whenever you schedule the project system updates the date & same dates will be copied to material requirement date, if you maintain requirement date manually then scheduling will not affect the requirement date...
so this is completely depend on scheduling & requirement date...
I hope this will help you...
In case of error in cost - that is nothing to do with scheduling
just check activity cost calculation ( based on work center & activity type)
Venkatesh

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

Purchase Order Version Management / Amendment Number

Hi All,
Can anyone help with the following......
Everytime we re-print a Purchase order the amendment automatically increases.
For audit purposes we have to identify every change to a PO but we do not want to have to document hundred of re-print every year.
Is there a way of controlling what justify's a changes or what triggers the amendment number to increase?
We basically want the amendment number to increase if the Po has been changed but not if we are simply reprint the document.
Many Thanks in advance, points will be rewards immediately.
Chris

Please check these helpfull links:
problem with PO amendment
po amendment
For better answers, please post your query in ABAP forum.
Edited by: Afshad Irani on Jun 3, 2010 2:42 PM

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)

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

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 Requisition Item Version Completion

Dear Friends,
In a purchase requisition line item, In the version tab when the version check box is newly ticked, I want to capture that change. I tried to use get_datax method of IF_purchase_requisition _item in the line item check user exit. but the structure doesn't have the field. please let me know is there any way to find out if this field is changed newly.
Thanks & regards,
sudhahar R.

found myself.
Thanks.

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 of Purchase orders

Hi,
In the version Management for the perchase order can anyone tell me what is the use of following:
Materials Management - > Purchasing-> Version Management-> Set Up Change Displays

Hi,
In this work step, you can specify whether and in which change displays.
(E.g. for version via @II@) a certain field is to be displayed.
In ME22N or ME23N, under Version tab, once you click on "Display Changes" button then system will display you the changes of the those fields only which have been defined in this step.

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.

Manage Purchase requisitions

hi
To manage Purchase requisitions and to effect a stock transfer from DC (texas) to customer location (florida) what are the config setting I do in SNP
That is florida customer is purchasing directly from texas.
Using /SAPAPO/TL I can create a transportation lane.using source and destination fileds.that much I know ,what should I do in SNP1 and SNP2 tab in MAT1.? And what should I do in product location screen ,there I find a procurement tab there ..what config should I do there.if you have tried a similar SNP task before please share with me.I will try at my end according to my scenario.basically a stock transfer should be effected from texas to florida for a price.that is the crux of the matter
thnaks

that is i am using SNP hiuristics ...rite...now when i run SNP hiuristics it should create a procurement type of category stock transfer...and that stock transfer has to moved to a location at lower cost (cost settting has already been made by previous implementor...now it is a re-implementation project) in the SNP hiuristics screen we have one tab called "network " the client says once i press that SNP hiuristic network label ....ST should occur automatically...ie there should be zero manual intervention ..all automatic...once MC90 release happens to SNP..SNP hiuristic should take care of everything....demand is FC demand and customer demand .....SNP should handle customer demand seperately and FC demand seperately....i agree my question is broad..it is best you please suggest some links that carries screen shots....that would be a grt help to me mani

Version Management with Requisition

Hi,
We have activated version mangement for requisitions. Some of our requisitions are not routed through approval process.
Version management is working with requisitions not related to release strategy.
But version management is not triggering requisitions with release strategy.
Please advice.
Regards,
John K.

Thanks for your quick reply.
Yes, we checked Version Completed check box and selected the reason for change also.
In config we set version will trigger for quantity, account assignment, price, delivery date and short text. But PRs subject to release strategy is not triggering next version (for example Version 1) always on Version 0.
Please help.
John.

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.

Purchase Requisition - Version Management

Similar Messages

Maybe you are looking for