<?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 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355132#M804983</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;U have to poplate the structures like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HEADDATA&lt;/P&gt;&lt;P&gt;CLIENTDATA&lt;/P&gt;&lt;P&gt;CLIENTDATAX&lt;/P&gt;&lt;P&gt;PLANTDATA&lt;/P&gt;&lt;P&gt;PLANTDATAX&lt;/P&gt;&lt;P&gt;SALESDATA&lt;/P&gt;&lt;P&gt;SALESDATAX&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Documantataion&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;You use this method to create new material master data or to change existing material master data. The data on a material can be transferred for each call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When creating material master data, you must transfer the material number, the material type, and the industry sector to the method. You must also enter a material description and its language.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When changing material master data, you need enter only the material number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the header data, you must select at least one view for which data is to be created. Depending on the view selected, you must maintain other required parameters. If you do not enter values for all of the required parameters, the method is ended with an error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corresponding fields in the tables (such as CLIENTDATA) must first be supplied with data by the calling program. An indicator must also be set for each of these fields so that the data is written to the database by the method. This requires the calling program to supply the corresponding field with the indicator in a checkbox table (for example, CLIENTDATAX). Checkbox tables exist for tables that do not contain any language-dependent texts (MAKT, MLTX), International Article Numbers (MEAN), or tax classifications (MLAN). Several data records for a material can be created in these tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a structure contains fields for units of measurement (such as structure CLIENTDATA, field BASE_UOM), language indicators (such as structure MATERIALDESCRIPTION, field LANGU), or country indicators (such as structure TAXCLASSIFICATIONS, field DEPCOUNTRY), there is always a field of the same name with the ending _ISO. This makes it possible to transfer either the internally used SAP code or a standardized ISO code for the units of measurement, language indicators, or country indicators. ISO codes are converted to an SAP code internally for further processing. The ISO code is used only if the SAP code is not transferred. If you use ISO codes, there must be a unique assignment of the ISO code to the SAP code in the following activities in Customizing for Global Parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check Units of Measurement&lt;/P&gt;&lt;P&gt;Define Countries&lt;/P&gt;&lt;P&gt;If you want to maintain long texts (basic data texts, internal comments, purchase order texts, material memos, or sales texts) or customer-defined fields for a material, some special conditions have to be observed. They are described in the documentation for parameters MATERIALLONGTEXT and EXTENSIONIN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;HEADDATA&lt;/P&gt;&lt;P&gt;CLIENTDATA&lt;/P&gt;&lt;P&gt;CLIENTDATAX&lt;/P&gt;&lt;P&gt;PLANTDATA&lt;/P&gt;&lt;P&gt;PLANTDATAX&lt;/P&gt;&lt;P&gt;FORECASTPARAMETERS&lt;/P&gt;&lt;P&gt;FORECASTPARAMETERSX&lt;/P&gt;&lt;P&gt;PLANNINGDATA&lt;/P&gt;&lt;P&gt;PLANNINGDATAX&lt;/P&gt;&lt;P&gt;STORAGELOCATIONDATA&lt;/P&gt;&lt;P&gt;STORAGELOCATIONDATAX&lt;/P&gt;&lt;P&gt;VALUATIONDATA&lt;/P&gt;&lt;P&gt;VALUATIONDATAX&lt;/P&gt;&lt;P&gt;WAREHOUSENUMBERDATA&lt;/P&gt;&lt;P&gt;WAREHOUSENUMBERDATAX&lt;/P&gt;&lt;P&gt;SALESDATA&lt;/P&gt;&lt;P&gt;SALESDATAX&lt;/P&gt;&lt;P&gt;STORAGETYPEDATA&lt;/P&gt;&lt;P&gt;STORAGETYPEDATAX&lt;/P&gt;&lt;P&gt;FLAG_ONLINE&lt;/P&gt;&lt;P&gt;FLAG_CAD_CALL&lt;/P&gt;&lt;P&gt;NO_DEQUEUE&lt;/P&gt;&lt;P&gt;NO_ROLLBACK_WORK&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;MATERIALDESCRIPTION&lt;/P&gt;&lt;P&gt;UNITSOFMEASURE&lt;/P&gt;&lt;P&gt;UNITSOFMEASUREX&lt;/P&gt;&lt;P&gt;INTERNATIONALARTNOS&lt;/P&gt;&lt;P&gt;MATERIALLONGTEXT&lt;/P&gt;&lt;P&gt;TAXCLASSIFICATIONS&lt;/P&gt;&lt;P&gt;RETURNMESSAGES&lt;/P&gt;&lt;P&gt;PRTDATA&lt;/P&gt;&lt;P&gt;PRTDATAX&lt;/P&gt;&lt;P&gt;EXTENSIONIN&lt;/P&gt;&lt;P&gt;EXTENSIONINX&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;1001UEB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Feb 2008 06:01:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-06T06:01:51Z</dc:date>
    <item>
      <title>bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355129#M804980</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 need documentation of bapi material_save_data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 05:37:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355129#M804980</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T05:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355130#M804981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Explore the function module &lt;STRONG&gt;BAPI_MATERIAL_SAVEDATA&lt;/STRONG&gt; in &lt;STRONG&gt;T.code SE37&lt;/STRONG&gt;. You can find the Documentation about this function module. The following is the documentation available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI_MATERIAL_SAVEDATA&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;____________________________________________________&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Short Text&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Create and Change Material Master Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Functionality&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You use this method to create new material master data or to change existing material master data. The data on a material can be transferred for each call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When creating material master data, you must transfer the material number, the material type, and the industry sector to the method. You must also enter a material description and its language.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When changing material master data, you need enter only the material number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the header data, you must select at least one view for which data is to be created. Depending on the view selected, you must maintain other required parameters. If you do not enter values for all of the required parameters, the method is ended with an error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corresponding fields in the tables (such as CLIENTDATA) must first be supplied with data by the calling program. An indicator must also be set for each of these fields so that the data is written to the database by the method. This requires the calling program to supply the corresponding field with the indicator in a checkbox table (for example, CLIENTDATAX). Checkbox tables exist for tables that do not contain any language-dependent texts (MAKT, MLTX), International Article Numbers (MEAN), or tax classifications (MLAN). Several data records for a material can be created in these tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a structure contains fields for units of measurement (such as structure CLIENTDATA, field BASE_UOM), language indicators (such as structure MATERIALDESCRIPTION, field LANGU), or country indicators (such as structure TAXCLASSIFICATIONS, field DEPCOUNTRY), there is always a field of the same name with the ending _ISO. This makes it possible to transfer either the internally used SAP code or a standardized ISO code for the units of measurement, language indicators, or country indicators. ISO codes are converted to an SAP code internally for further processing. The ISO code is used only if the SAP code is not transferred. If you use ISO codes, there must be a unique assignment of the ISO code to the SAP code in the following activities in Customizing for Global Parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Check Units of Measurement&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Define Countries&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If you want to maintain long texts (basic data texts, internal comments, purchase order texts, material memos, or sales texts) or customer-defined fields for a material, some special conditions have to be observed. They are described in the documentation for parameters MATERIALLONGTEXT and EXTENSIONIN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if uesful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 05:44:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355130#M804981</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T05:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355131#M804982</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;can u explain what are structures we need to include such as bapimathead&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;plz dont send program as i already have them&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 05:52:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355131#M804982</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T05:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355132#M804983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;U have to poplate the structures like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HEADDATA&lt;/P&gt;&lt;P&gt;CLIENTDATA&lt;/P&gt;&lt;P&gt;CLIENTDATAX&lt;/P&gt;&lt;P&gt;PLANTDATA&lt;/P&gt;&lt;P&gt;PLANTDATAX&lt;/P&gt;&lt;P&gt;SALESDATA&lt;/P&gt;&lt;P&gt;SALESDATAX&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Documantataion&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;You use this method to create new material master data or to change existing material master data. The data on a material can be transferred for each call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When creating material master data, you must transfer the material number, the material type, and the industry sector to the method. You must also enter a material description and its language.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When changing material master data, you need enter only the material number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the header data, you must select at least one view for which data is to be created. Depending on the view selected, you must maintain other required parameters. If you do not enter values for all of the required parameters, the method is ended with an error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corresponding fields in the tables (such as CLIENTDATA) must first be supplied with data by the calling program. An indicator must also be set for each of these fields so that the data is written to the database by the method. This requires the calling program to supply the corresponding field with the indicator in a checkbox table (for example, CLIENTDATAX). Checkbox tables exist for tables that do not contain any language-dependent texts (MAKT, MLTX), International Article Numbers (MEAN), or tax classifications (MLAN). Several data records for a material can be created in these tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a structure contains fields for units of measurement (such as structure CLIENTDATA, field BASE_UOM), language indicators (such as structure MATERIALDESCRIPTION, field LANGU), or country indicators (such as structure TAXCLASSIFICATIONS, field DEPCOUNTRY), there is always a field of the same name with the ending _ISO. This makes it possible to transfer either the internally used SAP code or a standardized ISO code for the units of measurement, language indicators, or country indicators. ISO codes are converted to an SAP code internally for further processing. The ISO code is used only if the SAP code is not transferred. If you use ISO codes, there must be a unique assignment of the ISO code to the SAP code in the following activities in Customizing for Global Parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check Units of Measurement&lt;/P&gt;&lt;P&gt;Define Countries&lt;/P&gt;&lt;P&gt;If you want to maintain long texts (basic data texts, internal comments, purchase order texts, material memos, or sales texts) or customer-defined fields for a material, some special conditions have to be observed. They are described in the documentation for parameters MATERIALLONGTEXT and EXTENSIONIN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;HEADDATA&lt;/P&gt;&lt;P&gt;CLIENTDATA&lt;/P&gt;&lt;P&gt;CLIENTDATAX&lt;/P&gt;&lt;P&gt;PLANTDATA&lt;/P&gt;&lt;P&gt;PLANTDATAX&lt;/P&gt;&lt;P&gt;FORECASTPARAMETERS&lt;/P&gt;&lt;P&gt;FORECASTPARAMETERSX&lt;/P&gt;&lt;P&gt;PLANNINGDATA&lt;/P&gt;&lt;P&gt;PLANNINGDATAX&lt;/P&gt;&lt;P&gt;STORAGELOCATIONDATA&lt;/P&gt;&lt;P&gt;STORAGELOCATIONDATAX&lt;/P&gt;&lt;P&gt;VALUATIONDATA&lt;/P&gt;&lt;P&gt;VALUATIONDATAX&lt;/P&gt;&lt;P&gt;WAREHOUSENUMBERDATA&lt;/P&gt;&lt;P&gt;WAREHOUSENUMBERDATAX&lt;/P&gt;&lt;P&gt;SALESDATA&lt;/P&gt;&lt;P&gt;SALESDATAX&lt;/P&gt;&lt;P&gt;STORAGETYPEDATA&lt;/P&gt;&lt;P&gt;STORAGETYPEDATAX&lt;/P&gt;&lt;P&gt;FLAG_ONLINE&lt;/P&gt;&lt;P&gt;FLAG_CAD_CALL&lt;/P&gt;&lt;P&gt;NO_DEQUEUE&lt;/P&gt;&lt;P&gt;NO_ROLLBACK_WORK&lt;/P&gt;&lt;P&gt;RETURN&lt;/P&gt;&lt;P&gt;MATERIALDESCRIPTION&lt;/P&gt;&lt;P&gt;UNITSOFMEASURE&lt;/P&gt;&lt;P&gt;UNITSOFMEASUREX&lt;/P&gt;&lt;P&gt;INTERNATIONALARTNOS&lt;/P&gt;&lt;P&gt;MATERIALLONGTEXT&lt;/P&gt;&lt;P&gt;TAXCLASSIFICATIONS&lt;/P&gt;&lt;P&gt;RETURNMESSAGES&lt;/P&gt;&lt;P&gt;PRTDATA&lt;/P&gt;&lt;P&gt;PRTDATAX&lt;/P&gt;&lt;P&gt;EXTENSIONIN&lt;/P&gt;&lt;P&gt;EXTENSIONINX&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;1001UEB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 06:01:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3355132#M804983</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-06T06:01:51Z</dc:date>
    </item>
  </channel>
</rss>

