CRM Conditions Update

Hi All,
I am currently busy on a project that requires conditions to be updated to a CRM 'Contract'. I have tried using FM's 'CRM_PRIDOC_MAINTAIN_MUL_OW' and 'CRM_ORDER_MAINTAIN' but have not been successful.
With both of these FM's I am populating the IT_PRIDOC table with what I think is all the correct information, but it still does not save the conditions.
Is there anyone who might have some sample code to assist with my issue?
Regards
John

This example works fine for me. Modify it according to your needs...
Price
              IF it_item-value IS NOT INITIAL.
                ls_cond-kschl = 'PR00'. " add price
                ls_cond-kbetr = it_item-value.
                ls_cond-waers = st_head-currency.
                INSERT ls_cond INTO TABLE ls_pridoc_com-cond_add.   
                index_2 = 1.
                CLEAR: ls_cond.
              ENDIF.
Discount
              IF it_item-discount IS NOT INITIAL.
                ls_cond-kschl = 'ZPPP'. " add discount
                wa_procent_calc = it_item-discount * 10.
                ls_cond-kbetr = wa_procent_calc."it_item-discount.
                ls_cond-waers = '%'."st_head-currency.
                INSERT ls_cond INTO TABLE ls_pridoc_com-cond_add.   
                index_2 = 1.
                CLEAR: ls_cond, wa_procent_calc.
              ENDIF.
              IF index_2 = 1.
                ls_pridoc_com-ref_handle = counter.
                ls_pridoc_com-ref_kind = 'B'.
                INSERT ls_pridoc_com INTO TABLE gt_pridoc_com.
                CLEAR: index_2,ls_pridoc_com.
              ENDIF.

Similar Messages

  • Update rules:Conditional update

    Hi
    Can we use update rules to conditionally update fields in a record.
    By condtionally i mean to say that, from a delta record ,can we have some conditions so that based on that, we will update the fields.
    Like based on conditions , we will update only selected fields .Is it possible using
    update rules or by any other ways at the BW side.
    Regards
    Leon

    Hi Dash
    Please have a look at the req. below.
    We have a scenario in which we have values for few fields when a record is created. But once the record is updated ,we will lose those by overwriting that with initial.But we need to maintain those values for those fields to be retained in the BW system in the delta update.
    Eg. We have 50 fields in the extract structure , and for fields X,Y we have values 'S1','S2' respectively(char values ) when a record is created,but when the record is updated in CRM system,it will be overwritten by initial.So in the available delta record ,we don’t have the values 'S1','S2'.But in the BW system, we need to have the same      original values instead of initial value in the delta record.
    Can you suggest a solution to maintain the original values ?
    Does BW support conditional update,like based on condition check,update the some selected fields of the record instead of updating with all the fields in the delta record?
    Regards
    Leon

  • Condition update in sales order

    Dear All,
         I am trying the condition update functionality in the condition records. The condition type is a discount condition type maintained in percentage.
    I have updated the check box in the condition type and created a new condition record with the maximum allowed value for it.
    But when i create the order, delivery and billing the condition record is not getting blocked and the system is not giving the warning message even the value exceeds the amount given in the additional tab in the condition record.
    Regards,
    Parthasarathy.R

    Hi Partha,
                     Creating condition update is a special scenario.Let us take the following Scenario.Company xyz decides to sell a new product ABC for a discounted price ,say,Rs 100 until the cumulative value of the dicount reaches 10000.This means that effectively for the first 100 orders this special discount is applicable.Once the first 100 orders are raised then the system automatically stops processing that special discount.But it never blocks the order.
    Regards,
    K.V.S.Phani Prasad.

  • CRM 2015 Update 0.1 Install Fails with SQL Error

    Hi, anyone managed to install CRM 2015 Update 0.1?
    The software installed fine but the DB updates fail with a SQL error. Just want to know if this is just my issue or if MS have a bug in the update. This is the SQL error:
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The current transaction cannot be committed and cannot support operations that write to the log file. Roll
    back the transaction.
    Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.
    All of the ORGs fail with this error, even when I try to apply the DB update via Deployment manager. I've had to back out the rollup.

    The issue appears when the update process creates the index cndx_BusinessDataLocalizedLabel. This is a known cause which is under investigation internally. Currently it seems to plan to release in CRM 2015 SP1

  • Use of Condition update while creating Condition Records

    Hi Experts,
    I have to maintain MRP for a product which will be applicable for only 1 particular order. after which system should pick up old MRP.
    By using CONDITION UPDATE feature , i have tried to do it , but once maintained , its always picking new MRP for every order.
    (If it being a record where only new price to be defaulted in one order and no need to create 2nd order , this is ok ., but not in my case)
    Can any one suggest me how to go with this
    Thanks in advance,
    Jignesh

    Hi,
    This can be done using the CONDITION UPDATE
    In the condition type check the CONDITION UPDATE AND SAVE IT
    While creating the CONDITION RECORDS, maintain the values and click ont he ADDITIONAL DATA (F7) then maintain the value in the field MAXIMUM NUMBER OF ORDERS , PUT The sales order as 1.
    Then try
    Please revert if you need further details
    thanks,
    santosh

  • How to create conditional update trigger in sql server

    How to create conditional update trigger in sql server

    You cant create a conditional update trigger. Once you create an update trigger it will get called for every update action. However you could write logic inside it to make it do your activity based on your condition using IF condition statement
    Say for example if you've table with 6 columns and you want some logic to be implemented on update trigger only if col3 and col5 are participating in update operation you can write trigger like this
    CREATE TRIGGER Trg_TableName_Upd
    ON TableName
    FOR UPDATE
    AS
    BEGIN
    IF UPDATE(Col3) OR UPDATE (Col5)
    BEGIN
    ....your actual logic here
    END
    END
    UPDATE() function will check if column was involved in update operation and returns a boolean result
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Condition update error  :There is no condition update from sales orders.

    I am testing the condition update by condition type K005 , which have been set the condition update indicator ,and I have also set the Max.number.of.orders  to 1 , but after I created the first sales order ,the condition record still make effect in the second  and third sales order ,which was created without referece to the first one .
    And  when I  look at the cumulative value in the condition record ,it says "There is no condition update from sales orders."
    Anyone can give me some light ?
    BTW , the sales order type is ZOR ,which I copy from the standard order type .And the item category is ZTAN , copy from  standard IC TAN .
    thanks for your help in advance .

    hello, friend.
    there are at least 3 things that you will have to check, since records for condition type K005 is created for a specific combination:
    1.  check if the item category with condition update was the one determined in the order
    2.  check if the customer has a valid K005 record
    3.. check if the material has a valid K005 record
    also, since you specified "1" as maximum number of orders, this could have prevented any updates.
    regards.
    Edited by: jonathan y on Sep 17, 2009 2:59 PM

  • Condition Update-How to increase Max. No of orders?

    Hi
    i have activated condition update and want to give discount to first 10 customers (in first 10 sales orders) who are buying the material. Now in condition record, when i select the material and goto additional data, the max no. of orders i can mention are 3. how to make it upto 10.
    Any config settings are available?
    thanks
    Deepak Mehmi

    Hi,
    Go to T-Code SE11, Enter "ANZAUF" in Domain and Execute
    click on the Value Range Tab under that you can see the Upper limit 03 ask your ABAPer try to maintain 10
    If you want to do Changes I think system will ask Access Key , ask BASIS Consultant he/she will provide
    Regards,
    Prasanna

  • Condition update???

    hai all,
      i want to use a condition type K004, and i have checked condition update
    feature in the condition type template, i have maintained maximum condition value
    in the condition record as 2000. and when iam creating order, the condition type should automatically get swithched after reaching the value of 2000.
    but it is still appearing in the next created order.
    whatis the use of condition update feature ?
    kindly update the issue.
    regards
    sriram.

    HI Sriram.,.,
                  This is the consept of condition update ,Please go through & check out whether you followed the same process or not
    Condition update
    Controls whether limit values are relevant for pricing.
    E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.
    This total value can be specified in the condition record.
    Condition Update -
    This function is configured at the condition type level. it is basically used to update the pricing elements at various levels of the order cycle. like for example price calculated at the order level may differ by the time is delivery is due for that order. Pricing elements such as freight, taxes change periodically. therefore a condition update is needed inorder to update the pricing elements.
    For validating the condition record for the first 100 orders,
    you need to Customise the Condition type by checking the *condition update. *This will make the condition type updates.
    In the maintaining screen condition record of the condition type go to Additional data and give the value either total value or the total number of orders(like 100 in your case).
    This will make the condition record work for 100 times. You can also see the status of number of records that were already been utilised, in the Change condition record screen go to the environment and the cumulative values will give you total consumed sales orders. This will work for you
    In a standard SAP system the check against number of orders is limitted to 3. So if you want to check against 100 you will have a problem. In this case you have to change the domain for "ANZAUF" as the value range is limited from 01 to 03. If you can convince your customer that you limit to first 99 than you only have to extend the range.
    If you have to go for 100 or higher you have to change the length of the domain from 2 digits to whatever is required.
    In both cases you change a standard SAP setting which will have an impact when you do a release upgrade.
    REWARD if helpfull
    Thanks & Regards
    Narayana

  • No condition update from the sales orders exist - VK322 Message

    Hello All,
    I have activated " Condition Index" & " Condition Update" flag for one of my discount condition type and then created it's condition record along with scales on three levels. The condition type which I mentioned above is set as " Value Scale" in Scale Basis for checking the document value and apply the applicable discount percentage.
    I have created three sales orders wherein the discount percentage is getting applied as per my condition record ( so, the document value is getting accumulated and compared with the condition record correctly )  but when I try to check the cumulative values ( ctrl +shift + F4 ) from the condition record, I get information message " VK322" mentioned in the subject.
    VK322 -
    No condition update from the sales orders exist
    Message no. VK322
    Diagnosis
    The following causes are possible:
    1. There are no sales orders for the condition record that you selected.
    2. Updating condition records in the sales order entry is not active.
    Procedure
    Concerning 1:
    Check the sales orders created for the condition record that you selected.
    Concerning 2:
    Activate the updating for condition records in the sales order entry.
    I have checked everything in SPRO for this but could not find anything which can give me a clue to resolve this problem, especially " Concerning 2" part of this message.
    My requirement > To be able to see the cumulative values from condition record.
    Also, in which table the accumulated values get stored?
    Appreciate your expert advise on this issue.
    Regards,
    Hrishi
    Edited by: Hrishikesh Bhalwankar on Sep 13, 2011 1:59 AM

    Hello Everyone,
    I would like to thank each one of you for giving valuable inputs in regard to my requirement and I would like to let you know that I am able to achieve the results as per the expectation.
    I would also like to share some key things which I did ( with the help of all your expert inputs ) due to which the requirement is met:-
    1. Activation of ' Condition Index, Condition Update' in V/06 for the discount condition type.
    2. Maintained ' B - Value Scale' in Scale Basis for the said condition type in V/06 - my requirement was to check against a value to apply the necessary scale base percentage.
    3. Activation of ' S071' info structure via OM01
    4. Condition record maintenance as per the required scales.
    4. Written a new routine to check the accumulated condition base value from S071 along with the current document condition base value.
    5. Put this routine in ' Scale Formula' in V/06.
    This is giving me the perfect results for the correct application of the discount.
    Just last question - How to re-organize the S071 info structure as I tried to re-organize it with Standard Program ' RV15F001' but it is not re-organizing this info structure... Any idea on this?
    Thanks a lot friends for all your advice...
    Regards,
    Hrishi
    Edited by: Hrishikesh Bhalwankar on Oct 11, 2011 2:11 AM

  • Condition update for discount

    the scenario is:
    there are 3 materials which has same material group.
    X  material, material group AA
    Y material,  material group AA
    Z  material,  material group AA
    the condtion tables in the access sequence is sales office/material group. that means the customers under  selecteed sales office will get ex;Rs.2/- as discount if they buy the material which has material group AA.
    here the sales office say for ex:01-India
    here there are 3 customers under 01-India sales officde
    Customer A,B,andC
    the requirement is :
    1. How we control if X and Y material is allowed for discount 2/- and Z is not allowed though it is having AA material group
    2. If condition update is set for differenet customers at different quantity for ex:for A customer 100 units and for B customer 150 units and for C customer 200 units, when we are not considering customer field in VK11.
    requested quick reply please

    Dear Mr Paruchuri,,
    Are you open to including a requirement in the pricing procedure?.
    If so, the material number to be excluded may be identified, in say an external table (with validity).
    By this, the material would get ignored, during evaluation of pricing procedure.
    An alternative would be to introduce a condition type in the pricing procedure, which refers the original (discount) condition,  which has a material (normally along with SO, DC)access, such that it returns a value equal but opposite to the referring condition.
    By this the value evaluated in the original condition would be automatically discounted in the next step.
    Trust these views help you.
    Regards,
    K Gopidas.

  • Condition Update and Condition Record

    Hi Friends
    We have maintained Condition record validity and same will be used for u201CCondition updateu201Dfeature.
    Condition Update says that Condition record to be executed only first 10 orders for one customer as per our configuration and from 11th order on ward new condition record to be triggered automatically.
    Note: we are not sure that how long customer will take time to finish first 10 orders.
    So kindly let me know if there is any way to resolve above mentioned issue.
    Warm Regards
    Vijay

    hi Raghu,
    thanks for the your response but condition record is based on material ....and you must be expecting if it is on customer based we can manage it through validity right ....but how can we sure that customer will be closing his orders by some time.
    please let me know if you have any volition.
    warm regards
    Vijay

  • Condition update issue

    Dear all,
    could you please help out on this issue
    1. i created one condition type n that condition type condition update check box is activated.
    2. maintained condition record as discount in percentage then click on additional tab there will be appeared 3 fields
    MAX value
    no. of orders
    MAX QTY
    3. this scenario i able to see the determination of condition type in only number of orders but another 2 categories or options are not working.
    Thanks in advance

    Hi Shiva,
    PFA here with condition type control

  • Condition Update field

    Hi,
    I know we can set the condition update field in the condition type so that, it can store accumulated values, for example, discount only upto maximum of 3000pcs.
    But this is one is based on Sales Order value and not Billing value.  how can I set so that it considers only the invoice quantity and not the order quantity?
    If I reject the Sales Order (using reason for rejection).. the accumulated value is not deducted or reset back to zero.. it still considers the quantity of the rejected item.  What should we do so that it will not

    I am not sure that will function, but check the customizing options behind the reason for rejection.
    Another option would be to force a new price determination in the billing document (look at the copy control between the delivery note and the billing document at the item level).
    Best Regards,
    Franck

  • Difference between Condition update & condition ndex

    Hi Guys,
    Could u tell me whatz he differnce btween condition update and condition index?
    Cheers
    Chitty

    Condition update provides the basis for the following pricing functions:
      Maximum Value
      Maximum quantity
      Maximum Number of Sales Orders
    Condition Index :
    Use
    You can create and use condition indices. You can use these indices to display, change and
    create condition records with reference. This transaction can include condition records with
    several condition types and tables. For example, you can use a condition index if you want to see
    all condition records that apply to a particular product regardless of whether the records are
    prices or discounts. In this case, you can use one of the standard condition indexes. Or you may
    want to see a list of condition records that contain a particular sales deal and a material from a
    user-specified list of products. To display this information, you can create your own condition
    index.
    Hope it helps. Reward points if found useful.
    Rajesh

Maybe you are looking for