<?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: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121510#M985324</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;function module is called form standard program WS_MONITOR_OUTB_DEL_GDS.&lt;/P&gt;&lt;P&gt;don't know the reason for dump&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Jul 2008 13:12:57 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-02T13:12:57Z</dc:date>
    <item>
      <title>Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121506#M985320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;while doing post goods issuse for a delivery causing a following dump&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The call to the function module "CEI0_COMPARE_CONFIGURATIONS" is incorrect:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The function module interface allows you to specify only fields&lt;/P&gt;&lt;P&gt;of a particular type under "IV_EXCL_IND". The field "'#'" specified here&lt;/P&gt;&lt;P&gt;has a different field type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"IV_EXCL_IND" is of type CHAR1 and default is value 2.&lt;/P&gt;&lt;P&gt;in debugging fields is empty, that must be a reason for dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please help me out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;rajyalaxmi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:07:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121506#M985320</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121507#M985321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you sure the field is empty or does is contain a hexadecimal value which looks like "empty" when displaying in character mode?&lt;/P&gt;&lt;P&gt;&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;John.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:09:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121507#M985321</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:09:56Z</dc:date>
    </item>
    <item>
      <title>Re: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121508#M985322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajyalakshmi,&lt;/P&gt;&lt;P&gt;   The balnk might be a TAB character and not a space.&lt;/P&gt;&lt;P&gt;hance the dump.&lt;/P&gt;&lt;P&gt;Check if you have any TABs in your data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:10:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121508#M985322</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121509#M985323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rajyalaxmi,&lt;/P&gt;&lt;P&gt;Always remember,as a rule of thumb that whenever you call a FM, make sure that the parameters you pass to the FM are of the same data type as they are declared inside the FM. This will avoid CONFLICT DUMPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign points, if it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;Raghu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:10:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121509#M985323</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121510#M985324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;function module is called form standard program WS_MONITOR_OUTB_DEL_GDS.&lt;/P&gt;&lt;P&gt;don't know the reason for dump&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:12:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121510#M985324</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121511#M985325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please help me out&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;function module require IV_EXCL_IND field as mandatory and in defination we have default value as 2, but while calling this function module this field is commented.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2008 13:19:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module-cei0-compare-configurations/m-p/4121511#M985325</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-02T13:19:14Z</dc:date>
    </item>
  </channel>
</rss>

