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

Similar Messages

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

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

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

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.

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

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.

Inclusion of Purchase group in service entrey sheet release strategy

Hi
We are trying to include the purchase group in service entry sheet release strategy but system is not considering it.
Pl. let us know which table you have considered for purchase group character. We had considered EKKO table and Field EKGRP.
Regards
Kandre

Thanks Solved. The same field is done in development server, but after the request is moved to 201 and we manually changed to EKKO and EKGRP, that why the release strategy is not picking.
Thanks for fast response.
B.Kandre

Error "Account assignment 00 for purchase document does not exist " when u

Hai,
I am encountering the following problem when posting a PO based Invoice using BAPI_INCOMINGINVOICE_CREATE.
The error says " account assignment 00 for purchasing document does not exist".
The scenario is very simple. I need to raise an Invoice against a PO. the PO has a single line item of quantity 10 net price 10. Tax code is U2 ( 7% tax).
I am passing the following at header level.
Invoice_indicator ( as 'X'),company code,doc date , posting date, gross amount (107, currency USD, calc tax indicator as 'X'.
At line item i am passing Invoice document item 000001, po number , po item number, tax code(U2) item amount (100),
Does this error has got any thing to relate configuration matters?
Regards,
Upender

Hi Upender,
In some cases, depending on the type of PO / Posting,
you might have to populate the accounting data itab and pass in the BAPI parameter.
you can select the accounting data from EKKN for the PO.
Again it depends on the PO category, wether you need to populate Qty & Unit in accounting data.
Further, the accounting data should be exactly the same as there in EKKN ( all the fields except Qty & Unit ).
Thanks,
Ram

'Purchasing document does not exist' error while testing Inbound PO Idoc

Hi experts,
i am working on Inbound PO Idoc scenario. I am testing Idoc in WE19 with ORDRSP mesage type.
Idoc type:ORDERS05
Process code:ORDR
FM:IDOC_INPUT_ORDRSP
while trying to create PO it is giving an error 'Purchasing document does not exist' in we05.
please suggest me how to resolve this???
Regards,
Bhuvan.

Hi,
first time i am testing this IDoc and i don't find any field in Idoc structure to provide purchase order value.
any more inputs plz??
regards,
bhuvan.

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

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

Add new Purchasing Org. to the Cheracteristics of Release Strategy

Dear Experts,
We have around 100+ Release Strategies for which Purchasing Organization is one of the Cherecteristics.
I have a requirement to add a new Puchasing Organization in the Charecteristics for all these strategies.
I think in CL20N, manually, I can add a new Purch. Org. But doing this for 100 times is time consuming.
Can you please let me know if any alternate quick solution available to do this?
Regards,
Shashidhar

Hi,
Check the link:
http://www.sap123.com/a/138/#load-release-procedure-values-using-lsmw-direct-input-method
Regards,
Biju K

Release strategy error in RFQ

Dear MM gurus
I have maintained all the steps for release strategy for RFQ, while clicking on release flag in ME42 it is giving following error. please guide
Purchasing document 6000000015 not subject to
release strategy
Thanks in advance
kailash N. thakkar
9869171090

Hai,
Release strategy gets effected when all the characteristics mentioned for the release strategy are complied otherwise the strategy will not affect the RFQ.You might have given any value not relevant to the characteristic.For eg you might have given alower value than the value mentioned for the characteristic RFQ value.
Regards,
Gangadhar

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

Purchasing document 13000040 not subject to release strategy

Similar Messages

Maybe you are looking for