ME55 error - Release via individual release

Hi I have a question,..
We are using overall release strategy.
Now I have 2 line item in a same purchase requisition, and when run ME55 it show me the message "Release Possible".
Then after that, using ME52N we change the requisition and cancel 1 of those items, of couse a new release strategy was defined by the amount we defined.
But now, when go to ME55 now the messahe said "Release via individual release"... ann with ME55 cannot be release.. I need to go to ME54 and ME54N.
Do you know why SAP do that? what is the reason of this?

Dear,
As available in SAP NOTES 668940
Program error.
This problem occurs after deleting one item of a purchase requisition. The consequence is that all documents created afterwards will no longer be releasable via ME55.
Check the corrective information.
Please also check: Note 69792 - ME55->ME54 Changes from ind.release updated wrongly
Note 92315 - Call individual release - call transaction
Note 72100 - Individual release - only allowed items
Regards,
Syed Hussain.

Similar Messages

Problem in creating Release group for Release Procedure for PR

Hi Experts,
I could not able to create Release Group ( 01 & 02 ) for Release Procedure and assigning it with a Class
( Z_CLASS_PR ) in Set up Procedure with Classification.
The following error is getting displayed.
Please check release classes (see long text)..
How to over come this problem.
Thanks in advance.
Regards,
Nani

Release group:
You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are only allowed to use one class for the overall release or individual release. If you use the overall release for purchase requisitions, you must mark this for the document type (transaction OMEB, flag for V_T161-GSFRG) and the release group (transaction OMGQ, flag for V_T16FG-FRGFG). In the overall release, the system only takes into account characteristics that are identical for all items. If, for example, item 10 of a purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.

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

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**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**
**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**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
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
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*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 continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

Error while billing document releasing to accounting.

Hi Experts,
Please give me possible reasons for below error while billing document releasing to accounting.
"Valuation with material cost estimate: error with product "500258045"
Message no. KE350
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate a line item using the current standard cost estimate.
In order to determine the current plan period, the system needs to read the valuation segment of the material master.
The system has found that the current plan period is not filled forproduct "BDE98561002" in plant "9856".
Display material (View: Costing)
The system looked for the material cost estimate using costing key "ZK1", as defined in the Customizing settings for CO-PA.
System Response
The document cannot be processed.
Procedure
Contact your system administrator".
I have checked CKR1 transaction there were no cost estimates with KF costing status.
NOTE: Material Ledger Activated.
Please suggest the possible reasons and what to check?
Regards
Chandra.

Check the cost estimate that is mentioned against the Costing key ZK1 whether it exists in the system and as you are saying there seems to be no cost estimate for the said material.
Hence release the std cost estimate for the said materia using CK11n or CK40n

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

Error during production order released

The profile selected for the capacity availability is not suitable error comes during po released.
Pls tell me how to resolve it

Dear
Maintain the Capacity Overall profile SAPSFCG011 in Production Scheduling profile in OPKP and the same prod. schduling profile to be assigned in Material master work scheduling view. Please check and revert.
Regards
Ganesh.M

Error Only one EhP release is allowed additionally

Short Text
Error Only one EhP release is allowed additionally:
Long Text
Hi experts,
I have installed EHP3 using transaction saint. Now when I try to upgradeto EHP4 , I am getting following error in MOPZ.
Error Only one EhP release is allowed additionally:
Information Make sure you have implememented note 1287216
Information Select at least one of the technical usages additionally:
Information *HCM - Learning Solution*
Information *Learning Solution - ABAP only*
But when I go back on previous screen
learning solution is greyed out and red,
HCM learning solution is also greyed out (not Red).
Even if I choose EHP3, still both these components are greyed out.
I have looked at note 1287216 and 1139602 but can't find what is missing.
please advise how can I make these 2 components selectable .
thanks,
Daljit boparai

Hi,
To apply these components have you generated xml file ? If yes, then is xml file contains these patches ?
Please check and revert back...
Thanks
Sunny

P.O - DIFF. BETWEEN INDIVIDUAL RELEASE & COLLECTIVE RELEASE

Dear All ,
Kindly explain the difference individual release & collective release , as i m using ME29N to release here this P.O is to be released by 3 persons - execut. Mgr & G.M , what is scenario in Collective rel procedure
sap11

Hi
It is not possible to release all POs in one time through ME28.
Through by this Tcode you can view list of all unreleased POs under one released code then one by one you can release all POs.
In SAP, there is not any provision to release all POs in one time.
Vishal...

Fatal Error: This J2EE SDK release runs only on Java 2 (JDK1.2 or later)

Hi
Can any one help me
i install the j2ee
i have jdk 1.4 version
i set the JAVA_HOME & J2EE_HOME path also
but when i run j2ee.bat i got the folloing error
Fatal Error: This J2EE SDK release runs only on Java 2 (JDK1.2 or later)
so any one solved my problem
Regards
Nimesh

Another possibility might be the J2EE implementation itself.
In the code for j2sdkee1.2.1, the error you see appears to originate in the checkJVMVersion method of com.sun.enterprise.util.Utility:
if ( !javaVersion.startsWith("1.2")
&& !javaVersion.startsWith("1.3") ) {
errmsg += "Fatal Error: This J2EE SDK release runs only on " +
"Java 2 (JDK1.2 or later)\n";
fatal = true;
This method is called first by J2EEServer. If you are using a later implementation of J2SE, then you will probably have some problems.

Northern Softworks via Apple released Leopard Cache Cleaner 4.0.19 today (shareware)

Northern Softworks via Apple released
Leopard Cache Cleaner 4.0.19
today

24 hours after my first post about this issue, I've just fired up the G5 and it's still running smoothly AND the airport is being recognized and is connected to the wifi. +(But no more...see below.)+
I did one last step yesterday regarding the AirPort, but am not sure that it's what fixed it. After research on these forums, I deleted a file called "AppleAirPort2.kext in my /System/Library/Extensions folder. Apparently it is an older Tiger-only AirPort Driver that is no longer used on Leopard.
I also ran (for the second time) the newest Airport Driver. After doing both of those yesterday, I unhooked all hardware, and re-booted - but saw no change.
However, as I said, it's working now....apparently it needed to re-sync in its own time.
Thanks all for your help. Smooth sailing now - the ultimate reason for a successful update, was starting up in Safe Mode and installing the updates from there.
So don't forget:
1. Do a BACKUP.
2. *Repair Permissions* from your System Disk
3. Start up in *Safe Mode*
4. Download & Install the update combo from the Apple Site (Although I used Software Updates)
5. *Repair Permissions* from your System Disk again.
5. Cross your fingers.
My G5 is definitely snappier now.
*+Edited to say: I just glanced at the wifi and IT'S NOT CONNECTED. And the Airport won't turn on in System Prefs. So something is still a little dodgy with that.+* At least the System Profiler is now showing that I have an Airport Card, etc.
-Lela/owl5126
Message was edited by: owl5126

Error relate to PO Release Strategy

Hi expert,
I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.
I have finished configuring PO Release Strategy and Release Group is ZT with 2 release code (01, 02).
After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.
Thanks for your help

Hi,
What procedure did you follow while deleting the release group ? The process for release group deletion should be as mentioned below.
1. First delete the classification data for the release strategies you want to delete
2. Delete release strategies ( from detail view in SPRO )
3. Then delete release codes ( including description in different languages - translation )
5. Lastly delete release groups ( including description in different languages - translation )
If you dont follow the above process inconsistency might be there.
After deletion if you want to create new release groups follow the steps in reverse reverse order.
1. Create Release group ( including description in different languages - translation ) Check table - T16FG
2. Create Release Codes ( including description in different languages - translation ) - Check table - T16FC/T16FD
3. Create Release Strategies ( ( including description in different languages - translation ) - Check table - T16FS/T16FT
- Assign codes to Release Strategies
4. Maintain classification values - Tocode CL20N
Please let me know ifyou need any further help.
Regards
Sayan
Edited by: Sayan Pal on Dec 8, 2011 3:28 AM

Stack file is invalid: 'SEM-BW' (stack release 600 source release 602)

Hi experts,
I encountered the following error while patching my BCS SEM system using EHPi.
Servere error(s) occured in phase PREP_EXTENSION/EHP_INCLUSION!
Last error code set: Stack file is invalid: component 'SEM-BW' (stack release 600 < source release 602)
The BCS SEM system is currently installed with SEM-BW 602. But the xml stack file generated by solution manager contains SEM-BW 600. From SMSY, under the Software Components tab, the release for software component SEM-BW is 602.
Where does solution manager obtain the data when calculating the xml stack? How can I generate a xml stack with SEM-BW release 602?
Thanks,
Tzyy Ming

Hi.
When installing this system you have used an installation guide. If i were you i would try to configure the system described in the guide. SAP note 852447 talks about an IInstallation SEM-BW 600 on SAP NW 2004s AS ABAP;
So why not try to configure this system as netweaver as abap in smsy and add the add-ons as relevant. But i am not completely sure - i am at home and can not look to our SolMan system.
I do not think that the configured system should be the problem. You said, the smsy contains the correct data. Did you refresh the product data in your solution manager. That could be the reason why the queue ist not calculated correct ly.
regards,
Martin

Donu00B4t release tasks after releasing a phase

Hi guys,
after searching a lot and programming in dpr_events i have no further idea.
Does anybody know if it´s possible to do not release a task after releasing the upper phase?
I tried the method set_data_ext from cl_dpr_task_o in dpr_events but there is no field for changing the sytem status from '1701' (released) to '1700' (created).
Thanks for advice,
Tobias

Hi Zhenbo,
thanks for the help. I solved the problem with your suggestion. In DPR_EVENTS first I buffered the task types and then I removed them, so that the system cannot release the tasks.
In the project itself, I import the buffered task types and then I search in the project for tasks that have no task types. If the GUID matches I set the task type and remove the entry from the buffered task type table.
Now I can release a phase without releasing the underneath tasks.
Because of the filtervalue ON_PPO_RELEASED in DPR_EVENTS I can release top-tasks so that also sub-tasks are released.
So the behavior is correct again except that there are some error messages when I release the project. But that´s OK so far.
Regards & thanks again,
Tobias

Proces order release not possible/Release rejected

Hi PP Guru,
While process order release the system shows error that the order release not possible / release rjected.
pl tell me what r the possibilities to be check to resolve above problem.
Bye
subhash

The Possible reasons could be one of the following -
Missing Parts - Some of the components required for the order may not be available
Missing Capacity - Capacity required for the order is not available
Error in Cost calculation
Error in Batch allocation to the component materials
When a process order is release some of the functions are carried out in background like Creating a reservation, material availability check, capacity check, precosting......
If something goes wrong in one of the step the order may not release.
Please check the logs during release it will have the clear message.
Hope this helps you.

ME55 error - Release via individual release

Similar Messages

Maybe you are looking for