cancel
Showing results for 
Search instead for 
Did you mean: 

purchase order changes

Former Member
0 Kudos

Hi,

presently system is allowing users to make changes in purchase order qty, values even after making of GR or making advances.

how to control that, once GR or advances or partial delivery of qty or partial line items delivered system should not allow users to make any changes in the purchase order qty and values..etc.

suggest the configuration flow for this requirement

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Dear,

Please configure PO release strategy.

If once po is release user can't change it, If he required to change so first unreleased po then made change

Please find below detail for po release strategy.

How to implement purchase order release procedure in sap?

First follow below mention path.

SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.

Three steps involved in release process of purchase order.

1) Edit Characteristic: -

Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP

2) Edit Class: -

After creation of characteristic, create class for release purchase order. In which you can take reference of

Class Type: - 032,

Status: - Release,

Class group: - Release strategy class,

And put reference of your characteristic, which are created by you in first step.

E.g: - Class - REL_PO

3) Define Release Procedure of purchase order: -

In this step four processes involved.

1) Release Groups

2) Release Codes

3) Release indicator

4) Release Strategies

1) Release Group: - In which you can define release strategy group

For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.

2) Release code: - In which you can define release code. Enter value as

Release group: - 01,release code: -01 - Purchase Head,

Release group: -01, release code: - 02 - Auditor.

3) Release indicator: - In this step you have to define release indicator.

Like X - Blocked, I - Under process, S - Release.

4) Release Strategy: - This is the final step for release strategy.

Assign release code 01, 02.

Click on release prerequisites, select 02 - check box and click on continue.

Click on release status button, enter release indicator X, I, S and click continue

Click on classification button, Enter values of purchasing group for which you want to created release strategy.

Regards,

Mahesh Wagh.

Former Member
0 Kudos

HI

You can set up the release strategy and there you find the option, whether changes allowed without unrelease or so but everyboby can not make a change in the PO.

Regards

former_member192897
Active Contributor
0 Kudos

The Possible Best solutions are Configuring the Release Procedure or Version Management for Purchase Order Relevant Fields.

Regards,

Ashok

deiva
Active Contributor
0 Kudos

Hai,

You can control this by activating release strategy or work flow method.

Former Member
0 Kudos

Hi,

Presently we are using purchase order release strategy. could u please explain me how to use this fields control for not changing by user after making goods receipt or having subsequent transaction.

former_member192897
Active Contributor
0 Kudos

If you have Configured already Release Strategy for Purchase Documents Just Set Release Indicator as 01 and save.

From Next time Once Purchase Document is Released System Will not allow any one to Change anything and throw an error called Document already Released, No changes possible.

Regards,

Ashok

Former Member
0 Kudos

Hi,

It's working fine.But, in case where genuine case how to handle.

if purchase order has 5 line items, user had taken goods receipt for 3 line items and rest of items during goods receipt found that purchase order prices need to be changed as per approval.

In this case system is not allowing any changes/me22n transaction. how to handle these kind of scenario.