MEPO822:Release tab is occuring in PR

Hi Friends,
I am not getting the release tab in PR at item level. I am getting the error MEPO822 while changing the PR in ME52N T-code.
Please guide me for getting the release tab in PR.
Krishan

Hi,
Please check your release strategy with below detail.
Business Process: -
Purchase requisition is creating PPA person than PPA head release this purchase requisition.
Process of Release Strategy: -
Procedure with Classification: -
Edit Characteristics: -
For implement release strategy for purchase requisition you have to create Characteristics u2013 CT04.
For Example: -
Suppose you want to create release strategy for purchase requisition document type wise. So you create characteristics for purchase requisition document type with CT04 u2013 document_type.
Edit Classes: -
After creation of characteristics, Create Class u2013 CL01 for release strategy of purchase requisition.
For Example: -
Create class for purchase requisition like: Release_PR
Set Up Procedure with Classification: -
In this node you can maintain following details.
Release Group
Release Codes
Release Indicator
Release Strategies
Now we see above details in briefly
Release Group: -
You can maintain release group in this node. This permits the multiple usage of the same release strategy key
For example: - Create 01 u2013 Release Group for purchase requisition release strategy and assign your class of release strategy.
Release Codes: -
You can maintain release code against release group with this node.
For example: - Create release code 01 u2013 PPA Head against release group 01 u2013 release group.
Release Indicator: -
You can create release indicator with this node, like blocked, in process, Release.
For example: - Create two indicators, Like X u2013 Blocked, 9 u2013 Release.
Release Strategy: -
After click on this node you can see four different step for release strategy of purchase requisition.
Release prerequisites, Release status, Classification, Release simulation.
First off all maintain your release code in Release code tab. Than done some bellow settings.
Release prerequisites: -
Click on release prerequisites tab, change your required changes and click on continue button.
Release Status: -
In this node you can set your path of release strategy.
For example: - you want to create release strategy like when PPA head tick on release indicator at that time purchase requisition made release. So you can set it via release status.
Classification: -
In this node you have to enter value of characteristics.
For example: - enter NB u2013 standard pr for document_type.
Note: - Before enter value in Classification, You have to maintain value in characteristics u2013 CT04 in value tab.
Release simulation: -
Check release simulation for release strategy.
After done this process, Create purchase requisition for document type NB u2013 Standard PR.
At the time of check release strategy will be implemented in your purchase requisition.
You can release it via ME54N. List of purchase requisition release with ME55.
Regards,
Mahesh R.

Similar Messages

Release Tab in purchase order disappear after release using ME29n

Hi there,
We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem. When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy. Using the older ME28 transaction to release this purchase order, everything is fine. We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order). When we use transaction ME29n the release tab in the purchase order just simply disappears after saving. In the purchase order header changes, the release change is visible, but the release tab is missing. This purchase order is now not subject for release, and a goods receipt is possible without release. I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
Has anybody had a similar experience? Any advise would be greatly appreciated.
Regards
Christo Vermeulen

Hi Christo Vermeulen,
I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
Thanks in advanced,
Eder Nicoleti

How can i block PO adopt from PR with no release tab

Dear Experts,
I need to block PO creation ( by adoptation of PR) from PR which has no release tab active. Kindly help me how can i do this.
From unreleased PR , PO can not be created and it is standard SAP function. But if PR has no release tab then PO can be created from that PR and no error or warning is there. But i need to block PO creaation from the PR which as no released tab active.
Please help.
Kind regards,
Zusen

Hi Zusen,
Would not be good idea to place those PRs in release strategy? In this way PO(s) will not be created until PR(s) is released. Have a look at release strategy of PR under the path; IMG-Materials Management-Purchasing-Purchase Requisition-Release Procedure
Otherwise you have to develop some coding. You can use BADI: ME_PROCESS_PO in order to control unreleased PR. If EBAN-FRGRL is NULL in PO then you can place an error message as you want.
Kind regards

Broken PCI card release tab question

Ordered and received the ATI 4870 video card upgrade from Apple and read the included instructions. In lifting up the plastic card release tab at the end of the PCI express slot to release the ATI 2600 video card the plastic tab broke off and fell down into the machine. I was able to remove the old card and install the new one without other problems. The new card seems to be working well.
Should I be concerned about this broken release tab and the plastic piece which has fallen who knows where? I have Apple care on the Mac Pro and there is an Apple store in the area.

Apple will probably not cover it since you broke it. There should be no problem using it without the plastic latch, but if you ship the Mac Pro, make sure the card is pushed all the way in before connecting power.

PO Release TAB not trigered in Purchase Order

Dear all,
We have created a Release strategy in our test system.Its works fine.But when we create the same in our clients development
system the "Release Strategy "Tab is not triggered in Purchase order.We did the following steps while creation
1) Created new characteristics and class and when we had assigned it to new user group system gives following error
    "Please check release classes (see long text) Message no. ME492".....
2) So we used the existing class in clients system and assigned new required values in characteristics (Plant,Purch.Org,
   Company code,total net order value,Purch.Group).
3) In classification tab we get all the required value and no problem to release strategy.In "CHECK RELEASE STRATEGIES"
     system shows green signal for Release code and release strategy..
Kindly suggest were we went wrong????
Regards
Sachin

Hi,
You should use only release class for PO.Hope one release class assigned to release group(TR transported to dev-client) & now you created another release class and want to assign to release group, so you are getting the error. Now create same release class which assigned to release group & design release strategy and you will have release TAB in PO.
Note:Better to keep one release class always for purchasing documents....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.
Regards,
Biju K

Release tab at release PO indicator

Hi Guys,
I'm wondering what is the purpose of release tab (tick / untick) at release PO indicator?
Thx in advance

Hi,
The release tab in purchasing documents shows if the document is subject to release strategy and needs to be approved before any follow on documents can be created (PO, goods receipt, invoice). So it may be the case where ther is a 3 level hierarchy for the pucase document to be released. so for example manager 1, manager 2, manager 3. If there is a green tick set for these release codes then the document has been approved by manager 1, manager 2 ,manager 3.
All release strategy setup is set in customising. The release indicator can be set in customising for the release code. So for example in this case you can set it that until all the managers approve the document the document is blocked for further processing. When released by all release codes (manager 1, manager 2, manager 3) then the document can be set for release and follow on documents can be created.
Kind regards,
Lorraine

Release Tab getting deactivated when changing SRM GOA

Hi,
I have created GOA long back.I have also have release PO`s against that GOA. But now when I am trying to change any item level data like condtion or any other data and try to release it that time release tab gets gryed out.
Does any one faced this issue in past...if so then please let me know the probable reason.
Regards.

Hi Navneet,
The release button gets grayed out usually when the contract have some errors.
It could be some problem related to your target value or target quantity. As per my understanding the target quanity/value at the header level always should be more than the release quantity at the line item level.
Also please check the note numbers: 863656, 1082548
which deals with similar issues.
Please award points if the answer was usefull.
Thanks & Best Regards
Raj

EXIT_SAPLEBND_004 lets release tab disappear on PR

Hi, Gurus,
I created an enhancement project ZMM_005 throught CMOD,It was assigned with M06B0005.
After activating it, I found that release tab disappeared from PR screen.
(In my R/3 system, PR release was set into overall release.)
After I entered PR number and release code on ME54, SAP gave the error message "Purchase requisition not subject to a release strategy".
It's why?
Please give me some suggestion.
Edited by: Mic chen on Feb 15, 2010 9:20 AM

Thanks very much.
I found the solution(SAP Note 371667).
Edited by: Mic chen on Feb 15, 2010 10:48 AM

When releasing PO error occured Express Document " Update Terminated"

hi all
     i am getting a strange problem ,
while doing release of PO(purchase order) by t.code ME29N, i am able to release and SAVE it properly with out any error.
But when returning back to ME22N t.code to see that PO .
i am getting this error :
Note : - this error is coming for a particular TYPE of PO's and with
            in that TYPE all PO are not giving ERROR,
            Please tell me what can be reason,
Express Document "Update Terminated"
Runtime Error          POSTING_ILLEGAL_STATEMENT
       Occurred on     15.07.2008 at   11:03:24
Statement "CALL DIALOG" is not allowed in this form.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSTXW " had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXW " in "DISPLAY_OTF".
The main program was "RSM13000 ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXWU02 "
of the source code of program "LSTXWU02 " (when calling the editor 820).
The program "SAPLSTXW " was started in the update system.
000710
000720     if ( sy-binpt = false and
000730        ( ( cl_gui_object=>www_active = true or
000740            itcpp-tdscreen = 'ITS' ) or
000750          ( cl_gui_object=>javabean = true and
000760            itcpp-tdscabap = false ) ) ).
000770
000780       perform cc_display_pdf.
000790
000800     else.
000810
>       call dialog 'DISPLAY_OTF'                "ABAP-List-Preview
000830              exporting otf itcpp 0
000840            importing itcpp.
000850
000860     endif.
shall i concern this with BASIS person , coz every PO not having this problem,
i think it is related to time taken by SERVER for UPDATE is more then this error comes .
OR is there any technical issue related to ABAP.
regards
sachin

This problem will be caused by an output which will be triggered when releasing the PO. Check the messages in the PO for which one is causing the update error.
Regards,
John.

STO: Condition tab not occuring

Hi Friends,
I have configured a STO purchase order and not getting condition tab at item level. Please suggest how can i get Condition tab in Purchase order.
Kraheja.

Hello,
Pricing configuration for STO: -
In SPRO > MM > Purchasing > Conditions > Define Price Determination Process > Define Schema Determination > Determine Schema for Stock Transport Orders > Here assign Calculation Schema "RM2000" i.e. Stock Transfer Document to Schema Grp Pur. Org, STO Type (For e.g. UB) and Supplying Plant.
Calculation Schema "RM2000" has condition type P101 which will pick up the MAP of supplying plant automatically during creation of STO in ME21N (Conditions Tab).
Regards,
Shailesh

Importance and relevance of the "release" tab in WE82

Hi all,
I want to know the relevance of the <b>RELEASE</b> field while assigning IDoc type to a message type. This field is mandatory! so, what is its importance? As of now, I have used a number '640' to create a new entry for my custom defined IDoc type. This number is the release number of the SAP software I am using.
Thanks for your answers!!

Hi,
/people/r.eijpe/blog/2006/05/22/d-xie-soap-part-3-determine-software-component-version-of-standard-sap-idocs-and-rfms
check it out..

Release strategy tab is not coming in SES

Hi All,
I am facing a issue where I have created an SES, and release strategy is assigned to this SES. Problem is somehow the user is not able to see the release tab when he go wants to release the SES. The release tab is missing from the SES.
Am sure somebody has faced this kind of issue and have any idea how to correct this.
Thanks

Hi,
The direct reason that there is no release icon available in ML81N
is inconsistency in the field ESSR-FRGRL for affected SES's.
This field should be filled with 'X' as all those SES are subject
for release.
Have you changed customizing for involved release strategy recently ?
If a relase strategy is created with a certain name and documents are
created with respect to it afterwards, this release strategy should be
changed then IF AND ONLY IF a NEW name is assigned to it as well. In
other words, if such a strategy is already use, it should be RENAMED
before applying the desired changes.
Otherwise you will run into the observed inconsistencies when trying to
edit documents which were created BEFORE the strategy was changed
(since the system at some point always checks the NAME of the strategy
to be changed, NOT the content).
So if this case happens only for already created SES a good solution
for it is to delete affected SES and create a new one with changed
release strategy.
I would delete affected SES and create it again.
It seems to be the fastest way to resolve this issue.
If you need a correction for this inconsistency issue, please open a SAP ticket for your problem.
Regards,
Edit

Released PR showing unrleased during PO creation..

Hi,
While creating PO from a released PR, I am getting below error although PR is fully released
" Purchase Requisition xxxxxxx , item 00020 not released for ordering."
Message no 06055
One thing i want to come to your notice that here in our organization we have not configured release strategy at item level.
Here PR is released at header level only.
Thanks
Nikesh Patel

Hi,
Please check the release indicator in the PR and check whether its maintained correctly as shown below:
Also, if the release is at header level, you cant find the release tab in item level and you cant find different release status in item level. I guess that the release strategy configuration was changed from item level to header level or vice versa. Due to this, the inconsistency occured. It is not recommended to change the release strategy config once its in use. Refer the KBA: 1635346 - Add a new release code to the release strategy of PR issue
Regards,
AKPT
Message was edited by: AKPT MM

Release strategy determination for PO item level characteristic value

Hi Experts
I have user material group as release characterstic for PO.
I have created two line items with two different material groups.
How the release strategy determination occurs when the two different material groups are linked to two different strategies?
regards
ramSiva

Hi,
in this case system is NOT able to find the release startegy.
Please take care of the following explanation (see note 365604)
o For OVERALL RELEASE (purchase order and purchase requisition) the
   item fields such as Plant and Material Group will be aggregated
   to header level.
   For example you use Plant/material group
as one of your characteristics. If all
items do not belong to the same plant/material group
then
*******the relase strategy will not be found***********
unless you have maintained a blank value as one
of your allowed values for the characteristic Plant/material group
. If all items
belong to the same plant7material group
then that plant is aggregated to the
header; if one or more is different then a blank is aggregated to
the header.
If you use an overall release strategy all
characteristics which you have defined in the customizing (CEKKO-MATKL
must have the same value. If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing (Transaction: OMGS
: OLME >release procedure for PO > rel. strategy ) the
system won't find a release strategy.
you need
to add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save. Now in OMGS you can select
this value as an allowed value for the characteristic.
(Example:
To avoid this you can do the following:
- go into transaction CT04
- enter the characteristic 'CEKKO-MATKL'
- click on the tab 'values'
- set a flag in 'additional values'
- in the column 'Char. value' do not enter anything
- in the column 'Description' enter a text like 'no material class'
- save this setting
Now
- go into transaction OMGS -> button 'release strategy'
-> button 'classification'
- double click on CEKKO-MATKL' and set a flag in 'no material class' )
Please also have a look into the attached note 365604 point 2d).
BR
Nadia Orlandi

OO4O 9.2.0.4.8 production release is available

OO4O 9.2.0.4.8 production release is available for download on OTN.
New Features
============
New Features supported for the 32-bit In Process OLE Automation Server:
With this release, OO4O provides four new objects that enable developers to access and manipulate the new datetime and interval datatypes introduced in Oracle9i.
OO4O Objects Oracle Datatypes
OraIntervalD INTERVAL DAY TO SECOND
OraIntervalY INTERVAL YEAR TO MONTH
OraTimeStamp TIMESTAMP
TIMESTAMP WITH LOCAL TIME ZONE
OraTimeStampTZ TIMESTAMP WITH TIME ZONE
Instances of these types can be fetched from the database or passed as input or output variables to SQL statements and PL/SQL blocks, including stored procedures and functions.
These new datatypes are not supported as elements in collections such as PL/SQL Indexed Tables, VARRAYs, or Nested Tables. Please refer to the OO4O doc for more information.
Summary of problems fixed
=========================
2797039 - SIGNIFICANT DELAY IN MONITORSTART DETECTING AN ENQUEUED MESSAGE
3049591 - OOBJECT.GETATTRVALUE() RETURNS NAME OF ATTRIBUTE TO BE RETRIEVED INSTEAD VALUE
2843494 - 0040 VB APPLICATION FAILS WITH ACCESS VIOLATION
2647144 - SETTING ORACOLLECTION NOTHING CAUSE ACCESS VIOLATION
2787093 - GETFIELDCHUNK FUNCTION DOES NOT READ MORE THAN 4096 BYTES
2614824 - ACCESSING VARRAY OBJECT OF DEQUEUED MESSAGE THROWS EXCEPTION
2594695 - OFIELD::SETXMLASATTRIBUTE(TRUE) HAS NO EFFECT
2594037 - USING OFIELD::SETXMLTAGNAME RESULTS IN A OIP-04096: INVALID ADVISORY CONNECTION
2594032 - OFIELD::GETXMLTAGNAME RESULTS IN AN INVALID CHAR*
2457000 - MEMORYLEAK HAPPENS WHEN EXECUTING "ODYNASET.OPEN" AGAINST LOB ON OO4O+VC
2391180 - OO4O RETURNS OIP-4117 WHEN UPDATING FOR CASE SENSITIVE COLUMNS.
2555543 - UNNECESSARY FETCH OBSERVED IN SQL TRACE WHEN USING UPDATABLE DYNASET
2311470 - IF CREATING DYNASET "SELECT BLOB,LONGRAW FROM TAB", GPF OCCURS AT GETCHUNKBYTEEX

Is the recommended 9.2.0.4 patchset needed for the Database Server only? Is there a patchset to upgrade the 9i Client to 9.2.0.4 also?

MEPO822:Release tab is occuring in PR

Similar Messages

Maybe you are looking for