PRs not finding a release strategy

Hi All,
I am having a issue with creating PRs, when i create PR with one line item, it is finding the release strategy but when i create PR for more than one line item SAP can't find the release strategy.
The only common factor for the problem would appear to be that they are multi-line PRs.
Please help what should i do.
Thanks in advance.

Hi Madhur,
Kindly check below
1.If for each line item the material group is different
2.Using Header level release strategy
Thus this material group is aggregated at header level and " " value
used as document in the below note
47089 Release procedure for purching docs - Aggregation
The release procedure for purchasing documents is carried out on header
level. For this, the following values are aggregated from the items on
header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items coThe same fun
same plant. If only one alternative plant exists, ' ' is aggregated on
header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was
maintained for the characteristic 'Value' as an object value.
The same functionality applies to the material group as for the plant.
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.
(: OLME >release procedure for PO > rel. strategy)
system won't find a release strategy.
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.
THIS PART YOU HAVE ALREADY DONE
CT04 > PO_MATERIAL_GRP has blank entry
SO JUST maintain it in customising of Release strategy.
Please also have a look into the attached note 365604 point 2d)
regards,
Lalita

Similar Messages

PO not subject to Release strategy but PR is.

Hi Friends,
I am trying to check what purchases have occured in my organisation which have not been authorised at some point.
I first have done a search using table EKKO for PO's not assigned a release strategy and found many. Therefore I thought well maybe they have been authorised at the PR level using a release strategy. I looked at one and this seems to be the case.
Am I right in thinking that what has happened in this scenario is that a PR has been created, been released via the appropriate release codes and then automatically become a PO but the PO has not met the criteria of a release strategy and so been released automatically?
I'm a little confused because we only appear to have release strategies defined for PO so how would these pick up PR?
BTW our release strategies are classified on PO approval - reasons and PO approval - Plant.
Last thing:
So if I want to check which orders have not been authorised I was thinking of using table EKPO to look for PO documents with no PR (Do all PO's need a PR?) and no release strategy assigned to the PO. Using table viewer SE16 how do I specify "null" i.e. no value? Do I just type NULL?
I guess then I need to look at all PR's that come out to see if they have got a release strategy assigned?
Thanks for your help, sorry for the rambling question...
Chris

Chris,
1. Your PRs might not be subject to release strategies at all
Go to SE16 and look up T16FG, and run it wide.. look for the release object .. if you see "1" you have Release configured for PRs as well, else 2 is for POs
2. Tcode ME2N, select dynamic selection and under PO header choose Release status and Subject to release indicator and play around with them the way you want.
also, choose Purchasing item>> purchase requisition and in teh field .. right click and choose options..= and leave teh field blank, that 'd mean null
execute the report based on other criteria if any
Not all POs require a requisition although they should theoretically.

HT1338 Software Update is not finding latest release (April 3) of Java 2012 001 Update for Mac OS X Lion 10.7.3 on iMac mid-2007 that downloaded automatically on iMac mid-2011

Software Update is not finding latest release (April 3) of Java 2012 001 Update on my iMac mid-2007, but it downloaded it automatically on my iMac mid-2011 yesterday. Both are running Mac OS X Lion 10.7.3. When I try to download the update manually from Apple on my older iMac, it downloads okay, but when I try to open the dmg file, I get a warning message saying that opening this update may make your computer LESS secure. Do you want to proceed? (I did not).
Why would Software Update find this update and install it automatically on one iMac and not the other, if they are both running the same version of Mac OS X Lion? I checked the installed software list on my old iMac and the Java update does not appear there. Why would this update make my old iMac less secure?

Recall that Java is not installed as part of Lion.
You have to install it (and are asked if you want to) when you first try to run some java stuff.
Is it possible that the iMac 2007 does not have Java yet?
Try this: open Terminal (from Utilities) and type java -version (exactly like that, with the space before the hyphen).
What do you get?
Consistent with this theory is that the dmg thing gave you the warning - installing java might make your machine less secure because java is a means for bad guys to try to do bad things to your computer.
charlie

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
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   0
                        1
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
ravikant dewangan

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Purchasing document not subject to release strategy

Hi
I created Scheduling Agreement using BAPI ' BAPI_SAG_CREATE ' . Document number created successfully but when go to release release strategy in
ME33L then it gives information 'Purchasing document not subject to release strategy ' . How i resolve this issue using BAPI .
Regards,
Suvakant

Yes it is created by using same input for ME31L .
report zsa_creation_test.
data:   poheader     type bapimeoutheader,
        poheaderx    type bapimeoutheaderx,
        poitem       type bapimeoutitem occurs 0 with header line,
        poitemx      type bapimeoutitemx occurs 0 with header line,
        i_bapireturn type bapiret2 occurs 0 with header line.
data : i_bapireturn1 type bapiret2 occurs 0 with header line .
data: l_ebeln type ebeln.
poheader-comp_code   = 'ABC'.
poheader-doc_type     = 'ZPA2'.
poheader-creat_date    = '20140507'.
poheader-created_by     = 'ABAP'.
poheader-ITEM_INTVL = '00010' .
poheader-vendor       = '0000100176'.
poheader-purch_org = 'AB01'.
poheader-pur_group = 'RR1'.
poheader-currency    = 'INR'.
poheader-doc_date    = '20140520'.
poheader-vper_start    = '20140520'.
poheader-vper_end     = '20200507'.
poheader-incoterms1    = '1'.
poheader-pmnttrms     = 'YP04'.
poheaderx-comp_code    = 'X'.
poheaderx-doc_type   = 'X'.
poheaderx-creat_date = 'X'.
poheaderx-created_by = 'X'.
poheaderx-ITEM_INTVL = 'X' .
poheaderx-vendor = 'X'.
poheaderx-purch_org     = 'X'.
poheaderx-pur_group     = 'X'.
poheaderx-currency = 'X'.
poheaderx-doc_date = 'X'.
poheaderx-vper_start = 'X'.
poheaderx-vper_end = 'X'.
poheaderx-pmnttrms = 'X'.
poitem-item_no = '00010' .
poitem-material    = 'RT010006'.
poitem-plant = 'PL02'.
poitem-stge_loc     = 'ST01'.
poitem-trackingno    = 'F'.
poitem-rel_create_profile    = 'ZAB1'.
poitem-jit_relvt = '1'.
poitem-target_qty    = '10.000'.
poitem-po_unit = 'EA'.
poitem-orderpr_un    = 'EA'.
poitem-conv_num1 = '1'.
poitem-conv_den1 = '1'.
poitem-net_price = '10.000000000'.
poitem-price_unit    = '1'.
poitem-tax_code    = '00'.
poitem-info_upd    = 'C'.
poitem-item_cat =   '0'.
poitem-acctasscat     = ''   .
poitem-apo_planning     = '1'.
append poitem .
poitemx-item_no = '00010'.
poitemx-item_nox = 'X'.
poitemx-material = 'X'.
poitemx-plant      = 'X'.
poitemx-stge_loc    = 'X'.
poitemx-trackingno = 'X'.
poitemx-rel_create_profile = 'X'.
poitemx-jit_relvt      = 'X'.
poitemx-target_qty    = 'X'.
poitemx-po_unit        = 'X'.
poitemx-orderpr_un    = 'X'.
poitemx-conv_num1        = 'X'.
poitemx-conv_den1      = 'X'.
poitemx-net_price       = 'X'.
poitemx-price_unit    = 'X'.
poitemx-tax_code    = 'X'.
poitemx-info_upd    = 'X'.
poitemx-item_cat    = 'X'.
poitemx-acctasscat = 'X'.
poitemx-apo_planning = 'X'.
append poitemx.
call function 'BAPI_SAG_CREATE'
exporting
    header             = poheader
    headerx            = poheaderx
importing
    purchasingdocument = l_ebeln
*   EXP_HEADER         =
tables
    return             = i_bapireturn
    item               = poitem
    itemx              = poitemx.
call function 'BAPI_TRANSACTION_COMMIT' .

Entry Sheet Not Subject to Release strategy

Hi Gurus,
I have a situation ,an end user is trying to release the Service Entry Sheets,but he gets an error saying "Entry Sheet Not Subject to Release strategy message 0k000,i dont know what exactly is going on???
Can some one help me out with this.
Thanks,
Srikanth

Hi
Check out the release statergy with classification values and also check - your service sheet falls under this criteria.
Regards
Anand

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

Re: Purchasing document 13000040 not subject to release strategy

Dear all
i am create PO some qty it's showing release indicates,but some PO's as 0 qty ,that po's not showing release indicates below error is showing,
Purchasing document 13000040 not subject to release strategy

hi..
please check your release strategy characteristics ..whether it is net value or quantity...
bcz..i think u have taken quantity as one of ur characteristics and given cond that..quantity should not greater than zero.
Please chk this setting and let me know..
Thanks

Purchasing document 13000040 not subject to release strategy

Dear all
iam create Po
30 or 30+ qty it is showing Release code but less-then 30 qty its showing bellow error
how rectify this error
Purchasing document 13000040 not subject to release strategy

HI
you are creating two thread for same requirement
check your following thread
[how to set Release indicator ,ofter quantity change PO release cancel;
as qty change your value will get change in PO
as you are changing qty now try following
keep qty less than 30 and change price increase it you will get Po for release,means your release procedure set for value of PO
Regards
Kailas Ugale

PR Cost Center Release Strategy for Item Level not Working

Hi All,
I have a class with 2 Characterictics, CEBAN-ESTKZ (Creation indicator) and CEBAN-KOSTL (cost Center) and I have 2 release strategies the first one should trigger when MRP creates a PR ( ESTKZ=B and KOSTL=No input) this strategy is working fine, but the second strategy should trigger is if manually I create a PR and it is relevant to a cost center (ESTKZ=R and KOSTL=XXXX) This is not working, I dont know why sistem is not triggering the release strategy if everything seems to be ok.
I know ceban structure has kostl field, but I checked and this field is not in the EBAN table, maybe this is the reason but then how will this work and as far as I know, this is standard field.
I checked in CL24N and all the objects are assigned to the class, all hace status released (1) and and the "OK" check mark
I checked in CL30N and if I enter in the ESTKZ characteristic=R and KOSTL=XXXX Then it finds the correct and only strategy, so I don´t know why this is not working, the only strange thing is that in CL30N if I only enter value R and leave empty the cost center, the system finds and shows me the 2 release strategies, this is strange.
Is it mandatory to include the acc assignment field in the release strategy?
Please give some guidance.
Thanks
Edited by: Julio on Nov 14, 2011 12:14 PM

Hi, thanks for your reply,
I have entered with leading zeros to complete 10 characters and is not working, I really don´t understand what is going on here, It should work even if I just have 1 characteristic assigned to the class right? this characteristic is CEBAN-KOSTL but this is not working.
Any more ideas?
Regards

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

Release strategy not working

Hi All,
I am working on a release procedure.All the release procedure configurations have been done for PO release .I have modified the user exit that determines the approvers which is a part of role 2000027 and I am using the standard WF 20000075 itself.
But after that when I creating a PO it is not triggering the WF.
When I am test the WF in SWUS by giving PO number and release code,its working fine.
But when I am Creating PO from ME21N workitem is not going to the user.
Can anyone please help me to resolve this.
Thanks
Raju

Does the PO have any Release Strategy tab in the Header of the PO. If not then your Release strategy is not configured in SPRO. Search this forum for configuration
2)If the PO has Release Strategy tab then please check in SWE2 whether the Linkage between the event and Workflow is activated. If not activate it. Also please check entries in SWEL Transaction code.
Thanks
Arghadip

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

Escape Release strategy based on purchasing group

Dear Experts,
In our system, PO release strategy is set up,
But, some of the POs are not subjected to release strategy because they belong to a perticular Purhasing Group (P01).
Where this set up is done?
Regards,
Shashidhar

Hi Shashidhar,
In your system it seems there is a characteristic created for Purchasing Group, if you want it activated for a particular Purch Group, then please do the following
Determine the strategy that you want to be called ( You can see any existing PO to find it out), once done, you need to identify the characteristics and class
SPRO-MM-Purchasing-Purchase order-release strategy, define release strategy, select your strategy and go to details and click on classification, in case you get an error and not able to, click on release pre requisites, come back and then try again, in classification you will get to see the various characteristics maintained and also the class name at the top.
Once you have done that, please go back to the node Edit Class, please put the class that you obtained earlier and get the characteristics for Purchasing Group.
Then go to the node Edit Characteristic, put your characteristic name say PO_RELEASE_EKGRP, Click on the tab values, and add your Purchasing group here and save it.
Then go to transaction CL24N, provide the class, and select the release strategy you are interested in, and select change, and detail, there for the characteristic for Purchasing group, you can add the previously added Group, and you are good to go.
Please let me know if this helps.
Regards
Shailesh

PRs not finding a release strategy

Similar Messages

Maybe you are looking for