Release Strategy for more than 8 levels

Hi experts,
Can anybody have a clue how to get Release Strategy for more that 8 levels or anybody who have configured the same. Standart SAP supports 8 levels of Release Strategy. So How to enhance the standard feature with additional Levels.
Thanks in Advance

Hi Senthil,
Thanks for the suggestion.
You mean to say :
That a purchasing document which has some 16 llevels of release strategy can be accomplished through :
1. Release Strategy configured through 8 levels.
2. A custom table needs to be created where based on one of the classification (Usrc01) feild of 1st Release Strategy should be mapped to another Usrc01 feild for some other Release Strategy2.
OR
2. Custom table have Release Strategy 1 name and another feild will have Release Strategy 2 lined to 1st Release Strategy.
3. Based on FRGGR and FRGCO and ZTable should trigger next Release Strategy 2. But hou will this be displayed and what about Change History?
Thanks that was an innovative idea but can u please elaborate.
Thanks in advance.
Ashutosh

Similar Messages

Release strategy for PR with materials having different prices

Hai Gurus
Can we make a release strategy for a variant configured material ?
I mean create a strategy in such a way that price is critical factor and the materials what ever we choose for the PR has different characteristics dependencies like for example ( A chair having different characteristics like color, material ( like steel, leather etc) and other features like wheels etc and whatever characteristics we choose has a different price.......... so when v come to the release strategy it has to be approved by the next level if it reaches $ 1000 and so on.
please help me out in this issue

Hello Arif Mansuri
thanks for your reply, yes I have taken it as total value only. The scenario is I am asked to use three different characteristics ( total value, materials, MRP Controller) and assign them to a class and if the customer picks any number of different materials and if the price is more than 1000 then it has to reach to the next level for approval. i thought i am suppose to use object dependencies here......... can we do this in a normal release order if so how would be the strategy played here?
thanks for your time

PO Release Strategy for a single Plant

Dear Friends,
I have created a new release strategy to trigger multiple plants
Release Strategy is triggering in case of PO is having more than one single Plants but not in case of a single plant in one item or multiple items for the same plants.
I know that PO release strategy is at header level so I have not entered plant in CL24N.My purpose is solved in case of aPO is having more thatnn one plant but still i need to get the Release Strategy to trigger in case of any single plant or more than one time by using a single plant in PO.
Has anybody done this? Could you please suggest any logic to be developed if available
Thanks
Ranjith'

Hi Ranjit,
Do you have PLANT as the Characteristics in the Release procedure?
If not there, add PLANT as Characteristic and enter plant code in CL24N & also make the plant value as blank and check.
eg. suppose You Have two plants codes 1000 & 2000
So enter both plant codes(1000 & 2000) in plant value & also enter one blank value in Plant field.
In characteristic value
Plant-1000
2000
No Plant
Thanks
Madhurendra Sharma

Release strategy for PR in Third party case

Hi,
We have this third party scenario where Purchase reqs are created at the time of Sales Order creation. A release strategy is attached to these purchase req by defining a custom field in MMaster, whenever qty goes up or equal to tht field release strategy is applied.
The problem is, for the same material's PR, the release strategy is set in one case whereas for other PR (of different sales order) it is not set. Please help let me know what could have gone wrong.
Thx.
Amit

Per your information you say that based on a custom field qty in material master release strategy is triggered. Do you have any charecteristic maintained for the Release strategy anything other than this parameter- because there must be some difference between the 2 Reqs.
Or check the change history in Material master it may be possible that at the time of second sales order if the field value was changed so that release strategy was not triggered.
Please give more details
Thanks
Deepak

Release Strategy for Credit Note un the QM Module

Good SAP Guru's,
I have a very important question for you:
Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
This should work on the same lines as the Purchase Order Release strategy.
Any guide lines and/or assistance will be gratefully appreciated.
Kind regards,
Leslie

Dear Leslie
We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer a notification will be trigered to manager and if he approves it will go for higher approval.
Please find my suggestion for this development
1) Make 3 task codes. for eg Task 1 for credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
2) According the need of the credit notes to be created let the user assign the task and release it.
3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
6) The credit memo creation will have to be developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
please let me know your apprehensions
Regards
gajesh

Release Strategy for PO not kicking in

Hello SAP Experts,
I have gone through all the steps of configuring release strategy for PO. I checked at the end with the transaction code OMGSCK and everything is good with no error. But when I test the strategy by creating a PO, the 'Release Strategy' tab does not come on in the PO Header. This means that the Release Strategy did not work. I have troubleshot over and over again right from the Characteristics/Class, all the way to the Release Strategy, but no breakthrough.
I will appreciate and award points for helpful hints.
Thank you in advance.
Joel.

Please list all your char you have created and the value of char.
Than please tell the PO details.
once i got this info than only i can see the problems.
you can do one more thing
goto CL30n and enter the class and class type 032
than hit enter and enter the value of char which you have used in the PO and then hit find initial class button from top menu
see if any release strategy is pulled or not?
if it is determine morethan one that means you have same value exist in more than one release strategy

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

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Release strategy for PR and PO

I have release strategy for PR and PO, suppose there is 3 levels of Release, at second level I want to set an alternative Release code, if either of the employee releases then it should go to third release.
How to configure for PO (with classifications) and PR (without classifications).
I am not using workflow than how to do it ???

follow the steps below.
Release prerequisites should not be checked
Release statuses do the following settings for alternate release
based on your requirement
you can make the release or blocked status manually in release config
than it will work.
without classification it will not work

What is the use of Release Strategy for Sales Document

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.
Lowest Status No: Sale Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated; the old status with status number is deactivated. This is only valid under certain conditions. The system makes a note of the status with the highest status number that has been reached up to the present. The "lowest number" of this status number determines which status number a new status must have.
Highest Status No: Sales Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated, the old status with a status number is deactivated, provided the new status number does not exceed the 'highest number' defined for the old status number
If you want more clarity try to check below link
http://www.sapfunctional.com/SD/ReleaseStrategy/Index.htm
Regards,
Prasanna

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

Release strategy for Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Add Suppporting Details for more than one periods at the same time for the same Account in Planning.

As we know, in planning form, we can add supporting details to one cell for the level 0 members intersections.
But can we do that as below:
add supporting details for more than one cells at the same time?
I tried to do that in workspace and smartview, neither is working.(my workspace version 11.1.2.2.300.20)
I wonder if i am not with the right version, because i don't know how to get the below.
Can any one explain?
Thank you.

Hi,
I have tried in Smartview for a simple form where my period dimension was in columns and accounts in rows.
You need to select multiple period and select supporting details, it will show those selected period for which you can add the supporting details.
You can add these details and then submit the data in the form.
Regards,
Sourabh

My ipod touch 4th generation no longer holds it's charge for more than 40mins,needs new internal battery but I have no idea how to go about this. i love my ipod and don't want it to loose power completely, can anyone help?

My ipod touch 4th generation no longer holds it's charge for more than 40mins from full power, think it needs a new internal battery but have no idea how to go about this and am no longer covered by my guarantee. Can anyone advise me on what's best? Thanks in advance

Using the battery level meter in this manner is comparable to using your car's fuel gauge to calculate miles per gallon. The only thing that matters is the total amount of operating time from full charge to auto-shutdown.
Use an Apple wall-mount charger. Do NOT use a computer's USB port. Then, operate it normally until auto shut-down (ignore any low level alerts that may appear). An irony is that doing that test to determine the total operating time is also the exact procedure necessary to calibrate the battery level meter.
I'm not claiming that you do not have a problem. I am stating, however, that we don't yet know whether or not a battery problem exists.
According to Apple:
Use Your iPod Regularly
For proper reporting of the battery’s state of charge, be sure to go through at least one charge cycle per month (charging the battery to 100% and then completely running it down).
Elsewhere, Apple elaborates and explains that two half-discharges (or four quarter-discharges, etc.) equals one full discharge.

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Payment Terms for more than 3 payment terms in OBB8

Hi Gurus,
Please advise as to how to create for more than 3 instances, say 4 or 5. Because standard SAP provides only for 3. Let me brief you as below :
- I created the 5 payment Terms in OBB8. 5001 (clicking as instalment) ; 5002 for 5% - 30 days ; 5003 for 4% for 60 days ; 5004 for 3% for 90 days and 5005 for Net 180 days.
- I assigned these 5002 to 5005 to 5001 with say 25% instalment each in OBB9.
- Now I assigned this 5001 payment term in the Vendor Master.
- Posted new FB60 invoices with say 01st Oct 09 as Document Date with say Rs. 25000/-
- Now, I have to make the payment to the Vendor on say 15th November 2009.
- So ideally I am eligible for 4% discount on Rs. 25000/- since I am paying after 30 days and before 60 days.
- I am posting through F-53 with 15.11.2009 as the document data, and now the system is not calculating discount for the first instalment of 25% instalment and for the next 25% the discount is calculated @ 4% on 25% only.
- Now my requirement is to calculate 4% discount in Rs. 25000/-.
Can any one suggest the required approach.
Vikas

Hi,
Unfortunatelly payment terms in OBB8 is working as designed and the functionality cannot be enhanced. In the standard system you cannot add additional levels in the transaction OBB8.
Instead you can check the option of using Terms of Payment for Installment Payments (transaction OBB9). Terms of payment for installment payments are made up of individual terms of payment. An individual payment term can be assigned to each installment. When you post an installment payment, the total amount is split up into individual items for each installment and each installment
is calculated with the relevant payment term. For more information on maintaining terms of payment, refer to the Implementation Guide for Accounts Receivable and Accounts Payable.
The terms of payment key can determine the following:
-The valid cash discount rate for an individual payment with a maximum of 3 payment terms (first cash discount period, second cash discount period, and due date for net payment) and also a baseline date for the payment
-The terms of payment for installment payments.
You define the following for the terms of payment key for installment payments:
- Sequential number of the installment
- Percentage rate for the installment
- New terms of payment key for the installment item
The percentage rates you specify must total 100%.
Example
Suppose you can create payment term NT30 (30 days net), NT60 (60 days net), NT90 (90 days net).
Installment terms of payment
RT01   1   30%   NT30
RT01   2   30%   NT60
RT01   3   40%   NT90
I hope this helps.
Regards
Ravinagh Boni

Release Strategy for more than 8 levels

Similar Messages

Maybe you are looking for