Scheduling agreements: reminders before expiring

Hi experts!!
for scheduling agreements, is there any way to send reminders to Procurement before they expire? If Procurement creates a scheduling agreement and the validity end is on 31.12.2010, Procurement would like to receive a reminder generated by the system 1 month before advicing that the scheduling agreement is about to expire.
Best regards

Hi,
The concept of SA is at the time of required the matl only it is appliacble, when u craete SA be sure that u give the delivary date or schedule lines in delivary tab.
The SA concept is to control the inventory & get at regular intervals of time
Then if release procedure is appliacble release the SA.
Then do MIGO the date u mentioned in the SA . then it will allow u to do it.
then do MIRO
Pandari

Similar Messages

  • GR for scheduling agreement even before actaul delivery date

    Hi,
    Is is possible to to GR for schedule line even before the actual delivery date. ?
    GobinathanG

    Hi,
    yes it is. Use Transaction MB01 and activate the selection box 'Suggest Zero Lines'.
    Carola

  • Expired Scheduling Agreements still in Credit Check / Rescheduling

    Hello everyone,
    I am running into an issue with expired Scheduling Agreements on the SD side (VA31,VA32, etc.).  There are many Scheduling Agreements that expired on a range of dates from 2005 to 2009, SA's that customers will not send JIT delivery schedules for anymore and are basically just out in the open and unused.  The issue is that these Scheduling Agreements are still being taken into account when a credit check is run.  Additionally, when our rescheduling jobs run at off-hour times, the system is still attempting to allocate materials to these orders.  The main problem with this is that it causes additional processing time for the rescheduling job.
    The current business process for these old Scheduling Agreements is to reject all the line items within the applicable SA, and as a result our rescheduling jobs avoid these orders, and they do not show up in VKM4.  However, the Valid To date in the SA is clearly in the past and I'm wondering if there is a way to have these closed without having to reject every line item.
    Any help would be greatly appreciated.

    Andy
    For credit check I would recommend:
    1) Using your own routine to exclude expired sch agreements in OVA8- Document controlling- 'No credit check' field.
    2)  rejecting at header level/ using "mass'.
    For Rescheduling
    1) Using button "Unconfirmed documents required" checked.
    2) Creating your own copy of the program SDV03V02  including document number, document type in the selection fields and creating a variant excluding specific, expired Sch Agreements. To reduce processing time, you may also try the 'divide and rule' policy and  execute several parallel/serial runs by using ranges of materials, plants, document types. I am sure you might have already tried this.
    Hope this helps.

  • Schedule Lines generated for expired Scheduling agreements

    Hi All,
    We are facing problems in Scheduling agreements.
    Schedule lines are getting generated for those agreements whose validity has expired(i.e Validity in Past).
    Is there any check to restrict those Scheduling Agreements??
    Please Help.
    Regards,
    Ritesh.

    from OSS note 914607 - FAQ: Validity and status of scheduling agreements
    1. Question: When I process scheduling agreements without delivery schedules, I have the option to specify the validity of the scheduling agreement: "Valid" and "Valid to". What role does the validity play when the scheduling agreement is processed?
    Response: In the case of scheduling agreements without delivery schedules, the system checks the validity of the scheduling agreement if you create a new schedule line or change an existing schedule line. If the schedule line date is outside the validity interval, a warning message is issued. You can then decide whether or not to create the schedule line or whether to adjust the validity of the scheduling agreement. No error message is issued.
    2. Question: What role does the validity play in the case of scheduling agreements with delivery schedules?
    Response: The function is similar to scheduling agreements without delivery schedules. The only difference is that the entry of the validity is optional (unlike scheduling agreements without releases) and this is not checked by the system. If the validity is missing, the system does note issue a warning message. If you specify the validity, the system behaves in the same way as for scheduling agreements without releases.

  • Invoice verification For Freight  before GR in  Scheduling agreement

    I have one doubt like can we post the Planned delivery cost against the Scheduling Agreement just like Import Purchases with checking off the GR Based IV Indicator before doing the GR
    I tried it but its giving me that no delivery costs are Planned in the Scheduling agreements it runs fine in case of the PO because PO is a time independent Agreement , Please
    Let me know how to achieve the same in case of the scheduling agreements.
    Appreciate if you can suggest something in this case Urgently .

    HI Deep
    I am facing exactly the similar issue. Experts please suggest.
    Deep! If you already have an answer? Please disclose the same.
    Regards
    Arvind

  • Expired Scheduling Agreement could not be changed

    Hi Experts:
    I am trying to mark the delivery completed box of an expired Scheduling Agreement because the quantity still appears in MD04.  However, I could not change it because it says " validity of contract expired 28.05.2008". How could I change an expired Scheduling Agreement.

    It seems earlier for the line item the conditions was not maintained ,Due to this you are able to maintain the price for condition PBXX.
    Now PB00 condition is automatically comming means ,there should be some info record or contract is maintained for the sku.So system is picking the price from any one of master data.Check in conditions from there you will come to know from where is system is picking the price.Change the price in master data then it will pick changed price.

  • Printout of schedule agreement before Release

    hi all,
    i have created release strategy for schedule agreement at three level EX, MM & GM, problem is that i want to print schedule agreement number thru ME9l after releasing it from EX level. can anyone please tell me that is it possible to print schedule agreement before releasing from all three EX, MM & GM?
    if yes then how? or plzz tell me if any other option to print the same.
    regards saurabh.
    Edited by: saurabh srivastava on May 5, 2009 12:20 PM

    If your strategy is set up so that all three levels must release the agreement before it is final released I do not believe you can generate a printout.
    Regards

  • Delivery before the schedule line date in scheduling agreement.

    Hi All,
    I have a situation where in I am using JIT delivery schedule for processing the delivery requirement from customer. In this, lets say, I have a schedule as 08/05/2009 for material A to deliver 1000 qty and the material is made available to me after production as of 07/05/2009 and I want to despatch the material on 7th only and not on 8th. The system does not allow me to do this.It allows me to make a delivery only on 08/05/2009.
    Is there any alternative to this and is this SAP standard behaviour.

    I think you can change the schedule line date in scheduling agreement itself and do the delivery.
    regards,
    Sudhir

  • How to restrict GR before Shcedule date in Scheduling Agreement

    Dear All,
    Please tell me the message or Message number which actually doesn't allow GR befiore schedule line date. I am not able to see such error in our system.
    Regards,
    Sandeep

    Hi
    This is the message that you will get while performing GR for a SA line beofre the schedule date.
    M7 036 - No goods receipt possible for purchase order & &
    Diagnosis
    No provision has been made for goods receipts in respect of this purchase order or order item  .
    Possible reasons for this are:
    The purchase order contains no items in the specified plant.
    The item specified does not exist.
    Currently, the scheduling agreement has no open schedule lines, or the schedule lines have not yet been transferred.
    The item category of the purchase order items in the plant does not allow goods receipts.
    The purchase order items in the plant have been deleted or are blocked.
    For confirmation control for the order item(s) to be carried out, a confirmation ( shipping notification) must have been received. This has not yet been entered.
    This message is a standard message and the sytem deterines this automatically for schedule lines.
    Thanks & Regards
    Kishore

  • How to measure performance of supplier when using scheduling agreement ?

    Hello all,
    My client has an absolute need to be able to measure the performance of its suppliers based on delivery dates and delivered quantities. That is to say he needs to be able to compare what dates and quantities were asked to what has been really delivered.
    Most of the procurement processes used are based on scheduling agreements : schedule lines are generated by MRP and forecast is sent to supplier while firm requirements are sent through JIT calls.
    It seems that when doing GR in MIGO, it is done against the outline agreement number, and not against the call. Therefore, we have no way to compare dates and quantity with what was expected (in the JIT call).
    Do you know if SAP proposes a standard solution to this, and what could be a solution to this issue ?
    Thanks for your help
    E. Vallez

    Hi,
    My client faced the same problem and we ended up developing an own analysis in LIS. Since the GR is not linked to specific schedule line (SAP does some kind of apportioning, but it doesn't have to correlate to the correct match), one needs to do assumptions. Our assumption was the closest schedule line, i.e. each GR is related to the schedule line with the closest date. Then all GR the same day are totaled together before the quantity reliability is calculated, since the very same shipment can be reported through several GR transactions in SAP (one per pallet).
    If anybody has info about what SAP has to offer in this question (or is developing), please tell us!
    BR
    Raf

  • Unable to change the item category in existing Scheduling Agreement

    HI,
    I have a schedule agreement where there are already list of line items but saved without the appropriate item category field in all of the line items. Now I see that the Item category column is greyed out & unable to edit or change thru ME32 T.code.
    I am already aware that deleting the item codes & adding again with resolve the issue. But when try to delete, those codes shows that they have GR & PO not completed one.
    My question is :
    Is there a way to edit/change the Item category field without deleting the item?
    Whethere is it possible to do it in bulk update for group of items in SA?
    If it is possible, pls provide how to do it with steps.
    Kindly advice.
    Thanks. in advance!
    -Umesh

    Please try using MASS tcode with object BUS2013
    or MEMASSSA
    Its a direct table update where you can select the Table Item and Field Item category and input the document number to change the value os item category and try with one sample data then do it in mass.
    Before cahngin the item categry Please make sure all the dependancies are met then nly the system will allow you to save.
    Refer for Mass upload function it is common for all
    [Mass update|http://www.sapkshare.com/user/image/mass-maintenance---mm17.pdf]
    Edited by: Karthik on Jul 29, 2011 2:44 PM

  • Scheduling agreement, unnecessary delivery schedule lines

    Hello
    We use Scheduling agreements for purchasing spare parts. The MRP run checks the warehouse requirements and creates delivery schedule line to scheduling agreement.
    Now the MRP run creates unnecessary delivery schedule lines to scheduling agreement if the earlier created delivery schedule line's delivery date has been changed manually.
    For example,
    Today the MRP run finds requirement for one article  and creates the delivery schedule line, where delivery date is 2.9.2008 (determined from articles basic data).
    The Vendor confirms the delivery date as 3.10.2008 and the purchaser changes manually  (transaction ME38) the delivery date to delivery schedule line accordingly and prints the created message.
    The next MRP run creates new delivery schedule line, where delivery date is again 2.9.2008.
    now there are two open delivery schedule lines for this article with delivery dates 3.10.2008 and 2.9.2008.
    Why the MRP run does not notice the existing delivery schedule line with the new delivery date 3.10.2008?
    we have changed delivery dates manually several years and this has never happened before.
    could you please help me to resolve this.
    Thanks in advance,
    Srikanth

    In addition to the above post,
    as you changed the date manually from 2nd to 3rd....
    so there are was no report for 2nd generated ulitmately...and if generated it was changed...right...
    so when you again run the mrp...the system will generate one more pr for the same article....
    this ultimately happens because of the set del dates in the MMR as i told above..
    Hope it helps..
    Regards
    Priyanka.P

  • Scheduling Agreement

    Hello Guru it is very very urgent plz give me answer what to do
    This problem occurs in program Y_EX34_LVED4FZZ_001.  The problem is that the current code assumes that VBEP-ZZSID will never be repeated by the customer, so all deliveries in the history can be checked when deciding whether or not to retain a schedule line.  New information has confirmed that Nissan repeats their ZZSID numbers annually, which leads the current code to delete open schedule lines that had deliveries against them in prior years.  Here are the recommended steps to correct this:
    1.     After obtaining the VBEP data and before selecting from ZZDLVRANSID, find out when the relevant schedule line’s delivery schedule was posted, using the following steps:
    a.     Find the record in VBEH for VBEP-VBELN, VBEP-POSNR, and VBEP-ETENR that has the smallest nonzero value in the internal delivery schedule number field (VBEH-ABRLI).  If none is found, take the record with ABRLI = ‘0000’.
    b.     Find the record in VBLB for VBELN and POSNR that matches ABRLI.
    c.     Take fields VBLB-ERDAT and VBLB-ABRDT_ORG.
    d.     If ABRDT_ORG is not 00/00/0000 or 12/31/9999, use it as the comparison date for this logic.  Otherwise, use ERDAT.
    2.     When selecting later from LIKP, also get the planned and actual Goods Issue dates (LIKP-WADAT and LIKP-WADAT_IST).  If WADAT_IST is not 00/00/0000, use it for the comparison date for this logic.  Otherwise, use WADAT.
    3.     Before incrementing XLTOT_PGI or XLTOT_DEL, ensure that the delivery you are working with was shipped after the schedule line that you’re working with was received (the VBLB date from step 1d is less than or equal to the shipment date from step 2).  If it is, proceed with the calculations.  If it isn’t, don’t add the quantities from this delivery into the totals.
    Testing Strategy
    ·     In CTA, we will need to coordinate with the EDI team to find out if any customers exist that use replace logic for which data can be pushed in and tested.
    ·     In FTA, scheduling agreement 300027861 is an excellent example of this issue.  We can get the EDI team to re-send data for that scheduling agreement (or for other scheduling agreements under the same customer), and process the IDOCs individually to test that:
    o     Deliveries that were shipped prior to the open demand’s delivery schedule creation date are excluded from the assessment of whether or not to delete the schedule line.
    Deliveries that were shipped after the delivery schedule came in are included in the assessement
    regards
    sapman

    Only ABAPER will give the good result, but no body is taking risk
    it is very urgent case
    sapman

  • Scheduling agreement Fcst del schedules and JIT question

    We have a requirement of not sending forecast delivery schedules TOR to MRP from SA.
    Instead, we take this forecast delivery schedules and massage the data (add or delete) and then send it to MRP as regular forecast (PIR).
    so when the JIT schedules come, does the forecast get consumed with the JIT's in MD04?
    lets say, I got 100 pc for 2nd week of July 2011 as forecast delivery schedule from customer and I loaded them into MRP as PIR
    and I got JIT for only 90 PC for the 2nd week of july 2011.in MD04 will the 90 get consumed from the PIR??

    925,
    so in system it will show on 3/21 monday
    I guess this means that you are entering using a Day format rather than Week format.
    You have answered you own question already.  If the online SAP help, which you have read and reasonably paraphrased, is not clear enough to make you understand this, I cannot help you.
    JIT horizon is 3/23, Forecast is for 3/21. 
    As I stated before, even though it may in your mind represent a week's demand, it is still for one day.  There is no bucketing, nor time-based disaggregation, nor consumption.  It is just a scheduling agreement.
    You wrote
    am using MRP indicator D. that means within jit horizon, consider my jit quanity for requirements. and after jit horizon consider my forecast delivery schedules as requirements.
    .  This is a reasonable paraphrase of the SAP online help.  Do you believe this?
    Forecast schedule is for 3/21.  NOT for W 12/2011.  This is before the JIT horizon, isn't it?  What do you think will happen to the forecast schedule, looking at the last 'rules' you just wrote? and as stated in the SAP help that you read?
    Now you want to enter JIT schedules. 21/22/23/24/25/26.  JIT horizon is 23.  24/25/26 are after JIT horizon.  What do you think will happen, based on the 'rules' you just wrote? 
    I feel my time is being wasted when you keep asking me these questions, already having the answers explicitly stated in SAP oinline help.  Since you do not have access to a system, this cannot be a support issue, it is a evidently a matter of idle curiosity for you.  I therefore believe I will will move onto other forum questions, where there is a possibility that the questioners will get some business benefit from my answers.
    Best Regards,
    DB49

  • Delivery from sales scheduling agreement with one item per schedule line

    Hi all,
    I have a sales scheduling agreement where the same part number has 3 different JIT schedule lines and I need to create a delivery with 3 item lines: every item line of the delivery has to be referred to one schedule line of the scheduling agreement.
    When I create the delivery with transaction VL10E it has only one item line and its quantity is the sum of the 3 schedule lines of the sales scheduling agreement.
    I've tried to change the customizing of the User Role, choosing the Split Schedule Line = 2 ("One item per schedule line") but the delivery is created again with only one item line.
    How can I solve this issue?
    Thanks in advance for reply

    Dear Alex
    The SAP standard behaviour is that all schedule items with delivery date in the past have to be rescheduled anyway to one date and are combined therefore.
    Partially this behaviour can be influenced in VL10* by 2 parameters in
    the user role : Split per sched.line and Rule (delivery qty).
    Please find below informations about these different parameters
    "Split per sched.line propose you 3 Rule for creating one delivery item
    per schedule line. In a delivery list in item view with multiple
    schedule lines, you can decide for the same document item whether you
    want to generate one delivery item per schedule line or whether you want
    to deliver the cumulated quantity of the last schedule lines selected.
    About rule for delivery quantity, the following rules are currently
    implemented:
    1. No cumulation
    The open schedule line quantity to be delivered is the quantity at which
    the list line is delivered.
    2. Sum of all open schedule line quantities to be delivered that fall
    before the chronologically latest date in the to field (following the
    Deliv. creation date field) of the selection criteria.
    3. Sum of all open schedule line quantities to be delivered whose
    delivery creation date falls within the selection time frame (between
    the dates in the Deliv. creation date and to fields, respectively),
    making the calculation of the quantity to be delivered consistent with
    selection criteria. However, calculationof the quantities delivered with
    the order's schedule line quantities is not affected."
    Hope this helps.
    Regards
    Tonia

Maybe you are looking for