PO Complete Release Strategy

I have a situation PO completed release
and fileds Net Price in PO is display mode
I want to fileds amount is display mode too.
Pls! guiding me, how can i do?

Hi,
You can use BADI "ME_PROCESS_PO_CUST".
Rgds,
Vaikunt

Similar Messages

Old PR release strategy - release completed status change

Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RS

Hi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

Issue with PO Release strategy

Hi experts,
I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
For few purhcase orders release strategy has not been triggered.
If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
Some experts can share their experiance in this regard.
And how i should proceed further with this issue.??
Thanks

Hi,
You issue in your system has 2000Nou2019s purchase orders with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
& when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
Cause for above:
PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
Action:
Its completely business call for business users to go for options:
Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
Regards,
Biju K

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

Creation of release order possible during release strategy

Hi folks,
we have currently contract and purchase order release strategy parallel in place. Both are working fine.
We are using quantity and value contracts.
Quantity contracts are changed frequentely by the business; with every change (adding new items, changing prices of existing items), the release strategy is pulled again.
Our release indicator is set to 6 and has value change 0,00%.
The business requirement is now to release a contract with status X (e.g. 10 items and a total item value of 10.000EUR). After release, call offs can be created for all the released line items.
If a new line item 11 is added, it should still be possible to create call offs for item 1-10 but not for item 11.
Item 11 should undergo a new release.
Has anyone ever come across such requirement?
I have tried version management. However, version management will only force a new release whenever the version is completed.
Even then, the complete contract is subject to release strategy and it is not possible to create call offs.
We dont want to set error message ME347 "Release orders against contract xxxx not possible (contract not released)" to warning, as this will allow to always create call offs regardless of the contract being released or not.
Any ideas greately appreciated.
Thanks!!

I suppose program checks in EKKO whether contract is released,, irrespective of version exist it or not. IF you are able to direct it to EREV, then may be version 0 or ( current - 1 ) released can be returned.
Isn't it a special case that your version 0 data is intact in version 1; Even if someone change lines 1 to 10 , with or without adding line 11, it still triggers version 1. How do you ensure that lines up to 10 are not changed. you may have to look in CDPOS CDHDR with object Revision..
This is just an idea which you may discuss with your developer to see whether a copy of the program can be modified..

Purchase order -- release strategy

Dear Friends,
I have a requirement for Purchase order Release.
The problem area is in purchase order ... there will be 2 Relase approvals
01 Mr. Abcd
02 Mr. Xyz
After level 1 approval and before level 2 approval ... i want to do some actions.. these actions are related to another product named savvion .
My question is can i stop the document to be edited by 02 ( Mr.Xyz ) untill i complete my process after 01( Mr.Abcd ) has finished his work.
This is to be done on top priority.
Please help me.
Cheers
Jitesh.

Hi,
Yes, We can stop the document to be edited by 02 until 01 has finished his work.
After 01 approved the document need to be correct, go to PO header menu release strategy TAB and 01 approved to be revoked (means double click on the tick mark, it will revoked).
Hope it is useful for you.
Regards,
K.Rajendran

Release strategy of contract disappeared after using of MEMASSCONTRACT

Hi All,
May be some one can help me?
I have next problem it tr. MEMASSCONTRACT(ECC6)
Release strategy of contract disappeared after using of tr. MEMASSCONTRACT. I know why it happened, but I don't know how to correct it. Some time ago IN ECC5 we added a field to a table EKKO and used this field as one of characteristics in the release strategy of contracts. In order to transfer value of this field to field CEKKO-USRC1 we used User Exit EXIT_SAPLEBND_002. This User Exit is suitable only for online transactions (ME31K, ME32K). How can I feel field CEKKO-USRC1 in transaction MEMASSCONTRACT?
Regards, Liza

Thank you. Probably I didn't explain my problem clearly. It's section of code from User Exit EXIT_SAPLEBND_002:
ATA: reference(20) TYPE c VALUE '(SAPMM06E)EKKO'.
DATA: it_ekko TYPE ekko.
FIELD-SYMBOLS: <ymm_icl> TYPE ANY.
e_cekko = i_cekko.
*THE "ICL Contract" FIELD IS ONLY RELEVENT IN THESE TRANSACTIONS
IF sy-tcode EQ 'ME31K' OR sy-tcode EQ 'ME32K'
OR sy-tcode EQ 'ME33K' .
ASSIGN (reference) TO <ymm_icl>.
it_ekko = <ymm_icl>.
e_cekko-usrc1 = it_ekko-ymm_icl.
ENDIF.
Program SAPMM06E can only be reffered while using online transactions. Mass transactions does not use these program and it is completely class based. So, may be someone know how can i do the same , but for tr. MASS in ECC6.

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

Deleted purchase order with release strategy

Hi all,
When PO are deleted, the release strategy is disabled. However, if you mark final invoice and delivery completed indicators, the release strategy is triggered, even if the po is deleted.
Is it possible to disable the release strategy when final invoice and delivery completed indicator are marked?
Thank you for your answer

The technical expert in my team has found the explanation to that problem:
A deleted item is "statistical" => there is no release strategy (standard control in ME_REL_STRATEGIE_EKKO function module)
But if ''final invoice'' and ''delivery completion'' are marked, the item is NOT statistical (standard control in LMEPOF4X include)
Therefore, a release strategy is redetermined even if the item is deleted
Thank you all for having tried to help

How to determine the right PR Release strategy

Hi Experts,
Could u help me to solve this problem!
As our business, we want the system automatically determine the right Release Strategy based on the total Amount(amt) of PR such as
- if PR total amt <= 1000 USD --> must checked by only Department Manager (DM)
- if PR total amt >1000 USD --> must checked by Department Manager (DM) and General Director (GD)
so i've already configured system like that:
1. Create characteristic : CEBAN_GSWRT (Structure CEBAN ; Field GSWRT)
2. create anew Class CEBAN_GSWRT, which associated with above Characteristic
3. Create release Group "03", which associated with above Class (CEBAN_GSWRT) and cheked "Overall Release PR"
4. Create Release Code DM ; GD
5. Create two Release Strategy such as:
5.1. Strategy 01 - DM Only, which have only DM release code & assigned to class CEBAN_GSWRT and the value identified here is <=1000 USD
5.2 Strategy 02 - DM -GD , which have DM & GD release code & assigned to class CEBAN_GSWRT and the value identified here is >1000 USD
then, i created two PRs, one have amt <1000 USD , another >1000 USD, but the system alway get the same Release Strategy 01,its mean that system allway apply the first case Amt of PR <1000 USD.
Note: In the Document Type i checked Overall Release also!
So, pls help me to show out wrong or missing steps!
Thanks in advance
Vietttq.
Edited by: viettq on Sep 1, 2009 4:32 AM

Hi,
Please open the below link, it will help you to understand the complete step by step process:
http://www.sap123.com/showthread.php?t=59

New release strategy / Old PReqs

Hi,
New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
Many thanks in advance for your clues.
Regards,
Grzegorz

Hi,
Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

Release Strategy for Credit Note un the QM Module

Good SAP Guru's,
I have a very important question for you:
Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
This should work on the same lines as the Purchase Order Release strategy.
Any guide lines and/or assistance will be gratefully appreciated.
Kind regards,
Leslie

Dear Leslie
We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer a notification will be trigered to manager and if he approves it will go for higher approval.
Please find my suggestion for this development
1) Make 3 task codes. for eg Task 1 for credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
2) According the need of the credit notes to be created let the user assign the task and release it.
3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
6) The credit memo creation will have to be developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
please let me know your apprehensions
Regards
gajesh

Why PO is automatically assigned with release strategy?

I created a PO with PO document type NB and NB is not assigned with any release strategy.
But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO. Why?
And only when the PO is in held status, there is no release strategy assigned to NB PO.
Is the normal ERP behavior?
I only assigned a release strategy to PO document type DB, which means dummy document type.

Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

Release strategy PO/PR

Hello
Why we use structures CEKKO and CEBAN only for releasing PO and PR. why cant we use tables EKKO and EBAN or anyother table.
Anjan

Hi,
As I have said, this is something that I can't answer, I am not that technical.
But what it COULD be is as follows.
The Characteristics of a class have values and when you classify an object the value is stored.
In SAP you can allocate a table and field to the characteristic so that the data from the field on that table can be automatically used as the characteristic value.
For example if we were to create a material characteristic called "Unit of Measure" we can allocate the material master table MARA and the appropriate field from that table to the characteristic "Unit of measure" on the value tab in CT04. This means that if we then classify a material with the class that contains this characteristic, we don't have to enter the UOM, the system picks it up automatically from the MARA field.
BUT (and it is a BIG BUT), when we are using the classification functions in the release strategy we are <u>not actually classifying anything</u>. The PO does not actually get classified, the system just uses the classification <u>functionality</u> to check the values of various fields (characteristics).
So if the PO is not actually classified (like you would classify a material etc.) then the systemn cannot just use the field from the PO because there will be no classification record to store this on. The classification as such is purely temporary and so it has to use a temporary structure (such as CEKKO) so that nothing is actually stored or affects the actual EKKO table?
This may be completely worng, but until anyone can give you a firm anser to your question, then this is the best reason I ncan think of for having to use CEKKO instead of EKKO (because this is a temporary use of the class, the PO is not actually claassified as such).
Steve B

Processor of PR item level release strategy

Hi All,
I need to pass the Processor determined from an item level Purchase Requisition release strategy to a WF container. The event is RELEASESTEPCREATED in BUS2009. I have created an import element container called 'Processor' from ABAP dict. data type MEACTOR.
In the binding for the WF trigger RELEASESTEPCREATED I cannot bind the 'Processor' wf container to the Event Object.
What are the steps which I must follow to add the 'Processor' to the RELEASESTEPCREATED event?
The release strategy in SPRO for item level Purchase Req release is complete and the Set-up procedure for Workflow is complete.
Thanks
Mike

Hi,
Go to SWO1, enter BUS2009. Click on create subtype icon there. Then enter all fields as say ZBUS2009. Now save your new BO. then implement and release it , i.e;
Edit> Change Release Status> Object type> to implemented. Again Edit> Change Release Status> Object type> to Released. Then go to events in this objects. Click on event RELEASESTEPCREATED. Then click on event parameter and create a event parameter.
Hope this solves your problem.
Don't forget to delegate ZBUS2009 with BUS2009 in SWO6.
Let me know if you have any queries.
Regards,
Raj

PO Complete Release Strategy

Similar Messages

Maybe you are looking for