Search

Related Information
Related Business Objects Neighboring Context Simple Samples Where used

ES Workplace Basket
Open Basket ES Workplace Basket Loading..... Add to Basket

Create Service Product As Bulk

asynchronous inbound service operation (SAP A2A)

Definition

To create one or many service products asynchronously.

Technical Data

Technical Name	ServiceProductCRMBulkCreateRequest_In
Namespace	http://sap.com/xi/CRM/Global2
Latest Software Component Version	SAP CRM ABAP 7.02
First Shipped With: Software Component Version	SAP CRM ABAP 7.0
First Shipped With: Product Version	SAP CRM 7.0 - SAP Customer Relationship Management 7.0 (Easy Adoption)
Category	SAP A2A
Direction	inbound
Mode	asynchronous
Point-to-Point Communication Enabled	No
Release State	restricted
Idempotency	not applicable
Application Component for Customer Messages	CRM-MD-PRO
WSDL	WSDL (ESR)

Business Context and Use

The Create Service Product As Bulk inbound service operation creates one or many service products asynchronously, including such information as basic data, descriptive data, control data, and any other related data.

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

Related Operations

The Change Service Product inbound service operation changes a service product asynchronously, including such information as basic data, descriptive data, control data, and any other related data.
The Create Service Product inbound service operation creates a service product asynchronously, including such information as basic data, descriptive data, control data, and any other related data.
The Confirm Service Product outbound service operation confirms the creation or change of a service product asynchronously by returning all the information on the service product.
The Confirm Service Product As Bulk outbound service operation confirms the creation of one or many service products asynchronously by returning all the information on each individual service product in the bulk request.
The Find Service Product Basic Data by Elements inbound service operation finds the basic data of service products that match the specified search critieria.
The Read Service Product inbound service operation retrieves the complete data available on a specified service product.

Features

For each service product to be created in the bulk request, the following information is mandatory.

An internal identification for the product category (InternalID element)
An identification of the product category hierarchy (ProductCategoryHierarchyID element)
An identification of the source business system (SourceBusinessSystemID element)

Different elements must be filled depending on the use case.

Asynchronous service operations
The execution of this asynchronous bulk service operation triggers a confirmation message from the Confirm Service Product As Bulk service operation. This contains information on whether the creation of each individual service product in the bulk request was successful or not.

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

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

A service product 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 Customizing > 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

Forward Error Handling
The Create Service Product As Bulk inbound service operation supports Forward Error Handling (FEH).

The following error categories are used:

DCE: Determination & Conversion
Errors in this category normally indicate that the information sent is not in the correct format or not within acceptable ranges, for example as follows.
- The request passes alphanumeric characters for a data element that takes only numeric values
- The request passes a value of 8 for a data element that has a value range of 1-7
PRE: Processing Error
Errors in this category indicate errors in business logic processing for example as follows.
- The request is to create a service product that already exists.

For more information about the individual error categories, see the code list for the global data type LogItemCategoryCode .

Integration

This service operation belongs to the Service Product Processing In

service interface.

Notes on SAP Implementation

Processing
See the following SAP Notes:
1251659
1268068
1271052
1278289
1283386
1345305
1356542
1354286
1364288

Enhancements

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

Code Example
The following example is an excerpt of an XML message for the Create Service Product As Bulk operation.
Note: The example contains sample data that applies to a specific configuration and master data scenario.

<n0:ServiceProductCRMBulkCreateRequest xmlns:n0=" http://sap.com/xi/CRM/Global2 ">
<MessageHeader>
<ID schemeID="Str 1" schemeAgencyID="Str 2" schemeAgencySchemeAgencyID="Str">Str 4</ID>
<UUID schemeID="Str 5" schemeAgencyID="Str 6">Str 7                               </UUID>
<ReferenceID schemeID="Str 8" schemeAgencyID="Str 9" schemeAgencySchemeAgencyID="Str">Str 11</ReferenceID>
<ReferenceUUID schemeID="Str 12" schemeAgencyID="Str 13">Str 14                              </ReferenceUUID>
<CreationDateTime>2005-12-31T23:59:59.1234Z</CreationDateTime>
</MessageHeader>
<ServiceProductCRMCreateRequest>
<MessageHeader>
   <ID schemeID="Str 179" schemeAgencyID="Str 180" schemeAgencySchemeAgencyID="Str"></ID>
   <UUID schemeID="Str 183" schemeAgencyID="Str 184"></UUID>
   <ReferenceID schemeID="Str 186" schemeAgencyID="Str 187" schemeAgencySchemeAgencyID="Str">Str 189</ReferenceID>
   <ReferenceUUID schemeID="Str 190" schemeAgencyID="Str 191">Str 192                             </ReferenceUUID>
   <CreationDateTime>2005-12-31T23:59:59.1234Z</CreationDateTime>
</MessageHeader>
<ServiceProduct>
   <ActionCode/>
   <UUID schemeID="Str 12" schemeAgencyID="Str 13"/>
   <InternalID schemeID="Str 15" schemeAgencyID="Str 16">SERV_BULK_201</InternalID>
   <ServiceProductDescription languageCode="es"/>
   <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   <Common>
    <ActionCode/>
    <CustomerTransactionDocumentItemProcessingTypeDeterminationProductGroupCode>FS12</CustomerTransactionDocumentItemProcessingTypeDeterminationProductGroupCode>
    <BaseMeasureUnitCode/>
   </Common>
   <ProductCategoryAssignment>
    <ActionCode/>
    <InternalID schemeID="Str 28" schemeAgencyID="Str 29">SRV_ALL</InternalID>
    <ProductCategoryHierarchyID schemeID="Str 31" schemeAgencyID="Str 32">R3PRODSTYP</ProductCategoryHierarchyID>
    <BaseProductCategoryIndicator>true</BaseProductCategoryIndicator>
    <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   </ProductCategoryAssignment>
   <Description>
    <ActionCode>St</ActionCode>
    <Description languageCode="en">This Service Product BULK CREATE 1</Description>
    <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   </Description>

</ServiceProduct>
</ServiceProductCRMCreateRequest>
<ServiceProductCRMCreateRequest>
<MessageHeader>
   <ID schemeID="Str 1107" schemeAgencyID="Str 1108" schemeAgencySchemeAgencyID="Str"></ID>
   <UUID schemeID="Str 1111" schemeAgencyID="Str 1112"></UUID>
   <ReferenceID schemeID="Str 1114" schemeAgencyID="Str 1115" schemeAgencySchemeAgencyID="Str">Str 1117</ReferenceID>
   <ReferenceUUID schemeID="Str 1118" schemeAgencyID="Str 1119">Str 1120                            </ReferenceUUID>
   <CreationDateTime>2005-12-31T23:59:59.1234Z</CreationDateTime>
</MessageHeader>
<ServiceProduct>
   <ActionCode/>
   <UUID schemeID="Str 12" schemeAgencyID="Str 13"/>
   <InternalID schemeID="Str 15" schemeAgencyID="Str 16">SERV_BULK_202</InternalID>
   <ServiceProductDescription languageCode="es"/>
   <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   <Common>
    <ActionCode/>
    <CustomerTransactionDocumentItemProcessingTypeDeterminationProductGroupCode>FS12</CustomerTransactionDocumentItemProcessingTypeDeterminationProductGroupCode>
    <BaseMeasureUnitCode/>
   </Common>
   <ProductCategoryAssignment>
    <ActionCode/>
    <InternalID schemeID="Str 28" schemeAgencyID="Str 29">SRV_ALL</InternalID>
    <ProductCategoryHierarchyID schemeID="Str 31" schemeAgencyID="Str 32">R3PRODSTYP</ProductCategoryHierarchyID>
    <BaseProductCategoryIndicator>true</BaseProductCategoryIndicator>
    <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   </ProductCategoryAssignment>
   <Description>
    <ActionCode>St</ActionCode>
    <Description languageCode="en">This Service Product BULK CREATE 2</Description>
    <SourceBusinessSystemID>Q9MCLNT709</SourceBusinessSystemID>
   </Description>

</ServiceProduct>
</ServiceProductCRMCreateRequest>
</n0:ServiceProductCRMBulkCreateRequest>

ES Bundles

This operation is contained in the following ES Bundles:

Product Master Data Management

Search

Related Information

Simple Samples

ES Workplace Basket