<?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 problem in T-code FBBCX in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-t-code-fbbcx/m-p/7607269#M1568931</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In T-code FBBCX, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After save, BELNRs are displayed with popup screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But when in BDC mode, popup screen is not displayed and&lt;/P&gt;&lt;P&gt;then I can't get result(ie. BELNRs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any solution to get BELNRs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for reading.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Jan 2011 11:46:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-01-24T11:46:07Z</dc:date>
    <item>
      <title>problem in T-code FBBCX</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-t-code-fbbcx/m-p/7607269#M1568931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In T-code FBBCX, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After save, BELNRs are displayed with popup screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But when in BDC mode, popup screen is not displayed and&lt;/P&gt;&lt;P&gt;then I can't get result(ie. BELNRs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any solution to get BELNRs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for reading.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jan 2011 11:46:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-t-code-fbbcx/m-p/7607269#M1568931</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-24T11:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: problem in T-code FBBCX</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-t-code-fbbcx/m-p/7607270#M1568932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in BDC, collect your messages into a table....read the table for the new document number....standard BDC processing approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;data: bdc_msg     TYPE TABLE OF bdcmsgcoll.

 CALL TRANSACTION transact
     USING bdc_tab
     OPTIONS FROM bdc_opts
     MESSAGES INTO bdc_msg.

loop at bdc_msg into ls_msg.
   .....check your table content for new document number
endloop.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in rare instances, data might not be written to BDC_MSG, so grab sy-uzeit into variable....to get doc read your document header table for SY-UNAME (user), date = sy-datum.... time = &amp;gt;= minute or two before your sy-uzeit....also check for values that were in your input....last doc created is LIKELY (not 100% fool-proof) to be the doc your BDC created.  In some cases, I've obtained list of all relevant docs with a BAPI GET, stored that, then after BDC/BAPI update, get the docs again into another internal table....the doc in the "after" table that doesn't exist in the "before" table is the doc you just created (again, the caveat....may not be 100% reliable)... but try via BDC_MSG or BAPI return table first.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jan 2011 20:17:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-t-code-fbbcx/m-p/7607270#M1568932</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-24T20:17:04Z</dc:date>
    </item>
  </channel>
</rss>

