PO Release strategy release procedure

Hi
Any body can suggest
what is the procedure for release strategy transport to anther system means D to Q

Hi,
Release strtagy Configuration can be transported from one client to various client[Like creation Class,characterstic,Release code,release strtagy definations etc]
Where as assignments of Objects / class and various parameter for release strategy has to be done in individual clients in -T-code: CL24N.
Example : For Class -PO Release we need to assign -Values for Class -characteristic values has to assign in CL24N
with regards
Shrinivas Gangoor
Edited by: Shrinivas Gangoor on May 22, 2009 3:06 PM

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.

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

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.

Service Entry Sheet Release Procedure

Dear all,
I want to assign a new Plant to an existing service entry release strategy. In CL20N for Class Type 032 and maintaining the Release Group and Release Strategy I want, I hit ENTER and the Class SERVICE_RELEASE is displayed, which is correct (it is a service entry release procedure).
Selecting the item and displaying the values for the Class, I have Plant, Order Type and Cost Centre. I added a new row, include a new Plant and hit Save. I get the message "Saving changes to assignments" and then I exit the screen.
However, to double check that the object has been assigned to the class, I check in SPRO>Materials Mgt>External Services Mgt>Define Rel. Procedure for Service Entry Sheet> Release Strategies to confirm that the object was created in the classification for service entry release procedure. BUT IS NOT THERE!
However, if I performed the assignment in Classification in SPRO for the release strategy, and check in CL20N, IT IS THERE!!
How come I have created in CL20N and it is not displayed in SPRO for the same release strategy? The object assignment was successful with no error msg. It is not possible that you have done it in CL20N and you have to do the same in SPRO, right? Doesn't serve the purpose..
Pls help.
Thank you.

Dear Sir,
Go to CL02 give the Class and Class type, click on change icon
Copy the characteristic of Plant from Char. Tab
Then Go to CT04
give characteristic which is copied from class and click on change icon.
enter your new plant in Values tab, Save back
Go to CL20N, give release group and release code for which you want to maintain the new plant.
give the plant and save enter.
i hope this will help you.

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

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

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

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

Release procedure with classification not getting triggered

Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachin

Hi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM

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

PO Release Procedure Setup

I have configured the PO release procedure for PO with header value of more then 25000. In the process I have created the following -
1. Custom Characterstic
2. Custom class
3. Release group
4. Release code
5. Release indicator
6. Release strategy
but the problem I am having is that the workflow event 'ReleaseStepCreated' is generated in the system even for PO with header value of less than $25000. Also the 'Release' tab is not appearing in the PO header.
Please help. Appreciate you time.
Sridhar Jami

I think this issue is also related to mis entries in SWEC.
Go thru' this Note 797775 - Entry in Transaction SWEC hinders workflow. Verify all the steps stated in this note even you think it might not be the right note.
Regards, IA

PR release procedure

Hi,experts
Good Sunday.
I finished the configuration of PR release procedure,but it is not effective as I created PR.
My scenario of PR release procedure:
1) Create two characteristics Z_WERKS,Z_GSWRT mapped by CEBAN-WERKS and CEBAN-GSWRT.
2) Create a class Z_PR_REL_CLASS includes above two characteristics.
3) Create a release group named AA refer to class Z_PR_REL_CLASS.
4) Create three release codes L1,L2 and L3.
5) Create two release strategy S1,S2
S1 limits the PR total item value small and equal than 1000 RMB.
S2 limits the PR total item value great than 1000 RMB.
Yes, I finished the details of the above configurations,
However, I created several PRs with the various total item values,the corresponding S2 release procedure is not adopted.
I don't know what the problem is.

Hi,
All configurations done by you are correct. I doubt, you have selected Overall release for PR or Item wise release of PR.
IF you have selected Overall release , than you need to choose GFWRT instead of GSWRT from structure CEBAN.
Also, check in step -'Check release strategy', if everything is in Green.
If all of above is correct-
Check values in Classification tab of S2.
It should be >1000 RMB.
Values in Classification tab of S1 -
Its should be 0.00 - 1000 RMB
The characterstics Z_GSWRT, Should have flagged 'Interval Allowed'
Regards
Pushpam
Edited by: Pushpam Rastogi on Feb 22, 2009 9:04 PM

Purchase requisition release procedure through User-Exit

Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan Tiwari

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

Release Procedure - Currency

Hi,
I have release procedure for purchase order with value as one of the characteristics.
Now my characteristics has USD, however i need to incorporate the release for other currencies like EURO, Yen etc.
Let me know what should be my approach.
Regards
Raghavendra

Hi
Create New charactaristic for currency using structure CEKKO and field WAERS
Add that to ur class and configure release strategy
Vishal..

PO Release strategy release procedure

Similar Messages

Maybe you are looking for