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

Similar Messages

Note 1307108 - ME5xN: Purchase requsitions not subject to overall release

We have the following : release strategy tab is now showing even the purchase requisition is subjected to a release.
we have found note 1307108 but..... we are on 603 and this note is for 604 only.
I am sure that others have had the same problem, but since this note is not applicable, can someone tell if he . she had the same problem and how it has been solved...

What I could see in the screen captures looks fine.
What I could not see is: Is your class released? (check basic data tab in class)
I saw a valid from date 23.11.2009 for your class. What date does your requisition have?
Furthermore I saw that your release code does not have a description, the characteristic did not show any description too.
SAP sometimes goes odd ways.......better maintain the descriptions to be sure that they are not the root cause for your issues.

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

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

Purchase requisition not generated

Hi Gurus,
Purchase requisition not generated at the time of sales order for Item category tab. Can you please let me know the posible reason.
Thanks in advance...

Hi,
As per my understanding, you are running Third Party Process, if yes then, please maintain the following setting for the same;
Mater Data Settings:
1. Item Category Group as BANS in sales org 2 in MM02
2. in MRP2, in procurement type should be 'F'
SPRO Settings:
1. Item Category TAS: Maintain Billing relevance as 'F'
2. in VOV6 Schedule Line CS: doesn't have Movement type therefore keep the field as blank
3.ASSIGNMENT: assign Schedule line CS to item cat TAS in VOV5 and TAS to order type in VOV4
4. in vov6 Schedule line CS Item Cat as '5' i.e. Third party and account assignment cat as 'X"
Now run the process..I hope this will help you...
Regards,
Bharat B

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

Purchase requisition not to be created if sales order is incomplete.

Hi ALL,
I have a requirement from the business wherin they want purchase requisition not to be created for the incomplete sales order
in case of third party / invidiual P.O sales orders.
We have defined some fields in the item category incompletion status and if this fields are empty then the P req shld not generate.
Can anybody guide me what settings to be made to acheive this.
Please help me in this.

In t.code OVA2, try to assign an incompletion procedure at schedule line level. This procedure can be assigned with relevant status like checking goods movement, and general checked. Then test the scenario.
There is an OSS note out there, but it is NOT exactly represents your scenario. However you can have a look at it.
Note 623267 - Purchase requisition in spite of missing configuration II
Regards,

"Material purchase requisition" not allowed (Use Status PROV, object TM0000

Hello Gurus,
I am getting the following message every time I enter a material in the sales order. The material entered requires a Purchase Requisition (PR) to be created when it is entered in the order. We have done Configuration thru Order Status Profile that will prevent PR creation at time of Order creation.
The message is as follows:
"Material purchase requisition" not allowed (Use
Status PROV, object TM0000000001VB)
Solution requested: We do not want to see this message appearing so many times. Can you pl let me know if there is a way to avoid this.
Thank you
Vasavi

Hi Vasavi,
I am not talking about the po check above that one tab like check purchse order no in this feild keep emty and also below that enter po number also keep un check
and also please check when you creating sales order beside po date one tab is availble check any data in default that
that tab name is display doc header details in that tab purchase order tab in that any infirmation is default check that also
Hope this will helps you
Prem

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

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

IW31-Create Purchase Requisition automatically from PM order - Release 5.0

Dear Experts,
Currently we are working in the 4.6C Release but we are doing the migration for 5.0. In PM, in the 4.6C release when we
create a PM Order in tcode IW31 we select a component and the system shows us the screen to inform the quantity and
automatically the system shows us a screen to Create Purchase Requisition where we can fill or select some fields.
However, when we create a PM order in the 5.0 using the same tcode, the same material type, the system creates
automatically the Purchase Requisition without to show us the screen to fill or select the fieds. I´ve checked the customizing
comparing the systems but I couldn´t find something.
I was wondering If you could help me with this issue?
If my comments are not enough to understand me, please let me know...
BR
Valdevair

Dear friend,
Do check configuration node at
plantmaintenance and custonmer service - maintenance and service processing -maintenance and service orders - functions and settings for order types - define change documents,collective pur.requisitionsindicator,operation no.interval
here for your order type and plant , check whether generation of PURCGHASE REQUISITION from maintenance order settings.
there will be three options
1) never
2) from release
3) immediatly.
hipe this will help you.
Regards,
pardhu

Purchase requisition generated before service order release

Dear Experts,
We're testing the Logistics Integration Scenario for the Procurement of materials.
When we enter a spare parts item(which is configured to create a purchase requisition in ERP)
and just save the service order,
the purchase requisition is created in ERP as soon as the order is saved even though the order is not Released.
Is this a standard behavior?
We expect that the purchase requisition should not be created until the service order is released.
This symptom happens not only with purchase requisition scenario but also with the purchase order, reservation, too.
Does anyone have an information on this? Any information would be highly appreciated.
Thanks in advance for your help.
F.T.

As far as I know the standard behaviour is that the PR is created upon order save and not upon the status of the order or items changing to released.
To get around this you can set user status and use status management to prevent the PR getting created or use the BADI CRM_SRV_FIND_LOG_SC to supress creation of the PR.
Hope this helps.

Overall purchase requisition's Workflow : mechanism of release code

Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.

Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome

Purchase requisition not subject to a release strategy

Similar Messages

Maybe you are looking for