Version management

[Former Member]

Dear Experts,,

I am creating a PO. Release strategy is active. Then released the PO. Made some changes after that the system ask for the Version. Filled required entry in version tab for the same. I ticked version completed also. The n again i made some changes related to price and quantity. this time system did not ask for version management. on the other hand if i release the Po and then made some changes then the system is asking for the version management.

The question is

1. Is version management dependent on release strategy, If active?

If i want to have version for every changes made in the PO (irrespective of release status) what is the solution except user exit / badi?

Regards

Edited by: Kumar SAP MM on May 17, 2011 3:24 PM

[Former Member]

Hi Kumar,

I would like to suggest to check note 664928.

1. Question:

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

2. Question:

You change a purchasing document (request for quotation, purchase order,

contract scheduling agreement). Why does the system not generate a new

version?

Answer:

The system always creates a new version when the purchasing document

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 purchasing document lead to a new

version:

- All print-relevant changes (defined in purchasing Customizing

under -> Messages -> Fields Relevant to Printouts of Changes;

note that the system only takes fields of tables EKKO, EKPO,

EKET and ADRC into account)

- Changes to the document assignment

- Changes to time-dependent conditions

To ensure that a new version is created for a purchasing document, all

messages must be transferred (see also Note 768520).

No new versions are generated for purchase orders on hold.

see also

Note : 978597 Release not reset even when version completed

BR

nadia Orlandi

[Former Member]

Hi,

Version Management is an independent config with release strategy.

No need to go for user exit, for the fields relevant to changes can be specified in Customizing.

MM-Purchasing -Version Mgmt - Set up Change Displays.

Regards,

Bijoy Kumar

[former_member824495]

Version management gets activated only when print releavant fields are changed & outputted (Mail/Printout etc).

If it is not outputted yet, even after release system won't ask for version after amendment of PO.

[asik_shameem]

Hi,

It depends on the fields specified in the config.

IMG->MM->Purchasing->Version management->Setup Change Displays

No need to go for exits, Just specify list of fields (Table & Field) along with the document type which is going to affect the version.

[Former Member]

the fields have already been maintained (Quantity, Price etc), still it doesn't ask for version until unless PO is released.

[former_member329706]

Hi,

Before Posting a thread, have a look for all posted threads there are lot of posts regarding the same.....

Please refer the below wiki link it may help full to you..

http://wiki.sdn.sap.com/wiki/display/ERPLO/Version+Management

BR,

Patil

[Former Member]

I never post thread before searching forums rigorously. I have already gone through this before posting the thread. Still wanted to confirm with experts opinion.

Regards

Pradeep Paliwal