<?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 ISU_S_PROFHEAD_CREATE - ESOURCE issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/isu-s-profhead-create-esource-issue/m-p/10257056#M1829846</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;did anyone ever get a "DUPREC on ESOURCE table" short dump while using the ISU_S_PROFHEAD_CREATE function module?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESOURCE (Source of Object) is a table with the only one field: SOURCE (NUMC18).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A weird thing is that the above mentioned FM and its wrapper code had been working fine for weeks, but now it is failing due to a duplicate entry in ESOURCE table, whose key is provided by some standard code logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the weirdest thing of all, is that if I test twice the FM directly in SE37 with the same input parameters, it MAY fail at the first time and succeed at the second, and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hint is highly appreciated...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Apr 2014 13:18:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-04-14T13:18:07Z</dc:date>
    <item>
      <title>ISU_S_PROFHEAD_CREATE - ESOURCE issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/isu-s-profhead-create-esource-issue/m-p/10257056#M1829846</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;did anyone ever get a "DUPREC on ESOURCE table" short dump while using the ISU_S_PROFHEAD_CREATE function module?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESOURCE (Source of Object) is a table with the only one field: SOURCE (NUMC18).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A weird thing is that the above mentioned FM and its wrapper code had been working fine for weeks, but now it is failing due to a duplicate entry in ESOURCE table, whose key is provided by some standard code logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the weirdest thing of all, is that if I test twice the FM directly in SE37 with the same input parameters, it MAY fail at the first time and succeed at the second, and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hint is highly appreciated...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Apr 2014 13:18:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/isu-s-profhead-create-esource-issue/m-p/10257056#M1829846</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-04-14T13:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISU_S_PROFHEAD_CREATE - ESOURCE issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/isu-s-profhead-create-esource-issue/m-p/10257057#M1829847</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fixed, the issue was in the Number Range ISU_EDM_SC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are multiple number ranges defined for the above object, and the standard code was dynamically retrieving which one to use through a very weird logic in the common ISU_NUMBER_GET function module.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Apr 2014 13:38:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/isu-s-profhead-create-esource-issue/m-p/10257057#M1829847</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-04-14T13:38:46Z</dc:date>
    </item>
  </channel>
</rss>

