<?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: BAPI_INCOMINGINVOICE_CREATE: Edit own conditions in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205258#M1376819</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;within the bapi BAPI_INCOMINGINVOICE_CREATE&lt;/P&gt;&lt;P&gt;in&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
 PERFORM frseg_fill                 TABLES    itemdata
                                               accountingdata
                                     USING     s_rbkpv-waers
                                     CHANGING  tab_frseg[]
                                               return[]
                                               f_subrc.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;there is:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
*----- planned delivery costs, set flag XEKBZ or XEKBE ---------------*
    IF ( s_itemdata-cond_type IS INITIAL
         AND s_itemdata-cond_st_no IS INITIAL
         AND s_itemdata-cond_count IS INITIAL ).
      s_frseg-xekbe = c_x.
    ELSE.
      s_frseg-xekbz = c_x.
      s_frseg-kschl = s_itemdata-cond_type.
      s_frseg-stunr = s_itemdata-cond_st_no.
      s_frseg-zaehk = s_itemdata-cond_count.
      CALL FUNCTION 'ME_READ_COND_INVOICE'
        EXPORTING
          i_ebeln       = s_frseg-ebeln
          i_ebelp       = s_frseg-ebelp
          i_lifnr       = f_lifnr_initial
        TABLES
          xek08bn_curr  = t_ek08bn_temp
        EXCEPTIONS
          error_message = 02.
      IF sy-subrc NE 0.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here the conditions seem to be filled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so maybe you´ll just have to fill in fields &lt;/P&gt;&lt;P&gt;COND_TYPE&lt;/P&gt;&lt;P&gt;COND_ST_NO&lt;/P&gt;&lt;P&gt;COND_COUNT&lt;/P&gt;&lt;P&gt;of table ITEMDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation of ITEMDATA says the following:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Posting purchase order items or planned delivery costs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. If the fields Condition type (COND_TYPE), Level number (COND_ST_NO) and Conditions counter (COND_COUNT) are blank, the system creates an invoice for a purchase order item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If the fields Level number (field COND_ST_NO) and Conditions counter (field COND_COUNT) or Condition type (field COND_TYPE) are filled, the system creates an invoice for a purchase order item with planned delivery costs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do not enter any data in the following fields, the system determines the data according to the priorities specified. If the system cannot determine any data, it returns appropriate return messages from the method call. These are listed in the return parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Pablo Casamayor on Sep 23, 2009 5:15 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Sep 2009 15:10:28 GMT</pubDate>
    <dc:creator>former_member182371</dc:creator>
    <dc:date>2009-09-23T15:10:28Z</dc:date>
    <item>
      <title>BAPI_INCOMINGINVOICE_CREATE: Edit own conditions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205257#M1376818</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Transaction MIRO(enter incoming invoice) lets you enter conditions for each line of the invoice. Each line has a "Edit Own Conditions" button which when pressed, branches to a conditions entry screen. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corrensponding BAPI does not seem to support this functionality. There are no table parameters on this BAPI to specify conditions for each line. Has anyone found a way around this one? &lt;/P&gt;&lt;P&gt;Mind you, MIRO is an "enjoy" transaction, so CALL TRANSACTIONS and BDCs are  out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Michael Dirndorfer on Sep 23, 2009 3:44 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2009 08:42:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205257#M1376818</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-23T08:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_INCOMINGINVOICE_CREATE: Edit own conditions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205258#M1376819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;within the bapi BAPI_INCOMINGINVOICE_CREATE&lt;/P&gt;&lt;P&gt;in&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
 PERFORM frseg_fill                 TABLES    itemdata
                                               accountingdata
                                     USING     s_rbkpv-waers
                                     CHANGING  tab_frseg[]
                                               return[]
                                               f_subrc.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;there is:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
*----- planned delivery costs, set flag XEKBZ or XEKBE ---------------*
    IF ( s_itemdata-cond_type IS INITIAL
         AND s_itemdata-cond_st_no IS INITIAL
         AND s_itemdata-cond_count IS INITIAL ).
      s_frseg-xekbe = c_x.
    ELSE.
      s_frseg-xekbz = c_x.
      s_frseg-kschl = s_itemdata-cond_type.
      s_frseg-stunr = s_itemdata-cond_st_no.
      s_frseg-zaehk = s_itemdata-cond_count.
      CALL FUNCTION 'ME_READ_COND_INVOICE'
        EXPORTING
          i_ebeln       = s_frseg-ebeln
          i_ebelp       = s_frseg-ebelp
          i_lifnr       = f_lifnr_initial
        TABLES
          xek08bn_curr  = t_ek08bn_temp
        EXCEPTIONS
          error_message = 02.
      IF sy-subrc NE 0.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here the conditions seem to be filled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so maybe you´ll just have to fill in fields &lt;/P&gt;&lt;P&gt;COND_TYPE&lt;/P&gt;&lt;P&gt;COND_ST_NO&lt;/P&gt;&lt;P&gt;COND_COUNT&lt;/P&gt;&lt;P&gt;of table ITEMDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation of ITEMDATA says the following:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Posting purchase order items or planned delivery costs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. If the fields Condition type (COND_TYPE), Level number (COND_ST_NO) and Conditions counter (COND_COUNT) are blank, the system creates an invoice for a purchase order item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If the fields Level number (field COND_ST_NO) and Conditions counter (field COND_COUNT) or Condition type (field COND_TYPE) are filled, the system creates an invoice for a purchase order item with planned delivery costs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do not enter any data in the following fields, the system determines the data according to the priorities specified. If the system cannot determine any data, it returns appropriate return messages from the method call. These are listed in the return parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Pablo Casamayor on Sep 23, 2009 5:15 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2009 15:10:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205258#M1376819</guid>
      <dc:creator>former_member182371</dc:creator>
      <dc:date>2009-09-23T15:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_INCOMINGINVOICE_CREATE: Edit own conditions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205259#M1376820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Michael,&lt;/P&gt;&lt;P&gt;I am facing the same scenario,Could you please tell me how you resolved this ..?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vivek &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 13:40:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-incominginvoice-create-edit-own-conditions/m-p/6205259#M1376820</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T13:40:57Z</dc:date>
    </item>
  </channel>
</rss>

