Message no. CZ160 - Select a valid release strategy - IS Retail
while assigning PR release strategy to site thru' "Determination of Release Strategy" under tcode WB02, i am getting following error message.
Select a valid release strategy
Message no. CZ160
Diagnosis
The release strategy 01 is not defined.
Procedure
List the permissible values using F4, and choose a valid release strategy.
FYI, i configured PR release strategy "01" with required config. requirements and checcked the same thru' simulation and it is working fine.
Hi,
Please follow the steps;
1. Create characteristics via tcode CT04
2. Create Class for class type 032. Via tcode CL02
3. Then go to SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure. create release group, rel obj, class 032.
Next, set up release codes followed by release indicator.
Then the release strategies.
4. go to tcode CL20N to assign the release group and release strategy to the class and class type.
5. SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure -> Check Release Strategies
Similar Messages
-
I've defined several release strategies for contract ageement. When I create a contract, if the system cannot determine a valid release strategy, I can crate a document without release strategy.
How can I make a control when saving the document (tcode ME31K, ME32K) to verify that a strategy release is always defined?
For purchase order (tcode ME21N, ME22N) i've found a badi that works correctly, but it doesn't control in ME31K.
thanks,
MarcoI've definied several release strategy (100) with many parameters (company code, value, plant, etc).
Even if only one of parameters is not satisfied, the document has none release strategy, and I don't have any message about this.
By standard system I must define a phantom release strategy, with all combination not covered by the real strategies.
thanks,
Marco -
Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy when the amount is less than $2500.
Can anyone please tell me the name of the user exit that controls the 'Release strategy'.
Points will be awarded...
Thanks
RahulHi
Your settlement rule says "Settle to Cost Center" only.... I dont think any user exit can help in this case, if you want to settle occasioanlly to 2 cost objects
Try with these options
Option A
1. Remove the 100% validation tick in the settlement profile...
2. Maintain 2 settlement rules... i.e. One with Cost center and another with PSG... If any warning comes, ignore it
3. Execute settlement now
Option B
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, Menu GO TO > DETAILS and maintain Cost Center also....
3. Now execute settlement...
Option C
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, populate Cost Center also as a Valid Characteristic
3. Now execute settlement...
BR,Ajay M -
The message not completely displayed in validation
Hi,
I have created a new step in validation; this is when the post document without entering Reference key 1 (XREF1) will pop up this error message
in the message i have given " Select a valid value into the field &" and in message variable given BESG-XREF1.
but when the trying to post with no value in reference key 1, i am getting only the message "Select a valid value into the field"
and the character '&' is not replaced by field BSEG-XREF1.
what could be the reason for it.
thanks in advance,
ShwethaDear,
This is correct.
& is variable. BSEG-XREF1 is used as variable, if this field is blank then message will be displayed as & only.
For e.g if validation is set for company code and business are. Company code ABCD one thousand can not post business are other that 1000. And I have written a message Company Code & is not allowed to use business area & if business area is other than 1000 for company code ABCD.
In variables.
1. BSEG-BUKRS
2. BSEG-GSBER
Now when company code ABCD use business are 3000 then message will be displayed
Company Code ABCD is not allowed to use business area 3000.
In your case BSEG-XREF1 is blank so system is showing no value (&)
Your message should be Select a valid value into the reference field
Regards,
Chintan Joshi. -
Purchase requisition release strategy
I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
Pls advise.Hi Balaji
Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
Ex: Plant and doc type be the characteristics used in ur class.
Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
Try this using BAPI also. Get help from ur ABAPer.
Thx
Raja -
Item category control the release strategy?
Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
KetanHi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT -
No release strategy for service PO
Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
ShailendraKeep the release strategy at Plant level only....All the purchasing docs will get blocked
-
The following error showing up when I try to setup PO release strategy, Can someone help, please?
I try to do the everything following error states, but no luck. I am getting all RED Lights..
<b>Release strategy R for release group is inconsistent
Message no. ME_RELCHK058
Diagnosis
Release strategy R is not allowed because the associated release group no longer exists.
Procedure
1. Re-create release group .
Note
The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group in order to delete the release codes and release strategies.
2. Delete the release strategies and release codes for release group .
3. Then delete release group .</b>I tried that. Easy, but it didn't worked. Following is technical description of error
Message Text
Release strategy R for release group is inconsistent
Technical Data
Message type__________ E (Error)
Message class_________ ME_RELCHK (Check Customizing for Release Strategy)
Message number________ 058
Message variable 1____
Message variable 2____ R
Message variable 3____
Message variable 4____
Message Attributes
Level of detail_______ 3 (Level of detail 3)
Problem class_________
Sort criterion________
Number________________ 1 -
ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!
Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
RahulUse this exit.
MM06E005 -
No Release Strategy determined - Message no. Z_MESSAGES032
Hi All,
I am trying to creat PO without reference to PR and facing error:
No Release Strategy determined
Message no. Z_MESSAGES032
This is for newly created PO type and new cost center.
We don't have any PR, we are creating PO directly
please adviceHi Vishal,
As you mentioned you have created new PO type so I think release strategy is not created for this document type. You can go to the IMG ==> MM ==> Purchasing ==> Purchase Order ==> Rlease Procedure for Purchase order ==> Define Release Procedure for Purchase Order.
Select Release Strategies option and create new Strategy. Selecte the newly created strategy and go to details and click on Classification and then Add your document type and other information. If you have any existing release strategy you can select that and add another document type in the classification.
I hope this will help.
regards,
Ajay Mishra -
I keep getting the message: Your account is not valid for use in the US Store. You must switch to the Canadian Store before purchasing. I have selected the Canadian store, but still keep getting the same message. Any suggestions?
Hi hi-liter,
Are you certain that you are signed onto iTunes & Apps in the Canadian store?
Settings>iTunes & App Stores, click on your AppleID, and then click on View AppleID. Type in your password, then click on Country/Region. Once there, follow the prompts and then select the Canadian Flag.
Hope that helps!
Cheers,
GB -
Release strategy for Future validity period- (Outline agreements)
Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
AmarHi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
the contract is created and released on October the 1st
ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit -
Error message if no release strategy is applied for PO
Dear All,
In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
Is there any way to encounter this
Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
OR
While making GRN against this PO, System will give message Like say ... no release strategy is applied for the PO..
Please reply ...URGENT
Regards,
Rakesh ShelarDear Thanx.
my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
In this, case system is allowing to take GRN against such POs without release strategies -
Issue with retriggering Release Strategy
Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand SampathHi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew -
Error while creating new release groups in PO release strategy
Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
IllanDear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**Edit Characteristic Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
**Edit Class After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
*Define Release Procedure of purchase order In this step four processes involved.o Release Groupso Release Codeso Release indicatoro Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
Release code In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
Release indicator In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*Release Strategy *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh
Maybe you are looking for
-
I need to move my cs6 form old macs to new ones but but have not got the key
@These are three fully licensed versions does any one have an Idea
-
Hello together, we have an .Net application which implements the Change Notification using ODP.NET. On the customer site all worked well on the development and test environment connected to an Oracle database version 11.2.0.1.0. After setup of the pr
-
Lost Use of App Manager and Updates after Windows 8 install
I recently purchased Windows 8 and now the Adobe Application Manager will not run on my computer. In addtion, I am unable to update photoshop and several other CS6 programs. Does anyone have a fix for this?
-
Inheritance in mapping workbench
I try to use an existing class design with TopLink: I have for each table classes for value objects (*VO) containing only the attributes from the database tables (including the foreign keys). And I have classes for composite objects (*CO) inherited f
-
1487 error after moving ws object
Hello, I'm recieving the 1487 error when trying to remote control a WS after moving the WS object to a different container. I've search through many posts with the same problem but nobody seems to post a solution. Here is what I'm doing... 1. login a