PR release strategy - BADAT - PR date

Dear all,
I have following situation.
I have release strategy where one characteristic is PR date (CEBAN-BADAT).
First release level in this strategy is for the person who creates PR. This level is defined in order to give time to the person who creates PR to check and edit PR before it goes to the next level for approval (real approval by manager).
For example, I am creating PR with 100 items. Today I will put 70 items in PR and tomorrow 30, and afterwards I will release it on first level so that PR will be visible to next (management) level. In this way, when I finish all checks in PR I will release it.
(Without this level (in case if it is not set) PR is visible and available for approval earlier and there is a risk that it could be processed before it is completely filled with all items and before it is checked.)
BADAT is set as interval, 25.07.2014 - 31.12.9999
The problem is when I create PR with item on 25.07.2014, the strategy is activated. But tomorrow, when I add new item, strategy is not activated, message no. is me519.
I suppose that this is due to the new BADAT for new item, which is put on 26.07.2014.
But why the strategy was deactivated, since new date belongs to the specified interval also.
If this is the normal (standard) way how the strategy works (with more dates, values), do you know how can I solve my problem?
br
Dragan

Last week, we had a similar discussion PR Overall release issue
There, his problem was about user id and here your issue is about date.
Read the discussion, concept is same for both situations.

Similar Messages

Release strategy problem in RFQ

Dear cons
In release strategy of P.O we are using three characterstics. I.e- net order value, purchase group & plant. Wehave not made any Release strategy setting for RFQ..while we are creating RFQ the system ask to release the RFQ. wHY.wHAT IS THE REMEDY FOR THAT. BECAUSE WE DONOT WANT TO RELEASE THE RFQ. I saw which data I have entered for P.O release strategy The same data is available In RFQ path.The path is img-material mang- purchasing- P.o- rel. PROCEDURE for P.O- DEFINE REL. PROCEDURE FOR p.o. you can check same data is avaiable in RFQ PATH.
PL. GIVE ME SOME HINTS.

Hi,
Please use document category or document type or both as chanracteristics for the release class.

Why we Maintain the data in Trxn # CL20N / CL24N for Release Strategy ?

Dear All Gurus,
Please resolve my Query , that during maintaining the Release strategy for a P.O , i used to create characteristics for defined values such as plant , currency , doc. type etc, then creating class and assigning these characterstics with this class created.
Now after this i had create Release Group , Release Code and Release Strategy and assigned the Rel. Code with the Rel . Str and in Classification tab i had manually mentioned all those created Characterstics in CT04 and finally saved this Process.
Till now i had not at all made any entry in Trxn # cl20n.
But when i had create a P.O with all the values as same as defined in characteristsc , the Rel Str got triggered succesfully.
My Question is that , what is the use of mainiating data in Trxn # CL20N & CL24N ?
Please clarify my doubt.
Many Thanx in advance.
Rgds
sap11
Edited by: Rajeev Chaturvedi on Jan 20, 2011 5:08 PM

it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
You can do this from withion those objects, or from the central classification menu using the classification transactions.
People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

Cusotm data tab In ME52n, copy release strategy tab details in custom tab

I have created a custom data tab in Me52n using exit mereq001, and I need to get purchase requisition number, releasegroup, release code and release strategy values in the custom data tab screen in order to fulfill my requirement.
I am using the screen exit and trying to code in the include (PBO), But in the include I am not able to get the required data as afore said.
Can you please tell me the procedure for getting the global structure that I can use in the include to get these values?
*Please give me the solution ASAP.

HI,
Use the fm EXIT_SAPLMEREQ_001 and get the data ..............
data : wa type mereq_item .
call method im_req_item->get_data
receiving
re_data = wa
the structure wa will contain the data .....
Thanks,
Shailaja Ainala.

How to check the PR release Strategy change date?

hi,
how to check when the PR Release Strategy chagned by someone ...?
Regs,
S J Solanki

Hi
You can directly go into the Purcahse order & check for the Heder changes which will give the Changed Date
If you need to use two table to find out the date when the Strategy was changed.
Use Table CDHDR & CDPOS. Object key is the POurcahse order number
Thanks & regards
Kishore

How to get release date of PR at different levels of releasing strategy

Hi All,
In the releasing strategy of PR we have three levels R1 R2 & R3.
Suppose a PR is release at R1 level on 01.01.2009
at R2 level on 03.01.2009
at R3 level on 05.01.2009.
How will I come to know the relese date at all the three levels of a PR.
Please help.
Thanks ,
Salman Zahir

Hi Salman,
IT is not depend on the mateail number.
Based on object class 'EINKBELEG' and object id 'u r PR number* U can get the record from CDHDR.
In CDPOS u will have file fieldname also for which field u have 'Chnage document' check box is checked then those deails will be stored in.
Look at the FM 'CHANGEDOCUMENT_READ_HEADERS' and 'CHANGEDOCUMENT_READ_POSITIONS'
Get back to me if you need any help.
Thanks,

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 Sampath

Hi 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

Release strategy on doc. level isn't working because different values for B

Hi,
At my company we just created a new release strategy (3rd) for PR's. The old strategies were on item level, the new one is on document level. This is the third strategy in the system and with every new PR the strategy is decided based on the creation date (table EBAN field BADAT). For example:
Strategy 1 - BADAT < 2009.01.01
Strategy 2 - BADAT >- 2010.01.01 AND BADAT < 2011.01.01
Strategy 3 - BADAT >2011.01.01
These selection criteria are stored in the class.
This used to work fine between the 1st and 2nd strategy but now it doesn't. Whenever a new line item is added on a different day than the other line(s) the value's for BADAT will be different within the PR and the system isn't able to select a strategy. It's like no value is used for BADAT because there are more than 1 available. As a result the release tab will disappear and the PR will be ready to create a PO from it.
For example:
Line 1 BADAT 15.09.2011
Line 2 BADAT 15.09.2011
No problem releasing the PR
Line 3 BADAT 17.09.2011 added (release strategy reset)
Release tab disappears so no release can be done. However, this PR line 3 can now be converted into an PO without being ever released.
One solution we thought about is using the PR number BANFN. But no ranges are allowed in the class so it doesn't seem to work. Another option is to delete al the old strategies but what will be the consequences for all the old PR's?
We are not sure what to use. Maybe someone else worked out this issue before or has an idea?

Hi,
First of all why you want to release a PR based on Creation date ?
Anyhow, as I understand from the above explanation, since you have created your 3rd strategy @ header/document level. You are facing this issue.
If you have a strategy @ document level then why you want 2 separate strategies @ item level.
Following are the possible solutions as per my understanding
1. You can make the 3rd strategy as item level itself so that the different creation date for different items wont be a problem.
2. You don't have to delete the Old release strategies instead you can remove the characteristics assignment so that release strategy wont be determined @ item level & you can keep the new release @ document level. But in this case you cannot have creation date as a characteristic since it will result in the same issue..
Thanks & Regards,

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

ME38 resets Release strategy of Scheduling agreement

Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
Sunil

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

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

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

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
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 01
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,
Ashok

Creation of release order possible during release strategy

Hi folks,
we have currently contract and purchase order release strategy parallel in place. Both are working fine.
We are using quantity and value contracts.
Quantity contracts are changed frequentely by the business; with every change (adding new items, changing prices of existing items), the release strategy is pulled again.
Our release indicator is set to 6 and has value change 0,00%.
The business requirement is now to release a contract with status X (e.g. 10 items and a total item value of 10.000EUR). After release, call offs can be created for all the released line items.
If a new line item 11 is added, it should still be possible to create call offs for item 1-10 but not for item 11.
Item 11 should undergo a new release.
Has anyone ever come across such requirement?
I have tried version management. However, version management will only force a new release whenever the version is completed.
Even then, the complete contract is subject to release strategy and it is not possible to create call offs.
We dont want to set error message ME347 "Release orders against contract xxxx not possible (contract not released)" to warning, as this will allow to always create call offs regardless of the contract being released or not.
Any ideas greately appreciated.
Thanks!!

I suppose program checks in EKKO whether contract is released,, irrespective of version exist it or not. IF you are able to direct it to EREV, then may be version 0 or ( current - 1 ) released can be returned.
Isn't it a special case that your version 0 data is intact in version 1; Even if someone change lines 1 to 10 , with or without adding line 11, it still triggers version 1. How do you ensure that lines up to 10 are not changed. you may have to look in CDPOS CDHDR with object Revision..
This is just an idea which you may discuss with your developer to see whether a copy of the program can be modified..

Precautions to be taken before going for new PR Release strategy

Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RS

Hi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

New Release Strategy in case of PO amendment

Dear All,
We have the release strategy at PO level on 3 parameters,
Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
When ever users edit the PO, again system sets the release strategy as per above logic.
Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
Can any one send me a user manual and steps for this.
Thanks in advance,.
Vikas

Hi,
You can set a control within Config. there is a parameter called as release indicator.
Follow this IMG path:
SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
1     Cannot be changed
2     Changeable, no new determination of strategy
3     Changeable, new release in case of new strategy
4     Changeable, new release in case of new strat. or val. change
5     Changeable, new release if new strategy/outputted
6     Changeable, new rel. if new strat. or value change/outputted
     Changeable, new release in case of new strategy
Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
Hope this explanation was clear.
Prashant Rathore.

PR release strategy - BADAT - PR date

Similar Messages

Maybe you are looking for