New

Release codes are displayed incorrectly in ME52n, ME53n & ME54n or ME22n, ME23n & ME29n

MM/P2P

Ayhan Akkaya

Thursday, 04 October 2018

1 Replies

5.7K Visits

Votes

Undo

1635346 - Issues with release strategies in purchase requisitions/purchase orders

Symptom

Release codes are displayed incorrectly in ME52n, ME53n & ME54n or ME22n, ME23n & ME29n.
Incorrect statuses are assigned to already released codes in Purchasing documents
Already released lines have to be released again..

ME52n, ME53n & ME54n or ME22n, ME23n & ME29n

PO Release Strategy

Release Strategies

◦Release codes are displayed incorrectly

Ayhan Akkaya

6 years ago

#15

Accepted Answer

-1

Votes

Undo

Environment

Materials Management (MM)

SAP R/3

SAP R/3 Enterprise 4.7

SAP ERP Core Component

SAP ERP

SAP enhancement package for SAP ERP

SAP enhancement package for SAP ERP, version for SAP HANA

SAP S/4HANA
Reproducing the Issue

In transaction ME53n go to the release TAB to view the release statuses of a Purchase Requisition

In transaction ME54n go to the release TAB to release a Purchase Requisition

In transaction ME23n go to the release TAB to view the release statuses of a Purchase Requisition

In transaction ME29n go to the release TAB to release a Purchase Requisition
Cause

This issue is caused when you make a change to a release strategy that is already in use.
Resolution

You must absolutely avoid changes to release strategy customizing once the release strategy is in use. Please read question 6 of note 365604 about this.

If you have to introduce such a change you should do as follows:

make sure all of the old purchase requisitions have been released.

create a new release strategy with the copy function and extend the new release strategy as required

don't delete the original release strategy

This way the open purchasing documents will be unaffected by the changes.
Keywords

Release strategy, T16FC, my_hierarchy, FRGZU, ECC Freigabestrategie , inconsistent

Product

Product or Product Version
SAP ERP Central Component all versions
SAP ERP all versions
SAP R/3 Enterprise all versions
SAP R/3 all versions
SAP S/4HANA all versions
SAP enhancement package for SAP ERP all versions
SAP enhancement package for SAP ERP, version for SAP HANA all versions

References

This document refers to

Number	Title
365604	FAQ: Release strategies in purchasing

This document is referenced by

Number	Title
2445131	[WEBINAR] Identify and resolve common issues in Release Strategies for Purchasing Documents

Attributes

Name	Value
Other Components	MM-PUR-PO Purchase Orders
Other Components	MM-PUR-REQ Purchase Requisitions

Ayhan Akkaya selected the reply #15 as the answer for this post — 3 years ago

Ayhan Akkaya

6 years ago

#15

Accepted Answer

-1

Votes

Undo

Environment

Materials Management (MM)

SAP R/3

SAP R/3 Enterprise 4.7

SAP ERP Core Component

SAP ERP

SAP enhancement package for SAP ERP

SAP enhancement package for SAP ERP, version for SAP HANA

SAP S/4HANA
Reproducing the Issue

In transaction ME53n go to the release TAB to view the release statuses of a Purchase Requisition

In transaction ME54n go to the release TAB to release a Purchase Requisition

In transaction ME23n go to the release TAB to view the release statuses of a Purchase Requisition

In transaction ME29n go to the release TAB to release a Purchase Requisition
Cause

This issue is caused when you make a change to a release strategy that is already in use.
Resolution

You must absolutely avoid changes to release strategy customizing once the release strategy is in use. Please read question 6 of note 365604 about this.

If you have to introduce such a change you should do as follows:

make sure all of the old purchase requisitions have been released.

create a new release strategy with the copy function and extend the new release strategy as required

don't delete the original release strategy

This way the open purchasing documents will be unaffected by the changes.
Keywords

Release strategy, T16FC, my_hierarchy, FRGZU, ECC Freigabestrategie , inconsistent

Product

Product or Product Version
SAP ERP Central Component all versions
SAP ERP all versions
SAP R/3 Enterprise all versions
SAP R/3 all versions
SAP S/4HANA all versions
SAP enhancement package for SAP ERP all versions
SAP enhancement package for SAP ERP, version for SAP HANA all versions

References

This document refers to

Number	Title
365604	FAQ: Release strategies in purchasing

This document is referenced by

Number	Title
2445131	[WEBINAR] Identify and resolve common issues in Release Strategies for Purchasing Documents

Attributes

Name	Value
Other Components	MM-PUR-PO Purchase Orders
Other Components	MM-PUR-REQ Purchase Requisitions

There are no replies made for this post yet.

Submit Your Response

Post this reply anonymously so that others would not be able to see your name.

Attachments
Polls
Location
Links

Upload files or images for this discussion by clicking on the upload button below.
Supported: gif,jpg,png,jpeg,zip,rar,pdf,csv

· Remove

Upload Files (Maximum 100000MB)

You may insert polls into your post. The poll would then appear in the post.

Allow user to vote on multiple poll items.

Vote Options

Add Poll Item

Sharing your current location while posting a new question allow viewers to identify the location you are located.

Cite your Sources with a URL link to help readers verify facts or find more details.

Add Another Link

Release codes are displayed incorrectly in ME52n, ME53n & ME54n or ME22n, ME23n & ME29n

Symptom

Environment

Reproducing the Issue

Cause

Resolution

Keywords

Environment

Reproducing the Issue

Cause

Resolution

Keywords

Bottom menu module

Top menu

EasyDiscuss - Top Members

EasyDiscuss - Most Hit Discussions

EasyDiscuss - Most Likes Discussions

EWM Wiki - Similar Discussions

EasyDiscuss - Welcome