Scheduling Agreement: validity variation date on schedule dates

Hello everybody
I have a problem and  I appreciate your advice .
There is an agreement “A” which validity date is from 01.01.2007 to 31.12.2007.
And an agreement "B" with validity date from 01.01.2008 to 31.12.2009
After the MRP has been run, It creates the Delivery Schedule based on agreement "A" . But in a specific item, it was created two delivery date which are out of the validity date; those were 07.01.2008, and 12.01.2008
The question is why did the system create deliveries schedule out of the validity date base on agreement “A” and not based on agreement “B”? I mean,
Why did the system create this Scheduling delivery date out of the range of validity of the Agreement?
And, In the case that it had taken the validity date from Agreement "B" why did it put it on agreement "A"?
Could you give me any tip or suggestion where I need to verify or check in order to find out the reason why this happened?
I already verify the agreements, the source list and they seem to be ok.
Thanks in advance

Hi Adrianda,
The creation of schedule lines through MRP depends upon the Agreement( no "A" or "B" in your case) and the validity period,and the period for which the MRP is run the system will create the SL according to the period for which the MRP has run,as per my knowledge there are no other place you can check,so double check the source list.

Similar Messages

  • Validity end date tab is suppressed in scheduling agreement

    Hi ,
    In scheduling agreement , Validity end date tab is suppressed ,
    There is no layout is assigned to the doc type & standart transaction varient is acitve , but while doing ME31L above field is not coming ( it is in suppressed / hide mode )
    Please let me how to get that validity date tab in scheduling agreement.
    Thanks,
    Pradeep

    Hi,
    Go to SPRO > IMG > MM > Purchasing > Purchase Order > Define Screen Layout > NBF > Administrative data, header > make the fiels Validity Period field optional / Required.
    Hope this will help you.
    Regards,
    Manish Jain

  • 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

  • Scheduling agreement validity

    Dear SAP Gurus,
    I have a requirement where delivery should happen only within the validity period.
    I am trying to map the same through Scheduling agreement, where i can enter the From and To date.
    When i am entering the schedule line manually which falls after the validity end date, system is throwing the warning message V1448.
    I tried to make this message as ERROR in OBMSG/OBA5.
    Still the message is WARNING.
    Please advise on how this message can be made ERROR.
    Is there any other way to map this process other than by using scheduling agreement ( delivery should happen within the validity period only) ?
    Thanks & Regards,
    Hegal

    message V1448.
    The above message is being popped up from Include / Program MV45AF0D_DATUM_PRUEFEN_GUELTIG and I dont think, it can seen in the two TCodes indicated by you.
    Changing from Warning to Error is definitely not recommended.  You can however, definitely control this through your existing routine or with user exit.
    thanks
    G. Lakshmipathi

  • Changes to Rebate Agreement Validity Date Field

    Hi,
    We are trying to prevent people from changing the "Validity To" date field (KONA-DATBI) on Rebate Agreement masters (VBO3). They are back dating the field which is causing probelms for running billings.
    Is they any way this can be done via a validation on that field or a message that pops up when the field is changed to something earlier than current date?
    Thanks

    Hi,
    This fields is opened for a good reason, sometimes the end-date of an agreement should be reduced when you want to split a period and therefore create a new agreement for the remaining period.
    In my opinion this is a procedure problem, your users must know what they do.
    If someone still keeps on introducing incorrect data in the system, this person should receive additional training and / or be warned.
    To answer your specific question:
    There is no user-exit for the rebate agreement master data. Quite a shame.
    Best Regards,
    Franck

  • CIF of SA is not consistent for Validity End Date

    Hello gurus,
    Our company is quite new in using SNC, and we bumped into this problem (see description below), and hopefully this forum can help us.
    <Description>:
    When the Scheduling Agreement is CIFed from R/3 (ECC) to SNC, the Validity End Date does not get updated each time.
    It gets updated sometimes, but not always. It is inconsistent behaviour.
    <Example>:
    Scheduling Agreement A
    Validity End Date: 31.12.2012 Changed to 30.11.2012 in R/3.
    Performed CIF using Transaction Codes CFM1 and CFM2.
    Correctly updated the Validity End Date in SNC.
    For the same Scheduling Agreement A updated Validity End Date to 31.01.2013 in R/3.
    Performed CIF using Transaction Codes CFM1 and CFM2.
    The Validity End Date was not updated in SNC & remained as 30.11.2012.
    For the same Scheduling Agreement A updated Validity End Date to 15.10.2012 in R/3.
    Performed CIF using Transaction Codes CFM1 and CFM2.
    The Validity End Date was not updated in SNC & remained as 30.11.2012.
    Thanks guys
    Tuffy

    Hi Tuffy,
    1 - I am just wondering if after the Delete the existing External Procurement Relationship in SNC, and CFM1 and CFM2 the SA (i.e. changed my validity end date value) to the SNC, will the problem of the SNC side not able receive the changed SA??
    When there is a change in the SA, integration model would create the same in SNC if it does not exist. But the transfer from ERP does not happen just like that. First, make sure that the message type (CIFSRC) has been checked in BD50 and then schedule a job to periodically transfer the SAs.
    2 - What does the tcode the person in the SNC side have to double check to ensure the SA is transmitted there??
    The t-code is /SAPAPO/MTI2 - External Procurement Relationship.
    3 - Someone in our company advise BASIS team to check the transactions BD50 and BD52. What exactly does it mean and does it help?
    This is correct. I mean guys who are responsible for Integration model need to set-up BD50, BD52 so that changes to SAs are transferred periodically.
    Regards,
    Sandeep

  • Not valid Explosion Date for Production Version

    Hi Experts,
    I am creating a production order for a new item and I am getting the following error.
    version: xx
    is not valid on explosion date
    no other versions are available
    should the document link be transfered anyway?
    What is the right approach to correct this?
    if I choose yes, the production order does great created,
    but is it going to be a valid order?
    let me know
    Cheers
    JD Loera

    Hi,
    I believe it should be a warning message, else system would not allow you to proceed, so do a re-check on that.
    Coming to resolving the issue, this would occur when the valid-from date of the production version is later than the date on which bom & routing is exploded in the order. So before proceeding to make any changes, analyze the valid from dates of the BOM & Routing, now create the production version valid from that date.
    This would at the very minimum ensure that the production version will be valid. If you still get a warning message, it implies that validty dates of the BOM & Routing needs a re-visit as well.
    So go to MM02, MRP-4 / work scheduling view & modify the valid from dates of the production version. Once the same is done create a new order & system should read the production version.
    Regards,
    Vivek

  • Validity start and Validity End date in PO

    HI  gurus
       can you plz tell me how to activate  validity start and Validity End date in PO
    Neha

    Hi,
    It is applicable for PO done for Frame work oder with Doc type - FO(Frame work order)as its an agreement of supply of stock only between specified period.For this kind of Doc type system makes it mandatory to enter the valisity start and end date.
    Thanks

  • "Validity of data" in WAD

    I made a web report in the WAD containing a query in a table item.
    What I would like to display is "Validity of data" (as date/time) which I see when I display the query on the web from BEx with the default view.
    How do I display that?

    Thank you very much!
    I had already tried that one before but it must have flashed in front of my eyes cause I didn't see it.
    Problem solved...

  • Help reqd on Changing the Valid from "date"  for both BOM & Routing

    Hi all...
    Pls advise me how to do the changing of Valid from "date"....
    Is there any process in CC01 or ECM???....
    pls reply me in detail step format (step by step analysis)....
    I wrongly created in CS01 and CA01 as 05.10.2007 as my valid from date instead of 01.10.2007.....
    How to change to my actual one......
    I dont know how to change it exactly.....as im beginner in SAP...pls take this into consideration...and post ur replies imm.
    Pls reply me in detail....will be rewarded at the end while closing this issue.
    thanks & regards
    sankar

    Dear Sankarbabu,
    IF there's no setting for Date Check in OS54 - Engineering Change Management
    Control Data,then you can create a change number with past dates,and also to
    use the same one for changing BOM.
    Tell me one thing you are saying you want to use ECM.Was the earlier one
    created without BOM was created without an ECN?
    See already if you have created your BOM with an ECN,then remove the date
    check setting which I have mentioned in OS54.
    Now goto T code CC02 ,enter the Change number and give the valid from date as
    01.10.2007.
    After that check in CS03 whether this date(01.10.2007)is getting reflected or not.
    I'm sure this will solve your problem.
    Regards
    Mangal

  • Error: No valid complaint data was found in this sales area

    Hi All,
    I am getting below error while delta or request download of customer.
    No valid complaint data was found in this sales area
    Message no. CRM_SPL_BUPA_FRG0010203
    Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
    Message no. SMW3018
    Error case:
    ECC-->Customer(Sold to) extended to a sales area and saved.
         CRM-->Business partner gets updated in the CRM properly.
    ECC--> Deletion flag for same customer and same sales area is set. (Deletion flag - "Selected sales area").
         CRM-->Business partner gets updated in the CRM properly and is not shown as extended to the sales area via BP t code.
    ECC-->Deletion flag is removed for the customer.
         CRM--> BDOC fails to update the Partner and goes in error.
    Problem comes when deletion flag is removed in ECC.
    Any help would be highly appreciated.
    Thanks in advance.
    -Ram

    Hi Ram,
    Hope you have not make any field mandatory in the Complaint tab in the sales area section in the BP.
    When you are removing the deletion flag please check if any entry is mandatory in the Complaint tab.
    Hope this will be useful
    Thanks and Regards
    DJ

  • Table to find BOM valid-till-date

    Hi Friends,
      I have to check the vality of BOM components,  through transaction CS03 i could able to see the Valid-till-date and i need to check the same in my code.
    Looked into following tables, thre is a field valid-from-date(DATUV) but i'm not getting field Valied-to-date(DATUB).
    MAST Material to BOM Link
    EQST Equipment to BOM Link
    STAS BOMs header
    STKO BOM header
    STPN BOM follow-Up control
    STPO BOM item
    STPU BOM sub-item
    STST Standard BOM link
    STVB Bills of material - Serialisation of posting
    STZU Permanent BOM data
    Can any one please help me.
    Thanks in advance.
    /Kiran

    Hi kiran,
    I think the Valid-to-date is in table AEEF-DATE_HI which can be linked with the BOM Header table STKO by field AENNR. Try this.
    Otherwise you can also get the Date using the FM CS_BOM_EXPLOSION....
    Use it as follows;
    CALL FUNCTION 'CS_BOM_EXPLOSION'
    EXPORTING
    AUMNG = 0
    CAPID = ' '
    DATUV = DATVAL "valid-from date
    EHNDL = '1'
    MKTLS = 'X'
    MEHRS = 'X'
    MMORY = '1'
    MTNRV = MATNR
    STLAL = LAL "like mast-stlal default '1'
    STLAN = LAN "like mast-stlan default '2'
    SVWVO = 'X'
    VRSVO = 'X'
    WERKS = WERKS
    mmaps = 'X'
    IMPORTING
    TOPMAT = STARTMAT "includes structure CSTMAT
    TABLES
    STBD = TBD "includes structure CSXDOC
    STBE = TBE "includes structure CSXEQUI
    STBK = TBK "includes structure CSXKLA
    STBM = TBM "includes structure CSXMAT
    STBP = TBP "includes structure CSXGEN
    STBT = TBT "includes structure CSXTDL
    EXCEPTIONS
    ALT_NOT_FOUND = 1
    CALL_INVALID = 2
    MISSING_AUTHORIZATION = 3
    NO_BOM_FOUND = 4
    NO_PLANT_DATA = 5
    NO_SUITABLE_BOM_FOUND = 6
    OBJECT_NOT_FOUND = 7
    CONVERSION_ERROR = 8
    OTHERS = 9.
    After the function call you will get the Valid to Date(DATEUB) from table STBP.
    Hope this Helps you...
    Regards
    Karthik D

  • Table for Valid to date in BOM item

    Hi Exeprts,
    Can any one help me on this in which db table Valid to date:DATUB is Updates with reference to Change Number.
    Best Regards,
    Venkata Siva.
    Edited by: venkata siva reddy on Apr 27, 2011 9:28 PM

    Hi
    The Valid-to date will always be set to 31.12.9999. Instead you can get the valid-to date using the below logic.
    -> Get all the BOM from T415A table for the material number into T_T415A
    -->LOOP AT t_t415a.
        ON CHANGE OF t_t415a-matnr OR t_t415a-werks OR t_t415a-stlal.
          IF sy-tabix NE 1.
            MOVE : v_matnr TO t_dates-matnr,
                   v_werks TO t_dates-werks,
                   v_stlan TO t_dates-stlan,
                   v_datuv TO t_dates-datuv,
                   v_stlal  TO t_dates-stlal.
            IF v_matnr NE t_t415a-matnr.
              t_dates-datub = c_99991231.
            ELSE.
              t_dates-datub = t_t415a-datuv - 1.
            ENDIF.
            APPEND t_dates.
            CLEAR :
            v_matnr,
            v_werks,
            v_stlan,
            v_datuv,
            v_stlal.
          ENDIF.
        ENDON.
        v_matnr = t_t415a-matnr.
        v_werks = t_t415a-werks.
        v_stlan = t_t415a-stlan.
        v_datuv = t_t415a-datuv.
        v_stlal = t_t415a-stlal.
      ENDLOOP.
    Regards
    Dhurga

  • Table for Valid To date field in C203 Tcode

    Let me know the table name for "Valid To Date" field in C203 transaction.
    Thanks,
    Angavai.E

    Hi Angavai,
    Check with table PLMW.
    Regards,
    Raghu

  • Source List Validity Start Date

    I have noticed that, if the source list validity start date and contract validity start date are same then, the contract price is not considered while creating PO and receive error message as "Source not included in list despite source list requirement"
    If I change the validity start date of source list to one day before the validity start date of Contract then system is picking the contract price in PO and able to save PO successfully.
    Is there any way to create PO even if the validity start date of source list and contract are same?

    from OSS Note 44368 - ME51 ME57 Contract as source of supply
    A contract that is valid on the delivery date but not on the current date is not taken into account in the source determination process.
    Cause and prerequisites
    This is programmed this way.
    Solution
    For reasons of upward compatibility, check will continue to be carried out on basis of current date.
    However, if you wish the check to be against delivery date, you can implement the modification described under the advance corrections.
    If Note 116464 is implemented in a 4.0B Release, use the advance correction from Release 4.5A, however, in Release 4.0B the program name is LMEQRF01.

Maybe you are looking for