RELEASE PROCEDURE/ TCODE ME28

Hi,
We have upgraded our system from R/3 4.6 c to ECC 6.0 and the UPGRADE is PURELY TECHNICAL i.e new functionalities are not offered and R/3 4.6 c existing functionalities are maintained in ECC 6.0 as it is.
After upgrade ME28 is not displaying suitable purchaisng documents to be released by a user when he is using his release code and release group , though in Release strategy tab of PO it is showing that this document is to be released by the user as other two had alreadyapproved it.
Release strategy is working as for other release code it is coming ( checked in release simulation also) but not for this user who has to approve finally the PO as everytime he is using the code ME28 ' no suitable purchasing documents found' message is coming.
Rewarded if answered .
Regards
Ankur

Hi Ankur,
Since you mentioned that release strategy is working fine, try to trigger the release strategy for this PO once again. You can do either way:-
a. Go to change mode of PO, make a change in the the quantity, hit ENTER key, change back to the original quantity, THEN only Save the document. Try ME28 again.
b. Otherwise, you can try to re-create the PO by adopting the details again from the PR, but first flag the current PO for deletion first. See if this will help to solve the problem.
I have encountered this problem before, and the first method works.
Rgds.

Similar Messages

Release procedure problem

Hi Gurus,
          I created a release procedure for PO. i created a single chs based on total amount of PO and assigned it to a single class. then configured it for 5 release codes. all the simulation is working fine.
          But when I created the PO worth of 6 laks, which is above the level of last release code >=5 laks. when i go for release in ME29N or ME28 its giving an information message saying "document is not applicable for release procedure. in ME28 i am getting "message no documents found" for my release code and release group combination.
          Where should i have gone wrong. give me some suggestions.
Thanks & Regards,
Poorna.

Hi,
Your Maximum amount of PO which is applicable for release strategy is 5 Lakhs for your last release code.
Now if you create the PO for 6 lakhs then how the system will consider the release strategy.
Thats why you will not find the same in ME29N or ME28 to release the PO.
So you need to change your Characteristics value for last release code from = 5 lakhs to >= 5lakhs.
then system will consider the release str for any value above 5 lakhs for that last release code,
rgds
gsc

I have released one PO with tcode ME28 but the PO is still be blocked

I have released my PO with tcode ME28, and the PO is in released status in header data of the PO.
But when I go to MIGO to post a GR, I still get the information that the PO not yet released.
Can anyone tell why and how I can proceed?
Thanks,
Eda

Hi ,
Please check the status of release in ME23N , it might be possible that you would be having more than 1 release to be made .
Check in ME23N how may release status are there and see to it that all the release codes are relesed .
Regards ,
Dewang T.

T.Code for Release Procedure for Purchase Order Type

Hi Frd
im working in ECC 6.0.
OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
Thanks
By
Pari

Hi Rajasekharan,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Actually the tcode for releasing purchase order is ME28
Reward points if useful.
Cheers,
Swamy Kunche

Release procedure for this concept.

Dear Seniors,
1) I had set release procedure already for contract and purchase order. Whenever i do po w.r.to contract, i have to release both contract and PO to do GRN. For example, consider vendor X and Y, i have contract for these 2 vendors and i have released that contract too. When i raise PO w.r.to that contract with vendor X and Y, it should not ask for release. How could i set that and where can i do that particularly for that two vendor X and Y? For remaining vendors, it should ask for release at PO level also. kindly suggest me please.
2) Normally if we set message determination for PO, we can see print preview before release also. I would like to see the print preview after release of that PO. Before release of that PO, it should not show me the print preview. How could i set that ? Kindly suggest me please.
3) I am having 400 plants, if i want to maintain 400 sloc for those plants correspondingly. Do i need to do that manually or is there any tcode to create sloc in mass ?
Kindly clear my doubt please.
Regards,
JanaMM
Edited by: JanaMM on Sep 9, 2009 8:02 AM

Hi,
Solution for 1)
Simple way to tackel this is to create saperate document type for PO s which are created with reference to contract
Solution for 2)
Use development by using BADI in PO.
us logic check field FRGKE(release status) in EKKO.
Solution 3)
Create BDC for the extation of storage locations.
T-code = MMSC
regards,
sujit

Release Procedure For Contract

Dear Gurus,
I have created a release procedure for Purchase Order.Now i created a Contract , it also asking for release.I dont know y its happening??
Is ter any link between Po release and Contract Release??
Plz Explain ....
Thanks in advance...........

Hi,
Whatever document types you give in release procedure will undergo Approval process.
Since you have given MK & WK, your contract has been blocked for release. Unless it is released, it cannot be used for further transactions, say creation of PO.
Tcode to release contract is ME35K.
Release it using your release group & release codes, Afterwhich you will be able to create PO with contract reference.
If you donot want contract to undergo release procedure, please do not mention WK or MK in values for doc characteristics. Give the document type of PO alone. Say NB (standard PO)
Regards,
Divya

Regarding releasing procedure for p.o.

hi sapgurus,
the configuration for p.o. release procedure is working perfectly but whenever i go to me29n or me28 i am getting two step release procedure but in industry if the manager has given excess to me29n/me28 then himslef ca release the p.o by means of clicking both release steps, that means without general manager review the manager can release the p.o by means of clicking both. hence i am willing to restricate each user's acess to other stepd release procedure.
examaple
in me29n/me28 :-
1) manager.
2) general manager.
in this case i want the manager to click on his resepctive release step and should not allow to acess the general manager's relase step's.
thanking you
praveer

hi,
please visit
www.sap123.com
there is a thread which explain very clearly for the release procedure for PO.
In PR (With classification0 there is only difference , you use CEBAN communication structure instead of CEKKO for PO)
Regards,
vijay

Release procedure for Document Park / Post

Dear FI experts,
We want to set release procedure for Customer Credit Notes (FB75)
For this we did following configuration -
FI >> FI Global Setting >> Document >> Document Parking (all setting w.r.t. release approval)
Created and parked a document using FB75.
In MM procedure we give the authorisaiton of Release code to respective users and then he is able to release the PO.
What is to be done in this case ?
What is the process / tcode for releasing this parked document.
Thanks & Regards
Rajesh

Hi Prem
Thanks for ur reply
I tried MRBR but system is giving following message -
There are no blocked invoices that match your selection
Message no. M8654
In MM release procedure , authorisation of Release code is given to respective users and then he is able to release the PO.
What is to be done in this case ?
Can you please explain??
Regards
Rajesh

Release procedure for Purchase Requsition and especially f. a document type

Dear Experts,
how can I establish a release procedure. I need to set up the procedure
without classification. But it depends on a document type.
I have been to the customizing section with spro
Materials Management/Purchasing/Purchase Requisition/Release Procedure
and have choosen "Set up Procedure without classification. ".
But can I assign a document type and how is the handling generally with.
Release Codes
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Thanks
Ilhan

Hi Ramesh,
You are saying:
"Click on the Release strategy button under item tabs". Where is this button.
All what I have is: Tab for "Material Data", "Quantities", "Valuation", "Account Assignment",
"Source of Supply", "Status", "Contact Person", "Texts","Delivery Adress", "Customer Data",
on calling of Tcode me54n I get immediatly a message
"Purchase Requisition 5000000131 can not be released" although I didn't enter any number in it
Why does it refer to a PR Nr. generally . I think it is pre-filled- How can I call this transaction without this message ? Or how can I call this transaction so that I can type in my own Purchase Rq-Nr.
Regards
Ilhan

Release Procedure for PO not getting applied

Dear All,
I have created a Release procedure for PO, for the field - Order Type. I have defined & followed all the steps i.e., Characteristic, Class, Rel. Groups, Rel. Codes, Rel. indicator & Rel. strategy.
Then i go to CL20N and assign object to class.
But when i create a PO & try to release it in ME29N it says 'Purchasing Doc. cannot be released"
The same release procedure was working fine few days back.
Kindly let me know if i have missed out some steps or someother settings need to be made.
Regards,

hi kedar
I tried that, still I get the message "No suitable Purchasing Documents found"
any settings to be checked in characteristics ?
Hey, and one more thing... everytime I exceute ME28 or ME29n, and later when i try to open Class...... i get an error message "Class type 032: Class <class name> being processed by <username>"
Then i have to go and delete in the locked entries, only then I can see the Class.
Rgds,

Customisation of release procedure

hi,
how to do the customisation of release procedure.
thanks
katrina

The aim of this release procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle. The person responsible processes the relevant document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This procedure provides for the release (approval) not only of requisitions (i.e. internal purchasing documents), but also of the external purchasing documents RFQ, purchase order, contract, scheduling agreement and service entry sheet.
1. Create Characteristics
2.Create class
3.Set up release strategy with classification
4.Create release group
5.Create release code
6.Create release indicator
7.Create release strategy
Important Transaction codes
ME51N Create Purchase Requisition
ME21N Create Purchase Order
ME54N Individual Release (PR)
ME55    Collective Release (PR)
ME29N Individual Release (PO)
ME28    Collective Release (PO)
Communication Structure for characteristics
CEBAN - Purchase Requisition
Commonly used fields u2013
BSART     Purchase requisition document type
ESTKZ     Creation indicator (purchase requisition/schedule lines)
EKGRP     Purchasing group
AFNAM     Name of requisitioner/requester
MATNR     Material Number
WERKS     Plant
LGORT     Storage location
BEDNR     Requirement Tracking Number
MATKL     Material group
GSWRT     Total Item Value
CEKKO - Purchase order
BUKRS     Company Code
BSART     Order type (Purchasing)
LIFNR     Vendor's account number
EKORG     Purchasing Organization
EKGRP     Purchasing group
BEDAT     Purchase Order Date
INCO1     Incoterms (part 1)
WERKS     Plant
MATKL     Material group
GNETW     Total net order value
The fields from EKKO that are related to PO release strategy
FRGGR
FRGSX
FRGKE
FRGZU
Check the tables for the release codes
T16FG
T16FS
T16FB
SAP Help : http://help.sap.com/saphelp_47x200/helpdata/en/75/ee14a355c811d189900000e8322d00/frameset.htm

Regarding releasing procedure

hi sapgurus,
the configuration for p.o. release procedure is working perfectly but whenever i go to me29n or me28 i am getting two step release procedure but in industry if the manager has given excess to me29n/me28 then himslef ca release the p.o by means of clicking both release steps, that means without general manager review the manager can release the p.o by means of clicking both. hence i am willing to restricate each user's acess to other stepd release procedure.
examaple
in me21n :-
1) manager.
2) general manager.
in this case i want the manager to click on his resepctive release step and should not allow to acess the general manager's relase step's.
thanking you
praveer

hi,
this will be defined in user authorisations by the basis guy.
regards
venga

Use of Release Procedure / status in Condition Table

What is the purpose of Release Procedure / Release status when creating condition tables ?

Hi
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Rwd point if it helps.
Reward points if it helps.

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

Creating a new "Class type" in release procedure.

Hi guys,
how can I create a new <b>"Class type"</b> in release procedure?

Hi,
But I do not know why anyone would create a new batch type for release strategies, it is totally unnecessary and provides no additional options. The class type indicates which objects can be classified and there is already one for release strategies.
You can create a new class or add characteristics to the existing class used in the release strategy anyway.
Ther is also NO WAY that two classes can be used in the release strategy and this new class type would not change this either???
Steve B

RELEASE PROCEDURE/ TCODE ME28

Similar Messages

Maybe you are looking for