UserExit required - Do not Create PO without Release Strategy

Hi
My requirement is Do not Create PO without Release Strategy.
When user try to save PO, it should not allow to save, if it does not have Release Strategy.
For this scenario, we require which UserExit.
If UserExit, can you guide me which userexit and the following steps.
For this scenario, which is the best way to control.
If you got anyother options other than userexit can also be advised.
Pls advise me.
With Regards
Kamesh

Hi Shailaja
Very thanks for your reply.
Some more doubts,
I think Release strategy data will be populated in I_EKKO table.
I can use fields from I_EKKO-FRGSX & FRGKE.
If these fields are initial (ie) PO without release strategy, I want to exit PO without saving - Creation.
So here can i put Error message if the fields are initial.
IF i put Error message then the PO screen will be block ? in that Error message.
Just want to confirm before testing something with the Exit code.
Is this the way to proceed.
Thanks in advance,
With Regards,
Kamesh

Similar Messages

Requisition without release strategy

Hello everybody
Is it possible to block create purchase orders with reference to requisition without release strategy?
Example:
1. Purchase Requisition 100887 with release strategy R1 <> Purchase Order 300 created with reference to PR 100
2. Purchase Requisition 100888 without release strategy <> Purchase Order cannot be created.
Thank you for help in advance
Arek

Hi,
If you have seperate document type for PR's for release strategy
You can remove the link of PR document types to purchase order document types
other than release startegy in
Purchase order document type customizing spro>mm>purchasing>PO>define doc types>link to PR
this will not allow PO's to be created without Pr's having release strategy
BR
Diwakar
reward if useful

Not able to view release strategy tab in pr(change mode)

Hi,
i have created a pr at DEV and i am not able to view release strategy tab in change mode at DEV. please help???

Hi,
Please check if you activated the user exit EXIT_SAPLEBND_004
(Include ZXM06U31) This exit is relevant for the overall release.
If you activating the userexit, please ensure that you implement
the coding line E_CEBAN = I_CEBAN. in the include
. Please refer to point 3) of the attached note 365604.
BR
Nadia Orlandi

Incorrect Release code called which is not defined in a Release Strategy!

Dear Gurus,
I am facing a problem in Release strategy for a specific Purchase Requisition document type. My Release Strategy has two Release Codes for the Approval of a PR. When i create that document type of Purchase Requsition, Same Release Strategy is called, system picks the Two release codes from my Strategy but also pick another Release code which is not defined in my Release Strategy.
Kindly help me and let me know.
Thanks in Advance.
Johi Kapoor

Hi,
In Release Simulation (segment of Release Statergy), just click and you will have small pup up screen and there just double click the release codes all you have and you can see all unwanted release codes will be dissapeared and you have only now needed release codes what you configured for the release statergy. Now similuate release & set/reset release .
Regards,
Biju K

Purchase requisition not subject to a release strategy

Hi All,
When I will release PR, appears Error: "Purchase requisition not subject to a release strategy". I've check the configuration, but it was appropriate. Can anyone help me to find the solution?
Regards,
MamaRara

hi
In our case also we have faced this problem
Usually when you are executing ME54N the system displays the latest viewed / modified PR.
Hope in your case the latest PR viewd / modified is not subjected to release. Hence it is showing the message
Go to ME22N open your PR - Press save button. Then try to open the same in ME54N.
Hope this will help you
SAS

Contract without release strategy

Hi Gurus!!!
I have an issue with contracts that withour release strategy. it happens because in the contract there are more than one item and those items must have the same material group. If it's not equal the release strategy is not added to the contract but if they are equal the release strategy is added.
Message error: Purchasing document XXXXXXXXXX not subject to release strategy.
Is there any way to put more than one material group in a contract?

Dear,
For OVERALL RELEASE (purchase order, Contract) the item fields such as Plant and Material Group will be aggregated to header level.For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header.
So please maintain a Blank value in CL20N if you have multiple material group
For more please refer SAP note 47089
Edited by: redriver on Dec 8, 2011 1:45 PM

How to not create File without any payload?

Hi XI Experts,
I have the following integration scenario:
1. One input file
2. One or more output files (up to four files)
3. At any given time, I could have one or more files (up to four files) filled with data in the payload.
Question - there are times where only one file will have data in the payload and three files without any data in the payload (by design). In this case, I do NOT want to create files that does not have any data in the payload. Is there any way I can do this without BPM? The output files that does not have any data in the payload is not going to be 0 byte as it will still have blank XML tags.
Again, we do not want to use BPM if there is any way around it. We are running XI 2004s SP7 (equivalent to 2004 SP16). Any help would be greatly appreciate it.
Here is the content of the ouput file WITHOUT any data in the payload:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:entity-data xmlns:ns0="urn:dow-com:xi:data:vendavo:10">
</ns0:entity-data>
Here is the content of the ouput file WITH data in the payload:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:entity-data xmlns:ns0="urn:dow-com:xi:data:vendavo:10">
    <com.Dow.customer.DCorporate>
        <VName>DCorporate</VName>
        <VLabel>013-ZZ</VLabel>
    </com.Dow.customer.DCorporate>
</ns0:entity-data>
Thanks,
Jay

Hi Jay..,
You can achieve this without BPM too.Your input is one file,by doing the Multi Mapping (1: N) you can acheive this.If there is no payload for any of the four files means simply put your four message types occurences as 0..Unbounded.
Check / Put an condition on your input file payload which field is determining whether data is containg for all or for some of the files.
So, if your input file containg the data for four files, those files are would be populated otherwise the files are not getting populated.I guess there is no use to create the blank XML structure.
Let me know your feedback.., It would be work for your case ..
Cheers
Tiger woods

Dependents requirement not created

Hello Gurus,
I am running MRP through batch MRP run
(t.code - wc27),
Processing key NEUPL 3 3 1 1 1. I want to create dependents requirement future dated so date input I gave is 28/12/2018 last working day form factory calender., but requirement is not created.
Please help I am new in this module. Need help.

Hello Ameya
I don't see the point of running MRP with date 28/12/2018.
Dependent requirements will be created on future date according to the parent planned order date, not to the MRP date.
Please try to run MRP again it with today date.
If you want to have dependent requirements in the future, please make sure that there are planned orders with date in the future for the parent materials.
BR
Caetano

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

PR Release Strategy for MRP & Manually created PR

There is a scenario in which it's required when,
PR is generated automaticaly through MRP then Release strategt should be applicable and when
PR is created manually then release strategy won't be applicale.
Please suggest about this..........
Thanks in advance.

Hi,
You should have two document types ( as required by you here), MRP PR document type & Manual PR document type.Link plant, MRP group and the default order types as MRP PR document type in OMDT t.code.
You should create release characteristics (CT04) with the table & field and add all release characteristics in release class. For document type release characteristics with CEBAN & BSART and do not keep value ZNB which you do not want, just keep value ZMNB. During design of release strategy keep value only for document type ZMNB with other character values.
Regards,
Biju K

Setting release strategy for PR for mixed requirement

Dear SAP gurus,
I have a mixed requirement for PR release strategy. For instance, there will be 2 types of PR created in my company. One is created manually, the other one created from MRP. The requirement is that for PR created manually the release strategy will kicked based requisitioner data. While for PR created from MRP, the release strategy will be based on MRP controller.
At first I thought that it is possible to have 2 class set for PR (both should be released at header level), but apparently it is not. So I'm forced to create ONE class that supposedly able to cater both condition.
So at first I create one class with 2 chars: MRP controller and requistioner
For PR which is created manually: I put requistioner eq 'FINANCE' and MRP controller blank (with the hope that ALL value doesnt matter),
For PR which is created from MRP: I put MRP controler eq '001' and requsitioner blank (with the hope that it means that ALL value doesnt matter).
However it seems that SAP consider that blank means blank. I tried with * it also not working. How can I configure this kind of scenario?
Please help.
Best regards,
John

The solution that we implement is to have an exit to determine the requisitioner in the PR based on the MRP controller. Thus we have a common solution for both PR

System should not creates new version when value of PO increased..

Hi Experts,
Need your help to solve this problem. When i increase value of PO it should retrigger Release strategy but it creates version first, then i have to tick completion indicator and check then only release strategy retriggers..
It should not create new version when change po
Please check below screenshot
Please help

Hi
Please reveiw the following points in note
   - 493900 FAQ: Release Strategy
      4. Why is the release strategy not determined?
     "If you use version management, the determination of the release
      strategy starts when the version is completed.
      You complete a version by setting the "version completed"
      indicator in the version tab."
   - 662993 Resetting an already occurred release
     You edit a purchasing document with release strategy.
     You change the quantity or the price. In spite of that, the
     already set release is not reset.
The release strategy works the same with or without version management
active - the only difference in case - version management is active -
is that if release is to be reset, it will be reset only on version
I hope this helsp to clarify this issue
Kind regards,
Lorraine

PO Release Strategy not changed after deletion of few line items with less

Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
Dear Friends
We have issue with PO Release strategy. We have created the PO. with release strategy with multiple approvers. After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong.
Details of the PO
PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
Are there any OSS notes available to correct his bug.
Please let me know if you need more details
Thanks in Advance
Thanks
MVS

Hi,
release indicators change it to 4.It may works. Please explore to all 6 indicators..........
i.e,
1-cannot be changed
2-changable,no new determination of strategy
3-changable,new release in case of strategy
4-changable,new release in case of strategy or value change
5-changable,new release if new strategy/outputted
6-changable,new release if new strategy or value changed/ outputted......
And check Characteristic description and value in Classification of Release strategies ........
I hope this will help you. Thanking you.
Regards,
Venkat.

PO release strategy is not triggering if Quantity pre.Qty

Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

Hi.
According to note 493900, question 4, release strategy is reset only
for some specific case. Alternatively, please question 5 from this note
release strategy might be redetermined. However in order to determine a
new release strategy the field that is changed in PO must be included
as one of the fields in the strategy. Thus there is no standard way
for resetting/redermining release strategy for a change of e.g. text
on header or item level.
Please also kindly refer to other 2 useful notes for this area:
662993 Resetting an already occurred release
365604 FAQ: Release strategies in purchasing
BR
Nadia Orlandi

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

UserExit required - Do not Create PO without Release Strategy

Similar Messages

Maybe you are looking for