PO Release Strategy - Only for Non MRP generated materials

Hello,
I have a requirement in which any material which was generated via MRP (via PR) should not go through a release strategy at the PO level, but a non MRP generated PR should...
Is this possible at all? I know its possible at the PR level, but not sure at the PO... Would this be a case where we would need to added a field to the CEKKO structure thats for MRP generated PRs ?
Thanks

Hi,
By business any PO created, should follow release procedure as PO a committed document which will further send to vendor.
If you are sure about your requirement, PO created from MRP PR should not follow release strategy, then no need to go for any User Exit.
Just create separate document type for PR (ZMNB) , create separate document type MRP PO( ZMNB) and link MRP PO document type ( ZMNB) with MRP PR document type( ZMNB) in flowing path:
SPRO>MM>Purchasing>Purchase Order>Define Document Types
Now select your ZMNB B Purchase Order Document type and click link purchase requisition document type in Dialog Structure, enter ZMNB Purchase Requisition Document type with a new entry & save.
As you created release characteristics of document type (CEKKO with BSART), then do not keep Value u201CMRP PO document type (ZMNB) u201Cin the release characteristics of document type and design your release strategies.
Now create your PO with MRP PO document type (ZMNB) and see no release strategy triggered.
Regards,
Biju K

Similar Messages

PO Release Strategy - Only for non material based

Experts,
I have a requirement to implement a release strategy for a single plant for POs for NON material based purchases ( only for using account assignments, cost centers etc).
The release strategy I configured is working only for the specific plant I want... However, it works whether its a material based PO or a non material based PO.
How do i get the strategy to work for only the service based purchases, and not the material ones?

Thanks for the replies but I'm not sure if they are applicable...
I did create a characterstic for item categories and added the one's I wanted to have... I did NOT include a blank because i thought that would make the difference between the material based PO and non PO. When we I create Po with material (even with no account assignment) it still goes through release.
Any reason why that is?
I dont believe the material group solution will not work either because we require material group for material and non material based POs..
Side note - when i try to use CEKKO with KTTNP, i get a "KTTNP does not exist error." So i used EKPO - KTTNP... hopefully thats ok, but please let me know if its not.
Edited by: farmerj3 on Jan 30, 2012 3:36 PM
Edited by: farmerj3 on Jan 30, 2012 3:39 PM
Edited by: farmerj3 on Jan 30, 2012 3:48 PM

PO release strategy ONLY for change

I have a requirement to only have a release strategy for a purchase order only when it is changed
The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
How can I avoid having the release strategy written to the EKKO-table when the PO is created?
How can I have it written to the EKKO-table when it is changed?
Good answers will ofcourse be rewarded with points!
Edited by: Snowroller on Feb 11, 2012 4:00 PM

Dear,
Check this and try. Not tested.
Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
Try this option.
Regards,
Syed Hussain.
Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

Release Strategy Processor Names under Release Strategy tab for a PReq

Hello Experts,
We have situation in Release Strategy for Purchase Requsitions in which we need to display all approvers names under the Release strategy tab for a Purchase Requisition.
Senerio work as follows.
Based on the Release strategy customization settings,Purchase Requisition subjected to release strategy selects the approver names from a custom table.
In the Custom table we have names of the approvers with release codes.
Purchase Requisition displaying the names of the approvers according to alphabetical order.Hence it displays First one user or approver name under the release strategy according to the approver alphabetical order from the custom table.
Can we display name of all approvers in one line according to initial investigation there is room for 40 characters under the release strategy tab.
Let me know if any Standarad OSS notes available for this.
Amogh

Hi amogh if you configure with workflow the strategy and the name of the persons are in transaction SU01, you don´t need to put nothing. The release strategy shows the names of the persons that release the document, but if you change one person in the release strategy, the system don´t save history for this, all old documents that have been released for this person, release strategy is blank. You have to do a non standard report that shows what person releases what document.
I hope that this information help you
Rose

Release Strategy/Workflow for MB21 Reservation

Hello Gurus,
I know as per Standard SAP it is not possible to have a release strategy/workflow for MB21, but if any of you have come across this requirement where material reservation should be approved by related dept heads before the material is issued for those reservations, please reply back with the possible options to configure release strategy or work flow for MB21 even thru development or any other work around.
Your expertise advises will be very helpful for me to work around this requiremnt.
Thanks in advance, looking forward for your reply

Hi Anoop,
Reservations in SAP is just a logical value, which does not have any impact on any stock type. It would be interesting to know why the business needs approval process for reservations.
Anyways even if you need approval process, what you have to do is develop a custom object, where in when ever the business creates a MB21 reservation, assign a unique number to each reservation number.
As a dept head, the business will run the ZMB21, checks the reservation to which he needs to approve. In the back groud call up the unqiue id assigned and place approve button where in dept head can approve the same.
The authorization to this custom tcode should be given as per your requirement.
Hope this helps
Ilyas

Are QOS BUM Policer BUM Parameters applicable for virtual ports or only for non virtual ports?

Are QOS BUM Policer BUM Parameters applicable for virtual ports or only for non virtual ports?

Just FYI.
I probably overestimated RHEL/OEL-5.3 capability to "compete in Music Showbiz" as a digital studio workstation OS. Seems that "very old" alsa kernel drivers (1.0.17), compiled with actual kernel, don't like Audigy cards when it comes to MIDI interface, despite the fact the audio is perfect. Although I am still not sure nothing could be done as a workaround in order to get MIDI worked on OEL-5.3, the fact is that SB Audigy MIDI works like Roland Synth, sounding amazingly, if the kernel 2.6.18-128.1.1.0.1.el5 is recompiled with the actual alsa driver version 1.0.19 (modules snd-emu10k1, snd-emu10k1-synth, etc).
It's interesting that overall device and loaded-modules schema's picture is the same as with old alsa (original kernel). That's why I still think something could be done, at least as workaround, to get MIDI worked with original OEL-5.3 kernel.
NJ

Release strategy retrigger for all non significant changes

HI,
My client has the below requirement:
The Purchase requsitions and Purchase orders are released by different approval authorities. Any change made to any field like material short text, cost centre, payment terms, material long text, etc. the sytem has to cancel all the previous releases and release strategy need to be retriggred from the beginning.
I request all to provide me with an user exit or badi if any available in the system to achieve this.
Regards,
Rayeesuddin

Dear Ray,
First discuss this with your functional consultant (MM) from functional point is there is any setting.
Regards,
D.Srinivas.

Wrong release strategy assigned for a PM work order

Hi
Would like to seek your inputs on this.
I have created a work order that has a settlement rule for a WBS element. I then created a material, RELEASE the work order then SAVE.
I found out when going back inside the work order that the PR number generated was having a different release strategy, which is not appropriate for the approval.
The only time when you can fix the issue is when you do a change on the work order or you have to create the order, save, then open again the work order then release it, and save.
Have you had this same scenario? Can you please share any suggestion to address this issue?

Hi Nazarene
You may need to give us a background of how your organization have set up the release strategies. Some organization uses User Exits or Work Centers to set up release strategies. Either your work order is not picking the correct work Centre or if the work center is new you have to change the work order (IW32) and save it to pick the correct release strategy.
Alternatively you may need to check your workflow and the release limits.
Regards
Gibson

Assign new document type for automatic MRP generated PR

Dear Experts ,
I want to have a document type ZMRP MRP generated Purchase Requisitions ( automatic ).
Also i want it to have a release procedure .
Where do i make the said assignment of document type ?
The same is the case for Purchase requisition for automatically generated PRs through Maintenence orders .
Regards
Anis

Hello Experts ,
I have done the assignments , but the system is still picking up the document type NB .
I may or may not define MRP group in the material master as MRP group is not relevant for my client .
I want to know , from where does the system still pick the document type NB ?
Regards ,
Anis

No release strategy tab for purchase requisition

Hi Gurus
i have a user who is complaining about the release strategy not appearing after saving the requisition, but when i try to test it from dev using his profile, it works fine. he can create the req fine on other pc's but not on his pc. i have check his patch level and if he is using the latest gui version and he has both.
what could be causing this issue?
Please help
thank you in advance

Hi Roy
thanks for the reply
am i supposed to check this on his profile? he is the only person getting this issue other users are working fine. so my assumption is that it must something to do with his sap settings but i dont know the technical side of sap
please help

Release strategy reversal for the purchase requisition.

Hi all,
I have a scenario were we have three release levels to release the PR through ME54N tcode.
After all the levels are released,If at the first level the PR release is cancelled all other levels are automatically cancelled.
Now my concern is until the 3rd release cancellation is done, 2nd and 1st level should not be allowed to cancel the release of PR. and until 3rd & 2nd release cancelltion is done, 1st level should not be allowed to cancell the release of PR.
Please Let me know if any BADI or any enhancement is available to acheive this back release strategy for PR.
Regards,
Kumar
Edited by: kumar g on Jul 16, 2009 6:21 AM

-

Release strategy determination for PO item level characteristic value

Hi Experts
I have user material group as release characterstic for PO.
I have created two line items with two different material groups.
How the release strategy determination occurs when the two different material groups are linked to two different strategies?
regards
ramSiva

Hi,
in this case system is NOT able to find the release startegy.
Please take care of the following explanation (see note 365604)
o For OVERALL RELEASE (purchase order and purchase requisition) the
   item fields such as Plant and Material Group will be aggregated
   to header level.
   For example you use Plant/material group
as one of your characteristics. If all
items do not belong to the same plant/material group
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/material group
. If all items
belong to the same plant7material group
then that plant is aggregated to the
header; if one or more is different then a blank is aggregated to
the header.
If you use an overall release strategy all
characteristics which you have defined in the customizing (CEKKO-MATKL
must have the same value. If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing (Transaction: OMGS
: OLME >release procedure for PO > rel. strategy ) the
system won't find a release strategy.
you need
to add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save. Now in OMGS you can select
this value as an allowed value for the characteristic.
(Example:
To avoid this you can do the following:
- go into transaction CT04
- enter the characteristic 'CEKKO-MATKL'
- click on the tab 'values'
- set a flag in 'additional values'
- in the column 'Char. value' do not enter anything
- in the column 'Description' enter a text like 'no material class'
- save this setting
Now
- go into transaction OMGS -> button 'release strategy'
-> button 'classification'
- double click on CEKKO-MATKL' and set a flag in 'no material class' )
Please also have a look into the attached note 365604 point 2d).
BR
Nadia Orlandi

Release strategy & EBAN for project systems, purchasing

Hi
We have 2 different scenarios for which we use same account assignment category "Z".
1) Purchase Requisitions for capital expenses (Account assignment category "Z") - this is part of project systems requisition attached to WBS elements
2) Purchase Requisitions for expensed items (Account assignment category "Z")
I have configured release strategy with classification with following characteristics
1) plant
2) cost centers
3) total amount in PR
4) account assignment category
all 4 characteristics are same in both areas (capital and expensed)of purchase requisitions, account assignment category Z decides whether it is capital purchase or expense related purchases. Z uses order number that is internally tied to WBS element.
my question is - if some one has similar scenario then what is the best solution to handle invocation of release strategy.
how release strategy can be determine, do I need to use user exit and if yes what best user exit is available.
EBAN fields, I have researched and I cant use fields like "requisitioner" for determining release strategy.
I would like to invoke different release strategy for capital projects and different release strategy for expensed items in PR. there is a workflow attached to this later.
Please reply
Thanks and regards
Umesh

Umesh,
Well, there needs to be some way to differentiate the 2 types of purchase requisitions for you to use 2 different release strategies.
I am not sure if you have the option of using a different document type to differentiate the 2 requisitions. I would definitely look at this possibility and include the document type (CEBAN-BSART) as a characteristic in the release strategy.
Other options would be to look at using the purchasing group (CEBAN-EKGRP) or the requirements tracking number (CEBAN-BEDNR) as characteristics in your release strategy.
Hope this helps.
H Narayan

Release Strategy Authorizations for PR PO

Dear Friends,
Please explain how to configure Release Strategy for PR PO and how to configure user ID's maitained for authorizations of release PR, PO.
Thanks,
Javeed

hi,
depend upon the field restrictions which is at the document level, the user can be restrictied . hope this will help

Read Only for Non Trusted Users

Hi everyone:
Is it possible to forbid non trusted (or non certified) users for modifying the pdf (I'm interested in signing protection particularly) but allowing them to open the pdf in READ ONLY mode?
I'm wondering how to do it using Adobe Acrobat Professional 8 (info with Adobe Acrobat Pro X will be also appreciated) and opening the pdfs in their Reader corresponding versions (managing non trusted users as READ ONLY users).
Thanks for your time
Regards,
Javier

Thanks Bill:
I've been trying what you said, and is possible to "lock" the pdf so it's in read only mode via password (using Adobe Acrobat X). Is it possible to do the same with certificates? As far as I have seen, if you use certificates policies, you use the certificate to encrypt the document but then, non certified users are not allowed to access the pdf. I'm really interested in using certification restrictions but being able to access the pdf: I want to simulate the READ ONLY MODE for everybody and the WRITE mode for certified users.
Using this kind of restrictions, the only problem that I see (for end users) is that they should disable secure settings before editing / signing (this two options appear disabled with this method). Is it possible to get them available and open the "enter password" dialog when clicking them, not managing the security properties?
Thanks for your time
Regards
Javier

PO Release Strategy - Only for Non MRP generated materials

Similar Messages

Maybe you are looking for