<?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: Problem with BAPI (SD_SALESDOCUMENT_CHANGE) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198684#M1626012</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;Thanks for reply.&lt;/P&gt;&lt;P&gt;But, what is  "EXTENSIONIN" ? and how can I use it?&lt;/P&gt;&lt;P&gt;If I should modify FM"SD_SALESDOCUMENT_CHANGE", as it is not allowed in my project, I need aonther solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Aug 2011 02:33:04 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-08-17T02:33:04Z</dc:date>
    <item>
      <title>Problem with BAPI (SD_SALESDOCUMENT_CHANGE)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198682#M1626010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Experts!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've met problem about FM "SD_SALESDOCUMENT_CHANGE".&lt;/P&gt;&lt;P&gt;Situation as below;&lt;/P&gt;&lt;P&gt;1, create Sales Order(#1000 item1), with Purchase requisition(#2000 item1)&lt;/P&gt;&lt;P&gt;2, transfer Purchase requisition(#2000 item1) to Purchase Order(#3000 item1)&lt;/P&gt;&lt;P&gt;3, modify address for Ship-to Customer on Sales Order(#1000 item1) by FM above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From record of Sales Order, by this modification, schedule line at Sales Order(#1000) is once deleted, and then new schedule line is created.&lt;/P&gt;&lt;P&gt;At new schedule line, though Purchase requisition is same (#2000), its item is changed(item 2 is created.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I have two Purchase Requisition item, though I really need one! This is the problem I'm facing to!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My PGM exports data of schedule line, such as delivery date. quantity and so on, to this FM, except confirmed quantity and Purchase Requisition and its items.&lt;/P&gt;&lt;P&gt;I think this must cause this problem, but I have no idea what to deal with this, as this FM is normal, not add-on, so I can't add exporting item...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyone that has met same problem? and solve this one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 10:44:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198682#M1626010</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-16T10:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with BAPI (SD_SALESDOCUMENT_CHANGE)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198683#M1626011</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;There's the paramenter table EXTENSIONIN in order to manage fields not belonging to standard parameters&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 10:57:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198683#M1626011</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-16T10:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with BAPI (SD_SALESDOCUMENT_CHANGE)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198684#M1626012</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;Thanks for reply.&lt;/P&gt;&lt;P&gt;But, what is  "EXTENSIONIN" ? and how can I use it?&lt;/P&gt;&lt;P&gt;If I should modify FM"SD_SALESDOCUMENT_CHANGE", as it is not allowed in my project, I need aonther solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 02:33:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198684#M1626012</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-17T02:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with BAPI (SD_SALESDOCUMENT_CHANGE)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198685#M1626013</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;EXTENSIONIN is based on structure BAPIPAREX,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here you insert rhe structure name where the new field is and its value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to do is to enhance the structures in order to insert the field you need to manage&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example for scheduling data the reference structures for extra-fields are BAPE_VBEP and BAPE_VBEPX, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so you need to check these structure in order to verify if your fields is just included else you need to enhance them (by append structure)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The code to fill EXTENSIONIN will be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA: W_EXTENSIONIN TYPE BAPIPAREX.
DATA: T_EXTENSIONIN   TYPE TABLE OF BAPIPAREX.
DATA: W_BAPE_VBEP   TYPE BAPIPAREX.
DATA: W_BAPE_VBEPX TYPE BAPIPAREX.

CLEAR: W_BAPE_VBEP, W_BAPE_VBEPX. 
W_BAPE_VBEP-VBELN  = ............ 
W_BAPE_VBEP-POSNR = .............
W_BAPE_VBEP-ETENR  = ............

W_BAPE_VBEPX-VBELN  = W_BAPE_VBEP-VBELN.
W_BAPE_VBEPX-POSNR = W_BAPE_VBEP-POSNR.
W_BAPE_VBEPX-ETENR  = W_BAPE_VBEP-ETENR.


W_BAPE_VBEP-&amp;lt;field1&amp;gt;  = ...............
W_BAPE_VBEP-&amp;lt;field2&amp;gt;  = ...............
.........................................
W_BAPE_VBEP-&amp;lt;fieldn&amp;gt;  = ..............

W_BAPE_VBEPX-&amp;lt;field1&amp;gt;  = 'X'.
W_BAPE_VBEPX-&amp;lt;field2&amp;gt;  = 'X'.
.........................................
W_BAPE_VBEPX-&amp;lt;fieldn&amp;gt;  = 'X'.

CLEAR W_EXTENSIONIN. 
W_EXTENSIONIN-STRUCTURE = 'BAPE_VBEP'.
W_EXTENSIONIN+30                = W_BAPE_VBEP.
APPEND W_EXTENSIONIN TO T_EXTENSIONIN.

CLEAR W_EXTENSIONIN.
W_EXTENSIONIN-STRUCTURE = 'BAPE_VBEPX'.
W_EXTENSIONIN+30                = W_BAPE_VBEPX.
APPEND W_EXTENSIONIN TO T_EXTENSIONIN.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You also need to checl the structures VBEPKOM  and VBEPKOMX: if your extra-fields aren't here, you need to add them&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 03:00:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198685#M1626013</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-17T03:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with BAPI (SD_SALESDOCUMENT_CHANGE)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198686#M1626014</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;Thanks for your reply, but I'm still have problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I add  extensionin to CALL FUNCTION 'SD_SALESDOCUMENT_CHANGE', &lt;/P&gt;&lt;P&gt;but still I can't set purchase requirement item number in Sales Order's  schedule line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i use this FM, new item is created at Purchase Requirement and its number is set at Schedule line of Sales document.,,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well, I think I was setting another point as issue..&lt;/P&gt;&lt;P&gt;I want not to modify purchase requirement. That's the point!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anyone who can help me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: shizukya on Oct 23, 2011 10:04 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Oct 2011 03:52:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-bapi-sd-salesdocument-change/m-p/8198686#M1626014</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-10-18T03:52:05Z</dc:date>
    </item>
  </channel>
</rss>

