<?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: Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/fill-idoc-segment-e1idbw1-for-pexr2002-basic-type/m-p/8132002#M1619498</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;Basically the segment E1IDBW1 will always be filled via user exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you work with the IHC (In-House-Cash) application you have to fill&lt;/P&gt;&lt;P&gt;the E1IDBW1 segment as described in note 626577.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you don't work in an IHC environment the following conditions must&lt;/P&gt;&lt;P&gt;be fulfilled:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,&lt;/P&gt;&lt;P&gt;REGUH-DTWS1 - REGUH-DTWS4).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If this is fulfilled the payment data (REGUH, REGUP tables) will&lt;/P&gt;&lt;P&gt;be filled. The instruction keys will be moved to IDOC segment&lt;/P&gt;&lt;P&gt;E1IDKU3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction&lt;/P&gt;&lt;P&gt;keys from segment E1IDKU3 into E1IDBW1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also read note 496663, this note explains about user exit&lt;/P&gt;&lt;P&gt;EXIT_SAPLIEDP_002 to populate this field in the idoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you can check the note:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards,&lt;/P&gt;&lt;P&gt;Cristiano&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Aug 2013 18:41:59 GMT</pubDate>
    <dc:creator>former_member198032</dc:creator>
    <dc:date>2013-08-08T18:41:59Z</dc:date>
    <item>
      <title>Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fill-idoc-segment-e1idbw1-for-pexr2002-basic-type/m-p/8132001#M1619497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We send the IDOC for the Basic Type &lt;STRONG&gt;PEXR2002&lt;/STRONG&gt;, Message Type &lt;STRONG&gt;PAYEXT&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This IDOC doesn't fill the Segment &lt;STRONG&gt;E1IDBW1&lt;/STRONG&gt; (IDoc header - special instructions (INP) )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.&lt;/P&gt;&lt;P&gt;But doesn't have this functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's possible fill the segment &lt;STRONG&gt;E1IDBW1&lt;/STRONG&gt; in a user exit or any other enhacement at creation idoc moment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My idea is used the FM&lt;/P&gt;&lt;P&gt;  CALL FUNCTION &lt;STRONG&gt;'GET_SEGMENT_POS_FOR_INSERT'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;      I_BASIS_TYPE            = ch_edidc-idoctp&lt;/P&gt;&lt;P&gt;      I_EXT_TYPE              = ch_edidc-cimtyp&lt;/P&gt;&lt;P&gt;      I_SEGMENT_TYPE          = 'E1IDBW1'&lt;/P&gt;&lt;P&gt;    IMPORTING&lt;/P&gt;&lt;P&gt;      E_INDEX                 = li_tabix&lt;/P&gt;&lt;P&gt;    TABLES&lt;/P&gt;&lt;P&gt;      IT_EDIDD                = t_edidd&lt;/P&gt;&lt;P&gt;    EXCEPTIONS&lt;/P&gt;&lt;P&gt;      BASIS_TYPE_NOT_FOUND    = 1&lt;/P&gt;&lt;P&gt;      EXTENSION_NOT_FOUND     = 2&lt;/P&gt;&lt;P&gt;      EXTENSION_ERROR         = 3&lt;/P&gt;&lt;P&gt;      INVALID_IDOC_DEFINITION = 4&lt;/P&gt;&lt;P&gt;      IDOC_ERROR              = 5&lt;/P&gt;&lt;P&gt;      INVALID_SEGMENT_TYPE    = 6&lt;/P&gt;&lt;P&gt;      INVALID_START_INDEX     = 7&lt;/P&gt;&lt;P&gt;      NO_MORE_POSITION        = 8&lt;/P&gt;&lt;P&gt;      TOO_MANY_SEGMENTS       = 9&lt;/P&gt;&lt;P&gt;      OTHERS                  = 10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Fill 2 constants in this segment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have any other idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2011 12:50:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fill-idoc-segment-e1idbw1-for-pexr2002-basic-type/m-p/8132001#M1619497</guid>
      <dc:creator>Da_l</dc:creator>
      <dc:date>2011-09-01T12:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fill-idoc-segment-e1idbw1-for-pexr2002-basic-type/m-p/8132002#M1619498</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;Basically the segment E1IDBW1 will always be filled via user exit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you work with the IHC (In-House-Cash) application you have to fill&lt;/P&gt;&lt;P&gt;the E1IDBW1 segment as described in note 626577.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you don't work in an IHC environment the following conditions must&lt;/P&gt;&lt;P&gt;be fulfilled:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,&lt;/P&gt;&lt;P&gt;REGUH-DTWS1 - REGUH-DTWS4).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If this is fulfilled the payment data (REGUH, REGUP tables) will&lt;/P&gt;&lt;P&gt;be filled. The instruction keys will be moved to IDOC segment&lt;/P&gt;&lt;P&gt;E1IDKU3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction&lt;/P&gt;&lt;P&gt;keys from segment E1IDKU3 into E1IDBW1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also read note 496663, this note explains about user exit&lt;/P&gt;&lt;P&gt;EXIT_SAPLIEDP_002 to populate this field in the idoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you can check the note:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards,&lt;/P&gt;&lt;P&gt;Cristiano&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2013 18:41:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fill-idoc-segment-e1idbw1-for-pexr2002-basic-type/m-p/8132002#M1619498</guid>
      <dc:creator>former_member198032</dc:creator>
      <dc:date>2013-08-08T18:41:59Z</dc:date>
    </item>
  </channel>
</rss>

