<?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: BAPI for VL06G in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236775#M481802</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have u seen this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;FU BAPI_OUTB_DELIVERY_CONFIRM_DEC&amp;lt;/b&amp;gt;____________________________________________________&lt;/P&gt;&lt;P&gt;Short Text&lt;/P&gt;&lt;P&gt;BAPI for Outbound Delivery Verification from a Decentralized System&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;You can use this method to report back outbound deliveries from a WM system to an enterprise resource planning (ERP) system. Essentially, the report consists of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header data from the delivery,&lt;/P&gt;&lt;P&gt;that must always be reported&lt;/P&gt;&lt;P&gt;Delivery items,&lt;/P&gt;&lt;P&gt;whereby you only need to report those items that have changed. Non-reported delivery item data is confirmed without changes. &lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;Two examples of how the BAPI is used are shown below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Reporting back the delivery without (quantity) changes of the item data.&lt;/P&gt;&lt;P&gt;2. Reporting back the delivery with changes of the item data.&lt;/P&gt;&lt;P&gt;The following lists show a selection of example fields for the reported segment types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The item data of the delivery is reported back unchanged.&lt;/P&gt;&lt;P&gt;DELIVERY - Document number of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_DATA - Header data of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_CONTROL - Header control data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field POST_GI_FLG - Indicator: Post Automatic Goods Movement&lt;/P&gt;&lt;P&gt;2. The items of the delivery are reported back changed.&lt;/P&gt;&lt;P&gt;DELIVERY - Document number of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_DATA - Header data of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_CONTROL - Control data header level&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field POST_GI_FLG - Indicator: Post Automatic Goods Movement&lt;/P&gt;&lt;P&gt;ITEM_DATA - Item data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field DELIV_ITEM - Delivery item&lt;/P&gt;&lt;P&gt;Field DLV_QTY - Delivery quantity in sales unit of measure&lt;/P&gt;&lt;P&gt;or alternatively&lt;/P&gt;&lt;P&gt;Field DLV_QTY_IMUNIT - Actual delivery quantity in stockkeeping unit&lt;/P&gt;&lt;P&gt;ITEM_CONTROL - Item control data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field DELIV_ITEM - Delivery item&lt;/P&gt;&lt;P&gt;Field CHG_DELQTY - Change delivery quantity&lt;/P&gt;&lt;P&gt;Material number, plant, quantities in floating values, volumes, weights and their units are copied from the delivery, if not specified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error messages are recorded in BAPI return parameter RETURN with the following message types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E (ERROR)&lt;/P&gt;&lt;P&gt;W (WARNING)&lt;/P&gt;&lt;P&gt;I (INFORMATION)&lt;/P&gt;&lt;P&gt;Further Information&lt;/P&gt;&lt;P&gt;If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for packaging materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID). The fields can be found in the HANDLING_UNIT_ITEM segment. The handling unit must be copied into the HDL_UNIT_EXID_INTO field when the system reports back to packing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If batch splits that were created in the ERP are reported back, the&lt;/P&gt;&lt;P&gt;hierarchy fields HIERARITEM and USEHIERITM must not contain information. If you created split items in the Warehouse Management System and reported back, these two hierarchy fields must contain information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a non-SAP system was used as a decentralized Warehouse Management System, the IDoc structure must be defined carefully when the return message is constructed. It is very important that the segment sequence must not be altered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;HEADER_DATA&lt;/P&gt;&lt;P&gt;HEADER_CONTROL&lt;/P&gt;&lt;P&gt;DELIVERY&lt;/P&gt;&lt;P&gt;TECHN_CONTROL&lt;/P&gt;&lt;P&gt;HEADER_PARTNER&lt;/P&gt;&lt;P&gt;HEADER_PARTNER_ADDR&lt;/P&gt;&lt;P&gt;HEADER_DEADLINES&lt;/P&gt;&lt;P&gt;ITEM_DATA&lt;/P&gt;&lt;P&gt;ITEM_CONTROL&lt;/P&gt;&lt;P&gt;ITEM_SERIAL_NO&lt;/P&gt;&lt;P&gt;SUPPLIER_CONS_DATA&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_HEADER&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_ITEM&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_SERNO&lt;/P&gt;&lt;P&gt;EXTENSION1&lt;/P&gt;&lt;P&gt;EXTENSION2&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;TOKENREFERENCE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exceptions&lt;/P&gt;&lt;P&gt;Function Group&lt;/P&gt;&lt;P&gt;V50I&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Prabhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 May 2007 05:52:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-07T05:52:32Z</dc:date>
    <item>
      <title>BAPI for VL06G</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236774#M481801</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; Can i know the BAPI used for VL06G.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rajesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 May 2007 05:49:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236774#M481801</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-07T05:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI for VL06G</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236775#M481802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have u seen this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;FU BAPI_OUTB_DELIVERY_CONFIRM_DEC&amp;lt;/b&amp;gt;____________________________________________________&lt;/P&gt;&lt;P&gt;Short Text&lt;/P&gt;&lt;P&gt;BAPI for Outbound Delivery Verification from a Decentralized System&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;You can use this method to report back outbound deliveries from a WM system to an enterprise resource planning (ERP) system. Essentially, the report consists of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header data from the delivery,&lt;/P&gt;&lt;P&gt;that must always be reported&lt;/P&gt;&lt;P&gt;Delivery items,&lt;/P&gt;&lt;P&gt;whereby you only need to report those items that have changed. Non-reported delivery item data is confirmed without changes. &lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;Two examples of how the BAPI is used are shown below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Reporting back the delivery without (quantity) changes of the item data.&lt;/P&gt;&lt;P&gt;2. Reporting back the delivery with changes of the item data.&lt;/P&gt;&lt;P&gt;The following lists show a selection of example fields for the reported segment types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The item data of the delivery is reported back unchanged.&lt;/P&gt;&lt;P&gt;DELIVERY - Document number of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_DATA - Header data of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_CONTROL - Header control data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field POST_GI_FLG - Indicator: Post Automatic Goods Movement&lt;/P&gt;&lt;P&gt;2. The items of the delivery are reported back changed.&lt;/P&gt;&lt;P&gt;DELIVERY - Document number of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_DATA - Header data of outbound delivery&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;HEADER_CONTROL - Control data header level&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field POST_GI_FLG - Indicator: Post Automatic Goods Movement&lt;/P&gt;&lt;P&gt;ITEM_DATA - Item data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field DELIV_ITEM - Delivery item&lt;/P&gt;&lt;P&gt;Field DLV_QTY - Delivery quantity in sales unit of measure&lt;/P&gt;&lt;P&gt;or alternatively&lt;/P&gt;&lt;P&gt;Field DLV_QTY_IMUNIT - Actual delivery quantity in stockkeeping unit&lt;/P&gt;&lt;P&gt;ITEM_CONTROL - Item control data&lt;/P&gt;&lt;P&gt;Field DELIV_NUMB - Delivery number&lt;/P&gt;&lt;P&gt;Field DELIV_ITEM - Delivery item&lt;/P&gt;&lt;P&gt;Field CHG_DELQTY - Change delivery quantity&lt;/P&gt;&lt;P&gt;Material number, plant, quantities in floating values, volumes, weights and their units are copied from the delivery, if not specified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error messages are recorded in BAPI return parameter RETURN with the following message types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E (ERROR)&lt;/P&gt;&lt;P&gt;W (WARNING)&lt;/P&gt;&lt;P&gt;I (INFORMATION)&lt;/P&gt;&lt;P&gt;Further Information&lt;/P&gt;&lt;P&gt;If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for packaging materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID). The fields can be found in the HANDLING_UNIT_ITEM segment. The handling unit must be copied into the HDL_UNIT_EXID_INTO field when the system reports back to packing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If batch splits that were created in the ERP are reported back, the&lt;/P&gt;&lt;P&gt;hierarchy fields HIERARITEM and USEHIERITM must not contain information. If you created split items in the Warehouse Management System and reported back, these two hierarchy fields must contain information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a non-SAP system was used as a decentralized Warehouse Management System, the IDoc structure must be defined carefully when the return message is constructed. It is very important that the segment sequence must not be altered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;HEADER_DATA&lt;/P&gt;&lt;P&gt;HEADER_CONTROL&lt;/P&gt;&lt;P&gt;DELIVERY&lt;/P&gt;&lt;P&gt;TECHN_CONTROL&lt;/P&gt;&lt;P&gt;HEADER_PARTNER&lt;/P&gt;&lt;P&gt;HEADER_PARTNER_ADDR&lt;/P&gt;&lt;P&gt;HEADER_DEADLINES&lt;/P&gt;&lt;P&gt;ITEM_DATA&lt;/P&gt;&lt;P&gt;ITEM_CONTROL&lt;/P&gt;&lt;P&gt;ITEM_SERIAL_NO&lt;/P&gt;&lt;P&gt;SUPPLIER_CONS_DATA&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_HEADER&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_ITEM&lt;/P&gt;&lt;P&gt;HANDLING_UNIT_SERNO&lt;/P&gt;&lt;P&gt;EXTENSION1&lt;/P&gt;&lt;P&gt;EXTENSION2&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;TOKENREFERENCE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exceptions&lt;/P&gt;&lt;P&gt;Function Group&lt;/P&gt;&lt;P&gt;V50I&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Prabhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 May 2007 05:52:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236775#M481802</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-07T05:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI for VL06G</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236776#M481803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Check the Bapi&lt;/P&gt;&lt;P&gt;BAPI_OUTB_DELIVERY_CHANGE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 May 2007 05:55:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236776#M481803</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-07T05:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI for VL06G</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236777#M481804</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;Try these&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI_IBDLV_CREATE_FROM_OBDLV&lt;/P&gt;&lt;P&gt;BAPI_INB_DELIVERY_SAVEREPLICA&lt;/P&gt;&lt;P&gt;BAPI_OUTB_DELIVERY_SAVEREPLICA&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 May 2007 05:56:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236777#M481804</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-07T05:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI for VL06G</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236778#M481805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks to all,&lt;/P&gt;&lt;P&gt;Is the BAPI's above are used for doing PGI.&lt;/P&gt;&lt;P&gt;Rajesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 May 2007 06:02:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-for-vl06g/m-p/2236778#M481805</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-07T06:02:40Z</dc:date>
    </item>
  </channel>
</rss>

