<?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 to create Purchse View for Article in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-to-create-purchse-view-for-article/m-p/7564146#M1564708</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hi,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I have created article using MM41 and maintained BASIC DATA and ADDITIONAL BASICDATA for it. I have to now maintain PURCHASE VIEW for that article.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am using FM WRF_MATERIAL_MAINTAINDATA_RT to create purchase view.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am passing data to two structure  INFORECORD_GENERAL STRUCTURE  BAPIEINA&lt;/P&gt;&lt;P&gt;&amp;gt;                                                          INFORECORD_PURCHORG STRUCTURE  WRFBAPIEINE&lt;/P&gt;&lt;P&gt;&amp;gt; that holds purchase view data.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; BAPI returns telling article is changed. but if i go check in MM43 it is not changed.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; BAPI works fine if i try to modify any data except for the above.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Can any one suggest me how to tackle this or is there any other way to create new purchse view for existing article.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Vanitha P&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here a simple example code for upload Material data:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;*&amp;amp;---------------------------------------------------------------------*
*&amp;amp;      Form  call_bapi
*&amp;amp;---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM call_bapi USING is_head  TYPE bapimathead
                     is_mara  TYPE bapi_mara
                     is_marax TYPE bapi_marax
                     is_marc  TYPE bapi_marc
                     is_marcx TYPE bapi_marcx
                     is_mbew  TYPE bapi_mbew
                     is_mbewx TYPE bapi_mbewx
                     is_mvke  TYPE bapi_mvke
                     is_mvkex TYPE bapi_mvkex
                     is_mlan  type bapi_mlan.

  Data: lt_mlan type table of bapi_mlan.
  Append is_mlan to lt_mlan.

  CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
      headdata                   = ls_head
      clientdata                 = ls_mara
      clientdatax                = ls_marax
      plantdata                  = ls_marc
      plantdatax                 = ls_marcx
*   FORECASTPARAMETERS         =
*   FORECASTPARAMETERSX        =
*   PLANNINGDATA               =
*   PLANNINGDATAX              =
*   STORAGELOCATIONDATA        =
*   STORAGELOCATIONDATAX       =
      valuationdata              = ls_mbew
      valuationdatax             = ls_mbewx
*   WAREHOUSENUMBERDATA        =
*   WAREHOUSENUMBERDATAX       =
     salesdata                  = is_mvke
     salesdatax                 = is_mvkex
*   STORAGETYPEDATA            =
*   STORAGETYPEDATAX           =
*   FLAG_ONLINE                = ' '
*   FLAG_CAD_CALL              = ' '
*   NO_DEQUEUE                 = ' '
*   NO_ROLLBACK_WORK           = ' '
    IMPORTING
      return                     = gs_return
    TABLES
      materialdescription        = gt_makt
*      unitsofmeasure             = gt_uom
*      unitsofmeasurex            = gt_uomx
      internationalartnos        = gt_mean
*   MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         = lt_mlan
*   RETURNMESSAGES             =
*   PRTDATA                    =
*   PRTDATAX                   =
*   EXTENSIONIN                =
*   EXTENSIONINX               =
            .


*  READ TABLE gt_return INTO gs_return WITH KEY type = gc_return_s.
*  IF sy-subrc = 0.
  IF gs_return-type EQ gc_return_s.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*     EXPORTING
*       WAIT          =
*     IMPORTING
*       RETURN        =
              .
  ELSE.
    WRITE: /.
    WRITE: ls_mara-old_mat_no, gs_return-type,
              '   ', gs_return-message(50).
  ENDIF.

  CLEAR gs_return.

ENDFORM.                    "call_bapi&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Jan 2011 11:17:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-01-11T11:17:01Z</dc:date>
    <item>
      <title>BAPI to create Purchse View for Article</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-to-create-purchse-view-for-article/m-p/7564145#M1564707</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;I have created article using MM41 and maintained BASIC DATA and ADDITIONAL BASICDATA for it. I have to now maintain PURCHASE VIEW for that article.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using FM WRF_MATERIAL_MAINTAINDATA_RT to create purchase view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am passing data to two structure  INFORECORD_GENERAL STRUCTURE  BAPIEINA&lt;/P&gt;&lt;P&gt;                                                         INFORECORD_PURCHORG STRUCTURE  WRFBAPIEINE&lt;/P&gt;&lt;P&gt;that holds purchase view data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI returns telling article is changed. but if i go check in MM43 it is not changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI works fine if i try to modify any data except for the above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can any one suggest me how to tackle this or is there any other way to create new purchse view for existing article.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vanitha P&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jan 2011 10:57:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-to-create-purchse-view-for-article/m-p/7564145#M1564707</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-11T10:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI to create Purchse View for Article</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-to-create-purchse-view-for-article/m-p/7564146#M1564708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hi,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I have created article using MM41 and maintained BASIC DATA and ADDITIONAL BASICDATA for it. I have to now maintain PURCHASE VIEW for that article.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am using FM WRF_MATERIAL_MAINTAINDATA_RT to create purchase view.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am passing data to two structure  INFORECORD_GENERAL STRUCTURE  BAPIEINA&lt;/P&gt;&lt;P&gt;&amp;gt;                                                          INFORECORD_PURCHORG STRUCTURE  WRFBAPIEINE&lt;/P&gt;&lt;P&gt;&amp;gt; that holds purchase view data.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; BAPI returns telling article is changed. but if i go check in MM43 it is not changed.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; BAPI works fine if i try to modify any data except for the above.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Can any one suggest me how to tackle this or is there any other way to create new purchse view for existing article.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Vanitha P&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here a simple example code for upload Material data:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;*&amp;amp;---------------------------------------------------------------------*
*&amp;amp;      Form  call_bapi
*&amp;amp;---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM call_bapi USING is_head  TYPE bapimathead
                     is_mara  TYPE bapi_mara
                     is_marax TYPE bapi_marax
                     is_marc  TYPE bapi_marc
                     is_marcx TYPE bapi_marcx
                     is_mbew  TYPE bapi_mbew
                     is_mbewx TYPE bapi_mbewx
                     is_mvke  TYPE bapi_mvke
                     is_mvkex TYPE bapi_mvkex
                     is_mlan  type bapi_mlan.

  Data: lt_mlan type table of bapi_mlan.
  Append is_mlan to lt_mlan.

  CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
      headdata                   = ls_head
      clientdata                 = ls_mara
      clientdatax                = ls_marax
      plantdata                  = ls_marc
      plantdatax                 = ls_marcx
*   FORECASTPARAMETERS         =
*   FORECASTPARAMETERSX        =
*   PLANNINGDATA               =
*   PLANNINGDATAX              =
*   STORAGELOCATIONDATA        =
*   STORAGELOCATIONDATAX       =
      valuationdata              = ls_mbew
      valuationdatax             = ls_mbewx
*   WAREHOUSENUMBERDATA        =
*   WAREHOUSENUMBERDATAX       =
     salesdata                  = is_mvke
     salesdatax                 = is_mvkex
*   STORAGETYPEDATA            =
*   STORAGETYPEDATAX           =
*   FLAG_ONLINE                = ' '
*   FLAG_CAD_CALL              = ' '
*   NO_DEQUEUE                 = ' '
*   NO_ROLLBACK_WORK           = ' '
    IMPORTING
      return                     = gs_return
    TABLES
      materialdescription        = gt_makt
*      unitsofmeasure             = gt_uom
*      unitsofmeasurex            = gt_uomx
      internationalartnos        = gt_mean
*   MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         = lt_mlan
*   RETURNMESSAGES             =
*   PRTDATA                    =
*   PRTDATAX                   =
*   EXTENSIONIN                =
*   EXTENSIONINX               =
            .


*  READ TABLE gt_return INTO gs_return WITH KEY type = gc_return_s.
*  IF sy-subrc = 0.
  IF gs_return-type EQ gc_return_s.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*     EXPORTING
*       WAIT          =
*     IMPORTING
*       RETURN        =
              .
  ELSE.
    WRITE: /.
    WRITE: ls_mara-old_mat_no, gs_return-type,
              '   ', gs_return-message(50).
  ENDIF.

  CLEAR gs_return.

ENDFORM.                    "call_bapi&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jan 2011 11:17:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-to-create-purchse-view-for-article/m-p/7564146#M1564708</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-01-11T11:17:01Z</dc:date>
    </item>
  </channel>
</rss>

