Loading.....

Definition

To create a material.

Business Context and Use

The Create Material inbound synchronous service operation creates a material, including such information as basic data, descriptive data, control data, and any other related data. The returned information includes all the information on the newly created material.

Further business context is provided in the documentation for the Product Data Maintenance process component and the Material business object.

Related Operations

• The Find Material Basic Data by Elements inbound service operation finds the basic data of materials that match the specified search critieria.
• The Change Material inbound synchronous service operation changes a specified material, including such information as basic data, descriptive data, control data, and any other related data.
• The Read Material inbound service operation retrieves the complete data available on a specified material.
• The Read Material Attachment Folder inbound service operation retrieves a specified document or all documents attached to a given material.

Features

To create a material, the following information is mandatory:

• The internal identification for the product category (InternalID element)
• The identification of the product category hierarchy (ProductCategoryHierarchyID element)
  

This service operation creates a material with the attributes specified in the input of the operation, such as:

• Product Category
  
• Description
  
• Text Collection
  
• Attachment Folder
  
• Global Trade Item Number
  

A confirmation will be returned with the newly created internal identifier of the material (MaterialInternalID element), along with other information. 
 

The service operation allows products of product type “Material” to be created. The minimum amount of data with which a product can be created comprises the following:

• InternalID (the normal case, that is, when internal number assignment is not being used)
• Logical system
• Base category

When creating materials, you can also create relationships to other materials, services, and warranties. The related entity records must, however, already exist in the system.

For new units of measure, the unit and conversion must be passed together.

Quantity information (characteristics) is available for each unit of measure, since it does not only depend on the conversion factor to the base unit of measure, but also on the packaging (with the exception of net weight, which is calculated using the conversion factor from the net weight of the base unit of measure). For quantity characteristics the following information is required:

• MeasureUnitCode - the unit of measure to which the information applies, for example PCE (ISO code for piece)
• Quantity - unitCode - the unit of the physical dimension, for example, cubic meter in ISO code (MTQ)

                                 - the actual value of the quantity

• QuantityTypeCode - type of physical dimension, such as volume (VOLUME)

A material can be deleted using the change service operation and setting the product status appropriately (I1104 - To archive).

MeasurementUnits
MeasurementUnitCodes of physical materials are specified in a "base unit of measure" using ISO-Codes
(for a list see Implementation Guide IMG > SAP NetWeaver > Check Units of Measurement > Button Isocodes).

The most common examples of base units of measure are for:

• solid materials, KGM (=kilograms) and MTR (=meters)
• fluids, LTR (=liters) 
• more complex materials, for example manufactured goods, EA (=each).

MeasurementUnits are split into three parts.

A) Declare the base unit and the units of measure.
    For example sand has a base unit "KGM" and its units of measure are bags of different sizes e.g small, medium and large.
    KGM
    smallbag
    mediumbag
    largebag

B) Conversionfactor (or ratio) of a unit in terms of its baseunit of measure.
    To continue the same example using sand.
    1 smallbag = 2 KGM
    1 mediumbag = 5 KGM
    1 largebag  = 10 KGM

C) Characteristics or physical dimensions of a unit, specifically length, breadth, height, volume, gross weight and net weight.
    Unit KGM > net_weight is 1 KGM, gross_weight is 1 KGM, volume is 0.2 LTR
    Unit largebag  > net_weight is 10 KGM, gross_weight 10.2 KGM 

Notes
1. A product can have only one base unit, as indicated in the statement
 <BaseQuantityUnitIndicator>true</BaseQuantityUnitIndicator>
2. Each QuantityUnit_tag must have a corresponding conversionfactors_tag. The tags for the QuantityUnits must come first, followed by the
  conversionfactor_tags.
3. The characteristics "Net_weight" and "Gross_weight" must be in the same unit e.g KGM.
4. The characteristic "Net_weight" can only be given in the base unit. If it is given in other units of measure e.g. smallbag it is ignored. But if the net weight is given for the base unit of measure, the net weight of other units is calculated using the conversion factor.  E.g. a netweight of 1 KGM for the base unit of measure KGM for sand and a conversionfactor 1:10 for a large bag gives a net weight of 10 KGM for the large bag
5.  Additional rules can be input to allow for sales restrictions imposed for business reasons by the Sales organization or Distribution channel, for example minimum price and minimum quantity.
6. Servicematerials can contain non-tangible services such as a "repair hour". In this case, the quantity and conversionfactor are specified as before, but the characteristics such as gross_weight are not supported.

Example 1

The base unit can be declared in the tag common as a shortcut.  For example to set the base unit to EA.
  <Common>
   <BaseMeasureUnitCode>EA</BaseMeasureUnitCode>
  </Common>

This is equivalent to the following.
  <QuantityUnit>
   <MeasureUnitCode>EA</MeasureUnitCode>
   <BaseQuantityUnitIndicator>true</BaseQuantityUnitIndicator>
  </QuantityUnit>
   <QuantityConversion>
   <Quantity unitCode="EA">1</Quantity>
   <CorrespondingQuantity unitCode="EA">1</CorrespondingQuantity>
  </QuantityConversion>

Example 2

The following declares the MeasurementUnits in three parts.

A) Quantity.

  <QuantityUnit>
   <MeasureUnitCode>EA</MeasureUnitCode>
   <BaseQuantityUnitIndicator>true</BaseQuantityUnitIndicator>
  </QuantityUnit>
  <QuantityUnit>
   <MeasureUnitCode>BX</MeasureUnitCode>
   <BaseQuantityUnitIndicator>false</BaseQuantityUnitIndicator>
  </QuantityUnit>

B) Conversionfactor.

 - <QuantityConversion>
  <Quantity unitCode="EA">1</Quantity>
  <CorrespondingQuantity unitCode="EA">1</CorrespondingQuantity>
  </QuantityConversion>
 - <QuantityConversion>
  <Quantity unitCode="BX">1</Quantity>
  <CorrespondingQuantity unitCode="EA">2</CorrespondingQuantity>
  </QuantityConversion>

C) Characteristics of the unit, specifically length, breadth, height, volume, gross weight and net weight.

 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="KGM">1.2</Quantity>
  <QuantityTypeCode>GROSS_WT</QuantityTypeCode>
  </QuantityCharacteristic>
 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="KGM">1.1</Quantity>
  <QuantityTypeCode>NET_WT</QuantityTypeCode>
  </QuantityCharacteristic>
 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="MTQ">0.8</Quantity>
  <QuantityTypeCode>VOLUME</QuantityTypeCode>
  </QuantityCharacteristic>
 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="MTR">1.0</Quantity>
  <QuantityTypeCode>LENGTH</QuantityTypeCode>
  </QuantityCharacteristic>
 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="MTR">1.0</Quantity>
  <QuantityTypeCode>BREADTH</QuantityTypeCode>
  </QuantityCharacteristic>
 <QuantityCharacteristic>
  <MeasureUnitCode>EA</MeasureUnitCode>
  <Quantity unitCode="MTR">0.8</Quantity>
  <QuantityTypeCode>HEIGHT</QuantityTypeCode>
  </QuantityCharacteristic>

Processing

Reuse Components

AttachmentFolder

TextCollection

Scheme Attributes at IDs and Codes

Error Handling

For every error from validation, mapping and API Adaptor phases, an appropriate error message that often helps to correct the error is sent to the GDT Log . This is returned as part of the response message.

Prerequisites

Any materials or services that are lnked to this new material must have been created previously.

Integration

Notes on SAP Implementation

Processing

See the following SAP Notes
1251659
1257228
1258822
1271052
1274356
1277508
1275945
1283386
1270938
1284122

Enhancements

The Business Add-In (BAdI) CRM_SE_MATLCRTRCI is available for this operation.

Code Example

The following example is an excerpt of an XML message for the Create Material  operation.

Note: The example contains sample data that applies to a specific configuration and master data scenario. 

<n0:MaterialCRMCreateRequest_sync xmlns:n0=" http://sap.com/xi/CRM/Global2 ">
 <Material>
  <InternalID schemeID="Token 11" schemeAgencyID="Token 12">MAT0919</InternalID>
  <SourceBusinessSystemID>Q0MCLNT709</SourceBusinessSystemID>
  <ProductCategory>
   <InternalID schemeID="Token 23" schemeAgencyID="Token 24">MAT_HAWA</InternalID>
   <ProductCategoryHierarchyID schemeID="Token 26" schemeAgencyID="Token 27">R3PRODSTYP</ProductCategoryHierarchyID>
   <SourceBusinessSystemID>Q0MCLNT709</SourceBusinessSystemID>
  </ProductCategory>
 </Material>
</n0:MaterialCRMCreateRequest_sync>

ES Bundles

This operation is contained in the following ES Bundles:

• Product Master Data Management