<?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 Using BAPI_REQUISITION_CREATE to maintain VEND_MAT_LONG in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-bapi-requisition-create-to-maintain-vend-mat-long/m-p/6458231#M1415134</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After upgrading to ECC 6.0 , we are no longer able to maintain the &lt;STRONG&gt;VEND_MAT_LONG&lt;/STRONG&gt; field of the purchare requisition using BAPI_REQUISITION_CREATE. We had applied note 455876 when we had 4.6c, but since the upgrade the VEND_MAT_LONG field doesn't get updated. It seems that the upgrade backed out some of the changes implemented by the note. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the table structures in BAPI_REQUISITION_CHANGE don't show VEND_MAT_LONG only VEND_MAT. How can we maintain IDNLF ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your suggestions .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Dec 2009 15:49:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-12-23T15:49:48Z</dc:date>
    <item>
      <title>Using BAPI_REQUISITION_CREATE to maintain VEND_MAT_LONG</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-bapi-requisition-create-to-maintain-vend-mat-long/m-p/6458231#M1415134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After upgrading to ECC 6.0 , we are no longer able to maintain the &lt;STRONG&gt;VEND_MAT_LONG&lt;/STRONG&gt; field of the purchare requisition using BAPI_REQUISITION_CREATE. We had applied note 455876 when we had 4.6c, but since the upgrade the VEND_MAT_LONG field doesn't get updated. It seems that the upgrade backed out some of the changes implemented by the note. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the table structures in BAPI_REQUISITION_CHANGE don't show VEND_MAT_LONG only VEND_MAT. How can we maintain IDNLF ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your suggestions .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Dec 2009 15:49:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-bapi-requisition-create-to-maintain-vend-mat-long/m-p/6458231#M1415134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-23T15:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: Using BAPI_REQUISITION_CREATE to maintain VEND_MAT_LONG</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-bapi-requisition-create-to-maintain-vend-mat-long/m-p/6458232#M1415135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Was this ever resolved? If so, how?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are in the process of upgrading to EhP4 on ECC 6.  All of the notes have been applied but the vendor catalog number is still truncated after 22 characters when we transfer the cart over  to the backend.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are on SRM 4.0.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 May 2010 19:22:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-bapi-requisition-create-to-maintain-vend-mat-long/m-p/6458232#M1415135</guid>
      <dc:creator>former_member114630</dc:creator>
      <dc:date>2010-05-19T19:22:16Z</dc:date>
    </item>
  </channel>
</rss>

