Contract validity periods triggering

Hi Gurus,
I came to know that the contract validity periods price will trigger based on PO document creation date...
In our case
Market price is changed every quarter, and there is no way we have to wait until the new validity period to come to create PO.
For example:
Validity period 1 : July-Sep (Q3/2009)
Validity period 2 : Oct-Dec (Q4/2009)
If we want delivery in Oct, while lead time is two months (for this tinplate), we have to create PO in August. The question is now, how can I make PO taking the correct price / Q4 Price ?
Please advice how to do it ?

Hi
Please set the price date category in VMR, Contract & Purchasing inforecord to achieve your requirement.
This will be taken for valuation purpose during the Goods receipt posting.
There are few options available
     No Control
1     Purchase Order Date
2     Delivery Date
3     Current Date
4     Manual
5     GR Date
Hope it helps
Thanks / karthik

Similar Messages

  • Contract validity period

    Hi,
    We have some querries regarding Contract;
    E.g:
    1) The validity period of Service contract is 17.07.2008 to 17.07.2008
    2) Service PO created on 17.07.2008
    3) For creating the  Service entry sheet on 18.07.2008, whether system will have any control of the contract validity period as the Help on the Validity period explains regarding the srvice entry sheet, however system is not giving any message while creating service entry sheet on 18.07.2008;
    Please find the help available on contract validity;
    *"Start of validity period*
    *Date as of which services can be performed or materials delivered.*
    *Use*
    *In the case of outline agreements:*
    *Start of the stipulated validity period of an outline agreement.*
    *In the case of RFQs:*
    *Start of the period in which the quotation is to be submitted.*
    *In the case of purchase orders:*
    *Start of the period in which the service is to be performed or the material delivered.*
    **Note**
    ***Service entry sheets can only be created within the specified period."***In this help, all points are cleared except the last one regarding service entry sheet. Could you please explain the impact of last sentence in the help for service entry sheet.
    Thanks in advance;
    Regards
    Shp
    Edited by: Shp shp on Jul 18, 2008 7:15 AM
    Edited by: Shp shp on Jul 18, 2008 7:16 AM

    Hi
    Thanks for quick reply, we have tried with both the delivery date 17.07.2008 & 18.07.2008, in both case system has accepted the service entry sheet.
    Please suggest.
    Thanks
    Shp

  • Goods Receipt (MIGO) outside PO and/or Contract Validity Period ?

    Hi Gurus,
    Within our PO process, I created a PO which references a contract. Both have a Validy Period Start and End set up in customizing and filled in. But my problem is that I can still enter a Goods Receipt in MIGO to that PO, after validity has ended. I've set up in customizing the system message 06-041 as Error, and I've put in Screen Layout the checkbox 'GR message' for both PO and Contract.
    Is there a way to block the GR threw IMG outside of the Validity Period ?
    Thx in advance,
    N.H.

    Hi,
    The validity period for any outline agreement, can stop you from creating release orders or schedule lines , if OA is expired.
    Ex: Its very much logical, on the very last day of validity end date, u will create release orders.
    In this case you will receive your goods, only after the Validity end period.
    So there is no such control, for stopping the GR to be made.
    One can only stop Release orders from getting created,outside the validity period, not the GRs.
    Check for  Any user exit, that may help
    Regards
    Krishna U

  • Contract Validity period expired throw error message?

    Hi All,
    We created the contract and its validity date expired but the system allows to create the sales order with warning message that that validity of contract expired.
    We need here error message so that the system should not allow to create the sales order with reference to that contract.
    Regards,

    You can try this.
    Go to OVA2, select "A-Sales Header" and double click on Procedures.  Again select "10-Inquiry/Quotation" and double click on Fields.  Now tick the box "Warning" for VBAK / BNDDT
    thanks
    G. Lakshmipathi
    ps:-  It has been observed that out of total 15 questions you posted, you have not responded properly for 9 threads which are still open.  Please develop the habit of updating the forum periodically as and when you post any questions.  It is the other way to show that you respect forum members time.

  • Service contract with multiple validity period

    Hi,
    I am having a requirement where i need to create service contracts with multiple validities.
    some contracts may have 1 year validity, some six months.
    I already have a transaction type for contract which is having 1 year validity period assigned in its date profile.
    can i use the same transaction to create contracts for 6 months???
    Regards,
    PePe

    Hi,
      Yes you can use the same transaction type for the other validity period. What you can do is when you create a service contract, it will automatically pick up the 1 year duration since you have defined that way. But you can write some enhancement in ORDER_SAVE Badi.
    First you create a Z table and maintain the different durations (say based on your item) in a Z table.
    For example,
    item    duration(months)
    100       6
    200       12
    300       18
    400       24
    So at the time of saving the contract, your Badi implementation will be triggered and there you can pick up relevant duration (say 6 months) based on the item entered in your contract. And once you get the duration, you can change the Contract End date accordingly and then it will be saved. This way you can get the Contract duration as per your requirement.
    Hope it HELPS...
    Regards,
    Shailesh Jadhav

  • Valid Period in contract (me31k, me32k)

    Hi!
    In a contract with a lot of lines of materials and services, Its possible to change in a masive way the validity period of the price conditions?
    Now I have to enter to each  line condition of the contract and create a new period.
    One contract that is valid for 2009 year,  I want to copy it for 2010 year, I have to ajust some prices, and change all the validity period.
    Please, any help will be appreciate.
    Thanks in advance.
    Sonia.

    Hi Ashish Kansara,
    You can use customer exit "MM06E005". In that use the Function exit "EXIT_SAPMM06E_012", there is an internal table as "TKOMV" which will contain the condition tab. Keep your conditions as required.
    Note : This exit will get triggered in ME21N/ME22N etc. So keep proper conditions.
    Thanks & Regards,
    Rock.

  • MM - Goods Receipt (MIGO) and Validity Period End (Contracts and PO)

    Hi Gurus,
    Within our PO process, I created a PO which references a contract. Both have a Validy Period Start and End set up in customizing and filled in. But my problem is that I can still enter a Goods Receipt in MIGO to that PO, after validity has ended. I've set up in customizing the system message 06-041 as Error, and I've put in Screen Layout the checkbox 'GR message' for both PO and Contract.
    Is there a way to block the GR threw IMG outside of the Validity Period ?
    Thx in advance,
    N.H.

    Hi,
    Anyone has any clues ?

  • How to determine the contract header's valid period...

    1. How to determine the service contract header's start date, end date, when related muliple items with different start date and end date?
    i.e., what is the different between the header's valid period and item valid period?
    For example:
    Sold to A has 5 items, which has different contract line item start date and end date, e.g.,
    item 2: 2010.9-2011.9
    item 3: 2011.4-2012.4
    As for combined the all item bolonged to sold to A to one contract, so the item should have different contract start date and end date.
    However, how to determine the contract header's start date and end date?
    2. Another question is: When process service contract data migration from legance to CRM, how to design the above scenario logic?
    Thanks in advance,

    Sent again, to wait the answer....

  • Report for Service price conditions in contracts esp. validity periods

    Hi all
    I need a report that will show validity periods against price conditions for services in a contract. Can't find anything through the menus, SAP Help, Google.
    Is there something as standard or will I need to cobble something together? The report needs to display conditions and validity periods by service / contract.
    Any ideas?
    Regards
    David

    Hi
    Thanks for those, I had already found and tried a couple of those transaction. For some reason, those transactions aren't returning any results. I can get results if I branch into the 'Conditon info' screen, but unfortunately in this case the actual service numbers aren't quoted.
    Regards
    David

  • Contract specie validity period pricing

    Hi all,
    My client business process is there creating Sales Contracts base on validity period pricing
    Sales Contracts are created for long periods.The base price changes every year / for defined period.
    For Example: Contract created for 10 years. First 2 years the base price is fixed as 25 USD.
    The next 3 years the base price is fixed as 30 USD.
    The next 3 years base price is fixed as 33 USD.
    The next 2 years the base price is fixed as 38 USD.
    can any one guide me how map this functionality in SAP. it is base on Contracts price is created for long periods
    Thanks
    Rajesh

    Hi
    you can create routine in pricing if your base price is increasing in fixed rate  year on year or else by maitaining condition records also you can full fill the requirement.
    Regard,s
    Ramkrishna.

  • Contract Price wrt validity period

    While creating a contract, it picks price from info record based on the current date(date of contract creation), not based on validity period. This is a standard functionality in sap.
    Ex.
    I have a info record with following condition
    Validity period : 01.01.2010-31.12.2010 - Price 10Rs
    Validity period : 01.01.2011-31.12.2011 - Price 12Rs
    Now when I try to create a contract today for a validity period of 01.01.2011 - 31.12.2011(Manually changed), system picks price as 10 Rs( Based on document date of contract), instead of taking 12 Rs (Based on the validity period).
    Is it possible that system will take the price in contract from info record, based on the validity period rather than the current date.

    Hi Ananya,
    In Std SAP it is not possible, syestem always refer the current data and calculate on the basis of that date

  • 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

  • Fetch the netprice from the validity period which always matches with the

    Let me describe the same.
    Suppose the PO creation date is 04.07.2007
    The conditions for an item in a contract for the PO are as follows;
    1. Validity from 04.07.2007 validity to 04.07.2007 Netprice = 100.00
    2. Validity from 05.07.2007 validity to 31.12.9999 Netprice = 200.00
    We need to always fetch the netprice from the validity period which always matches with the PO creation date. here the value 100.00 should be the correct netpr as the PO creation date matches with the first validity period.
    But the program is fetching the netprice 200.000 which belongs to the second validity period. That is beacuse the select statement which fetches the data for contracts collects on the basis of EKKO-kdate and ekko-kdtab.the fields kdate and kdtab retrieves the validity period of the contract which is from 04.07.2007 to 31.072007. This data is then used to retrieve the netpr data from EKPO and it fetched 200.00 as it retrives the netprice of current data in contract validity and h not with respect to PO creation date.
    This data is then used to fetch the get the netpr data from EKPO.
    what we need is the netprice for that validity period of item(Conditions) that matches with the PO creation date..
    Below is the code where I'm selecting the data from ekko and ekpo for the contracts data..Can you please add the code snippet to the below attachesd subroutine to get the required data from KONV and KONP so that we can retrieve the correct Netprice.
    FORM select_contracts USING p_s_cebeln LIKE s_cebeln[]
    p_c_k_bstyp TYPE ebstyp
    p_p_bukrs TYPE bukrs
    p_p_ekorg TYPE ekorg
    p_p_ekgrp TYPE bkgrp
    *Begin of Mod-004
    fp_p_cernam type ty_r_ernam
    p_p_cernam TYPE ernam
    *End of Mod-004
    p_s_werks LIKE s_werks[]
    p_s_matnr LIKE s_matnr[]
    p_s_lifnr LIKE s_lifnr[]
    p_s_val_dt LIKE s_val_dt[].
    *mod-002
    data : l_amount type BAPICURR_D, " Net price
    l_waers TYPE waers, " Currency Key
    l_eff_amount type BAPICURR_D. " Effective value
    data: l_v_netpr type bprei.
    *mod-002
    SELECT ebeln
    bukrs
    bstyp
    aedat
    ernam
    lifnr
    zterm
    ekorg
    ekgrp
    waers
    wkurs
    kdatb
    kdate
    inco1
    INTO TABLE i_ekko
    FROM ekko
    WHERE ebeln IN p_s_cebeln
    AND bstyp EQ p_c_k_bstyp
    AND bukrs EQ p_p_bukrs
    AND ekorg EQ p_p_ekorg
    AND ekgrp EQ p_p_ekgrp
    *Begin of Mod-004
    AND ernam EQ p_p_cernam
    AND ernam IN fp_p_cernam
    *End of Mod-004
    AND lifnr IN p_s_lifnr
    AND ( kdatb IN p_s_val_dt OR kdate IN p_s_val_dt ).
    IF sy-subrc EQ 0.
    Populates internal table i_ekpo using EKPO table.
    SELECT ebeln
    ebelp
    loekz
    txz01
    matnr
    werks
    ktmng
    menge
    meins
    bprme
    netpr
    peinh
    webaz
    mwskz
    uebto
    untto
    erekz
    pstyp
    knttp
    repos
    webre
    konnr
    ktpnr
    ean11
    effwr
    xersy
    aedat
    prdat
    INTO TABLE i_ekpo
    FROM ekpo
    FOR ALL ENTRIES IN i_ekko
    WHERE ebeln = i_ekko-ebeln
    and aedat = i_ekko-aedat
    AND werks IN p_s_werks
    AND matnr IN p_s_matnr.
    LOOP AT i_ekpo INTO rec_ekpo.
    MOVE rec_ekpo-ebeln TO rec_contr-ebeln.
    MOVE rec_ekpo-ebelp TO rec_contr-ebelp.
    MOVE rec_ekpo-loekz TO rec_contr-loekz.
    MOVE rec_ekpo-txz01 TO rec_contr-txz01.
    MOVE rec_ekpo-matnr TO rec_contr-matnr.
    MOVE rec_ekpo-werks TO rec_contr-werks.
    MOVE rec_ekpo-ktmng TO rec_contr-ktmng.
    MOVE rec_ekpo-menge TO rec_contr-menge.
    MOVE rec_ekpo-meins TO rec_contr-meins.
    MOVE rec_ekpo-bprme TO rec_contr-bprme.
    MOVE rec_ekpo-netpr TO rec_contr-netpr.
    move l_v_netpr TO rec_contr-netpr.
    mod-002
    read table i_ekko into rec_ekko with key
    ebeln = rec_ekpo-ebeln.
    l_waers = rec_ekko-waers.
    CALL FUNCTION 'BAPI_CURRENCY_CONV_TO_EXTERNAL'
    EXPORTING
    currency = l_waers
    amount_internal = rec_contr-netpr
    IMPORTING
    AMOUNT_EXTERNAL = l_amount.
    rec_contr-netpr = l_amount.
    mod-002
    MOVE rec_ekpo-peinh TO rec_contr-peinh.
    MOVE rec_ekpo-webaz TO rec_contr-webaz.
    MOVE rec_ekpo-mwskz TO rec_contr-mwskz.
    MOVE rec_ekpo-uebto TO rec_contr-uebto.
    MOVE rec_ekpo-untto TO rec_contr-untto.
    MOVE rec_ekpo-erekz TO rec_contr-erekz.
    MOVE rec_ekpo-pstyp TO rec_contr-pstyp.
    MOVE rec_ekpo-knttp TO rec_contr-knttp.
    MOVE rec_ekpo-repos TO rec_contr-repos.
    MOVE rec_ekpo-webre TO rec_contr-webre.
    MOVE rec_ekpo-konnr TO rec_contr-konnr.
    MOVE rec_ekpo-ktpnr TO rec_contr-ktpnr.
    MOVE rec_ekpo-ean11 TO rec_contr-ean11.
    MOVE rec_ekpo-effwr TO rec_contr-effwr.
    mod-002
    CALL FUNCTION 'BAPI_CURRENCY_CONV_TO_EXTERNAL'
    EXPORTING
    currency = l_waers
    amount_internal = rec_contr-effwr
    IMPORTING
    AMOUNT_EXTERNAL = l_eff_amount.
    rec_contr-effwr = l_eff_amount.
    *mod-002
    MOVE rec_ekpo-xersy TO rec_contr-xersy.
    APPEND rec_contr TO i_contr.
    CLEAR: rec_ekpo,rec_contr.
    mod-002
    CLEAR : rec_ekko,l_amount, l_eff_amount,l_waers.
    mod-002
    ENDLOOP.
    Modifying i_contr using i_ekko.
    SORT i_ekko BY ebeln.
    LOOP AT i_contr INTO rec_contr.
    READ TABLE i_ekko INTO rec_ekko WITH KEY
    ebeln = rec_contr-ebeln
    BINARY SEARCH.
    MOVE rec_ekko-bukrs TO rec_contr-bukrs.
    MOVE rec_ekko-bstyp TO rec_contr-bstyp.
    MOVE rec_ekko-aedat TO rec_contr-aedat.
    MOVE rec_ekko-ernam TO rec_contr-ernam.
    MOVE rec_ekko-lifnr TO rec_contr-lifnr.
    MOVE rec_ekko-zterm TO rec_contr-zterm.
    MOVE rec_ekko-ekorg TO rec_contr-ekorg.
    MOVE rec_ekko-ekgrp TO rec_contr-ekgrp.
    MOVE rec_ekko-waers TO rec_contr-waers.
    MOVE rec_ekko-wkurs TO rec_contr-wkurs.
    MOVE rec_ekko-kdatb TO rec_contr-kdatb.
    MOVE rec_ekko-kdate TO rec_contr-kdate.
    MOVE rec_ekko-inco1 TO rec_contr-inco1.
    MODIFY i_contr FROM rec_contr.
    ENDLOOP.
    ENDIF.
    REFRESH: i_ekko,
    i_ekpo.
    CLEAR : rec_ekko,
    rec_ekpo,
    rec_contr.
    ENDFORM. "select_contracts
    Thanks.

    Hi,
    Please get the valid condition ( based on date ) from A016 (MK & LPA). With the appropriate KNUMH read the Condition header. You can access the different condition items viz., PB00, RA00 etc., for the values from table KONP. Further if you have Value scales / Quantity scales, you can read the data from KONM, KONW.
    An additional tips: in KONP, if you have a condition like RA00 - Rebate, the value will be multiplied by 10 and saven in database to accomodate the discount to the third decimal.
    I could not completely understand your requirements like nature of development ( Is it a Report / SAP Script ??) you are working etc., so that I could help you precisely.
    Hope this helps,
    Best Regards, Murugesh AS
    Message was edited by:
            Murugesh Arcot

  • MIGO/GR w/ PO and Validity Period Specific Pricing

    We have a business requirement to maintain validity period specific pricing on our outline agreements (Scheduling Agreements/Contracts).  The question is can receiving be controlled to pick the correct price based on delivery date and not when the goods are actually received?
    Example:
    Part A
    4/10/2014 to 4/20/2014 - $4.00
    4/21/2014 to 4/30/2014 - $5.00
    Scenario #1- Contract--> Release PO
    This scenario is working correctly due the release purchase order pricing is referenced based on when the purchase order is created.
    Scenario #2-Scheduling Agreement-->Delivery Schedule
    During the prototype, when setting up a validity perios specific price as above, the price is only taken into account at the start of the validity period.
    If the delivery schedule line says 4/18, but it's not received until 4/22, SAP will pull the 2nd validity period price instead of the 1st period.  Is there a way to ensure that the correct validity period gets pulled?

    I think its possible, though i did not check for Scheduling agreement but it works for PO
    Can you please explore Vendor master>Purchasing Data> Pricing Date Control field options
    It should help
    Thanks
    DD

  • Data Migration of Contracts with periodic billing and revenue recognition

    Hello Experts,
    I am trying to develop a legacy data migration plan for Contracts with periodic billing plan and revenue recognition.
    Example of the scenario is given below:
    Customer signed a contract for one year starting 01/01/2009.
    Customer is billed quartely, billed in advance.
    SAP going live on 04/01/2009
    Customer is billed for 3 months and also for initial set up fees.
    Revenue recognition is done monthly.
    We have to migrate this contract to SAP.
    Billing document posting may be necessay as it affects revenue recognition which spans across the total contract period.
    Any ideas how to do this?
    Thanks  A Lot
    Anil
    Edited by: Anil  Jose on Sep 17, 2008 9:38 PM

    Hi Anil
    How did you manage this? We also had the same problem in one of our contracts and what we did was that we copied the contracts from the legacy with the full value. That is suppose SAP went live on 1st April, 2009 and the contract was created on 1st January 2009 for a value of suppose 100 USD, with the first billing being done on 1st Jan for 33.33 USD for 4 months. We first created the contract with a validity from 1st Jan 2009 in the new system. We billed it with a billing type that we created that did not actually create new accounting entries as the accounting entries had already been created in the legacy system. In the new system then we recognised the revenue till the go live, so that the actual value remaining of the contract reduced. Then we started the billing plan of the contract from 1st of April 2009 for the remaining amount. So next invoice was created on 1st april for 33.33 USD. Can you share your solution.
    Regards
    Indranill

Maybe you are looking for