Requirement Date in Scheduling agreement

Hi
There are 6 line items in scheduling agreement created in ME31L for subcontracting process .
Hi
For first 4 line items , delivery schedule mentioned is 02/08/2008 .
For last 2 line items , delivery schedule mentioned is 05/07/2008.
I think this could be the reason always delivery split has been happening when creating th e delivery .( 1 delivery for first 4 line items and another delivery for last 2 line items )?
Is it right ?
Can I request you to clarify below points .
1.Can I tell user to change delivery schedule for last two line items as 02/08/2008 ? in which transaction user can change this delivery schedule ?
In ME32L , When I try to change , I found it grayed out , can I know why it is so ?
2. For many days , this scheduling agreement is existed , delivery has been happening for this scheduling agreement .If we change this delivery schedule now , what could be the ramification .
Thanks In Advance

Hi
Reply for your 1st point:
Maintain the delivery schedule at ME38.
Regards
Prasanna

Similar Messages

  • Restriction of Validity start date in Scheduling agreement

    Hi,
    I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting  back  validity start date in the header of Scheduling agreement (me32l)
    What can be the possible reason.
    Regards
    Sachin

    Hi,
    I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
    Laufzeitbeginn in der Vergangenheit -
        IF ekko-kdatb < sy-datlo.
          MESSAGE w170 INTO gl_dummy.
          mmpur_message 'W' '06' '170' '' '' '' ''.
    Please consul your ABAP Team on this to change it to Error.
    But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
    Regards
    Chandra Shekhar

  • 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

  • Calculation of goods issue date in scheduling agreements with routes

    Hello together,
    i have a problem with the calculation of goods issue date in scheduling agreements when we use route, because the system ignore the days of transit.
    Example:
    We had customized the route 4711 with a transit time of 3 days. This route would be related to a scheduling agreement. But this setting has no influence to the calculation of the goods issue date for the schedules. The same happens with loading date and so on.
    Can anyone give me a tip, which setting is additional necessary?
    Regards
    Andreas Walter

    Hi,
    check the following settings
    1, Route determination Path : IMG>sales and distribution>Basic function>Routes>Route determination
    2, Activate the route Determination for your sales document type in following path :IMG>sales and distribution>Basic function>Routes>Route Schedule Determination-->Schedule with route schedule for sales document type
    3, Maintain Delivery scheduling and transportation scheduling in the following path:IMG>sales and distribution>Basic function>Delivery scheduling and transportation scheduling>Maintain Duration
    Regards
    Senya

  • Information on Requirements type in scheduling agreement

    Does anyone can give me infomation about 'requirements type' found in the procurement tab of the scheduling agreement?

    Hi,
    The requirement type determination in orders/ SA as follows:   requirements types are determined according to a specific search strategy beginning with the material strategy group. Strategy for Determining the Requirements Type
    1. First, an attempt is made to find a requirements type using the strategy group in the material master.(note: Define a requirement type and a class for each strategy which you will  define in the production module)
    2. If the strategy group has not been maintained, the system will determine it using the MRP group.
    3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
    4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
    5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
    6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements
    Hope this will help you to understand better
    Regards,
    Krishna O

  • Delivery date in scheduling agreement

    If delivery date in scheduling aggrement is 20th  and vendor has supplied the material on 15 th iteslf then are we able to do grn on 15th or Not.
    Or we should wait for the date 20th.
    Thanks,
    Kiran

    Hi,
    If you have maintained Delivery Schedule for Scheduling Agreement as 20.05.2011 and Vendor has supplied materials on 15.05.2011 then you can not do GR on 15.05.2011 since Delivery schedule of Scheduling Agreement are firm and have control over dates.
    You need to revise the delivery schedule in ME38 to 15.05.2011 and then do GR.

  • Next JIT schedule date in  Schedule Agreement

    H, This is reg JIT - in Schedule Agreements
    JIT schedules are created to day 10.02.2010 ..
    In Creation profile for JIT, 'Changed or next date' is given & 'Weekly trans' option is chosen
    I could see system calculated 'Next JIT sched' date as 15.02.2010 [Next week monday] , it is as expected
    I created JIT today and i am not able to release today itself as part of testing solution. Even in production environment cant i release on same day of JIT schedules creation? why so ?
    Help Says  only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation."

    I found the issue ...
    output message for JIT was an issue
    when i see JIT out message type properties for this message, Print parameters field was set to blanck
    When i chenged to Purchase Group, it worked ..
    Can some one help me what effect it had in generating message, before that message was green but i was not able to genertae JIT schedules

  • Wrong delivery date in Schedulling Agreement

    Dear All,
    We maintained scheduling agreements for our Customer's Materials.
    For all tomorrow's deliveries i.e of 05.07.2008 all scheduling agreements are showing today's date i.e 04.07.2008 in VL10e as delivery.
    Delivery Date : 05.07.2008
    Goods Issue Date : 04.07.2008
    Loading Date : 04.07.2008
    Material Availability Date : 04.07.2008
    Trans. Planning Date : 04.07.2008
    Interesting point is that no delivery is showing pending for 05.07.2008 in Vl10e. All the deliveries of 05.07.2008 are appearing in today's date.
    I checked factory & Sales calender of company. Saturday is working day
    Regards,
    Sagar Pande.
    Points will definitely awarded.

    Hi,
    If you have maintained Delivery Schedule for Scheduling Agreement as 20.05.2011 and Vendor has supplied materials on 15.05.2011 then you can not do GR on 15.05.2011 since Delivery schedule of Scheduling Agreement are firm and have control over dates.
    You need to revise the delivery schedule in ME38 to 15.05.2011 and then do GR.

  • GR qty is updated in future delivery date in Scheduling agreement

    Dear All,
    In one of our Scheduling agreement  delivery schedule, the Goods receipt qty got updated in  future delivery date (ie., 30.07.2011 & 19.10.2011). Any idea how this got updated wrongly? or is there any standard functionality that controls this GR qty field.
    Thanks in advance
    Benny

    HI,
    Both  Planned delivery time and GR processing time are having 1 day , please let me know any other factor influencing this data.
    Thanks
    Benny

  • 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

  • Goods receipt to be done earlier to scheduled date for scheduling agreement

    Dear Experts,
    We have a scenario where in the goods is received earlier than the scheduled date mentioned in the scheduling agreement, but system does not allow to do the GR. Everytime Stores people have to contact the purchase guys to change the scheduled date.
    Please let me know how to overcome this.
    Regards,
    Praveen

    sapPraveen wrote:
    Dear Experts,
    >
    > We have a scenario where in the goods is received earlier than the scheduled date mentioned in the scheduling agreement, but system does not allow to do the GR. Everytime Stores people have to contact the purchase guys to change the scheduled date.
    > Please let me know how to overcome this.
    >
    > Regards,
    > Praveen
    Hello Praveen,
    Set Message Number 254 (Work Area M7) to warning in customizing for Inventory Management and Physical Inventory under Define attributes of the system message.
    This should solve your problem!!
    Thanks,
    Reetesh

  • Dump after implementing the Note 741385 Goods receipts up to current date for scheduling agreements

    Hi,
    I implemented the sap note 741385, but while performing GR getting dump
    I unable to figure out why the EXIT_SAPLEINR_003 has been called, please find the following run time error .
    Runtime Errors    
    CALL_FUNCTION_PARM_UNKNOWN
    Except.           
    CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Date and Time     
    10.04.2014 11:39:15
    Short text
    Function parameter "ISU_ENHANCEMENT" is unknown.
    What happened?
    Function module "EXIT_SAPLEINR_003" was called
    with the parameter "ISU_ENHANCEMENT".
    This parameter is not defined.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
    not caught in
    procedure "WE_BEWERTEN" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Function module "EXIT_SAPLEINR_003" was called
    with the parameter "ISU_ENHANCEMENT".
    This parameter is not defined.
    Missing RAISING Clause in Interface
    Program                            
    SAPLEINR
    Include                            
    LEINRF25
    Row                                
    8
    Module type                        
    (FORM)
    Module Name                        
    WE_BEWERTEN
    Trigger Location of Exception
    Program                            
    SAPLEINR
    Include                            
    LEINRF25
    Row                                
    151
    Module type                        
    (FORM)
    Module Name                        
    WE_BEWERTEN
    Source Code Extract
      122  
    IMPORTING
      123    
    e_vkwrt          
    = pot-vkwrt
      124    
    e_vkwra          
    = pot-vkwra
      125  
    TABLES
      126    
    i_tkomv          
    = tkomv
      127  
    EXCEPTIONS
      128    
    OTHERS           
    = 01.
      129
    IF sy-subrc EQ 0.
      130  
    MODIFY pot.
      131
    ENDIF.
      132
    EXIT.
      133   ENDIF.
      134
      135   MOVE-CORRESPONDING pot TO ekpo.
      136
      137   DATA: p_menge LIKE ekpo-menge,                       
    "1.2 KR
      138    
    p_datum LIKE sy-datum.                         
    "1.2 KR
      139                                                        
    "1.2 KR
      140 * pot-erfmg wird in pot_aufbauen schon entsprechend vorbelegt
      141   p_datum = budat.                                     
    "1.2 KR
      142   p_menge = pot-erfmg.                                 
    "1.2 KR
      143
      144 *- Userexit um Preisfindungsdatum und -menge zu ändern ----------------*
      145 * --> kann auch bei Bestellungen genutzt werden, um das Datum zu ändern
      146 *  nicht aber die Menge (macht keinen Sinn und ist nicht programmiert)
      147   MOVE ett[] TO cett[].
      148
      149 ENHANCEMENT-POINT WE_BEWERTEN_05 SPOTS ES_SAPLEINR.
      150
    >>>>   CALL CUSTOMER-FUNCTION '003'
    152 
    EXPORTING i_ekko  = ekko
    153           
    i_ekpo  = ekpo
    154           
    i_budat = budat
    155           
    i_bldat = i_bldat
    156           
    isu_enhancement = ls_enhancement        
    "IS2ERP
    157 
    TABLES
    xeket   = cett
    158 
    CHANGING  c_datum = p_datum
    159           
    c_menge = p_menge.
    160   REFRESH cett.                                        
    "99794
    161   IF ekko-bstyp EQ bstyp-best.
    162
    p_menge = pot-erfmg.
    "damit wird die Bestellmenge verwendet
    163   ELSE.
    164
    pot-erfmg = p_menge.
    165   ENDIF.
    166
    167 *  MOVE-CORRESPONDING pot TO potkey.
    "Preisfindungsmenge merken
    168 *  READ TABLE ekp WITH KEY potkey.     
    "MWE-HPR-HW-205016
    169   READ TABLE ekp WITH KEY ebeln = pot-ebeln
    170                      
    ebelp = pot-ebelp

    Hi,
    please implement SAP note 916474 - A dump occurs when you call user exit EXIT_SAPLEINR_003
    SAP enhancement MEVME001 contains both
    EXIT_SAPLEINR_001
    EXIT_SAPLEINR_003
    Regards,
    Klaus

  • Delivery date of schedule agreement

    Dear All,
    Can u tell me how to set tolerance in delivery date and pls tell me how system calculate delivery date from MRP.
    Abhinay

    Hi,
    I don't think you can set Tolerance in Delivery dates.
    how system calculate delivery date from MRP --> System calculates delivery date considering Planned Delivery time mentained in material master.
    Regards,
    Vikas

  • Tables for following scheduling agreements and PR data

    Hi All ,
    Please can you tell me table names if I want the following information
    1. Scheduling Agreement Created By, Amended By, Modified Date, Plant
    2. Req Created by, Released by, Cost center, plant
    Thanks in advance
    Vinayak

    To view the fields listed in a table go to Tcode SE11 and enter the table name and execute
    EBAN  - Purchase Requisition 
    EBKN  - Purchase Requisition Account Assignment 
    Req Created by Table:EBAN Field ERNAM
    Released by- Table:EBAN Field FRGGR
    Cost center- Table:EBAN Field FISTL (Funds Center)
    plant-Table:EBAN Field WERKS
    For Scheduling Agreements following are the tables:
    EKEH    - Scheduling Agreement Release Documentation 
    EKEK    - Header Data for Scheduling Agreement Releases 
    EKET     - Scheduling Agreement Schedule Lines 
    EKETH   - Scheduling Agreement Schedules: History Tables
    You will find the following list of fields in these tables:
    MANDT                          Client
    EBELN                          Purchasing Document Number
    EBELP                          Item Number of Purchasing Document
    ETENR                          Delivery Schedule Line Counter
    EINDT                          Item Delivery Date
    SLFDT                          Statistics-Relevant Delivery Date
    LPEIN                          Category of Delivery Date
    MENGE                          Scheduled Quantity
    AMENG                          Previous Quantity (Delivery Schedule Lines
    WEMNG                          Quantity of Goods Received
    WAMNG                          Issued Quantity
    UZEIT                          Delivery Date Time-Spot
    BANFN                          Purchase Requisition Number
    BNFPO                          Item Number of Purchase Requisition
    ESTKZ                          Creation Indicator (Purchase Requisition/S
    QUNUM                          Number of Quota Arrangement
    QUPOS                          Quota Arrangement Item
    MAHNZ                          No. of Reminders/Expediters for Schedule L
    BEDAT                          Order date of schedule line
    RSNUM                          Number of Reservation/Dependent Requiremen
    SERNR                          BOM explosion number
    FIXKZ                          Schedule Line is "Fixed"
    GLMNG                          Quantity Delivered (Stock Transfer)
    DABMG                          Quantity Reduced (MRP)
    CHARG                          Batch Number
    LICHA                          Vendor Batch Number
    CHKOM                          Components
    VERID                          Production Version
    ABART                          Scheduling agreement release type
    MNG02                          Committed Quantity
    DAT01                          Committed Date
    ALTDT                          Previous delivery date
    AULWE                          Route Schedule
    MBDAT                          Material Staging/Availability Date
    MBUHR                          Material Staging Time (Local, Relating
    LDDAT                          Loading Date
    LDUHR                          Loading Time (Local Time Relating to a
    TDDAT                          Transportation Planning Date
    TDUHR                          Transp. Planning Time (Local, Relating
    WADAT                          Goods Issue Date
    WAUHR                          Time of Goods Issue (Local, Relating to
    ELDAT                          Goods Receipt End Date
    ELUHR                          Goods Receipt End Time (Local, Relating
    ANZSN                          Number of serial numbers
    NODISP                         Ind: Reserv. not applicable to MRP;Purc
    hope this helps!

  • SCHEDULING AGREEMENT AND SCHEDULING LINE CREATION

    Hello Guys,
    I trying creating a scheduling agreement(SA) for vendor & material combination.
    I have created a Scheduling agreement in ME31L then maintained in ME38.
    In ME38 i have also mentioned the delivery date. when i am checking EKKO for Purchasing document , its created with the delivery date specified.
    My question is how to create a schedule line ? Do we need to maintain a source list of that material, plant and vendor.
    If we have the source list maintained, then what is the next step after SA is created and maintained.
    Do we need to do MIGO? because i tested by creating one SA in ME31L and maintained in ME38. I mentioned the delivery date as today and when i checked EKKO table the Purchasing document is created.
    Do i need to create a Purchase Order?
    If no then do i need to do MIGO? If i need to do MIGO, for what reference do i need to do MIGO???
    My client never maintained a Scheduling agreement, they want the scheduled lines to be created and sent to vendor and we need to receive  the goods on specified delivery date.
    Help will be appreciated.
    Thanks.

    Hi,
    You need to make a distinction between the scheduling agreement (ME31L/ME32L) and the delivery schedule creation (ME38/ME84)
    With ME31L you create the scheduling agreement. In the scheduling agreement which is created for a vendor you maintain the parts that you will order at this vendor, the target quantity that you will order over a certain period and the price.
    In ME38 you use the scheduling agreement number that is created with ME31L to create schedule lines (manually). These schedule lines consist of a date and an quantity. This is the data that needs to be transmitted to the vendor and against which the vendor is shipping the ordered materials.
    Once the vendor ships the materials you post the goods receipt in Migo against the scheduling agreement number.
    That is the basic working of the scheduling agreement and the delivery schedule.
    Now some remarks.
    You need to set-up the required output conditions for transmitting the data to the vendor either via print, fax, email or EDI.
    You can do this manually in each scheduling agreement and each release but typically you maintain the output condition records.
    For scheduling agreement contract (ME31L) you use transaction MN07.
    For the delivery schedule (ME38/ME84) you use transaction MN10.
    In order for you to be able to post the goods receipt the delivery schedule needs to have been transmitted otherwise you will get a message that not requirement are found when trying to post goods receipt.
    Also the goods receipt can only be posted if the requirements are valid on the day that you are performing MIGO. This means if you would post GR today then the open requirements in the scheduling agreement need to be for today or already from previous dates. The system will not allow you to post GR for quantities that are only due tomorrow (if this is required a user exit needs to be set-up).
    If you want schedule lines created via MRP then you need to set-up a source list using ME01. You have to make sure that the MRP key is set to 2 in orer for the system to generate schedule lines and you also have to make sure that you have the correct MRP parameters set-up.
    You can use ME84 to transmit the delivery schedule lines generated by MRP if no changes are required. With the ME84 you can transmit multiple releases at once, however this transaction can not be used to make manual changes to the MRP proposal.
    The scheduling agreement offers lot's more possibilities but the above should get you going with the basics.
    Hope this will help you on your way.

Maybe you are looking for