<?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>Question Re: Outbound Delivery - Repeat Output Type in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/outbound-delivery-repeat-output-type/qaa-p/502411#M93751</link>
    <description>&lt;P&gt;Yes,this is possible without any abap coding.You need to maintain appropriate output type for delivery change.Else you may continue to use same output type(for both create/change-though not advisable).&lt;/P&gt;
  &lt;P&gt;You need to maintain partner profile with change message code and process code,output message determination.&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Avik&lt;/P&gt;</description>
    <pubDate>Tue, 01 Aug 2017 07:01:13 GMT</pubDate>
    <dc:creator>former_member365886</dc:creator>
    <dc:date>2017-08-01T07:01:13Z</dc:date>
    <item>
      <title>Outbound Delivery - Repeat Output Type</title>
      <link>https://community.sap.com/t5/technology-q-a/outbound-delivery-repeat-output-type/qaq-p/502410</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
  &lt;P&gt;We have an output type (IDOC) that is configured to trigger after a successful PGI is completed. This is working fine. In some instances we may need to update a field at the header level and save the delivery again using BAPI though a report. When this field is updated we need to re-trigger the output type (IDOC) again which will automatically pick up newly updated value. We are using DESADV Message Type and the field is BOLNR. All these are already there in the IDOC segments so no customization required.&lt;/P&gt;
  &lt;P&gt;Need to understand if there are any ways to achieve this using configuration instead of ABAP programming to either trigger the output again or generate a new IDOC. &lt;/P&gt;
  &lt;P&gt;Your insights are appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2017 04:18:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/outbound-delivery-repeat-output-type/qaq-p/502410</guid>
      <dc:creator>former_member327092</dc:creator>
      <dc:date>2017-08-01T04:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: Outbound Delivery - Repeat Output Type</title>
      <link>https://community.sap.com/t5/technology-q-a/outbound-delivery-repeat-output-type/qaa-p/502411#M93751</link>
      <description>&lt;P&gt;Yes,this is possible without any abap coding.You need to maintain appropriate output type for delivery change.Else you may continue to use same output type(for both create/change-though not advisable).&lt;/P&gt;
  &lt;P&gt;You need to maintain partner profile with change message code and process code,output message determination.&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Avik&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2017 07:01:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/outbound-delivery-repeat-output-type/qaa-p/502411#M93751</guid>
      <dc:creator>former_member365886</dc:creator>
      <dc:date>2017-08-01T07:01:13Z</dc:date>
    </item>
  </channel>
</rss>

