cancel
Showing results for 
Search instead for 
Did you mean: 

Purchase Requisition Cannot be Released

Former Member
0 Kudos

Hi SAP Experts,

Good day!  We have two conditions for a PR release code.  Condition A and Condition B.  As shown below:

Condition A = for PR value <=100,000.00

Release Code 1 - Alpha

Release Code 2 - Beta

Condition B = for PR value >100,000.00

Release Code 3 - Charlie

Release Code 4 - Delta

We configured the release strategy to the ff:

Condition A = for PR value <=100,000.00

Release Code 3 - Echo

Release Code 1 - Alpha

Release Code 2 - Beta

Condition B = for PR value >100,000.00

Release Code 3 - Echo

Release Code 4 - Delta

Changes:

1. We changed the release code 4 description from "Charlie" to "Echo"

2. We added release code 3 in condition A before Release Codes 1 (Alpha) and 2 (Beta).

We tested it in the testing environment and it was successful.

When it was transported in the Production environment, when the user used his id to release the PR, it gave a message "Purchase requisition "XXXXXXXXXX" cannot be released.  When I tried using my id (my id can access all tcodes), it allowed me to release the PR.  May we know what might be the problem?

Thanks,

Matt

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Pls check the authorization assigned to the user, Release code & Release Group. using Tcode SU01

Regrads

Nireesh

Former Member
0 Kudos

Hi Nireesh,

Thanks for the advise.  We checked and authorization object that were assigned.  Thank you everyone for the advise.

Regards,
Matt

Answers (3)

Answers (3)

ajitkumar
Active Contributor
0 Kudos

is the release code attached to the releasing authority with proper activity type?

former_member186100
Active Contributor
0 Kudos

please see if the PR number in message is same as PR number u were trying to release. Check if PR in message is subjected to release strategy. Such message is generally triggered when u open a PR irrelevent to release strategy in ME54n

Former Member
0 Kudos

Did he get this message when he went to me54n right away? If so, make sure it's the correct PR number. Many times it will,pull the last PR # that user touched.

Also check to see if he can release via me55.