<?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: Logic needed for FI BDC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350409#M1398785</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;You have to first capture the meesages(error + success) in one internal table&lt;/P&gt;&lt;P&gt;in the call transaction statement itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : it_messtab type standard table of bdcmsgcoll.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*CALL TRANSACTION F-53 USING it_bdcdata&lt;/P&gt;&lt;P&gt;                                            MESSAGES INTO it_messtab*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then after getting all the messages in internal table it_messtab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can use function Module &lt;STRONG&gt;Format_Message&lt;/STRONG&gt; , in one of its&lt;/P&gt;&lt;P&gt;parameters the document number which is getting generated &lt;/P&gt;&lt;P&gt;will get captured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mansi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Nov 2009 12:08:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-11-25T12:08:28Z</dc:date>
    <item>
      <title>Logic needed for FI BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350407#M1398783</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;I ned to write Bdc for the FI transaction f-53. In that BDC various entry is uploaded in trnsaction thr flat file . After Upload Document No is generted and it should stored in the excel file and at the last col of th flat file .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to do this . I have no clue for thsi . How to capture valus of document no which is genrated ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2009 10:44:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350407#M1398783</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-25T10:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: Logic needed for FI BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350408#M1398784</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kiro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA : ist_msgtab          type standard table of bdcmsgcoll.

CALL TRANSACTION c_co02 USING ist_bdcdata
                                OPTIONS FROM opt
                                MESSAGES INTO ist_msgtab.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the Messages are caught into the table ist_msgtab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now use FORM_MESSAGE function Module to get the Created Document number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also check this table in Debug mode and can be assured of the Created Document number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheerz&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2009 10:50:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350408#M1398784</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-25T10:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Logic needed for FI BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350409#M1398785</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;You have to first capture the meesages(error + success) in one internal table&lt;/P&gt;&lt;P&gt;in the call transaction statement itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : it_messtab type standard table of bdcmsgcoll.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*CALL TRANSACTION F-53 USING it_bdcdata&lt;/P&gt;&lt;P&gt;                                            MESSAGES INTO it_messtab*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then after getting all the messages in internal table it_messtab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can use function Module &lt;STRONG&gt;Format_Message&lt;/STRONG&gt; , in one of its&lt;/P&gt;&lt;P&gt;parameters the document number which is getting generated &lt;/P&gt;&lt;P&gt;will get captured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mansi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2009 12:08:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350409#M1398785</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-25T12:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: Logic needed for FI BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350410#M1398786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can also use parameter ID 'BLN' if you are calling individual transactions. Some variants of the FI transactions will use different success messages, so if you use a common routine for the call, you'll definitely want to use this approach instead of hardcoding message numbers and fields to read.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before the call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
SET PARAMETER ID 'BLN' FIELD SPACE.
CLEAR GV_BELNR.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After the call, insert the proper error handling and for successful calls:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
GET PARAMETER ID 'BLN' FIELD GV_BELNR.  " GV_BELNR defined as type BELNR_D
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2009 14:56:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-needed-for-fi-bdc/m-p/6350410#M1398786</guid>
      <dc:creator>brad_bohn</dc:creator>
      <dc:date>2009-11-25T14:56:49Z</dc:date>
    </item>
  </channel>
</rss>

