About release procedure

hi sap guiders
any body can explain me the procedure of "release Procedure at Item level with using classification"

Hi Lucky
Sorry for interrupting but this is told many times that Purchasing documents(PO,RFQ, SA and Contracts) can only be released at header level and not possible to release at item level.If you observe there is a basic logic behind this PO is released to Vendor which is a external party and you never wanted to send the same PO multiple times to the vendor as and when item release takes place.
where in case of PR it is a internal document and you can get initimation any number of times as it is not going out of your company.
having said that if still you want to release a PO at item level then you can achieve it in 2 ways but both are not advisable and it is like cheating the system.
1) Suppose you want to release a PO based on material group which is different for each line items(say 5 are there in your PO). now 1 st thing you should this charaterictics defined under release strategy. then in CL24N you should have a value X for material group. now you have to keep in mind that this X should always be there in line item number 1 in the PO as a value for material group. as system will search for 1st line item and if this value matches with CL24N then it will release your po. but still basic purpose will not get solved.
2) In CL24n do not assign any vaue to material group , leave it blank. then also system will allow you to release the PO.
Request you to please check both the cases and let me know the results.
regards
Yogesh

Similar Messages

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.

Release procedure problem and error

Dear Friends ,
I facing some major problems in release procedure , i had configured one release procedure in 4levels , due to some reason i had deleted 3release groups and codes due to it was not working . But after deleteing in purchase order it showing all release level and only firest level is working unable to make MIGO and other release levels are not working . The relese code which i had created is appearing in RFQ/CONTRACT etc automatically . I had not created for this any release level . It's very very different case ....till date never faced and heared . How to resolve this probelm . Due to what reasons this kind of problems occurs .
RB

Hi,
Try to delete all the release procedure available in the system.
First try to do the documents coorectly and configure.
You might have done mistake in assigning the charcteristics to the class
Please try create a NEw release procedure once again.
Don't worry about the procedure in the RFQetc...
G.Ganesh Kumar

Release Procedure for Quantity Contract

Dear All,
We have a business requirement to ensure that Quantity Contracts are released by the Account Receivable Accountant before the Sales Support Staff can create Sales Orders against them.
Process : Create Quantity Contract (VA41) -> Release Contract (VKM3)->Create Sales Order (VA01)
Currently, users can create sales order against the quantity contract before the contract has been released.
I need guidance on how to implement system control to prevent this creation of Sales Orders before Quantity Contracts are released..
How can i configure release procedure for quantity contract?
Any assistance will be appreciated.
Many Thanks

Hi
There is a concept of User Status / Status Management in SAP. By using this you can set status as default that is Blocked, and then the authorised person can release the document, only after that a person can create an Order, with reference to that Contract.
The Customisation setting is in :- IMG> sales and Distribution>Sales > Sales Document>Define and assign User Profile(T Code is BS02)
To know more about this you can search the Forum, also check the below given Link:-
[http://web.mit.edu/sapbiz/docs/Explanation%20of%20Status%20Management%20functionality%20v3.doc]
[http://help.sap.com/saphelp_crm40/helpdata/en/73/29943a7acb9023e10000000a114084/content.htm]
Hope this will help you.
Regards
Amitesh Anand

Need information about release codes

Hi,
I need information about release codes.In which Transcation we will get it.
Please give the information ASAP.
Regards,
Chow.

Hi Naidu,
Release code is a two-character identifier with which a person responsible for processing a document can release/ approve an item of a purchase requisition, a complete purchase requisition, or a complete external purchasing document, or cancel a release.
If a link to SAP Business Workflow has been defined for the release code, the person can refuse to effect release (withhold approval), thus rejecting the item or document.
You can find the relelase codes Using the following path :
Go to Transaction : SPRO and click on SAP Reference IMG and follow the menu :
-> Material Management ->Purchasing->Purchase Requisition->Release Procedure ->Procedure with classification -> Setup procedure with classification
Hope this helps..
Thank you
Srinivas

Re-Activate Release Procedure anytime when perform changes in PO

Hello,
I need to know how can I reactivate Release Procedure in PO, anytime the PO was changed in Header or Items, doesn't matter what type of change is.
Let say if I will fix by user exit,
What fields told me there is a change in PO?
What fields I need to modify to reactivate the Release Strategy for PO?
I appreciate any help.
Hector

hi,
PO release strategy will get set again if and if u have increase the old net value of po,
but in this scenario u suggest ur client about the version management, PO version will get updated if u make any change in document nad new version will be created.
i think clinet is more concern that any change in PO document must be noticed
so i think version management is good option
regards,
pankaj

Can you any body tell about release codes in workflow

Hi,
Can any body tell about release codes in workflow.
Regards,
Boddu Rosaiah.

Hi Naidu,
You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet

RELEASE PROCEDURE THROUGH WORK FLOW

Dear Sirs,
        How to configure Release procedure through work flow for the purchasing documents? Which are the modules integrated for this configuration? Kindly
give me the procedure in detail.
Regards
Yoga

Hi Anand,
    Thanks for your response. In my question I had not mentioned about the criteria.
The criteria for release of P.O. is on the basis of net value of the P.O. and there are
two levels of approval as follows.
If the Value of P.O. is less than Rs.50,000/=, approval of level1 is required.
If the Value of P.O. is greater than or equal to Rs.50,000/=, approval of both level1 and level2 is required.
    1.If the value of P.O. is Rs.30,000/=, then it should appear in the mailbox of level1 only. It should not appear in the mailbox of level2.
    2.If the value of P.O. is Rs.60,000/=, first it should appear in the mailbox of
level1 and after the approval of level1, it should appear in the mailbox of level2
for next level of approval.
    Is there any detailed documentation available to cofigure the above scenario.
Regards
Yoga

Return Order Release Procedure

Hi,
I have a PO Doc Type for Returns, and I want to implement a release procedure that will check the Expiration Date of the Batch. If the expiration date is within three months for example, the RO will be blocked and cannot be released. Is this possible? Or is there another way to go about it? I just need to block the creation of a Return Order if the material is within three months of expiration.
Thanks,
Lee

Hi
You have to use user exit for PO creation, which will trigger when u are raising the return order with return order document type.In this exit, u can write a logic to check the whether the expiry date is within the three months or not?. If it is within the three months, you can configure a error message in the exit it self so that it will block the creation of PO.
Regards
Ramakrishna

Release Procedures-Classification

Hi Gurus,
I am working on Release Procedures. I know where to use with Classification and without Classification. But I am not pretty sure what is this Classification. If any body knows more about Classification please explain me.
Thanks in advance
KK

Hi
The following link is very useful. I got this link from this forum only in "new to MM/WM" section.
http://www.sap123.com/showthread.php?t=59
Regards,
Jagadeesh

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.

Report with information about release documents in VKM1

Hello
I need to know if exists some report that gives me more information about release documents in transaction VKM1. What user releases some document? How many documents a credit account had been release or block in a year or between dates?
The transaction VKM2 just gives the release date of the document and not the user.
Where I can find more information?
Regards
Daniel Teles

Hi,
There is a field to know which account is the parent account, but you can't have others informations from the parent account except the name. In the new R16, you have others field called "Parent Account external unique ID" and "Parent Integration ID". What can I do with this field? Is it possible to display the parent account phone field in the report?
regards

Creating a new "Class type" in release procedure.

Hi guys,
how can I create a new "Class type" 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

How restrict the release procedure tab in ME21N

Hi,
We have the Condition tab for free goods Iin PO.
Now, we want to implement release procedure in PO, and also restrict the release procedure for free goods in the same based on the combination of document type (EKKO-BSART) and free goods (USMON)field. Please provide the solution.
Regards,
Mars.

Hi
Try using the exit M06E0004.
Regards
Shiva

Error in Release procedure for PO

Hi
I have created a release procedure for Purchase groups and plants. But now I want to add a new Purchasing group to the same strategy. How to do this.

Hi Garapati,
Release strategy is configuration in customisation screen. Do not merely do assignment of object via CL20N or CL24N. Though assigning the object would work, but is better to do it in customisation.
Go to this path: -
SPRO>IMG>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Order (Execute)-->Release Strategies
Go to: Position>Identify the Group> Identify the Release Strategy code
(How to know what is the release strategy code? In the PO where a release strategy for this value and characteristic is triggered, you can go to the Header-->Release Strategy tab, you would be able to see that the release strategy is triggered. Simply remember the release strategy code. If you already know the code, ignore this step)
When the search is complete and located the right release strategy that you want to amend, select it and click on Details.
Inside, go to Classification. Check that this release strategy contain the characteristic that you want to amend. You would be able to see the Characteristic "Purchasing Group" already maintained. Click on Purchasing Group line and click on "Add rows" icon below, then key in the the Purchasing Group value that you want to add.
Hit Back, and then Save this customisation.
Now, the PO release strategy will trigger the Purchasing Group you just added if the PO details entered matched the Purchasing Group, Plant and Document Type value that you maintained for this release strategy.
Hope this helps.
Rgds.

About release procedure

Similar Messages

Maybe you are looking for