Version Management in Purchase Order

[Former Member]

Hello Experts,

Q.1 >

Firstly whats is version management in Purchase order and why it is used and effect of it on output determination?

Q.2>

My client is currently uses version management for the purchase order. They are using the versions from 0 to 4 say for different reasons under which the amendments are done in PO.When version is created system immediately creates the print out immediately.

. Now my client wants the system to give warning or message or release procedure so that system will not able to create the print out immediately.

I short after saving the version systeme should not print the ammended PO immediately.

Reagrds,

SP

[former_member335885 · Accepted solution]

HI,

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

Thanks & Regards,

Kiran

[Former Member · Accepted solution]

Hi Kiran

is there any relation between the PO output and the Version manage ment . for automatic version activation Po Output Should be mandatory . pls tell me

[Former Member · Accepted solution]

Thanks for replying.

Part two of question is still not answered.

How can avoid the immediate printing of the PO after saving version?

Regards,

SP

[pankaj_singh9 · Accepted solution]

Hi,

Go to SPRO > MM > Purchasing > Messages > Output Control > Define Message Types for Purchase Order > Fine-Tuned Control: Purchase Order > Here delete your message type of PO (for e.g. NEU) with operation "2" (i.e. Change)

And then check.

[former_member581212]

hi

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:

o Activate version management

If version management is active, changes to a purchasing document

are managed in versions.

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

process

spro>mm>purchase>version mang

set up version management for purchasing doc create ur new entry and tick version man active

save come one step behind

below it define reason for change

do it ur version management will be active

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.

Hope it helps...

Regards

Priyanka.P

AWARD IF HELPFULL

[former_member537524]

Hi Priyanka,

I have done all configuration mentioned by you in Development Server and there version management working fine. Moved these changes to Quality server (through TR) & it's not working on Qulity Server. Please suggest what will be the reason.

Regards,

AV