Scheduling agreement Release strategy release indicator

Hi all
For the Scheduling aggreement Release strategy is present & release indicator is 6 , Now the requirement is whenever user is changing the any value Scheduling agrrement it should go for rerelease. for any minor change in value even the value lies between the same Release strategy
Release strategy is configured on Purchase group & Value character
Also what is the difference between release indicator 4 & 6. for any changes in the SLA release strategy will be reset in this two release indicator.
Thanks & Regards,
Rajesh

Hi,
This is a standard phenomena any change in value (increase)will reset the release stategy
and indicator 4 & 6 are same only in case od indicator 6 if you have taken the oout also it will get affected

Similar Messages

Scheduling agreement in SD, release number

Dear All,
I trying to implement an automatic process for one customer, getting in an EDI 862; transferring this in an IDOC message type DELINS of Basictype DELFOR02 and updating the scheduling agreement accordingly.
This is working fine, for simple cases, but this customer is sending different release numbers for the same product at one time, and also sending the release numbers multiple times.
e.g. today I am getting for product A a release number 111 with multiple schedule lines, and also a release numberr 112 for the same product with multiple schedule lines.
tomorrow I might get again an EDI 862 for this same product, containing revised information for release number 111 and 112.
This is in my understanding not matching the SAP logic, where it's clearly stated, that a new release number is replacing completely the old release number.
Does anybody has any idea how to implement such a process?
I already have studied all documentation, tried to implement it in different ways, but I am reaching every time only a 80 % solution.
Do we have in this community any experts on scheduling agreements on the SD side, which might be able to help me?
Thanks for any possible help.

check these
BAPI_CUSTSCHEDULAGREE_CONFDELV Customer Sched. Agreement: Confirmation of Delivery; Document Flow Upd
BAPI_SALES_DEL_SCHEDULE_CREATE BAPI for creation of releases in scheduling agreements

Old PR release strategy - release completed status change

Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RS

Hi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

PO Release strategy release procedure

Hi
Any body can suggest
what is the procedure for release strategy transport to anther system means D to Q

Hi,
Release strtagy Configuration can be transported from one client to various client[Like creation Class,characterstic,Release code,release strtagy definations etc]
Where as assignments of Objects / class and various parameter for release strategy has to be done in individual clients in -T-code: CL24N.
Example : For Class -PO Release we need to assign -Values for Class -characteristic values has to assign in CL24N
with regards
Shrinivas Gangoor
Edited by: Shrinivas Gangoor on May 22, 2009 3:06 PM

PO release strategy - release code

Hi Experts,
I have completed the release strategy and transported to production.
However noticed that the release codes that has been configured earlier wasn't in the production.
Is there a way to update the release codes in the production besides using SPRO (no authorisation for maintaining - only display) like using CL24N to update the characteristics?
Thanks and regards

Hi,
Please first check the attached notes that refer to transport issues.
365604   FAQ: Release strategies in purchasing
186809   OMGQ/CL24: Inconsistency for release strategy class
   86900   Transport of Release strategies (OMGQ,OMGS)
   45951   Transporting class data: system / client
   10745   Copying classification data to another client
The classification data must be sent over using ALE. It does not get
transported directly. Notes 45951, 86900 and note 365604 should help.
Please follow the instructions in note 45951.
You can obtain more information about how to set-up ALE in the Online
Documentation CD (R/3 Library > CA - Cross Aplication Components >
Business Framework Architecture > ALE Integration Technology > ALE Quick
start).
However, if you can't set-up ALE, you can re-create the classification
data agin in your target system. For that you have to:
1- assign new values to the characteristic master data (t-code CT02)
2- assign the new data to the classification system (t-code CL30)
3- verify the consistency with t-code CL24. Please see note 186809.
For more information, please see note 365604.
The transport of release procedure customizing data can only be done
in a restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
Classification data can only be transported via ALE as per note 45951.
Note 45951 explains what class data for the release strategy will be
distributed from one system to another. It does not describe how to
implement as this involves a lot of explanation and is truely a
consulting issue.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Best Regards,
Arminda Jack

Scheduling Agreement Release

Hi All
Scheduling agreement is created & released. Release indicator is 6, after the release again some line items are blocked & some line items are deleted without affecting any characteristic of release strategy
( No Change in value , Document type , Purchase group on which release strategy is based)
Wheteher release strategy will be reset in this condition form release to unrelease
Please suggest
Thanks in advance
Regards
Rajesh

Hi,
If no user exit is activated in support for your release strategy, then any change which results in no revision of your original value will not cause any release strategy reset.
Cheers,
HT

Schedule Agreement release report

All,
Is there any report to have the Schedule agreement releases to be generated online or in background?
Kindly advice.
Thanks

Hi,
Pls go to ME3N, choose dynamic selection on the top
Release group
Release Strategy
Release indicator
Release status
Subject to release
and execute, you get the report accordingly.
Reward points
Thx
Raju

Scheduling Agreement - Automatic Release Individual Schedule Lines

Dear all.
I've create a "LPA" scheduling Agreement and its release type is "JIT". So, I use to ME38 to maintain the individual JIT delivery schedule lines.
The problem I have is this method requires the person to manually release each individual delivery schedule line document on the due date before GR is allowed. Hence, is there a SAP system function that can automatically release any due delivery schedule line document without having to manually track and release using ME38 each day/week/month?
Thanks.
Steven

Hello
use t.code ME84 then system release the sch.lines automatically those maintained with me38.
Laxman

Badi for Purchase Requisition Release Strategy

Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to control the PO Price for a PR release strategy
Thanks for your help

This badi is for schedule agreement ?
BAdI: Release Creation for Scheduling Agreements with Release Documentation
Use
You can use this Business Add-In (BAdI) to influence release creation.
This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
This BAdI includes the following methods:
Change Data Before Release Creation (BEFORE_CREATION)
Change Data After Release Creation (AFTER_CREATION)
This BAdI is called during manual and automatic release creation.

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the 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.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

Work flow for release strategy for PO & PR

Hi Gurus
Can anybody explain workflow for release strategy for PO and PR
Thanks in advance.
Atul Kulkarni

Hi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT

PR Release Strategy Re-determining due to Change in Text

The PR release strategy was configured by a previous company. There are existing PRs that are not completely approved (Release Indicator = 2). The SAP instanced was transitioned to the company that broke away.
The PR release has now been re-configured with new release strategies (groups, codes..etc). What we are experiencing is that the existing PRs that are "released" do not show the new release strategy when the combination of release strategy/release group does not exist- This OK as well.
When a user made a change to the Item Text and nothing else, SAP re-determined the release strategy and started the release process over again. Is there a way to stop these PRs from re-determining and therefore restarting?

Hi There
Though the release strategy is different, i think all the classifications are same or old classification (even 4 or 5 parameters) may also part of your new full release strategy(You may be trimmed from old release).
So when you do any changes or just go to the change mode and Check (F7) , system may find the new rel strategy.
i have not tested the above scenario, i could recall some older posting based on that i did suggest the above
Thanks Senthil P

PR Release Strategy work flow

Hi Guys ,
I have a work flow requirement , In Which i have to know in Purchase requisition items history . how to identify the new item and
change items for triggering the work flow .
Here i am using a badi to triger an event . ( BADI : ME_REQ_POSTED )
Any idea , Plz share .
THanks
Nags

Hi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT

Pr& po -new release strategy?

Hi Friends,
My requirement is to add new release strategy for pr & po.
Characteristics & Class are remain unchanged.
Pl advise to how to proceed, i mean
i have to set/create new release procedure, ie.,
New release groups
New release codes (bcos new codes are added & release levels remained same)
New release strategies
How i can retain the Old PRs & POs released with earlier release strategy/release codes?
PRs & POs not released can be with new release strategy, but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
Also, I need ur advise, how the new release strategy works for workflow
pl help
thanks & regards
Srihari

Hi,
First of all, if you would only like to create the new release strategies, then the only possible settings you should do are -
1)   Create the new release code;
2)   Create the new release strategy;
3)   Assign the release characteristics values to your new release strategy in CL20N transaction.
For those old PRs and POs (regardless of if they were released or pending for release), the same old release strategy remains unchanged (and therefore, you should be much careful if you wish to delete the outstanding release codes and/or release strategies through configuration). Having said that if you would like to keep the same release strategy though changes are to be made to your old purchasing documents, then you will have to assign the proper value to the "Changeability" field of your "released" release indicator.
In case of release strategy in support by workflow, basically, the workflow item will be triggered (in accordance with the pre-defined logics that you built in terms of task ID). As soon as the approver determination is made in background, the workflow item will be then sent to such agent who will then take a proper decision (approve, reject or forward).
Cheers,
HT

User exit (To change the PO Release Strategy): M06E0004

Dear Experts,
         I am trying to implement the enhancement for changing the PO release strategy, using exit M06E0004 for following situation.
If PO is already released and then if any changes made to it affects the net amount which makes it less than previous net amount. We have to change the PO Release indicator to 'Blocked'.
We have tried to change the value of USRC1 USRC2 USRN1 USRN2 of structure E_CEKKO but it is not workingu2026
Please help me *how / what to change in the E_CEKKO structure*.
I am new to User Exit.

Hi Nagarajun,
I am able to solve this problem.!
All u have to do is follwoing two step.
1.maintained a flag in ur enhacement part (FM to Z_FIND_PO_RELEASE_STRATEGY)
inorder to know whether the current PO is without PR or not then export its value to memory.
2.Do enhancement in standard FM ME_REL_STRATEGIE_EKKO
(which is used to reset release strategy and indicator).
Inside this fm u can find below code
if xchange ne space.
*- Strategie geändert --------------------------------------------------
    if e_frgst ne i_frgst or
       e_frggr ne i_frggr.
      perform reset
         using e_frgst e_frggr
               e_frgzu e_frgkz e_frgrl.
      e_reset = 'X'.
*- Wertänderung prüfen -------------------------------------------------
    else.
      if t16fb-kzfae eq '4' or
         t16fb-kzfae eq '6' .
         perform currency_conversion using *cekko-waers
                                          bwkurs_old
                                          hwaers
                                          fwaers
                                          bwkurs
                                    changing *cekko-gnetw.
        f1 = *cekko-gnetw * t16fb-tlfae / 1000.
        f1 = f1 + *cekko-gnetw.
        if cekko-gnetw gt f1.
          perform reset
            using e_frgst e_frggr
                  e_frgzu e_frgkz e_frgrl.
          e_reset = 'X'.
        endif.
      endif.
    endif.
else.
    perform reset
       using e_frgst e_frggr
             e_frgzu e_frgkz e_frgrl.
endif.....
above code is use to check the PO amount and with old net amount,Since normally code is done to reset indicator only when amount is greater than old one, u can copy above code and modify with ur condition(i.e flag) and paste in last line.
Please check & reward is useful.

Scheduling agreement Release strategy release indicator

Similar Messages

Maybe you are looking for