SAP's Release Strategy on R/3 LIS

Hi All
Dose someone can provide me information regarding SAP's Release Strategy on R/3 LIS? I heard sometimes ago that SAP is not going to support R/3 LIS in the future to promote BW report. Is there any document on this strategy?
Thanks for help.
Jessica

Jessica,
LIS is not supported ... further on it will be LO , however , I guess
1. Existing LIS will anyway continue to work
2. You could look at migrating the LIS structures / extractors created to LO...
Will see if I can dig up any dope on the same...
Arun
Message was edited by:
Arun Varadarajan

Similar Messages

Accessing Release Strategy defintion from outside SAP

Hi !
I'm trying to integrate SAP MM with other 3rd party application. We want to access and read SAP's release strategy definitions and also document classes, to avoid having to maintain that information from the 3rd party too.
Is there any standard approach to access this info ? a BAPI maybe ? or do we have to access the data tables from a custom made RFC that reads specific tables ?
Thanks.
Regards,
Matias

Hi Rajoo,
As per I know, in standard sap, you can achieve this requirement.
Just make sure you have the characteristic for Total net value (CEKKO-GNETW) , and maintain the currency to USD. As long as you have USD to INR conversion in OB08, the system will able to fetch the correct release strategy for the PO based on the amount you set in the Release strategy.
Regards,
w1n

Release Strategy should be effected even if the PO Price is lowered?

Hi users,
Another doubt of mine is based on the release strategy (the Purchase order goes for rerelease) only in case of the increase in the PO Order Price (that is if the price is manually increased in a PO or if it indirectly increased by the increase in quantity)
Requiremnent: the current requirement is the po should go for a rerelease even if there is a decrease in the po price. alternately any change in the PO effecting a rerelease would also be acceptable.
anticipating an rearly answer.
thanks and regards
vinay

This is standard SAP. Release strategy will be reset only on increase in value. You have to make the release strategy think that the value has increased (even if it has decreased).
Please see (the second part of) my comment in
Re: release strategy is not reset in PO?
Reproduced here for your ease:
You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
Hope this resolves.
Lakshman

Release Strategy for Plants

Dearest Friends,
we have Plant A & Plant B
for Plant A     PR and PO <50K will be released by R1   and value >50K   by R1 and R2, R3.
*for Plant B   PR and PO >50K will be released by R1, S1 and >50K R1, S1, R2, R3.
how can we define the above release strategy.
hope you guys will help me.
Thanks and Best Regards,
Rajesh G

Hi,
for Release streagty either for PR or PO.
Steps :-
1. Create a Class T code CL01....Put Class type "32".
2. Crate Charateristics CT04 for ur case
Suppose for Plant ....in Addidtional data Put Table Name CEKKO and Field Name - WERKS
For Value ......... maintain CEKKO - GNETW
For PR .....
Table Name CEBAN --- WERKS for Plant
                      CEBAN -- GSWRT for Value
either go to se11, give the table name....u will get all the field there for which u want ur charterstics will work.
3. Assign Charcatristic to Class either in CL01 or cl24n.
3. Now go to Spro --> MM --> Purchase ---> release streatgy
first define Release code as R1, S1, R2, R3
Define GRp and Streatgy....
for Plant A PR and PO <50K will be released by R1
Suppose Grp is XY and Release Ste R1....click on details ....fill release Code R1 and in classification maintain Values <=50 and plant A.
Similarly Mainatin other....
Also u can document from
http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
http://sapdocs.info/sap/materials-management-2/automating-purchasing-approval-sap-release-strategy-tips/
Hope Help U !
Regards,
Pardeep malik
Edited by: Pardeep Malik on Sep 19, 2009 11:53 AM

Release strategy should revert

hi
in PO we r using only release strategy not version management .
our scenario is like this , once a PO has released and if any body tried to do any change in PO after that , then those release strategy should revert to unreleased status.
guide us where to do right configuration .
what currently happening is , if in changing mode we are giving Quantity more then previous it is reverting release strategy other wise not .
regards
sachin sharma

Sachin,
As SAP standard, release strategy will be reset if:
- the changeablity of relesae indicator set to '4' incase of PR and '4' or '6' in case of another purchasing doc (PO, RFQ, contract)
-the document stii subject to previous release strategy
-the new TOTAL NET ORDER VALUE is higher then the old one
For release strategy reset in PO i suggest to use user exit.
Reward if useful

Re: SAP Versions & Releases

Hi,
I want to know about the SAP ERP Release strategy. upto my knowledge ECC6 is the latest version in ERP.
Is their any change in installation procedure or environment between 4.7ee and ECC6.
vivek

Hi Vivek,
The SAP releases newer versions, these new versions has more functionality and features to meet the present business requirements,
for eg: You dont prefer to work Windows 98 no since you dont have all the additional features what you find in your present windows systems, like ease of use. Similarly SAP needs to come up with new functionality in order to make the client/customer feel comfort in running his business.
Similarly the installation procedure varies from 4.7EE to ECC5, in earlier versions you have installation tool R3setup which works in slightly different way and GUI screen input options are different.
From ECC5 we had SAPINST tool where you have more user friendly screen and easy to understand what each feild means and also you can restart the installation from where stopped.
About maintanence, SAP will give free support to its cleints for a term i think 5yrs, later there will be additional support for 3 yrs(this has to be paid), and later if still customer wanted support SAP provides for another 2 yrs(the cost is more) and after this SAP doesnot provide any support for that version and the client has to upgrade his software (since client pays for license every yr, which cost him same for older and newer version, its better suggested to get it upgraded)
Now most of companies has moved to ECC6(due to extensive functionalities of java stack) and many features of SAP work with SAP kernel 620 and above.
Hope this helped you to certain extent........
Regards.........

Purchase Order Release Strategy and SAP user RelationShip

Hi,
We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
E.g
A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
I am need to know can we develop a relationship b/w the release code and sap user or employee
Regards
Kamran ellahi

Hi,
We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
E.g
A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
I am need to know can we develop a relationship b/w the release code and sap user or employee
Regards
Kamran ellahi

Re: Cancelling of approval in standard SAP release strategy.

Hello All,
At present the release strategy used by our client has the standard SAP strategy. The release strategy works fine for the approval part. The issue lies with withdrawal of approval.
At present when a lower level approver withdraws his approval, higher level approvals are withdrawn automatically. Our client requires that when a higher level approver has approved the doc, the lower level approver ( who has already approved the doc) should not be able to withdraw it.
i have looked around on SAP but i don't believe that standard SAP allows for a strategy for withdrawal of release. I believe this is a common requirement for many businesses. Could you please show me how to go about this. Should it be done through customizing. We do have a workflow in place.
If your business had the same requirement, how did you configure.
Thanks for reading this.
Regards,
Soumyadeep Paul

Hi,
I think you have configured you release matrix in such way that even higher level approver is dependent on the approval of the lower level approver.
In release prerequisite, don't set lower level approver's approval as a prerequisite for approval of higher level approver and then check. But this should be first discussed with the Business users and then only can be implemented.

SAP Note PO release strategy based on net price

Hi
As we know this is standard sap as the PO release strategy can configure on PO net price not any other prices e.g. effective price etc.
can any body suggest me the related SAP NOTE for the same.
It's highly required for me to convince to the client.
Thanks in advance
Jayesh

Check the below exit and include which can be used in your case to consider the effective price.
Exit: EXIT_SAPLEBND_002
Include: ZXM06U22
Ask you ABAPER to include Logic as per your case

CCreate Release Strategy using department name in "Release Code", not User ID SAP.

hi experts...
i wanna create new release strategy, but in part "choose activities => Workflow => assignment of role to release code"
in field Agent ID usually we fill SAP user ID, but i wanna using department name.
is there anyone can help me
thanks,

Hi Raju,
Are you setting release for purchase requisition or purchase order ? If you are setting the release strategy for purchase requisition you need to enter table name as CEBAN and for purchase order give table name as CEKKO.
Enter tcode SE11 and give database table name as CEKKO and choose the appropriate field name for the desired component from here. Do the same with table name CEBAN for pur req.
Hope this was helpful.
Cheers,
XsNitin

Release Strategy ERROR in SAP-MM

Dear gurus,
I got a error while doing release strategy in SPRO. When click the Classifiaction button this error shows below:
ERROR: Error in classification(class TITAN CLASS RP class type 032)
Kindly give me brief solution for this error.
Regards,
Raju

Dear Raju,
The problem is that class and characteristics are available on system but the classification is missing. It arises among other reasons, if the release strategy has No classification.
You may need to transport again the classification data.
Regards,
ian, Wong Loke Foong

Sap release strategy

dear gurus,
             I have created a release strategy. it is working fine. if i edit it in such a manner, that the po value increases, it goes for re-releasing. but the issue is, if i edit it in such a manner that the PO Value decreases it does not go fo re-release.
              so my requirement is that, if the PO value goes down it should go for re-releasing
thanks
ujwal

Hi,
please see the note 662993 Resetting an already occurred release.
"When you reduce quantities or values the system only resets the release
if another release strategy is determined for the lower quantity or the
lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
This is a standard functionality and is desired.
A change of this functionality is only possible by means of a
customer-specific modification."
In standard there is no customizing setting to change this behaviour.
You need to use userexit EXIT_SAPLEBND_002 or modify
the standard function module ME_REL_STRATEGIE_EKKO for this.
Regards,
Edit

SAP - Release strategy Characteristics Default Value Usage

Hi,
I am currently working on Release strategy where in I wanted to set the Default Values for the Characteristics. However, Even though I have flagged the Default values, system it is not defaulting the same.
Secondly, I tried to use Option CL20N Where the value are apper, but when I Save, It is not stored.
I wanted to know, Is there any setup need to be done for default value or is some thing I am Missing out.
Please Let me know ASAP
regards
Arvind

Maintain the default values in char itself.
Goto CT04 enter your char and in Value tab enter all your default values which will be defaulted while char selection in release startegy.
Note untill the char values are not checked during assigning class and release startegy in CL24N they will not be saved.

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.

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

SAP's Release Strategy on R/3 LIS

Similar Messages

Maybe you are looking for