Functionality
You use this method to create new material master data or to changeexisting material master data.
Besides creating and changing material master data, you can also deletedata for the following structures:

• MATERIALDESCRIPTION


• UNITSOFMEASURE


• INTERNATIONALARTNOS


• VENDOREAN


• UNITOFMEASURETEXTS


• LAYOUTMODULEASSGMT


• MATERIALLONGTEXT

For the system to recognize that a data record is to be deleted, thefield FUNCTION must contain the value 003 in the correspondingstructure. This field is of no relevance when creating or changing data.
If the material specified in structure HEADDATA is ageneric material, you can specify data onthe generic material and also on the variants in the structuresconcerned (CLIENTDATA, and so on). Normally, this is of use only if youwant to maintain special data on the variant differently from the dataon the generic material. If no explicit data on the variants exists, itis created automatically on the basis of the data on the genericmaterial.
If a variant is created, an entry must be defined in structureVARIANTSKEYS for this variant. This makes it possible to also create newvariants for an existing generic material.
If a structure contains fields for units of measurement (such asstructure CLIENTDATA, field BASE_UOM), language indicators (such asstructure MATERIALDESCRIPTION, field LANGU), or country indicators (suchas structure TAXCLASSIFICATIONS, field DEPCOUNTRY), there is always afield of the same name with the ending _ISO. This makes it possible totransfer either the internally used SAP code or a standardized ISO codefor the units of measurement, language indicators, or countryindicators. ISO codes are converted to an SAP code internally forfurther processing. The ISO code is used only if the SAP code is nottransferred. If you use ISO codes, you must ensure that the SAP code canbe uniquely determined from the ISO code in Customizing for units ofmeasurement, language indicators, and country indicators.
The data transferred is updated synchronously; that is, not using anupdate task. This is necessary because this method is also used indistribution by Application LinkEnabling (ALE), where asynchronous updating cannot be supported ininbound processing because the processing status of the assignedIDocs cannot otherwise be set reliably.
If a serious database error occurs during synchronous updating of theapplication data, a rollback for all database changes made so far istriggered in the method. If the method is called in a commit unittogether with other methods, the database changes of the previouslyexecuted method calls are also rolled back as a result. The rollback isnecessary to prevent database inconsistencies due to only part of theapplication data being updated correctly.
Any information or error messages that are issued while the data isbeing processed are recorded in the application log. If you want to viewthese messages, a commit must be performed after this method is calledso that the data in the application log is written to the database. Evenif the structure RETURN returns an E-type (error) message in field TYPE,a commit must be performed so that the application log is written. Inthe event of an error, the method itself ensures that the data is resetcorrectly. The commit is also necessary to trigger the updating of theclassification data because the update module for the classificationdata is registered by means of PERFORM ON COMMIT and is started only bya COMMIT WORK.

Notes
To create or change data, you require the necessary authorizations formaintaining the corresponding material master data.

Further information
As of Release 4.5A, this method can also be used to distribute deletionflags correctly. Deletion flags are only set in retail forclient-specific material data (parameter CLIENTDATA) and plant-specificmaterial data (parameter PLANTDATA). If deletion flags (field DEL_FLAG)are transferred for one of these two parameters, a correspondingworkflow is generated during updating. Depending on the value of thedeletion indicator, this workflow triggers the discontinuation of thematerial for the client or for a specific plant, or the cancelling of anexisting deletion flag.

Description
INCLUDE STRUKTUR OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Since numerous information messages and error messages can be issuedwhile the material is processed, the messages created are collected inan application log. The return parameter merely tells you the numberunder which the messages in the application log can be displayed.
INCLUDE GRAVIEREND OBJECT DOKU ID TX LANGUAGE EN
Note
See also the documentation for the fieldNO_APPL_LOG in the parameter HEADDATA.

Value range
Type,,ID,,Number,,Message
S,,MG,,537,,Messages for material <(>&<)>: log number <(>&<)>
E,,MG,,537,,Messages for material <(>&<)>: log number <(>&<)>

Description
In this structure, you define the essential data necessary to maintaina material. The fields essentially correspond to those available on theinitial screen when creating a material online.
When creating material master data, you can specify only a singlematerial or a configurable material in this structure because variantscan be created only using the configurable material assigned. Whenchanging material master data, you can specify a single material, aconfigurable material, or a variant in this structure,
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN

Notes
When you create data, the following fields in the structure mustalways contain values:


• MATERIAL


• MATL_TYPE


• MATL_GROUP


• MATL_CAT

When you change data, the field MATERIAL in the structure mustalways contain a value.
At least one of the following user departments must be selected:

• BASIC_VIEW (always necessary when creating a material)


• LIST_VIEW


• SALES_VIEW


• LOGDC_VIEW


• LOGST_VIEW


• POS_VIEW

All other fields are optional. You can enter values in them asrequired.
If corresponding characteristics profiles have been assigned to thematerial group (MATL_GROUP) in material group maintenance, and if theyprovide other characteristics for value assignment, you can define thecorresponding characteristics profile in field CHAR_PROF. If you do notspecify a characteristics profile, the system uses the characteristicsknown at material group level for value assignment.
If you do not specify an explicit reference material (REF_MATL), it isdetermined on the basis of the material group specified (MATL_GROUP).If no corresponding reference material is found, you must make surethat the user data structures provide data for all the required fieldsbecause the material cannot otherwise be created. If a suitablymaintained reference material exists, only those values in the userdata structures need to be transferred that are to be maintaineddifferently from the reference material. All other data is copied fromthe reference material.
If the material number (MATERIAL) is an externally assigned number thatis to be checked against a number range interval, field CK_NO_RNGE mustcontain the value X.
Corresponding update structures (such as CLIENTDATAX and PLANTDATAX)exist for individual user data structures (such as CLIENTDATA andPLANTDATA). These update structures contain information on which fieldsof the assigned user data structure are change-relevant.
When you transfer data for the first time, the majority of the userdata fields are normally change-relevant. To avoid having to specify adata record with the change-relevant fields for each data record, youcan enter X in field ALL_FIELDS. This makes all fields in alluser data structures change-relevant. However, do so only if you arecertain that all essential user data fields contain values because theinitial value for the corresponding user data field is transferred forall fields not containing values, even if a default value other thanthe initial value could have been provided by the reference material.If a suitably maintained reference material exists, do not set fieldALL_FIELDS during data transfer, but enter values in the user datafields and flag them as change-relevant if they are to be maintaineddifferently from the reference material. In the simplest case, it issufficient to enter values in the header segment only, and not tospecify any user data.

Description
You can use this structure to transfer additional retail-specific basicdata for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN

Notes
INCLUDE HEADDATAALR OBJECT DOKU ID TX LANGUAGE EN


• PUR_GROUP


• LOADINGGRP

INCLUDE MUSSEINGABENALR OBJECT DOKU ID TX LANGUAGE EN
You need specify a unit of measure in the fields SALES_UNIT (orSALES_UNIT_ISO) and ISSUE_UNIT (or ISSUE_UNIT_ISO) only if the salesunit or issue unit is not the same as the base unit of measure (fieldBASE_UOM or BASE_UOM_ISO in the structure CLIENTDATA).
INCLUDE FOLG_FELDALR OBJECT DOKU ID TX LANGUAGE EN

• SALES_UNIT (or SALES_UNIT_ISO)


• ISSUE_UNIT (or ISSUE_UNIT_ISO)

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (ADDNLCLIENTDATA) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
You use this structure to transfer a list of characteristics data.
If a generic material has been specified in structure HEADDATA, thisstructure can be used to define characteristic value assignment datafor the variant-creating characteristics and also for the informativecharacteristics. In addition, characteristic value assignment data canbe transferred for all characteristics assigned in material groupmaintenance for the generic material's variants. Characteristic valueassignment data for informative characteristics at generic materiallevel is copied to the variants automatically. For this reason, you areadvised against explicitly transferring characteristics data forinformative characteristics for variants. This can result in variantsbeing differently maintained so that future changes to the basic dataon the generic material are no longer copied to the variants.
If characteristic value assignments for variant-creatingcharacteristics are specified at generic material level, they areinterpreted as a characteristic value restriction; that is, just as indialog mode, you can restrict at generic material level the totalcharacteristic values in the characteristic so that variants can becreated only for the restricted selection of characteristic values. Ifa variant-creating characteristic allows the insertion ofcharacteristic values that do not yet exist, the new characteristicvalues can be transferred at generic material level in this way. Thenew characteristic values are interpreted as a characteristic valuerestriction at generic material level. In this case, the characteristicvalues that already exist in the characteristic for the genericmaterial must also be transferred so that the characteristic valuerestriction does not prevent variants from being created for theexisting characteristic values.
If a single variant is contained in structure HEADDATA, this structurecan be used to define only characteristic value assignment data forcharacteristics not flagged as variant-creating in material groupmaintenance.
If a single material is contained in structure HEADDATA, this structurecan be used to define characteristic value assignment data for allcharacteristics assigned in material group maintenance.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN

Notes
In the case of variants, changes to the characteristic value assignmentare possible only for non-variant-creating characteristics.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (CHARACTERISTICVALUE) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
You use this structure to transfer general basic data on a material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Important
As of Release 4.6A, the field BASIC_MATL is no longer used due to anextension of the data type (domain). The field BASIC_MATL_NEW is nowresponsible for the old function. The field has been extended from 14characters to 48 characters. As a result, when data is sent from a 4.6Aor subsequent system to a pre-4.6A system, the field value can betransferred only if it is not longer than 14 characters. Data can betransferred from a pre-4.6A system to a 4.6A or subsequent systemwithout restriction.

Notes
INCLUDE HEADDATAALR OBJECT DOKU ID TX LANGUAGE EN


• BASE_UOM or BASE_UOM_ISO


• TRANS_GRP


• TAX_CLASS (if a default country has been maintained in Customizing for
the Material Master in Make GlobalSettings)
In addition, other required fields relevant to the user departmentBasic Data must be filled in structures ADDNLCLIENTDATA andMATERIALDESCRIPTION.
INCLUDE MUSSEINGABENALR OBJECT DOKU ID TX LANGUAGE EN
You need specify a unit of measure in field PO_UNIT (or PO_UNIT_ISO)only if the order unit is not the same as the base unit of measure(field BASE_UOM or BASE_UOM_ISO).
INCLUDE FOLG_FELDALR OBJECT DOKU ID TX LANGUAGE EN

• BASE_UOM (or BASE_UOM_ISO)


• PO_UNIT (or PO_UNIT_ISO)

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (CLIENTDATA) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Example
You have a material with the number MAT01 and want to change only theold material number.
The entries in the structure CLIENTDATA are as follows:


• FUNCTION


• MATERIAL,,,,MAT01


• OLD_MAT_NO,,MAT01_OLD

The entries in the other fields in the structure CLIENTDATA are asrequired (in the most straightforward case, they contain the initialvalue).
The structure CLIENTDATAX must then have the following entries:

• FUNCTION


• MATERIAL,,,,MAT01


• OLD_MAT_NO,,X

All other fields in the structure CLIENTDATAX must contain the initialvalue.

Description
If the general basic data for the material has been extended to includecustomer-specific fields, you can use this structure to transfer thedata for these customer-specific fields.
The key fields are already specified. You can store thecustomer-specific data in the data container provided by fields FIELD1to FIELD4. The split into four individual fields was necessary forpurely technical reasons. If the data is transferred using thisstructure, the structure information for the customer-specific fieldsis lost.
Example
Extending table MARA using the following APPEND structure:
Structure name ZMARA
INCLUDE APPEND OBJECT DOKU ID TX LANGUAGE EN
The data can be transferred to this structure by appending the fieldcontents of FUNCTION, MATERIAL, ZCUST1, ZCUST2, and ZCUST3.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (CLIENTEXT) contain change-relevantinformation.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
List of the distribution chains for which distribution chain data(SALESDATA, POSDATA) is also to be created.

Description
You can use this structure to transfer forecast parameters for amaterial.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for theindividual fields.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (FORECASTPARAMETERS) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
You can use this structure to transfer forecast values for a material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for theindividual fields.

Description
You use this structure to transferInternational Article Numbers(EANs) for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Data on the main EAN and also on the alternative EANs is transferred inthis structure for each unit of measure. The main EAN is identified asthe EAN defined in field EAN_UPC in structure UNITSOFMEASURE for therelevant unit of measure.

Notes
If vendor-specific EANs are also used (see structure VENDOREAN), theymust be transferred in the structure INTERNATIONALARTNOS in addition.
INCLUDE UNITSOFMEASUREALR OBJECT DOKU ID TX LANGUAGE EN
If you want to change the EANs for the material (for example, theassignments of main EANs), you must also transfer all assigned units ofmeasure in structure UNITSOFMEASURE because this structure contains theinformation on which EAN is the main EAN for the corresponding unit ofmeasure.

Description
You can use this structure to transfer the material's layout moduleassignments.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Note
INCLUDE LAYOUTMODULE OBJECT DOKU ID TX LANGUAGE ENFor reasons of upward compatibility, you can continue to use theexisting structure to transfer layout module assignments. However, itshould not be used for this purpose in the longer term.
As of Release 4.6C, the field MAIN_LMOD in this structure is no longersupported.

Notes
INCLUDE UNITSOFMEASUREALR OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (LAYOUTMODULEASSGMT) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
All fields in the structure use the data elementBAPIUPDATE.
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
Note
INCLUDE LAYOUTMODULE OBJECT DOKU ID TX LANGUAGE ENFor reasons of upward compatibility, you can continue to use theassigned user data structure (LAYOUTMODULEASSGMT) to transfer layoutmodule assignments. Since the new method does not support checkboxstructures, the existing checkbox structure is obsolete as of Release4.6C.

Description
You can use this structure to transfermaterial descriptions for a material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for theindividual fields.

Notes
If no reference material has been maintained for the material group(MATL_GROUP) defined in structure HEADDATA, and if no explicitreference material (REF_MATL) has been defined in structure HEADDATA, avalid value must be entered in the field MATL_DESC.

Description
You can use this structure to transfer long texts for a material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Note
The field MATERIAL added in Release 4.5A is of no significance. It isrequired only in ALE outbound processing for the correct filtering ofsubordinate parameters, and is generally filled redundantly with thematerial number contained in the field TEXT_NAME when an IDoc iscreated in ALE distribution. In ALE inbound processing or if the BAPIBAPI_MATERIAL_MAINTAINDATA_RT is called directly (method cloneof business object retail material), only the material numberextracted from the field TEXT_NAME is considered.

Description
You can use this structure to transfer planning data for the material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for theindividual fields.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (PLANNINGDATA) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
You can use this structure to transfer plant-specific data for thematerial.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Note
As of Release 4.5A, the field EX_CERT_NO is no longer used due to adata type change. It has been superseded by the field EX_CERT_NO_NEW.The data type has been extended from NUMC8 to CHAR8. As a result, ifdata is sent from a system > Release 4.0B to a 4.0A or 4.0B system, thefield value can only be adopted if it is purely numerical. Data can betransferred from a 4.0A or 4.0B system to a system >4.0B withoutrestriction.

Notes
If no reference material has been maintained for the material group(MATL_GROUP) defined in structure HEADDATA, and if no explicitreference material (REF_MATL) has been defined in structure HEADDATA, avalid value must be entered in the following field:


• MRP_TYPE

The following fields are also required fields. However, no data has tobe transferred for them since default data is determined automatically.

• PUR_GROUP, LOADINGGRP

The values defined in structure ADDNLCLIENTDATA are used as defaultvalues.

• AVAILCHECK

The value defined in Customizing for Shipping inDefine checking groups default value isused as the default value.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (PLANTDATA) contain change-relevantinformation. This makes it possible to provide only the relevant fieldsin the assigned user data structure with valid values. These fields arethen selected in the checkbox structure, ensuring that all non-selectedfields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
If plant-specific material data has been extended to includecustomer-specific fields, you can use this structure to transfer thedata for these customer-specific fields.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure is used to determine which fields in the assigned userdata structure (PLANTEXT) contain change-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
List of the plants for which plant data (PLANTDATA, FORECASTPARAMERS,TOTALCONSUMPTION, UNPLNDCONSUMPTION, PLANNINGDATA) is also to becreated.

Description
You can use this structure to transfer POSdata for the material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for theindividual fields.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (POSDATA) contain change-relevantinformation. This makes it possible to provide only the relevant fieldsin the assigned user data structure with valid values. These fields arethen selected in the checkbox structure, ensuring that all non-selectedfields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
If the POS data of the material has been extended to includecustomer-specific fields, you can use this structure to transfer thedata for these customer-specific fields.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (POSEXT) contain change-relevantinformation.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
You can use this structure to transfer sales data for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (SALESDATA) contain change-relevantinformation.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE BAPIUPDATE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG1 OBJECT DOKU ID TX LANGUAGE EN

Description
If the sales data for the material has been extended to includecustomer-specific fields, the data for these customer-specific fieldscan be transferred using this structure.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure is used to determine which fields in the assigned userdata structure (SALESEXT) contain change-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
You can use this structure to transfer storage-location-specific datafor the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (STORAGELOCATIONDATA) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE BAPIUPDATE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG1 OBJECT DOKU ID TX LANGUAGE EN

Description
If storage-location-specific material data has been extended to includecustomer-specific fields, the data for these customer-specific fieldscan be transferred using this structure.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (STORAGELOCATIONEXT) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
List of storage locations for whichstorage location data (STORAGELOCATIONDATA) is also to be created.

Description
You can use this structure to transferstorage-type-specific data for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (STORAGETYPEDATA) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE BAPIUPDATE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG1 OBJECT DOKU ID TX LANGUAGE EN

Description
If storage-type-specific material data has been extended to includecustomer-specific fields, the data for these customer-specific fieldscan be transferred using this structure.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (STORAGETYPEEXT) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
List of storage types for which storage typedata (STORAGETYPEDATA) is also to be created.

Description
You can use this structure to transfer taxclassifications for the material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for thefields concerned.

Description
You can use this structure to transfer totalconsumption data for the material.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for thefields concerned.

Description
You use this structure to transferunit-specific texts for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN

Notes
If data is transferred for a unit of measure (field ALT_UNIT orALT_UNIT_ISO) that does not yet exist in the system, an entry in thestructure UNITSOFMEASURE must also be transferred for this new unit ofmeasure.

Description
You use this structure to transfer the material'sunits of measure.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
Data on the base unit of measure and also on the alternative units ofmeasure is transferred in this structure. The base unit of measure isidentified as the unit of measure defined in field BASE_UOM (orBASE_UOM_ISO) in structure CLIENTDATA.
Note
The fields UNIT and UNIT_ISO included in Release 4.5A are of nosignificance. They are required only in ALE outbound processing for thecorrect filtering of subordinate parameters and are generallyredundantly filled with information from fields ALT_UNIT orALT_UNIT_ISO when an IDoc is created in ALE distribution. In ALEinbound processing or if the BAPI BAPI_MATERIAL_MAINTAINDATA_RT iscalled directly (method clone of business object RetailMaterial), only the values of fields ALT_UNIT or ALT_UNIT_ISO areconsidered.

Notes
If data is created using structures UNITOFMEASURETEXTS,INTERNATIONALARTNOS, VENDOREAN, or LAYOUTMODULEASSGMT, and if thesestructures contain units of measure that do not yet exist in thesystem, an entry in structure UNITSOFMEASURE must also be transferredfor each new unit of measure.
If an International Article Number (EAN) that does not yet exist in thesystem is transferred in field EAN_UPC, an entry in structureINTERNATIONALARTNOS must also be transferred for this new EAN.

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (UNITSOFMEASURE) containchange-relevant information. This makes it possible to provide only therelevant fields in the assigned user data structure with valid values.These fields are then selected in the checkbox structure, ensuring thatall non-selected fields retain their current value in the database.
All fields in the structure use the data elementBAPIUPDATE.
Note
If the indicator ALL_FIELDS is set in the structure HEADDATA,the information in the checkbox structure is irrelevant; that is, nodata records are required in the checkbox structure (see also thedocumentation for data element UPDALL).

Description
You can use this structure to transfer data onunplanned consumption for thematerial.
For information on the meaning of the individual fields in thestructure, see the corresponding data element documentation for thefields concerned.

Description
You can use this structure to transfer valuationdata for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (VALUATIONDATA) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE BAPIUPDATE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG1 OBJECT DOKU ID TX LANGUAGE EN

Description
If the valuation data for the material has been extended to includecustomer-specific fields, the data for these customer-specific fieldscan be transferred using this structure.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (VALUATIONEXT) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN

Description
List of valuation types for which valuationdata (VALUATIONDATA) is also to be created.

Notes
Valuation data is created automatically for the valuation type
' '
and, in the case of split valuation, forthe valuation type
'RNORMAL '
If further valuation types are necessary, they can be created with thisstructure.

Description
You can use this structure to transfer a list ofvariants that are to be created for theconfigurable material specified in parameter HEADDATA.

Notes
Define the configurable material in field MATERIAL and the variant infield VARIANT.

Description
You use this structure to transfer vendor-specificEANs for the material.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
The main EAN and also the alternative EANs of the vendor concerned aretransferred in this structure. To identify the main EAN of the vendor,the indicator in field MAIN_EAN must be set.

Notes
INCLUDE UNITSOFMEASUREALR OBJECT DOKU ID TX LANGUAGE EN
If an EAN (field EAN_UPC) that does not yet exist in the system istransferred as the vendor-specific EAN, an entry in the structureINTERNATIONALARTNOS must also be transferred for this new EAN.

Description
List of warehouse numbers for whichwarehouse number data (WAREHOUSENUMBERDATA) is also to be created.

Description
You can use this structure to transferwarehouse-number-specific data for thematerial.
INCLUDE DE_DOKU OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (WAREHOUSENUMBERDATA) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE BAPIUPDATE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN
INCLUDE DEL_FLAG1 OBJECT DOKU ID TX LANGUAGE EN

Description
If the warehouse-number-specific material data has been extended toinclude customer-specific fields, the data for these customer-specificfields can be transferred using this structure.
INCLUDE FIELD1_4 OBJECT DOKU ID TX LANGUAGE EN

Description
This structure (checkbox structure) is used to determine which fieldsin the assigned user data structure (WAREHOUSENUMBEREXT) containchange-relevant information.
INCLUDE ANKREUZLEISTE OBJECT DOKU ID TX LANGUAGE EN
INCLUDE ALL_FIELDS OBJECT DOKU ID TX LANGUAGE EN