<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: routine problem for VOFM in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070753#M727858</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;its giving error - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors while transferring conditions: duplicates found&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Message no. VH806&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Diagnosis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    During the data transfer after successful pricing, the system recognized&lt;/P&gt;&lt;P&gt;    that document conditions with the same key exist for condition type&lt;/P&gt;&lt;P&gt;    ZFBP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System Response&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Transferral of the document conditions is canceled, in order to prevent&lt;/P&gt;&lt;P&gt;    incorrect system behavior or a cancellation of updates when you save. At&lt;/P&gt;&lt;P&gt;    the same time, the system set pricing of the item affected 000010 as&lt;/P&gt;&lt;P&gt;    containing errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    First find the cause of the problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1.  For a variant condition, is the system including a particularly      &lt;/P&gt;&lt;P&gt;     large number of characteristics for valuation?                                                                                &lt;/P&gt;&lt;P&gt;2.  Is a condition type being used as an additional condition?                                                                                &lt;/P&gt;&lt;P&gt;3.  In the pricing procedure, are there several condition types at the   &lt;/P&gt;&lt;P&gt;     same level number?                                                                                &lt;/P&gt;&lt;P&gt;The problem can only be solved removing the cause of the problem. If the &lt;/P&gt;&lt;P&gt; first cause applies, you should consider distributing the                &lt;/P&gt;&lt;P&gt; characteristics using several condition types. In the second case, you   &lt;/P&gt;&lt;P&gt; should check whether all conditions are required at the same time, or    &lt;/P&gt;&lt;P&gt; whether you can avoid their use altogether. In the third case, you will  &lt;/P&gt;&lt;P&gt; need to change the pricing procedure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Nov 2007 11:45:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-22T11:45:08Z</dc:date>
    <item>
      <title>routine problem for VOFM</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070751#M727856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi gurus , &lt;/P&gt;&lt;P&gt;in VOFM , I am creating a routine for VA01 , conditions formula, for customer discount, Z007 is condition type , but problem is that after running the program nothing is coming.&lt;/P&gt;&lt;P&gt;     &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM FRM_KONDI_WERT_860.&lt;/P&gt;&lt;P&gt;*{   INSERT         DFDK914010                                        1&lt;/P&gt;&lt;P&gt;if XKOMV-kschl = 'Z007'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data : basic like xkomv-KWERT,&lt;/P&gt;&lt;P&gt;       vat like xkomv-KWERT,&lt;/P&gt;&lt;P&gt;       X LIKE xkomv-KWERT,&lt;/P&gt;&lt;P&gt;       Y LIKE xkomv-KWERT,&lt;/P&gt;&lt;P&gt;       Z LIKE xkomv-KWERT,&lt;/P&gt;&lt;P&gt;       ZTERM LIKE KOMP-ZTERM,&lt;/P&gt;&lt;P&gt;       DAYS LIKE T052-ZTAG2.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;+SK21112007&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;data: z_zterm like vbkd-zterm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: ref_zterm(21) value '(SAPMV45A)XVBKD-ZTERM'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;field-symbols: &amp;lt;FS_ZTERM&amp;gt; type any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;assign (ref_zterm) to &amp;lt;FS_ZTERM&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;z_zterm = &amp;lt;FS_ZTERM&amp;gt;.&lt;/P&gt;&lt;P&gt;*+SK21112007&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;READ TABLE XKOMV WITH KEY KSCHL = 'ZFBP'.&lt;/P&gt;&lt;P&gt;if sy-subrc = 0.&lt;/P&gt;&lt;P&gt;BASIC = XKOMV-KWERT.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;READ TABLE XKOMV WITH KEY KSCHL = 'JIN7'.&lt;/P&gt;&lt;P&gt;if sy-subrc = 0.&lt;/P&gt;&lt;P&gt;VAT = XKOMV-KWERT.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*+SK21112007&lt;/P&gt;&lt;P&gt;SELECT SINGLE ZTAG1 INTO DAYS FROM T052&lt;/P&gt;&lt;P&gt;WHERE ZTERM = Z_ZTERM.&lt;/P&gt;&lt;P&gt;*+SK21112007&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;X = BASIC + VAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Y = ( X * 10 / 100 ) / 365.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Z = Y * DAYS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*komv-KWERT = Z .&lt;/P&gt;&lt;P&gt;*xkomv-kwert = z.&lt;/P&gt;&lt;P&gt;xkwert = z.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;*}   INSERT&lt;/P&gt;&lt;P&gt;ENDFORM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2007 11:09:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070751#M727856</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-22T11:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: routine problem for VOFM</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070752#M727857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you activated the routine (marked as active in VOFM)  and also run the program RV80HGEN to activate the Routine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points if useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2007 11:23:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070752#M727857</guid>
      <dc:creator>former_member195698</dc:creator>
      <dc:date>2007-11-22T11:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: routine problem for VOFM</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070753#M727858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;its giving error - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors while transferring conditions: duplicates found&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Message no. VH806&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Diagnosis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    During the data transfer after successful pricing, the system recognized&lt;/P&gt;&lt;P&gt;    that document conditions with the same key exist for condition type&lt;/P&gt;&lt;P&gt;    ZFBP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System Response&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Transferral of the document conditions is canceled, in order to prevent&lt;/P&gt;&lt;P&gt;    incorrect system behavior or a cancellation of updates when you save. At&lt;/P&gt;&lt;P&gt;    the same time, the system set pricing of the item affected 000010 as&lt;/P&gt;&lt;P&gt;    containing errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    First find the cause of the problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1.  For a variant condition, is the system including a particularly      &lt;/P&gt;&lt;P&gt;     large number of characteristics for valuation?                                                                                &lt;/P&gt;&lt;P&gt;2.  Is a condition type being used as an additional condition?                                                                                &lt;/P&gt;&lt;P&gt;3.  In the pricing procedure, are there several condition types at the   &lt;/P&gt;&lt;P&gt;     same level number?                                                                                &lt;/P&gt;&lt;P&gt;The problem can only be solved removing the cause of the problem. If the &lt;/P&gt;&lt;P&gt; first cause applies, you should consider distributing the                &lt;/P&gt;&lt;P&gt; characteristics using several condition types. In the second case, you   &lt;/P&gt;&lt;P&gt; should check whether all conditions are required at the same time, or    &lt;/P&gt;&lt;P&gt; whether you can avoid their use altogether. In the third case, you will  &lt;/P&gt;&lt;P&gt; need to change the pricing procedure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2007 11:45:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/routine-problem-for-vofm/m-p/3070753#M727858</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-22T11:45:08Z</dc:date>
    </item>
  </channel>
</rss>

