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

Similar Messages

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

Appluing release strategy for scheduling agreement

Dear Sapguru,
Can anybody explain.How to apply release strategy to scheduling agreement.I'm working on MRP implementation project.
Here already release strategy using for PO.
Pls explain steps of release strategy to scheduling agreement.

Hi,
Welcome you post on the forum.
Have you searched the forum already? Such as:
http://forums.sdn.sap.com/search.jspa?threadID=&q=%22applyreleasestrategy%22&objID=f245&dateRange=all&numResults=15&rankBy=10001
Thanks,
Gordon

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

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

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

Release strategy for sheduling agreement

Hi,
pl suggest me about release strategy of sheduling agreement.
Is there any different release class required for SA other than PO?

Hi,
Release Procedure method is same for all the External Purchasing Documents (RFQ, PO, Contract and Scheduling Agreements)
You have to use class with class type 032 and characteristics with Communication Structure CEKKO

Reset Release Strategy for any change in the Purchase Order

Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavan

hi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f

Mass po reset release strategy

i want to know transaction or program or function module name or any other ways for performing
" mass po reset release strategy " , please help

Hi Veeru,
You can release the PO's all at once. Please sit with your technical consultant and ask him/her to write the code which takes the inputs of the Release Codes and the indicator Released and pass this information (PO number, Release Code, Release Indicator etc what ever is required) in the BAPI_PO_RELEASE. Some coding needs to be done to do this.
Hope this helps.
Regards,
Saroopya.

Reset release strategy

I've added a logic in user exit "ZXM06U22" to reset release strategy once the net price have been changed both increase or deducted. The program source as below, but it can't work. How can i reset the release strategy once the net price deducted. Thanks!
    i_cekko-usrc2 = 'X'.
    loop at it_bekpo into wa_bekpo.
      select single NETPR into lv_netpr from ekpo where ebeln = wa_bekpo-ebeln and
                                                        ebelp = wa_bekpo-ebelp.
      if wa_bekpo-netpr < lv_netpr.
        clear i_cekko-usrc2.
        rel_flag = 'X'.
        exit.
      endif.
    endloop.

hey did you get the answer for this.... I am having the same problem ...
If posible could please reply on this as soon as possible... thank you in advance...

Release date and release no of Scheduling Agreement

Hi All,
I have a problem with Scheduling agreement.
I have created a scheduling agreement with long validity period.
I maintained delivery schedules within that validity period.
I have generated forecast schedules. then using ME84, creating a releases.
the problem is occurs here.
it was not updating the release no and release date for the schedule line.
still it is showing a *yellow light* .
where is the problem and why it was not updating.
and can u please explain the process and significance of those lights.
Thanks in Advance.
Regards
Kishore

Verify the table T161M has the values
kvewe = 'B'
kappl = 'EL'
druvo = 1
kschl = LHPA
as mentioned in the code.
The solution is add in SPAD the

Cannot reset release strategy for RFQ

Dear SAP gurus,
I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
Best regards,
John.

Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
Lakshman

Release strategy for Schedule Lines

Hi,
The requirement is MRP should not run for Line item unless it is released by an authorized user. Logically availability check has to happen at the time release of the requirement line for the consideration of realistic manufacturing time. Also, user should not be able to cancel the release, or edit the schedule line once Planned or Production Order is generated for the requirement line.
What we want is a Release Strategy in sales order for each schedule line individually similar to PO Release.
I have currently set up a status profile, which has 2 levels Processing and approved, which effectively block creation of DELIVERY doc, but I am unable to control the schedule line.
Any ideas?
Cheers.
Edited by: Sowmya Mohan on Sep 12, 2008 1:14 PM
Edited by: Sowmya Mohan on Sep 17, 2008 10:17 AM
Edited by: Sowmya Mohan on Sep 17, 2008 1:03 PM

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

Reset release strategy PR

Hi!!!
How can I do to reset an strategy when the document is modified in some level of approval in a document PR.
Thanks in advance!!!

Hi,
I have a similiar problem. We are running ECC6 and have noticed that when a user with no release approval makes a change to a PM work order (change of work order basic start date, TECO the work order etc) then the release strategy on the associtated purchase requisitions is reset.
This is causing PRs to be set as "blocked", even though the PR lines are deleted on TECO of the work order.
The opposite also occurs, where a user with release approval greater than the value of a released requisition changes the PM work order, it then deletes the PR release strategy as the release strategy would not have been initiated if that user created it in the first place.
Our release indicator "2 - RFQ/Purchase Order" has the changes after start of release set to 4 (changeable, new release in case of new strategy or value change) and 0.0% value change set.
As there are no changes to value when the date or PM work order status is changed, why does this reset the release strategy?
Any help will be greatly appreciated.
Matt

Reset received quantity in Schedule Agreement with IDOC DELINS.DELFOR02

Hi,
Does somebody know if there is a functionality in DELINS.DELFOR02 (VA32) to reset the received quantities by the customer?
On the MM side this is a standard functionality but I can not find it on SD side. I played around with some fields like AKUEM and "date of received quantities set to zero" but this didn't have the correct result
Thanks
Ron

No, there is not such functionality in the way you want, but
the cumulated quantity becomes zero only when changing the fiscal year of the customer and in Idoc the cumulated received quanity is decreased.
have a look to:
http://help.sap.com/saphelp_erp2004/helpdata/en/93/743b11546011d1a7020000e829fd11/content.htm
pls.reward points if helpful
regards
Roberto

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
Amar

Hi 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

ME38 resets Release strategy of Scheduling agreement

Similar Messages

Maybe you are looking for