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' .
Similar Messages
-
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. -
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.
Anisahhi
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 -
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,
SrikanthHi
Check out the release statergy with classification values and also check - your service sheet falls under this criteria.
Regards
Anand -
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 strategyhi..
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 strategyHI
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 -
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...
ChrisChris,
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. -
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,
MamaRarahi
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 -
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_LHi,
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 -
MRRL- Item 00002 for purchasing document not selectable
I have a PO which was created with ERS flag on, when we did GR we realized this should not be ERS activated PO. So we reverse the GR and unchecked the Inv. receiptm GR based IV and ERS flag on the PO but now this PO is keep showing up in MRRL with a message "Item 00002 for purchasing document not selectable". How do i get rid off this PO from MRRL report.
Please help!When an item is marked as ERS and a GR is done an entry is put in the EKRS table. My guess is that you did not do a settlement after you did the reversal so the EKRS table still has the original GR and the reversal which is why it is showing up when you execute MRRL. If you don't want that showing up when you execute MRRL I would add the ERS flag back long enough to do a settlement. The settlement will create a zero value MM invoice and clear out those two entries in the EKRS table.
Regards,
Sandra -
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. -
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 -
Send purchase order e-mail with release strategy
Hi!!
I have a problem with sending e-mails in purchase order that are blocked with release strategy.
I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
Somebody knows what is happening?
I would like to send e-mails without previous modification of the purchase order.
Thanks for your help.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 -
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,
HariHello 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 -
Purchase Document not appearing on GL Line item report
Hi gurus: Please help me figure out why even though I have activated the purchase document field in the field status group I still cannot see it in the line item reports when I run FBL3n. Note the purchase document field is showing up as a field for selection but it comes thru blank.
Please help me
thanks
Briani wanted to get the same output, it doesnt work for some reason. I had to craete a query to achieve this
Maybe you are looking for
-
Hello! Please change my subscription to my new order yesterday. I do not want to subcripsions on the same product. Nothing has happened yet. Why! I feel sad. Åke Rosén
-
How do I check the Oracle enviornment variables for a connection?
I am using Oracle JDBC 10.2.0.4 and trying to output the Oracle enviornment variables for a connection. I am trying to determine if the values output from sqlplus from the following two SQL select statements are different in the connection object: SE
-
Internet sharing suddenly not working, PC related problem
Here's the scenario. My Mac-Mini, using 10.7.4, is sharing its Wi-fi connection to my airport extreme base station through a hard-wired ethernet connection with a PC. So the mac is tethered via ethernet cable to the PC, so it can share its wifi conne
-
Hi All Can we create the any kind of Mapping Interface that allows for defining metadata that is then used to perform dynamic SQL calls. the SQL is created dynamically at execution time. Mapping involves a)Target Field Identification b)Source Identif
-
Page/point view of Planning web forms
how to set the members in ascending order in the page/point view of the hyperion planning webforms. I have tried with the SORTDESC command, but its does not gime me the expected result. Thanks in adavnce. Edited by: 798780 on Sep 29, 2010 9:52 AM