Block PO in ME22N - release strategy

Hello Abapers,
I have been trying to block a PO under the following scenario.
A user creates a PO for 1000 and submits to manager.
The manager approves the PO.
The user amends the PO and reduces the amount.
What the functional guys want to happen is that in this scenario, the PO should be blocked until the PO is reapproved by the manager.
I have tried user exits and BADIs and have changed the field EKKO-FRGKE to 'B' (blocked) upon saving when the conditions are met.
When I look at EKKO in SE16, the field FRGKE = B, so it looks like the change was successful.
However, when I look at the PO, the tab for 'Release Strategy' in the PO header is missing. The functional guys assure me that this tab should be visible.
So, my question is, is my logic too simplistic (changing EKKO-FRGKE to 'B' )?
Should I be changing data for the release strategy as well?
Thanks in advance,
Kevin

Thanks Christine.
I know that functionality is already in place using classification characteristics, that if the PO is over a certain amount, then the PO is blocked.
However, the functional guys told me that it is not possible to check for reductions in PO amount using classification data.
I will check out the FM in your post.

Similar Messages

About ME22N (Release strategy)

hello All,
currently i am working on me22n . i want to fix the below issue.
When a purchase orders price(net price) / (PO quantity)quantity has already been approved at a higher dollar amount, they should not have to go through approval process for a lower dollar/quantity amount. Currently it does not go through re-approval if it is lowered in the same level, but it does go through re-approval when it is lowered to a lower level.
In this case what should i check for first. What are the user-exits that i should look for.
Please reply. Thank you for your help in advance.
Sidd.

Hello all ,
Exact problem is,
The PO has been approved all the way thriugh all 5 levels. The original cost of the PO is $120,000.
Now , The PO price in the Net Price field was then lowered to $95,000.After the price was lowered, it canceled all of the approvals and retriggered the approval process. If the Net Price is raised, then the approval process should be retriggered, and it is; however, it should not be retriggered if the Net Price is lowered.
The same thing happens when the quantity is changed to lower the price. The original PO has been approved all the way through for 120,000 pcs at $1 for a total of $120,000.
When the quantity is changed to a lower number to bring the price down to another approval level, the approval process is started all over again.
Can anyone suggest me the way..
Thank you for your help in advance.

Release Strategy in Purchase Order

Hi,
Can any explain the usage of Release Strategy in Purchase Order.
ganesh

Hi Ganesh,
Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
Hope this will give u a better understanding on the function of a PO release strategy.
Rgds.

PO release strategy - blocking item

Hi SAPers,
I've put a PO release strategies on quantities and prices, my problem is that when i have many items in the PO, i don't see which one is blocking !!
do someone know about a way to identify easily (for users) the blocking item, or even a way to flag the blocking item
thanks
zak

Hi,
The PO is always released at the header level and not at the item level as is the case with purchase requisitions .
If you have put quantity as the characteristic then it will add up the quanitity of all the line items and cheks whether release strategy is applicable.
Kindly award points if helpful.

How to block PR creation with no release strategy

Hi,
We have this PR release strategy implemented. Currrently, user are able to create the PR even there's no release strategy determined. Thus, PO can be created as the processing state is "02 Active".
Would like to block user from creating the PR if there's no release strategy determined. How should we do in order to achieve this?
Many thanks in advance.
Sue

Hi Sue
Assuming that you are using release with classification.
Create a new characteristic for PR document type (CT04)
Attach this characteristic to your Class (CL02)
Create new release strategy and in Characteristic data you will have to assign all your PR document type. This will ensure that all the PRs need to be released.
Regards
Rajesh
-Do reward if this is useful.

Affect on release strategy by ME22N

Dear All,
I want to know that in which scenarios, ME22N will affect the release startegy in a relaesed PO or under release PO like any change in PO or some standard scenarios.
Thanks with regards,
Ankit Gupta

Hi,
Release startegy :
In the standard system, Release strategy will trigger changes in PO are done in to the quantity,unit of measure, or price .
This is controlled by Changeability indicator in release strategy.By this you can determine that release procedure will restarted if purchase order changed & value of item is increased by certain percentage or any change in the value.
Thanks,
AMIT

Badi for release strategy me22n

details Code for released status strategies on tcode me22n with function module .

please check there is BADI ME_PROCESS_PO_CUST for PO Process and checks can be built in various method availble in BADI before PO release. For release strategy check user exit EXIT_SAPLEBND_002 .
In case of any other details do revert back.
anya

HOW TO BLOCK A RELEASE STRATEGY

Sir,
ply help me in blocking a release strategy as in i want to configure a new strategy
ply help
regards
amey

hi,
You can do the blocking of current release strategy via:
removing the connection of the release group to the release class and then deleting the release strategy parameters inside the release strategy tab under spro settings ...
Paul,
If we only remove the characteristics, system also determines internally,,, then will it be deactivated??
Regards
Priyanka.P
Edited by: Priyanka Paltanwale on Apr 27, 2009 4:52 PM

Send purchase order e-mail with release strategy

Hi!!
I have a problem with sending e-mails in purchase order that are blocked with release strategy.
I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
Somebody knows what is happening?
I would like to send e-mails without previous modification of the purchase order.
Thanks for your help.

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
**Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

With a lock item in a purchase order, release strategy works?

Dear All,
I have a very important question for myself.
I have a purchase order with only one item.
I have set this item to locked.
Release strategy works without problems.
Is this situation correct?
I don't understand it but maybe the release strategy works normally too....
Please help me with a explanation
Thanks in advance

Yes, if a release strategy is applied to a PO, then even if you block / delete an item, it will still have the release strategy.
This is standard behaviour, because you can later remove the deletion indicator or unblock the PO, whence the PO will again have to go through the Release Procedure.

Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

User Exit/BAdI for transaction ME22N - Release status of PO

Dear All,
Requirement: Irrespective of any change to a PO having its release indicator set to approved, the release indicator must not get updated.
As of now, editing a PO (using ME22N) leads to the updation of release group, release strategy and release indicator - this should be prevented from happening for all POs that have a release indicator set to Approved.
We know that in the system, this is determined in the FM ME_REL_STRATEGIE_EKKO. However we are using the version 4.6C and not being able to find a suitable user exit or other enhancement option. Can someone help us with a way to prevent this change from happening.
Regards,
Nimish

Hi,
Did you check the BAdi: ME_PROCESS_PO_CUST.
Reddy

Block PO in ME22N - release strategy

Similar Messages

Maybe you are looking for