<?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 DEBMAS Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debmas-issue/m-p/5947783#M1335678</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenario is from SAP to PI and then 3rd party system :IDoc to JDBC.&lt;/P&gt;&lt;P&gt;Now for triggering IDocs for DEBMAS , standard configuration settings of ALE is maintained in ECC. Through BD21 IDoc is getting triggered. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In BD21 there are 2 BADI and 1 user exit which is used for all master interfaces provided by SAP . For this interface all are standard and only ALE settings and configurations are done .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now scenario is : In PI ,  Receiver determination : condition is there : The E1KNB1M is a mandatory field in PI . IDocs which dont have E1KNB1M segment (BUKRS field missing) getting fail in PI and which have E1KNB1M segment has been successful from PI .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly let me know how to resolve this issue .&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Asha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Jul 2009 07:57:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-07-23T07:57:45Z</dc:date>
    <item>
      <title>DEBMAS Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debmas-issue/m-p/5947783#M1335678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenario is from SAP to PI and then 3rd party system :IDoc to JDBC.&lt;/P&gt;&lt;P&gt;Now for triggering IDocs for DEBMAS , standard configuration settings of ALE is maintained in ECC. Through BD21 IDoc is getting triggered. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In BD21 there are 2 BADI and 1 user exit which is used for all master interfaces provided by SAP . For this interface all are standard and only ALE settings and configurations are done .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now scenario is : In PI ,  Receiver determination : condition is there : The E1KNB1M is a mandatory field in PI . IDocs which dont have E1KNB1M segment (BUKRS field missing) getting fail in PI and which have E1KNB1M segment has been successful from PI .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly let me know how to resolve this issue .&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Asha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2009 07:57:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debmas-issue/m-p/5947783#M1335678</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-07-23T07:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: DEBMAS Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debmas-issue/m-p/5947784#M1335679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Extend the IDOC which do not have Bukrs field with E1KNB1M  segment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jul 2009 09:57:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debmas-issue/m-p/5947784#M1335679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-07-24T09:57:20Z</dc:date>
    </item>
  </channel>
</rss>

