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

Similar Messages

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

Regarding Release Procedure with classification

Hi All,
Please anybody tell me,is't possible to release at item level in external document like PO,RFQ.
Thanks & Regards
Suresh.

In principle you wouldn't send (/release) part of an external document.
The information at Header level applies to the whole of the document, in other words it can also be considered as applying to each item. For example the payment terms apply to the whole of a PO, not the individual items. The individual items can not be considered complete without the Header information. Consequently the release strategy is set at Header level.
In theory all POs may be created with reference to preceding documents and these may be released at item level e.g. Purchase Reqs. Therefore at the time of creating the PO the individual PR items have been approved from a business point of view, the PO typically represents the overall commercial approval for the items.

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.

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

PR release procedure problem

We are using SAP 4.7 EE Version.
Regarding PR release procedure, I have created PR release procedure by using characteristics with Plant, Total value of the item, document type, creation indicator and account assignment category.
Created class PR_RELEASE with above-mentioned characteristics. The same is used in PR release procedure.
When I am creating PR, the release procedure not picking up for standard procurement (stock material) account assignment category.
We have identified the problem with account assignment category u2018 u2018 (Standard) while creating PR. For other account assignment categories (K, U, X, A), it is working fine.
Recommend any SAP note numbers if you have or known.
Points will be rewarded.
Thanks,
SK
Edited by: s k on Jun 9, 2008 2:11 PM
Edited by: s k on Jun 9, 2008 2:12 PM

Hi
Blank Account assignment does not work, as you cannot create a chracteristic Value as Blank.
You need to create a new release strategy without the account assignment category chracter.
Or remove the account assignment Chracterisitc from the release strategy
Thanks & Regards
Kishore

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

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

How to configure release procedure for rate contracts release

Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
                if c1 is not there c2 has to be approved
     Change in the value of the rate contract contract
     Change in the validity of the rate contract
     Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskar

Hi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

Work flow in Release Procedure

Hi all,
What are the steps involved to configur Work flow for the Release of Purchase
orders?
Yoga

Hi Yoga,
Work flow can be configured for release procedure through userexit M06B0001.
U need to assign the user id to the respective Release codes. Once this has been done, then u will get a mail in Business workplace inbox upon creation of PR/PO. If u double click the work flow item it will take u to ME54n transaction for approval. We have to take Basis team help to define authorisation for Each user. Since the User has to approve only for his relevant role.
Hope this helps a bit.
Reward if u find this useful.
regards
Anand.C

Purchase Order release procedure

Hi All,
My client is having following requirement for Purchase Order release procedure.
Plant 1                    -    1 Release code (Manager)
Plant 2             -    2 Release Codes (Manager, Sr Manager)
Plant 3             -    3 Release Codes (Purchase Officer, Manager, Sr Manager)
All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
Thanks & Regards,
Nagi

Hi Nagi,
In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
Refer the following thread and revert if any confusions...
http://**********************/2008/11/release-procedure-release-strategy-main.html
Regards
Shiva

Effect of payment terms on release procedure

Hi gurus,
Will their be any impact of payment terms on release procedure of purchase order?
As and when we change payment terms in a PO which is released earlier, the release procedure tab is getting disappeared
I hope my question is clear
Kindly reply soon
regards,
prasad

Hi Prasad Sathya
Be sure that Payment term in Po will not have any impact on release procedure. if u check the Table CEKKO throgh T code SE11 , there will not be any field for payment term. then how to create characteristic for the payment term.
and it is not logic to create Release procedure based on the Payment terms
friendly
Manickss
pl don't forget to reward if helpful

Purchase Requisition Release Procedure Modification

Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
Sriram

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

How to close an open PO of partial GR and release procedure

Hi friends,
I would like to know how to close an open PO where partial GR has done on it and release procedure exists for that particular PO.
I would also like to know if Invoice is not done for a PO and GR is done, then can we call it as open PO?
Please clarify
Thanks
Jyothi

hi antony..
thank u antony a lot...i ve tried it and working fine..
but can we go in me22n to tick delivery complete for a PO which has already been released? it is showing "u cannot make change because it has already been output
regards,
jyothi

RFQ release procedure deactivation

Hi Experts,
I have configured PO release strategy & its working fine.
But even its applicable to RFQ. My client dont want release strategy for RFQ.
How to deactivate RFQ release stategy.
Please suggest.
Thanks,
Jack

Hi,
Create NEW Release characteristics as purchasing document category CEKKO-BSTYP and during release strategy design you can keep VALUE as F for Purchase Order and save withy other vital release values.
This will not effect release procedure for RFQ or automatically deactivate release process fro RFQ and only Applicable for Purchase Order ONLY!
Regards,
Biju K

Regarding releasing procedure

Similar Messages

Maybe you are looking for