cancel
Showing results for 
Search instead for 
Did you mean: 

PR is de-released after change of purchasing group through MASS transaction

former_member1283268
Participant
0 Kudos

Dear All

Whenever I run MRP planned order is created.This planned order is then converted to PR.This PR is then released finally.Fiinal release indicator is having changeability option as "1" i.e. "Cannot be changed".After final release through MASS transaction purchasing group of PR is changed.After changing the purchasing group when I display the PR again it has completely de-released.Purchasing group is not part of my PR release strategy.

Why the PR has completely de-released after purchasing group change through MASS transaction???

Regards

Satish Kumar

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member1283268
Participant
0 Kudos

No solution.

former_member201758
Contributor
0 Kudos

Hi Satish,

I suggest you log this problem with SAP thru the service market place. They would log into your system and help you.

thanks,

Sanjeev

former_member201758
Contributor
0 Kudos

Hi,

I think you need to watch your changes thoughly.

A reset of the release strategy only takes place if

- the changeability of the release indicator is set to '4' in

case of a purchase requisition and '4' or '6' in case of

another purchasing document (purchase order, request for

quotation, contract, scheduling agreement),

- the document is still subject to the previous release

strategy,

- the new TOTAL NET ORDER VALUE is higher than the old one.

The total net order value is linked to CEKKO-GNETW for a purchase order,

CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT

for a purchase requisition overall release.

If you have maintained a Tolerance for value changes during release

(V_161S-TLFAE), the release strategy is reset when the value of the

document is higher than the percentage you have specified and if the

document is still subject to the previous release strategy.

In case you see any voilation to this, please report this problem to SAP support.

thanks,

Sanjeev