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

Similar Messages

No Release Strategy determined - Message no. Z_MESSAGES032

Hi All,
I am trying to creat PO without reference to PR and facing error:
No Release Strategy determined
Message no. Z_MESSAGES032
This is for newly created PO type and new cost center.
We don't have any PR, we are creating PO directly
please advice

Hi Vishal,
As you mentioned you have created new PO type so I think release strategy is not created for this document type. You can go to the IMG ==> MM ==> Purchasing ==> Purchase Order ==> Rlease Procedure for Purchase order ==> Define Release Procedure for Purchase Order.
Select Release Strategies option and create new Strategy. Selecte the newly created strategy and go to details and click on Classification and then Add your document type and other information. If you have any existing release strategy you can select that and add another document type in the classification.
I hope this will help.
regards,
Ajay Mishra

Necessity of the Partner Determination Procedure at Item Level

Hi Gurus,
What is the necessity of the Partner Determination Procedure at Item Level and in what case it is useful?
Regards,
Sarosh.

Dear,
It may happen that in a business transaction the partner in the document header does not apply to all items, for example, if specific goods for a customer are normally delivered to another ship-to party.
In sales documents and billing documents you can enter one of the deviating partners from the document header at item level.
You have planned to have the partner function in the partner determination procedure for sales document items or billing items.
When creating a document , the system copies the document header partners to the items. If you want to define another partner than the one in the document header at item level, overwrite the proposal from the item partner screen.
You have planned the partner function ship-to party in the partner determination procedure in Customizing for sales document items and have defined this as changeable.
Create a customer sales order as usual.
The system copies the partner from the customer master into the document header and then from the document header into the items.
Select the item, that should receive a deviating partner.
Choose Goto --> Item --> Partners.
The partner screen for the item appears. Here you can overwrite the changeable partner functions.
Try to read the SAP help. U will find some more info.
reward if helpful
Krishna Chaitanya

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

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

PO Release Strategy Determination

Hi,
Is there a user exit/badi where we can skip calling the FM ME_REL_STRATEGIE_EKKO (I believe this FM is responsible for re determining the release strategy of a PO) if this change is not related to any item price change ? What we want to have is for the PO to use the same release strategy if the header text is the only one changed.
Thanks.

Hi,
I dont think there is any EXIT/BADI to avoid FM 'ME_REL_STRATEGIE_EKKO'.
You can actually create an enhancement point at the start of this FM and check for the conditions when you want this FM to skip and EXIT from this FM.
But this is not the wise way of doing.
If you can elaborate your requirement in detail, may be some one can help you with other alternatives..
Regards,
Gautham Paspala

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

-

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

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

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 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

Search help for Custom Item level field

Hi All,
I have two custom fields at Item level. Both of them has fixed values defined at domain. The fixed values have a short text also given with them.
The problem I am facing is when SRM provides default search help for these custom fields, for first field the 'Value' and 'Description' comes in the search result screen, but for second, only 'Value' comes in the search result.
When I try to debug, it shows the SHLPTYPE as 'SH' for first one and for the second as 'FV'.
What does this indicate?
My requirement is to display both value and description in the search result screen.
Please suggest.
Thanks
Nandalal

Hi
Sorry for the delay. My User got locked for some time.
I have seen the document you sent me on my email id.
 I noticed in the case where the Search help is working fine, there is no space in between the contents of the Fixed values and their short text under the value range tab of the Domain element.
But in the case, where there is a problem with the search help. There both the Fixed values and their short description is having a space in between the words.
Try maintaining COND_A instead of "COND A". Also with the short description use "COND_A" instead of "COND A".
I hope this will resolve the issue.
Update me once you have any issues.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Business area not determined for line item?

Hello All,
I am trying to create a sales order. When I enter a line item and enter plant for the item, it gives me an error "Business area not determined for the line item #" and it does not accept the item.
I have already checked in the enterprise structure in IMG that the business area is defined and assigned for this plant.
Is there anything else need to be done? Do we have to define or assign the business area in material master?
I would appreciate if somebody can answer.
Thanks.

There are three rules for determining a business area:
o   Rule 1: plant and division
o   Rule 2: for each sales area
o   Rule 3: for each plant and item division
See what you are missing

Workflow for Changing Item Level Permission in SharePoint 2013 (Office365)

I am using OOTB Tasks List in SharePoint 2013 (O365). Now my scenario is like this:
I have two user groups: 1.Sales Managers 2. Sales Executives
Sales Managers can create & assign task to Executive. I want something like Sales Managers Can view all tasks (Which is by default view of tasks list i.e. perfact) but Executives can see only their tasks assigned to them. How can I achive this?
Can I use WorkFlow for this to Change item level permission or to assign permission to assigned to user? or JS
Can anyone have proper solution? thanks

1. make 2 SharePoint group 1>Sales Managers 2>Sales Executives
2. Show 2 WP of same task list in same page.
3. Use Audience Target for Sales Managers Sharepoint group in first Webpart property. (All
Iten view)
4. Show "My Task" view (assign to =[Me]) Bottom WP for same task list and use Audience Target for Sales Executives. Or if you want it to see
Sales Managers as well, the dont use any Audience Target.
Bottom line - SharePoint group use in Audience Target will do the trick. OOTB
Regards Sudip Misra [email protected] +1-412-237-5435 Pittsburgh, PA

Release strategy determination for PO item level characteristic value

Similar Messages

Maybe you are looking for