CONDITIONS IN A CONTRACT

Dear All,
Kindly guide that while making contract will i have to maintain conditions for contract in FV11 , as i have to make a value contract .
thanks in advance
sap11

Hi,
u need not to maintain any records while creating contracts, and that is depend on scenarios.
FV11 is to create a condition records for Tax condition types not for purchasing condition types. If that is the case create condition reords in MEK1 for ur purchasing  condition types.
while creating a contract u wil maintain a tax code. The conditions waht u have maintained for ur tax code that will propose during PO and MIGO.
Revert back for any clarifications.
Reward if useful
Regards
Viru

Similar Messages

  • Purchase condition based on Contract document type

    Dear Gurus,
    We have created a seperate documents for Domestic and Import Contracts. We want to trigger Domestic Pricing condition in Domestic Contract, and vise verse... We want only the domestic condition to apprear in the dropdown when the purchase team is creating a domestic contract. Does Condition sequencing provide any means to achive this?
    Waiting for a reply.
    Regards
    VPV

    >
    VIKAT verlekar wrote:
    > Dear Gurus,
    >
    > We have created a seperate documents for Domestic and Import Contracts. We want to trigger Domestic Pricing condition in Domestic Contract, and vise verse... We want only the domestic condition to apprear in the dropdown when the purchase team is creating a domestic contract. Does Condition sequencing provide any means to achive this?
    >
    > Waiting for a reply.
    >
    > Regards
    >
    > VPV
    Separate calculation schema are created for both domestic and import and they are attached to vendor. When  vendor is inputted in the contract, vendor is the determining factor of which calculation schema it should bring as attached in the vendor. So only conditions attached with vendor will be bought once vendor is entered in contract. It can be either local or import.

  • Transaction used for maintaining condition record for contract

    Hi All,
    In one of the issue user is not able to print contract,we have noticed that default printer is set for user.I need to check what condition record is maintained for user.
    Can anyone let me know what is the transaction used for maintaining condition record for contract output.
    Regards,
    Dharmesh

    Hi
    MN01 Create Message: RFQ
    MN04 Create Message: PO
    MN07 Create Message: Outline Agreement
    MN10 Create Message: Schd. Agmt. Schedul
    MN13 Create Message: Service Entry Sheet
    MN21 Create Condition: Inventory Mgmt
    MN24 Create Message: Shipping Notif.
    MN27 Create message: rough goods receipt
    MN10 / MN11 - Scheduling Agreement Delivery Schedule
    Vijay

  • Condition Groups in Contracts

    Hi,
    Is it possible to default few condition types in contracts transaction types in CRM under the Sales Agreeement tab?
    The issue is that, there is a condition group assiged to the transaction type instead of pricing procedure.
    Can some one help me to get the some default condition types?
    Regards
    Kamalesh

    Hi,
    Did n't really get the scenerio & problem? could you elaborate little more? What conditions & condition group is being used under the tab you mentioned?
    you can control the customizing of conditions & condition group visible in a TR in SPRO. Try following:
    1. check condition group being used to the application SAP CRM in SPRO > Customer Relationship Management> Master Data> Products> Special Settings for Sales Operations--> Assign Condition Group to Application CRM
    2.Assign the condition types in your pricing procedure to the above condition group by choosing SPRO>Customer Relationship Management> Master Data --> Conditions and Condition Technique --> Condition Technique: Basics Create Maintenance Group
    Let me know if this works....!!
    Best Regards,
    VIshant Jain

  • *Is it possible to put service conditions in sub contract PO?*

    We are giving an Item X for servicing to a vendor. The vendor can do to 2 services S1 and S2 to the item X and give it back.
    For this we made a recursive BOM with item X and created a sub contracting PO.
    But the problem is we are already having service master and SERVICE conditions for S1 and S2. The vendor needs to charge on the basis of these service conditions.
    Example:
    Item is TOOL-X.
    Service1 and condition: Polishing. 25 INR / each.
    Service2: and condition: Plating. 8 INR/ sq.mm
    As we need to keep account of items given to Vendor (sub-contractor), I selected item category L. But here I cannot put service conditions? Is it possible to put service conditions in sub contract PO?
    If I go for item category D (service) I will not be able to account for materials given to subcontractor.
    Please suggest how to reflect this scenario in PO.
    Ganapathi

    Hi
    It is always advisable not to put servicable materials in subcontracting.The reason being, every service would add value to the same material ( MAP will change) .If the material undergoes service many times then the Inventory value of the material will be Inflated.Hence to avoid this follow the steps
    1) Create a service PO against the vendors
    2) Issue the material via MB1B 541
    3) Recieve the material through MB1B 542
    4) Enter service entry sheet via ML81N
    5) MIRO for service vendor
    Regards
    Sandeep

  • How to add conditions when uploading contracts

    Hi experts
    I'm trying to upload contracts from a text file using BAPI BBP_PD_CTR_CREATE.
    I'm not able to create conditions with the contracts. Can anyone tell me the mandatory parameters that have to be passed in the BAPI in its it_conditions table.
    This is what I'm doing:
      wa_condition-guid = c_dummy_cnd.       "Dummy guid
      wa_condition-cond_type = l_condtyp.
      wa_condition-COND_PRC_UNIT = '0'.
      wa_condition-COND_RATE = l_condval.
      wa_condition-COND_CURR = l_condcurncy.
      wa_condition-COND_TAB = l_condtab.
      wa_condition-date_from = l_valstart.
      wa_condition-date_to = '99991231'.
      APPEND wa_condition to tbl_condition_ex.
    Points will be rewarded...
    Thanks

    Hi Neelima
    I tried with the code that you had provided but I still couldn't create the discount conditions.
    Here is my code in more detail:
      IF l_condtyp = '01AG'.                                "Header discount
        l_condtab = 'SAP019'.                               "Table for header discount
        wa_condition-p_guid = c_dummy_hdr.                  "Dummy guid of header
      ELSE.
        IF l_condplant IS NOT INITIAL .                     "Location dependant item discount
          wa_condition-INVENT_LOC_ID = l_condplant.         "Adding location
          l_condtab = 'SAP068'.                             "Table for location dependant discount
          wa_condition-p_guid = c_dummy_itm.                "Dummy guid of item
          wa_condition-COND_UNIT = l_unit.                  "Unit of item
        ELSE.                                               "Location independant item discount
          l_condtab = 'SAP016'.                             "Location independant discount table
          wa_condition-p_guid = c_dummy_itm.                "Dummy guid of item
          wa_condition-COND_UNIT = l_unit.                  "Unit of item
        ENDIF.
      ENDIF.
      wa_condition-guid = c_dummy_cnd.                      "Dummy guid
      wa_condition-cond_type = l_condtyp.       "(01AG)
      wa_condition-COND_RATE = l_condval.    "(15-)
      wa_condition-COND_CURR = l_condcurncy.   "(%)
      wa_condition-COND_TAB = l_condtab.      "(SAP019)
      wa_condition-date_from = sy-datum.          "(also tried vper_start ie. start date of contract)
      wa_condition-date_to = '99991231'.
      wa_condition-time_from = '000000'.
      wa_condition-time_to = '235959'.
      wa_condition-UOM_DENOMINATOR = '1'.
      wa_condition-UOM_NUMERATOR = '1'.
      APPEND wa_condition to tbl_condition_ex.
      CLEAR wa_condition.
    The importing table is still empty after the FM has been executed. There are no messages in the messages table either.
    Please help me out here.
    This is very urgent.
    Thanks

  • Absolute condition value in contract and release order

    Hi,
    We are creating quantity contract. When a absolute condition (value) is entered this value is considered for release qty in the contract for calculating the unit price.But when a release order is created for this contract, the same absolute value is for the PO quantity due to which there is a difference in unit price between contract and PO.
    Please advice.
    Regards,
    Pratap

    Hi,
    Verify you steps, find link below:
    http://help.sap.com/saphelp_470/helpdata/en/75/ee0f4d55c811d189900000e8322d00/content.htm
    Reetesh

  • Duplicate pricing conditions due to contract supplements

    Hi all,
    <br><br>
    We want our pricing conditions to appear automatically on a normal purchase order and on a purchase order with reference to contract, but they should only be on the purchase order once. We're experiencing difficulties since the condition is fetched and displayed twice (once coming from the condition supplement via the contract and a second time via the standard purchasing procedure).
    <br><br>
    Let me sketch the scenario.
    <br><br>
    We have two procedures used for purchasing:<br>
    - procedure ZM0000 as standard purchasing procedure<br>
    - procedure ZM000S as contract supplements procedure
    <br><br>
    Both procedures contain conditions ZA00, ZR01, ZR02, ZR03, ZR04, ZR05 and these conditions are not indicated as a manual condition.
    <br><br>
    For condition type ZA00 the pricing procedure ZM000S is defined so that condition supplements can be added in the purhcase contract. There is also an Access Sequence for this condition to prevent it from appearing twice on a purchase order with reference to a purchase contract.
    <br><br>
    When we create a normal purchase order, we get all conditions from the ZM0000 procedure without any problem.
    But when we create a purchase order with reference to a contract with condition ZA00 and condition supplements ZR01, ZR02, ZR03, ZR04, ZR05; then we see these ZRxx condition appearing twice instead of once.<br>
    It's displayed once coming from the ZM0000 procedure and a second time due to the ZM000S procedure.
    <br><br>
    I've had a look at the standard procedures, at sap notes and searched on the forums and can't find a feasible solution for this.
    <br><br>
    One way it is commonly solved is to make the ZRxx conditions a manual condition but that means the user will have to add these conditions manually to the purchase order. When we're talking about 50 or more conditions then it becomes a cumbersome to add all these conditions (if required) manually one by one for each purchase order that the user creates --> not feasible.
    <br><br>
    I guess another solution would be to create an access sequence for all ZRxx conditions based on purchase order type and then create condition records for all ZRxx conditions for the purchase documents without reference to a contract. That way the condition will be displayed once (from the condition record) on a normal purchase order and once (from the contract, since the condition record can't be found) in case of a purchase order with reference to a contract. When we're talking about 50 or more conditions and more then 2 document types, then maintaining all these condition records is quite some task --> not really feasible, not the prefered solution.
    <br><br>
    As an alternative to SAP standard we've found the following enhancement point in LV61AA11 where we could possibly delete the "duplicate" condition from KONV if the condition origin (KONV-KHERK) is not equal to "Condition supplement" (F) in case of purchase document type that references to a contract... but this is not the prefered solution.
    <br><br>
    <span style="font-family: Lucida Console">-----<br>
    get pricing result from database table<br>
    ENHANCEMENT-SECTION     KONV_EINLESEN_02 SPOTS ES_SAPLV61A.<br>
      select * into table hkomv<br>
               from konv<br>
               where knumv = komk-knumv<br>
               order by primary key.<br>
    END-ENHANCEMENT-SECTION.<br>
    </span>
    <br><br>
    Also, it's not a feasible solution to put a requirements formula on all these ZRxx condition because we're talking about more then 50 conditions.
    <br><br>
    Does anyone know a solution to this problem?<br>
    How can we make sure the condition is displayed only once? (be it on the standard purchase document or on the purchase document with reference to the contract)<br>
    Is there a standard approach for this?
    <br><br>
    Thanks in advance for your time.
    Edited by: Kevin Coquel on Apr 15, 2010 3:34 PM

    Bernhard, <br />
    Thank you, but as I mentioned in my starting post, this is not feasible as this is concerning over 50 conditions (some of which already have other requirements formulas). <br />
    Using requirement routine for all is an option we want to avoid at all costs.<br />
    It would mean we need to have edit our existing requirement routines to also include routine 15 (as you can only have one requirement routine per condition in a pricing procedure).<br />
    <br />
    Hardik, <br />
    Thank you for pointing us to EXIT_SAPMM06E_013.<br />
    Preferably we would like to solve this using SAP standard before turning to ABAP development.<br />
    <br />
    I'm a bit surprised not being able to find a SAP standard solution to this problem. Since it's not possible to define a different pricing procedure per purchasing document type I would expect a) there is a way to avoid duplicate conditions (coming from the contract supplements) when you're in a purchase document with reference to a contract and b) that the conditions will appear by default in a normal purchase document (instead of having to add them manually one by one when you use "Manual" in the pricing procedure).

  • Condition type in contract not reflecting on to the PO release

    Hi All,
    I have a contract wherein i have two condition types which are set i.e. PB00 and ZM07. Now i've made some changes and removed ZM07 and instead put ZM05.
    This new condition type (ZM05) is not reflecting on to the PO already released or on to the new line items that are being added to the already existing PO's. Kindly let me know what/where to change to effect ZM05 on the line items of release orders.

    Hi,
    One thing you could try is the Update button on the item Conditions detail tab.  Run the selection for B    Carry out new pricing
    C    Copy manual pricing elements and redetermine the others
    "B" is pretty good for adding in new condition types that are added after the PO has been created.
    Regards.

  • Service condition records in contract

    Hi
    We have created service master....maintained the condition records for the same(Vendor/Plant/Pur Org combination)
    When we are creating a contract and mention the service master in the services list,it is not picking the value maintained in the condition.
    Can somebody throw light on what could be the possible issue.
    Thanks

    Hi,
    Why you want value in Service condition record flow to Service contract?
    You have  maintained the condition records for Vendor/Plant/Pur Org combination but where as condition key for service master- which is missing!
    For your requirement on pricing, add field SRVPOS for Activity Number/Service Master in the following path:
    SPRO-> MM-> Purchasing  > Conditions -> Define Price Determination Process -> Extend Field Catalog for Condition Tables
    Now create Condition Table( 989 for example) with condition keys Service master/Vendor/Plant/Pur Org combination
    And go for following:
    1.Assign table 989 to your access sequence.
    2.In  t.code: M/06 -assign access sequence  to condition type for service 
    3.In t.code: M/08 - MM pricing procedure  procedure ,keep condition type for service
    4.Create condition record in t.code: MEK1 with combination Service Master/Vendor/Plant/Pur Org
    Go for creation of service purchase order, you will find data maintained in condition record flow to service purchase order.
    Refer how to have different condition type for material and service
    Different pricing for service and production
    Regards,
    Biju K

  • Condition records in contract management

    We are using contract management linked to our internal catalog.
    When we create the contract we have found that where the contract has multiple lines only the first 8 records get conditions associated with them.
    This is causing us an issue as when we download them to update them the task becomes very slow and it is better to manually update. This is not viable for a contract that has 10000 items.
    I have checked SAP notes and there do not appear to be any shown on this problem.
    Nick J

    Dear Poster
    Your thread has had no response since it's creation over
    1 year ago, therefore, I am closing the thread.
    Should the issue still be outstanding please create a new thread in the relevent forum.
    Thank you for your compliance in this regard.
    Jason Boggans
    SAP SRM SDN Moderator

  • Close PO princing conditions when ref. contract

    Hi,
    I have the following question.
    I'm creating a PO referencing to a contract, some conditions are determined automatically from the contract, and the user is not supposed the change any pricing conditions.
    The question is: is there some way to close the pricing conditions in the PO, the problem is that I need to close only for this specific PO type.
    Thanks.
    Alexandre.

    hi,
    You can delete the condotions which are not required in the PO can be deleted in the aggrement itself.
    But however you can create a info record for the same and and if you update it, with the deleted conditions and you can create PO with deleted conditions.This can be one possible solution.

  • Trans ME31K:Defaulting item condition validity to contract validity date

    Hello Experts,
    I have a request from my client which is as follows :
    On transaction ME31K (Create Contract), at header I can enter a start date and an end date for the validity of my contract.
    Program name : SAPMM06E
    FIELD-NAMES : EKKO-KDATB & EKKO-KDATE
    The users want the same date range to appear at item level for the conditions :
    Select a new created Item > Conditions.
    Program name :SAPMV13A
    FIELD NAMES : RV13A-DATAB & RV13A-DATBI
    Because, the transaction is changing the program name, it is very difficult for us to replicate the dates at the item's condition level.
    Can you please suggest any idea to implement this solution ?
    Thanks & Regards,
    Mahesh
    Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:52 PM
    Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:53 PM

    Hi raghavendra sai !
    Thanks for the answer.
    But actually, my client wants  'from date' of the items conditions to be defaulted to the date that he indicated on the contract's validity date at header (from date - EKKO-KDATB).
    A contract can be created with a validity interval that starts from a past date.

  • Conditions for service contract

    hello,
    I am creating service contract containing one line item ( i.e.activity) and no. of services in that line item. in the change mode i wanna put some condition on the activity level but not on service code level, but system is not showing the condtion in change mode. for activity level . pls advice

    Hi,
    For service contract you can not assign any condition type.
    You can assign at service level.
    Hope it will help you.
    Regards,
    Manish Agarwal

  • Change Condition price of Contract through IDOC

    Hi all,
                 I am changing  the condition type(PB00) price (KONP-KBETR) of Contract using Inbound Idocs using message type COND_A.The price is updated correctly.
                 But the change is not getting reflected in the net price (EKPO-NETPR).Is it some problem in the Idoc processing?
    Thanks in advance.

    Resolved

Maybe you are looking for