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.

Similar Messages

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

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

Purchase Order E-mailing with Release Strategy

Hello,
We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
Print Programs:
/SMB11/FM06P
/SMB40/FM06P
SAPFM06P (Sapscript Only)
Forms:
/SMB11/BL_MMPO_L
/SMB11/MMPO_L
/SMB40/MMPO_L

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

Goods receipt for purchase order not allowed for a particular wbs

hello everybody..
Am creating a good receipt for a purchase order using the T-CODE-: MIGO...
While doing so am getting an error as " goods receipt for purchase order not allowed(wbs element)".
What can be done to rectify this error?
Plz do help me....
Regards,
Deepika
Moderator message: not directly related to ABAP development, please have a look in the appropriate functional forum, study the long text of this error message.
Edited by: Thomas Zloch on Dec 1, 2010 5:52 PM

Hi Br. Ajay M,
Released the order and Status line as follow
REL AVAC BUDG GMPS
but the error changed while reverse the document
item 0001 Order is invalid.
Many thanks for your kindly reply.
regards,
Steven

Open Purchase Orders not considered as requirement for MRP Run

Hi ,
We are facing a issue of Open Purchase orders not appeared in Stock requirements list and also it is not considered as requirement for MRP Run against reservation.
As aresult for a reservation demand of 10 units we are ending with Open POs 10 units and a additional planned order 10 units.
Material Type : ERSA
MRP Type : PD (or VB)
Lot size : EX ( HB if MRP Type is VB)
Could you please throw some light to correct our settings to MRP to consider Open POs?
Saravanan

Can you check to see if there is a re-order point set up for this materia? That could be causing the problem too.

Purchase order not appearing as commitment for next fiscal year in KOB2

Hi Experts
Any help on this is highly appreciated.Our Fiscal year 2008 is ending on 27th september and fiscal year 2009 will start on 28th September.
We have some purchase orders created with delivery date as 30th september which falls into next fiscal year. Somehow these purchase orders are not appearing as commitments in KOB2 report even with data ranges for next fiscal year.
However we have many similar Purchase orders with delivery date in fiscal year 2008 with same internal order as account assignment and they are correctly appearing as commitments in KOB2 report.
Can you please let us know what could be the reason for purchase orders with delivery date as 30th september not appearing in KOB2 report.
Regards,
Santosh

Hi Ashok
Thanks for your continued support on this. I was going through these notes today.
One observation I made was cost elements in our system were valid till 27th september only when problematic POs were created.However their validity was subsequently extended after the creation of Purchase orders.This might be the reason for system not recognising these POs as commitments.
SAP Note 534993 seems to suggest that we need to run report RKANBU01 for all such purchase orders to redetermine commitments.I am in the process of testing this out in our systems.
Could you please let me know if my understanding is correct. Thanks again.
Regards,
Santosh

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

Release Strategy for Contract

Hello Experts
I am using release starategy for contract and using communication structure CEKKO in characteristics. I want to use other parameter such as material master number (MATNR) for characteristics. I see that CEKKO has component .INCLUDE (Communication Structure: PO release for User Exit). Does any one know how to use it in characteristics and if I use it can I design release strategy for particular materials?
Thanks
Ankit

this has been discussed multiple times on this forum - "Release strategy at item level for purchasing docs - PO/SA/Contract" not possible...
refer below threads
Why release strategies for PO at header level only
PO Release Strategy
Release strategy - item level
yogesh

Report to Purchase Orders with Good Receipt and pending for Invioce Receipt

Hello,
I'm looking a report bring me Purchase Orders with Goods Receipt and waiting for Invioce Verificacion (MIRO).
I appreciate any help.
Regards,
Hector

Hi,
ME2N - In selection screen, enter Selection parameters as
WE102 i.e. Goods receipt exists and in output screen put a filter on "Still to be invoiced (qty)" and "Still to be invoiced (val.)" as not equal to zero OR greater than Zero.
OR use RECHNUNG i.e. Open invoices and execute the report
OR Use MB5S - GR/IR Balances

Purchase order not create in sus

Dear customizer,
Ihave implemented a plan driven procurement with sus (r/3-sus) scenario,we have a problem when we transfer idoc from r/3 to sus.In sus sistem give me this error message
"An error occured within an XI interface: Exception occurredE:BBP_PD:BBP_PD:051 -No address found for partner function type Sold-to Party E:BS:002 -"Create" is not allowed (SUS Purchase Order 4500000006 )CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>"
I hope in your answer.Thank best regards.
Pernasetti Alessio

Hi,
Please check the following things.
Check whether the roles delivered by SAP meet your requirements. If not, you can create new roles and assign transactions to them. We recommend that you copy standard roles and tailor them to your requirements.
All users assigned to a respective role are then allowed to carry out the transactions. If required, you can refine the authorization check on the tab page Authorizations.
Standard SAP Single-roles
SAP_EC_SUS_ADMIN_PURCHASER (for purchasing administrators - SAP Supplier Self-Services)
SAP_EC_SUS_BIDDER (for bidders - SAP Supplier Self-Services)
SAP_EC_SUS_DISPATCHER (for dispatchers - SAP Supplier Self-Services)
SAP_EC_SUS_INVOICER (for invoicers - SAP Supplier Self-Services)
SAP_EC_SUS_ORDER_PROCESSOR (for order processors - SAP Supplier Self-Services)
SAP_EC_SUS_MANAGER (for managers - SAP Supplier Self-Services)
SAP_EC_SUS_SERVICE_AGENT (for service agents - SAP Supplier Self-Services)
If you want to use SAP Supplier Self-Services, proceed as follows:
1. Select one of the following single roles:
SAP_EC_SUS_ADMIN_PURCHASER
SAP_EC_SUS_ADMIN_VENDOR
SAP_EC_SUS_BIDDER
SAP_EC_SUS_DISPATCHER
SAP_EC_SUS_INVOICER
SAP_EC_SUS_MANAGER
SAP_EC_SUS_ORDER_PROCESSOR
SAP_EC_SUS_PRODUCT_MANAGER
SAP_EC_SUS_SAR_PROCESSOR
SAP_EC_SUS_SERVICE_AGENT
SAP_EC_SUS_SERVICE_MANAGER
2. Choose Change Roles.
3. Choose the Personalization tab page.
Note: The personalization applies to all roles, meaning the user can also create his own roles, for example copying the delivered SAP SUS roles. He can tailor these roles to his requirements by changing the SUS-specific attributes (BBP_SUS_ROLE_ATTRIBUTES).
1. Select the entry BBP_SUS_ROLE_ATTRIBUTES (SUS-specific role attributes).
2. Choose Change values.
A dialog box for maintaining SUS-specific roles appears.
3. If required, perform the following steps:
If the role should be displayed in the SUS User Management (UM) and should be able to be assigned to the relevant user by the supplier administrator, set the indicator to display the role in SUS UM.
If the user should be displayed as a service agent for the purchaser, set the Service agent indicator.
If you want to define the user as an SRM administrator, set the SRM administrator indicator. The user is then authorized to change all supplier data.
If want to assign the role SUS administrator automatically to the user during registration, set the SUS administratorindicator.
Sets the relevant indicators if you want users to receive the following notifications: Notification If Purchase Order Not Opened, Notification If Purchase Order Response Is Missing, Notification If ASN Is Missing, Notification If ConfirmationIs Missing, Notification If Invoice Is Missing,
Award the points for the help.
BR,
Vijay Mittal

Import Standard Purchase Order not picking data when submitted from backend

Hi,
As part of my code, I am inserting Purchase order information in the interface tables with process_code = 'PENDING'. Then using fnd_request , i am triggering the Standard Program for importing these Purchase Orders. The standard program is getting triggered and completing normally. But it is not picking any records. I am calling the program as follows:-
              -- Setting the org_id so that the import program will run for that particular org_id.
              fnd_request.set_org_id(r_org_id.org_id);
               -- Submit the Import Standard Purchase Orders by calling the standard program for respective org_id
              l_req_id := FND_REQUEST.SUBMIT_REQUEST(application => 'PO'
                            ,program      => 'POXPOPDOI'
                            ,description => 'Import Standard Purchase Orders'
                            ,start_time => SYSDATE
                            ,sub_request => FALSE
                            ,argument1 => NULL
                            ,argument2 => 'STANDARD'
                            ,argument3 => NULL
                            ,argument4    => 'N'
                            ,argument5    => NULL
                            ,argument6 => 'APPROVED'
                            ,argument7 => NULL
                            ,argument8 => NULL
                            ,argument9 => NULL
                            ,argument10 => NULL
              COMMIT;
When I am submitting this same program from front end, for the same set of records using the same set of parameters, the records are getting picked.
Any suggestions for this?

Hi
Do you have a copy of your insert statement?
regards

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

Similar Messages

Maybe you are looking for