Purchase Requisition Cannot be released

Dear SAP Gurus,
While doing ME54N to release PR. System showing the Error 'Purchase requisition cannot be released'.
PR created on 23.04.2009 then PO Created against it , again PR was dereleased now again when going for release of PR system is providing the error as mentioned above.
Message no. MEPO822
<< Moderator message - Everyone's problem is important >>
Thanks and Regards.
Anil Thakur
Edited by: Rob Burbank on Nov 10, 2010 3:52 PM

Hello Anil
During this period any release stratergies changed for pr ? after de release the pr just modified small value and make it same again this is nothing but refresh.
then check the pr release
Laxman

Similar Messages

Purchase requisition report via Release indicator

Dear All,
I would like to know if there is any standard report in purchasing that has the functionality to display purchase requisitions by their release indicator.
Thanks

Hi,
You can use table EBAN wth FRGKZ Field for Release Indicator.
You can t.code:ME5A and click Dynamic Selection and select "Subject to Release" in Purchase Requistion in Application Toolbar and execute to get the report for your PR's.
1.Enter "YES", It will give report for the PR's which are not Released.
2.Enter "NO" ,it wil give report of the PR's which are Released
Regards,
Biju K

Purchase Requisition Creation From Release

Dear PM Gurus,
For Manual material availability Check to work before release, the Purchase Requisition check is to be set to Immediately in SPRO-> Define Change Docs and Collective PR or Activating Pr from Now On from Maintenance Order. The issue is that I want to restrict the creation of Purchase Requisition to Release of Maintenance Order but what is happening is upon saving the Maintenance Order, the PRs for all non stock materials are created and I also want the manual availability check to work before release.
Simplifying above details:
I want Manual material availability check to work and PR generation from release both in my Maintenance Order to work..
Regards..

Hi DP Singh,
I had seen the configuration settings that you are telling me but you see the Problem is:
If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/PReq Indicator as Immediately, then the Manual Material Availability Check would work accurately but upon saving the Order, System would generate the Purchase Requisition.
and If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/Preq Indicator as From Release, then the Manual Material Availability Check would not work as no material is as such MRP relevant till the time of releasing the Order but the Purchase Requisition would be created only when the Order is released.
Now What I want is both the Manual Availability Check to work and Purchase Requisition Creation From Release, but this is not possible according to the Standard SAP System. A workaround could be that I configure the automatic material availability upon release and configure the Res/Preq indicator as From Release, that way the material availability would be checked when the order is released and Purchase Requisitions would also be created from Release but still the Manual Availability Check would not work.
The Ideal Solution should have been configuring the Res/Purchase Requisition Indicator for all Non Stock Materials to be From Release and the Res/ Purchase Requisition Indicator for all Stock Materials to be Immediately. This way your manual availability Check would work for all Stock Materials and Purchase Requisition for all Non Stock materials would only be created upon Release. But this But still this is an ideal solution not the actual solution for standard SAP does not give you the flexibility to do such a setting in customizing or using Enhancement.
The Work Around Solution given by SAP is as follows: The system provides the following workaround:
After you change the indicator for materials planning-relevance to
"immediately" you can execute the availability check as required. You must
not save the order or network.
Regards,
Muhammad Usman Kahoot
Edited by: Usman Kahoot on May 27, 2010 1:32 PM

Purchase requisition workflow - reset release via BSP and BAPI

Hello,
We have a small workflow to release purchase requisition.
A mail is send to the approver. The approver opens an BSP application to release or refuse the PR.
The approval works well.
The rejection doesn't work well.
I use the BAPI_REQUISITION_RESET_REL_GEN to reset the first release of the PR (00 release key)
We have 00, 01, 02 as release key, and all the release have to pass to release completely the PR.
00 is the requester level.
My problem is :
for example I am the 01 level. I received the mail from 00 level, I refuse the PR via the BSP. In ME53N, the current release key is now 00 but when I look at the workflow, the following agent (corresponding to 02 release key) is determined. Normally nothing has to happen.
Someone has an idea to stop the workflow ?
thanks
Véronique

Hi Martin,
When I checked the contain of container in the workflow (in the log), I saw that the release key is 02.
I don't know why but the WF received the event RELEASESTEPCREATED instead of normaly it is finished.
When I reset the release via ME54N, the WF ends correctly and no new event is received.
How can't I see why the event is started in the BAPI.
In fact it is very strange, if I used the BAPI alone, all works, no new event is started.
But if I used the BAPI in my BSP, a new event is started.
Thanks
Véronique

Purchasing Document cannot be released Urgent ?????

hi
when i try to unrelease the PO thru Txn ME29N
the system gives the said message
Purchasing document 4800003821 cannot be released
Message no. MEPO823
even when i enter the po no it on starts give the message
wat may be the reason
its urgent

may be missing of Authorizations ?
check ur SU53.
regards
Prabhu

Purchase |Order cannot be released Message BL001

Dear Friends,
I am new to this forum. I am facing a problem with Purchase Document release.
Two release codes GC and PH are assigned to same PO Class. Charecteristics for release are different for each codes. for release code GC is purchasing document type and Plant. For PH is again Purchasing document type, purchase order value and Purchase group. All have been put together in one class and i am not able to add a new class in release group. Request you to provide a solution for this.
rgds...KM

can you give some more details that you assigned the two release codes in same release strategy or different release strategy.
if it is assigned to same release strategy then the Charecteristics for release should be same.
for ex: you have two plants A & B
now you want to get a approval from a Asst.Manager, if the po price is more than Rs.200000. (for Plant A)
and you want to get a approval from a Manager, if the po price is more than Rs.400000.
in this case, you have to create two release code one is for Asst.Manager & another one is for Manager.
But the characteristics should be same that is your plant & doc type.

Purchasing document **** cannot be released

Dear exports,when I implement the Enhancement M06E0004, the Release strategy EKKO-FRGSX is null ,so i can't release Purchasing document, can anybody help me, and tell me why?

>
Chandralekha wrote:
> Hi,
>
> Check the entry EKKO and cehck the status for that FRGSX field. If it is null then try to update the entry using the UPDATE <<TABLE>> set frgsx ='<<value>>' where ebeln = '<<valkue>>.
>
> Pls try to udpate statement and try to set the entry and try to run the exit.
>
>
> Reward if helpful.
>
> Best Wishes,
> Chandralekha
NO, you do NOT do a direct table update on EKKO to fix a little problem like this - or to fix any problem.
The release strategy for your POs is set up for each PO order type in config. Ask your functional consultant why this is not set in the way you expect.

Issue in Purchase Requisition Release Strategy

Hi guru,
I've got an issue in the release strategy;
I have a PR with 3 lines. After Relase I've deleted the last line and system doesn't allow me to release it by ME55 transaction; I'm able to do it only by ME54N.
Thank you for your help.
M.

Hi Marco,
I had a problem with ME55 and i wrote to SAP OSS.
The first OSS answer was:
Can it be that your requisition has some deleted items?. If yes, then
take into account the following:
Please consider the definition of ME55 "Collective release":
You release ALL requisition ITEMS or COMPLETE requisitions that are
awaiting processing by your release code.
And also the definition of "the field overall release of PReq":
Determines that the items in a purchase requisition are ALL released at
at the same time (rather than individually).
That means:
If there are some items which can't be released (may be they are
deleted), the transaction ME55 can't be used - so you have to release
over the individual release (and that's why you get this
message in ME55).
If you get such a message for a purchase req. in ME55 you can go over
the menu to release this item(so you don't have to call ME54 directly):
Select the item and choose Goto -> Individual release.
There is a difference between overall release and collective release.
Overall release means that a purchase requisition is released on
header level and not on item level. Collective release means that
several purchase requisitions can be released at the same time.
When one line of a requisition subject to overall release is deleted
you are asked to use the "single release" functionality in transaction
ME54.
Once you delete a line item you MUST work with ME54 to release each
item. By deleting a line you effect the whole purchase requisition
hence collective cannot be used. This is standard SAP functionality.
In this case, you have to individually release each requisition item
through transaction ME54.
I hope this is useful to you.
Ciao
Alberto

Problem in purchase requisition release strategy code

Hi
We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
Note: new strategy was copied from other.
Thanks in advance.

hi,
As you said tht you have copied the release stategy n created the new one...
If you do so, you would have copied the class also...to which the release group is attached...
If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
Once you do this check the release strategy at OMGSCK...and then try at PR...
You do all settings at :
SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
Regards
Priyanka.P

Purchase requisition create/release

Hi
I am creating purchase requisition. And i want to release this requisition.
But in my created purchase requisition there is no tab such as release strategy
And i want to keep my purchase requisition as blocked initially and later i want to release it. Can u please tell me what are the configuration or release procedure i've to do to make this happen.
I know purchase requisition can be released be me54n. But my created purchase requisition is not release relevant.
I hope u understood.
with regards
mandeep

Hi Mandeep,
For release strategy cstomising u need to go spro
Matl mgmt>Purchasing>Purchase requisition>Release procedure with classification
there u maintain, characteristics, class, create release strategy and maintain, release group, release code and indicator etc. Once u do all this then u will get the tab in PR
hope this helps
regards
Anand.c

No Release without Purchase Requisition in Process Order(subcon)

Hi All,
We have one requirement :
The creation of purchase requisition happens during the creation of process order which is basically governed by control key.
But in case the creation of purchase requisition didn't happen , because of any issue with master data set up in recipe
or say wrong data .
We DO NOT want , the system should allow the release of that process order.
Is there any standard way to achieve the above requirement.
Thanks in Advance!!!!!!

Hello
You can implement your own logic to check the purchase requisition during the release using BAdI WORKORDER_UPDATE. There is a method specific for checks during the release.
BR
Caetano

Purchase Requisition Overall Release problem with several CostCenter

Hello Gurus!!
I need your comments!!!
I define the Purchase requisition as Overall Release, and woks !! but I have a Issue.
I have an entry in the CL24N txn as follow:
AccAssgCat = K
Plant              = CC01
CostCenters = 10001
                        10002
                        10003
totalAmt        = 1USD to 1000US
So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
I assume that as both are into the release strategy the system will take both CC and ask for release!!
What I can do to fix this situation??

Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005   EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros

Overall release strategy in purchase requisition

hi,
how do i configure overall release in case of purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics? is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
plz help me in details
regards
Aniruddha

Hi
For PRs, there are two types of release procedures available
With classification
With this we can release the PRs both items wise and in their entirety
Without classification
With this we can release only at item level
When you create the Release Group under the release procedure with classification
you check the box " ov Rel P Req (Overall release of purchase requisitions
This Determines that the items in a purchase requisition are all released at
the same time (rather than individually).
This should help to relsove your problem.
Regards
Vikrant

Overall release of purchase requisitions - pr document type

hi,
what is the importance of the indicator Overall release of purchase requisitions while defining the PR document type.
Overall release of purchase requisitions
Determines that the items in a purchase requisition are all released at the same time (rather than individually).

Hi Manipal,
overall release makes the release of all the items in the document.
u can also release itemwise in PR only and in all other external documents overall release is only possible
hope it wud have answered ur question.
Reward if useful
Shawn

PR cannot be released via ME55

Hi Gurus,
Unable to release the PR via ME55 Whenever PRs are changed , we have created a PR with 2 line items and deleted one of the line item but not able to release the same with ME55.
Header level Release strategy is maintained for PR.
Kindly guide how to release the changed PR via ME55.
Thanks & Regards.

Hi Anil,
Please consider the definition of ME55 "Collective release":
You release All requisition Items or Complete requisitions that are
awaiting processing by your release code.
And also the definition of "the field overall release of PReq":
Determines that the items in a purchase requisition are ALL released at
at the same time (rather than individually).
That means:
If there are some items which can't be released (e.g. they are deleted),
the transaction ME55 can't be used - so you have to release over the
individual release.
There is a difference between overall release and collective release.
Overall release means that a purchase requisition is released on
header level and not on item level. Collective release means that
several purchase requisitions can be released at the same time.
When one line of a requisition subject to overall release is deleted
you are asked to use the "single release" functionality in transaction
ME54.
Once you delete a line item you must work with ME54(N) to release each
item. By deleting a line you effect the whole purchase requisition
hence collective cannot be used. This is the standard SAP functionality.
In this case, you have to individually release each requisition item
through transaction ME54(N).
BR
Nadia Orlandi

Purchase Requisition Cannot be released

Similar Messages

Maybe you are looking for