Inbound Service Interface (public)

Description	Manage Sales Quotes
Name	CustomerQuoteProcessingManageCustomerQuoteIn
Namespace	http://sap.com/xi/A1S/Global
Process Component Description	Customer Quote Processing
Process Component Name	CustomerQuoteProcessing
Process Component Namespace	http://sap.com/xi/AP/CRM/Global
Deploymnent Unit Description	Customer Relationship Management
Endpoint Activation	By Scoping of Process Component
Operations	Check sales quotes Maintain sales quotes

Definition

An interface to create, update or delete a customer quote which can be used for customer quote replication or migration.

Business Context and Use

The web service interface Manage Customer Quote In enables you to connect external applications to your SAP system and to create and edit customer quote within your system. The web service interface Manage Customer Quote In is relevant if your company wants to access and manage customer quote data from external applications.

The web service interface Manage Customer Quote In offers the operations MaintainBundle and CheckMaintainBundle.

Prerequisites

Existence of required master data and related business documents in the system, like:

Master data of MOM and BusinessPartner: SalesUnit, SalesOrganization, Employee, Customer, and so on.
Product Master data
Price Master data
Opportunity or other business documents to be related to the Customer Quote in the BusinessTransactionDocumentReference

Constraints and Integrity Conditions

General Rules for Using this Web Service

Check Maintain Bundle vs. Maintain Bundle

Maintain Bundle operations enable external applications to create and change business document data. Check Maintain Bundle operations enable external applications to simulate maintain bundle requests without changing business document data. In particular, Check Maintain Bundle operations have the following functions:

Return system messages similar to corresponding maintain bundle operations
Provide the same message type as the corresponding operation Maintain Bundle
Do not assign internal numbers from a productive number range interval (number range statuses are not increased)
Do not change business documents

Action Code

Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.

Action Code	Description
01	Create; the system returns an error message if the node element already exists.
02	Update; the system returns an error message if the node element does not exist.
03	Delete; the system returns an error message if the node element does not exist.
04	Save; the system creates or changes the node element data.

Default action code: 04 (Save).

Note: Action code 04 (Save) creates business documents if the system cannot identify a matching target business document. This applies in particular if no business document ID or UUID is provided by the web service consumer. The web service consumer (external application) is responsible for providing correct business document IDs or UUIDs. This will avoid accidentally creating duplicate business documents.

List Processing

The processing of node elements with cardinality > 1 (for example, a list of quote items or contact of a Customer) can be controlled using List Complete Transmission Indicators (LCTI). The LCTI indicates whether a list of node elements is transmitted completely. The LCTI of a node element with cardinality > 1 is modeled as an attribute of its parent node element (attribute name: <name of child element>ListCompleteTransmissionIndicator).

LCTI	Description
false	The list of node elements is not completely transmitted. Hence, all node elements that are not transmitted remain unchanged. If transmitted node elements in the list can be uniquely identified, the system processes the node elements according to the action code. If transmitted node elements in the list cannot be uniquely identified, the system appends the node element to the corresponding list of node elements in the target business document.
true	The list of elements is completely transmitted. Hence, all node elements that are not transmitted are deleted. If no node element is transmitted, all the node elements in the system will be removed.

LCTI

Description

false

The list of node elements is not completely transmitted. Hence, all node elements that are not transmitted remain unchanged. If transmitted node elements in the list can be uniquely identified, the system processes the node elements according to the action code. If transmitted node elements in the list cannot be uniquely identified, the system appends the node element to the corresponding list of node elements in the target business document.

true

The list of elements is completely transmitted. Hence, all node elements that are not transmitted are deleted. If no node element is transmitted, all the node elements in the system will be removed.

Default list complete transmission indicator: false.

Note: The LCTI refers to the completeness of the list of node elements and does not imply completeness of sub-elements.

Empty and Missing Elements

Optional leaf elements in request messages that are not transmitted within a web service request are not changed in corresponding business documents.

Communication Timeout

Maintain bundle and check maintain bundle operations are mass-enabled stateless synchronous web service operations. Transferring or requesting amounts of data that are too large can cause communication timeouts. The web service consumer is responsible for ensuring reasonable sizes of data for mass operations.

Message Header

Maintain bundle and check maintain bundle operations support exactly one execution (idem potency). To ensure exactly one execution of web service requests, the web service consumer has to provide unique values for the elements ID or UUID of the BasicMessageHeader node element.

Change State ID

Using change state identifier (element name ChangeStateID), external applications can ensure that a modifying operation is not executed because the state of the business document has changed since the external application last read its data.

The change state ID is an uninterpretable string that is provided by query and read operations and can be utilized by all modifying operations. If the change state identifier is provided when calling a modifying operation, the system does not perform the operation if the state of the business document instance has changed since the change state ID was computed. If the change state ID is not provided by the web service consumer, the system performs the web service operation without checking the state of the business document.

The web service consumer (external application) is responsible for preventing accidental changes to business documents.

Note: For this web service the change state ID does not apply to the ContactPerson, Relationship, CommunicationArrangement, DirectResponsibility, SalesArrangement, or PaymentData node elements.

Object Node Sender Technical Identifier

Request node elements with cardinality > 1 contain an object node sender technical identifier to relate response message elements and log items to corresponding node elements in the request message.

The object node sender technical identifiers are provided as ObjectNodeSenderTechnicalID in request message types and referred to as ReferenceObjectNodeSenderTechnicalID in corresponding response message types.

If the object node sender technical ID is initial, the object node sender technical ID of the parent node element in the request is returned as the reference object node sender technical ID. If the object node sender technical IDs of all parent node elements are initial, the reference object node sender technical ID is returned as initial as well.

Note: The values specified in the ObjectNodeSenderTechnicalID are transient values that establish the correspondence between elements for only a single call. The web service consumer is not required to specify them or to use the same values for different calls. Also, the service provider does not interpret these values at all. Instead, the service provider returns them to the web service consumer in the ReferenceObjectNodeSenderTechnicalID elements.

Note: The ObjectNodeSenderTechnicalID is also used to identify failed business document modifications in a mass operation.

Example

Request:

 
<Child>
    <ObjectNodeSenderTechnicalID>999_A<ObjectNodeSenderTechnicalID>
    <Content>Child A: Some correct content</Content>
</Child>
<Child>
    <ObjectNodeSenderTechnicalID>999_B<ObjectNodeSenderTechnicalID>
    <Content>Child B: Some erroneous content</Content>
</Child>

Response:

 
<Log>
    <Item>
        <ReferenceObjectNodeSenderTechnicalID>999_B </ReferenceObjectNodeSenderTechnicalID>
        <Note>Error message for Child B</Note>
    </Item>
</Log>

Response Message

The structure of the response message consists of two parts:

A business document-specific part containing information about IDs and UUIDs of the created and changed business documents
Log items containing system messages including errors, warnings, and information messages raised by the system during processing of the web service request

More Information

General Information

You can find general information about Web services, their structure and consumption in the Web Services documentation.

Scenarios

Possible scenarios include the following:

Create a Customer Quote

The MaintainBundle operation is used to create a customer quote

Update a customer quote

The MaintainBundle operation is used to change, cancel or delete an existing customer quote

Example to create a customer quote:

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <CustomerQuote actionCode="01" ViewObjectIndicator="false" >
  <BuyerID>100</BuyerID>
  <Name languageCode="EN">CQ20121212</Name>
  <BuyerParty>
   <BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
  </BuyerParty>
  <SalesEmployeeParty>
   <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
   <MainIndicator>true</MainIndicator>
  </SalesEmployeeParty>
  <EmployeeResponsibleParty>
   <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
   <EmployeeID/>
  </EmployeeResponsibleParty>
  <RequestedFulfillmentPeriod>
   <StartDateTime timeZoneCode="UTC">2013-03-31T13:20:00Z</StartDateTime>
   <EndDateTime timeZoneCode="UTC">2013-04-01T13:20:00Z</EndDateTime>
  </RequestedFulfillmentPeriod>
  <DeliveryTerms>
   <DeliveryPriorityCode>1</DeliveryPriorityCode>
   <Incoterms>
    <ClassificationCode>FOB</ClassificationCode>
    <TransferLocationName>HAMBURG</TransferLocationName>
   </Incoterms>
  </DeliveryTerms>
  <Item actionCode="01">
   <BuyerID>1</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0001</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">10</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2013-03-28T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2013-04-28T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemText actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <ContentText>customer info for item 1</ContentText>
   </ItemText>
  </Item>
  <Text actionCode="01">
   <TextTypeCode>10024</TextTypeCode>
   <ContentText>General info for customer</ContentText>
  </Text>
 </CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

Example to update a customer quote:

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<CustomerQuote actionCode="02" ViewObjectIndicator="false"
salesEmployeePartyListCompleteTransmissionIndicator="true"
itemListCompleteTransmissionIndicator="true"
textListCompleteTransimissionIndicator="true">
<ID>1801</ID>
<Name languageCode="EN">CQ20121212</Name>
<EmployeeResponsibleParty>
<BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
<EmployeeID/>
</EmployeeResponsibleParty>
<Item actionCode="02">
<ID>10</ID>
<BuyerID>1</BuyerID>
<ItemRequestedScheduleLine>
<Quantity unitCode="EA">11</Quantity>
</ItemRequestedScheduleLine>
</Item>
<Item actionCode="01">
<BuyerID>2</BuyerID>
<ItemProduct>
<ProductID>MCF-0036</ProductID>
</ItemProduct>
<ItemRequestedScheduleLine>
<Quantity unitCode="EA">20</Quantity>
</ItemRequestedScheduleLine>
</Item>
<Text actionCode="02">
<TextTypeCode>10024</TextTypeCode>
<ContentText>changed general info for customer</ContentText>
</Text>
</CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

Description	Check sales quotes
Name	CheckMaintainBundle
Synchronous	yes

Description	Maintain sales quotes
Name	MaintainBundle
Synchronous	yes

Definition

To create or update (change, cancel or delete) a customer quote.

Business Context and Use

The request message of the operation MaintainBundle contains a BasicMessageHeader node element as well as a CustomerQuote node element that contains the customer quote data to be created or updated. The Customer Quote node can occur multiple times in the request message. This means that multiple quotes can be created and updated through a single web service request.

The response message type of the operation MaintainBundle contains log items, processing information, and a quote-specific node with ChangeStateID as well as ID and UUID of the customer quote.

With this request message, both internal and external customer quote can be created or updated. For internal quotes, the attribue ViewObjectIndicator shall be set to 'false' while for external quotes it shall be set to 'true'. Within one request message, only the same kind of quotes, either internal or external, are allowed.

Structure

The Customer Quote node contains all relevant information which is required for creation or update of a customer quote, such as

general information like identifications, name, posting date time
parties like buyer party, product recipient party
business terms for sales, pricing and delivery.
texts and attachments
item information like product and schedule line data.

General information

ID

The unique identifier of a customer quote. In creation case, it is automatically generated by the system. In update case, the ID (or UUID) must be provided.

UUID

The universally unique identifier of a customer quote. In creation case, it is automatically generated by the system. In update case, the UUID (or ID) must be provided.

BuyerID

The identifier of a customer quote assigned by the Buyer (external reference).

Name

The name of a customer quote.

ProcessingTypeCode

The processing type code is required if a customer special processing type code is used (instead of the default standard processing type code).

The special processing type code which is provided must be available in the system (configuration).

PostingDateTime

The posting date time of a customer quote is optional. If it is not provided in creation case, it will be filled with the creation date time.

DataOriginTypeCode

The DataOriginTypeCode which specifies the origin of the customer quote can be provided with the following values:

DataOriginTypeCode	Description
1	Manual data entry
2	B2B message
3	A2A message
4	Internet
5	E-Mail

ValidityPeriod

The validity period is optional and will be set by the system automatically in quote creation case if not provided.

CompleteSalesQuoteIndicator

If CompleteSalesQuoteIndicator is set to true, the action 'NotifyOfSalesOrderCreation' will be called to set the customer quote to 'completed' (if possible).

RequestConfirmationIssueIndicator

RequestConfirmationIssueIndicator is relevant only for internal customer quote.

If RequestConfirmationIssueIndicator is set to true, the action 'RequestConfirmationIssue' will be called to trigger automatically submit of the customer quote.

RequestExternalData

For document types using external pricing, this Parameter can be used to trigger the retrieval of external pricing data

PriceRecalculationTypeCode	Description
C	Keep Manually changed Rates

Currently only Value 'C' is supported.

RequestedFulfillmentPeriod

The requested fulfillment period is optional. If not provided it will be set by the system automatically in quote creation case.

SalesAndServiceBusinessArea

SalesAndServiceBusinessArea contains data such as sales organization, distribution channel, division and sales territory. These data are determined automatically if not provided in quote creation case.

PrimaryQuoteIndicator

The PrimaryQuoteIndicator can be set if the quote is linked via reference to an opportunity as successor. If the indicator is set, the

action UpdateOpportunity (via the UpdateOpportunityIndicator) can be used to push data to the opportunity.

UpdateOpportunityIndicator

Setting this parameter to true triggers the action UpdateOpportunity on the quote. It is only enabled, if the quote is also set as the primary quote for the corresponding opportunity.

Parties

BuyerParty

The BuyerParty is mandatory data of a customer quote and shall be provided in quote creation case.

In standard case, only the ID (BusinessPartnerInternalID) of the buyer party needs to be provided.

The AddressUUID is required if multiple addresses exist in the master data for the buyer party and if the default address is not used.

The Address data is required only if a document address has to be provided.

The ContactParty is optional. If not provided, the ContactParty will be determined automatically by the system.

Remark:

In quote update case, the BuyerParty shall not be provided once the quote has been submitted because change of the BuyerParty is then not allowed.

More than one ContactParty can be provided. In update case, all existing contact parties will be replaced by the provded contact parties if the contactPartyListCompleteTransmissionIndicator is set to true.

EmployeeResponsibleParty

The EmployeeResponsibleParty can be specified either with the BusinessPartnerInternalID or the EmployeeID.

If the EmployeeResponsibleParty is not provided, it will be determined automatically by the system.

ProductRecipientParty

The ProductRecipientParty can be specified exactly like the BuyerParty. It needs to be provided only if it is different to the BuyerParty.

BillToParty

The BillToParty can be specified exactly like the BuyerParty. It needs to be provided only if it is different to the BuyerParty.

PayerParty

The BillToParty can be specified exactly like the BuyerParty. It needs to be provided only if it is different to the BuyerParty or the BillToParty.

SalesEmployeeParty

The SalesEmployeeParty can be specified either with the BusinessPartnerInternalID or the EmployeeID.

More than one SalesEmployeeParty can be provided. If the salesEmployeePartyListCompleteTransmissionIndicator is set to true in quote update case, the existing sales employee parties in the quote will be replaced by the provided sales employee parties.

SalesPartnerParty

The SalesPartnerParty can be similarly specified like the BuyerParty (but without contact party).

The MainIndicator is to be set if the given Party shall be the main sales partner party.

If the salesPartnerListCompleteTransmissionIndicator is set to true in quote update case, the existing sales partner parties in the quote will be replaced by the given sales partner parties.

SalesUnitParty

The salesUnitParty is specified by its OrganisationalCentreID. In standard case, the sales unit is determined automatically by the system and therefore does not need to be provided.

CompetitorParty

The CompetitorParty can be specified exactly like the SalesPartnerParty.

If the competitorPartyListCompleteTransmissionIndicator is set to true in quote update case, the existing competitor parties in the quote will be replaced by the given competitor parties.

OtherParty

OtherParty can be specified by the BusinessPartnerInternalID together with its party role code.

The AddressUUID is required if multiple addresses exist in the master data for the party and if the default address is not used.

The Address data is required only if a document address has to be provided.

More than one OtherParty can be provided. If the otherPartyListCompleteTransmissionIndicator is set to true in quote update case, the existing other parties in the quote will be replaced by the given other parties.

Remark:

Z-party roles for the OtherParty need to be predefined in the system.
Other party can be any of the following special parties: sales employee party, approver party, competitor party or sales partner party. Therefore, if the ListCompleteTransmissionIndicator for the other party is set to "true", the ListCompleteTransmissionIndicator for these special parties shall not be set to 'true' again as this may lead to repeated deletion of one party which causes system exception. We recommend to use the ListCompleteTransmissionIndicator for the special parties, and not for the otherParty ( or always set it to 'false' ).

SellerParty

The SellerParty is a company and is specified with the OrganisationalCentreID. In standard case, the seller party is determined automatically by the system and therefore does not need to be provided.

DeliveryTerms

With DeliveryTerms the delivery priority code and incoterms can be specified. If not provided, these will be determined automatically by the system.

PricingTerms

With PricingTerms the currency code and price data time can be specified. If not provided, these will be determined automatically by the system.

SalesTerms

With SalesTerms the cancellation reason code can be provided to cancel the customer quote.

Remark: use only cancellation reason code values available in the system.

CashDiscountTerms

With CashDiscountTerms the code of the cash discount terms can be specified.

Remark: use only cash discount terms code values available in the system.

BusinessTransactionDocumentReference

The BusinessTransactionDocumentReference is specified by ID, UUID, TypeCode and RoleCode of the referenced business document.

The ID and UUID do not need to be provided both. However one of them must be given.

Allowed values for the RoleCode are 1 (Predecessor) and 2 (Successor).

More than one BusinessTransactionDocumentReference can be provided. If the businessTransactionDocumentReferenceListCompleteTransmissionIndicator is set to true in quote update case, the existing business transaction document references in the quote will be replaced by the given business transaction document references.

For external references which are linked to an external business transaction documents, the schemeID of the ID/UUID for the referenced business document shall be filled with the name of the logical system where the external document is located. Currently only references to external sales orders as follow-up document of the customer quote are supported. For internal references, the schemeID shall not be filled.

TotalValues

TotalValues is not relevant for internal customer quote. However it is mandatory for external customer quote.

With the TotalValues, the NetAmount and the PricingSubtotals can be provided.

Multiple pricing subtotals can be specified, however only TypeCodes with ListID '2' are allowed.

If the TotalValuesPricingSubtotalsCompleteTransmissionIndicator is set to true in quote update case, the existing pricing subtotals in the quote will be replaced by the given pricing subtotals.

Remark: all total values shall be provided in the same currency.

PriceCalculation

PriceCalculation is relevant only for customer quotes with internal pricing. They can be both internal quotes and external quotes.

With PriceCalculation, the main discount and price components can be created or updated.

Remark:

For update of price components, UUID of the price components is required.
The priceComponentListCompleteTransmissionIndicator shall not be set to true for internal quotes ( 'true' means deletion of all existing price components. This can lead to issue when some of them are not deletable ).

ExternalPriceCalculation

ExternalPriceCalculation is relevant for customer quotes with external pricing. They can be both internal quotes and external quotes.

Remark:

For price components, TypeCode is mandatory.
CalculatedAmount, InactivityReasonCode, ManuallyChangedIndicator, EffectiveIndicator and OriginCode are allowed only for external quotes.
For internal quotes, only prices are accepted ( Rate). CalculatedAmount, MajorLevelOrdinalNumberValue and MinorLevelOrdinalNumberValue are determined internally.
For update of price components, UUID of the price components is required.
The priceComponentListCompleteTransmissionIndicator shall not be set to true for internal quotes ( 'true' means deletion of all existing price components. This can lead to issue when some of them are not deletable ).

Text

With Text, texts can be provided for specified TextTypeCode.

Allowed TextTypeCode values are '10024' (Customer Information) and '10011' (Internal Comment).

If the textListCompleteTransmissionIndicator is set to true in quote update case, the existing texts in the quote will be replaced by the given texts.

Additionally the text creation date time can be given. The TextID can also be provided in quote update case, but is optional.

Remark: Texts for a specified text type can be provided either as plain text or as formatted text (if the formatted text is scoped in the BC configuration for the Sales Quote). Please be aware that the plain text and the formatted text shall have the same text content for the same text type. Therefore, please provide only one of them, but not both. If a formatted text is provided, the plain text will be derived from the given formatted text and filled automatically by the system.

Example for plain text:

   <Text actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <ContentText>This is customer information</ContentText>
    <CreationDateTime>2012-12-28T12:00:00.1234567Z</CreationDateTime>
   </Text>

Example for formatted text:

   <Text actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <FormattedText>&lt;p&gt;&lt;span style="text-decoration: underline;"&gt;&lt;em&gt;&lt;span style="font-size: 10pt;"&gt;This is customer information.&lt;/span&gt;&lt;/em&gt;&lt;/span&gt;&lt;/p&gt;</FormattedText>
    <CreationDateTime>2015-09-01T12:00:00.1234567Z</CreationDateTime>
   </Text>

AttachmentFolder

With AttachmentFolder, attachments can be provided.

The allowed attachment TypeCode for customer quote is '10001' (Standard attachment).

The allowed CategoryCode values are '2' (Document attachment) and '3' (Link attachment).

Multiple attachments can be provided within the AttachmentFolder. If the DocumentListCompleteTransmissionIndicator is set to true in quote update case, the existing attachments in the quote will be replaced by the given attachments.

The Document UUID can be provided in quote update case, but is optional.

Item

The Item node contains item special information such as product data, schedule line data, item texts and item attachments.

Example:

  <Item actionCode="01">
   <BuyerID>1</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0001</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">10</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2013-03-28T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2013-04-28T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemText actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <ContentText>Item Text for item 1</ContentText>
    <CreationDateTime>2012-12-28T12:00:00.1234567Z</CreationDateTime>
   </ItemText>
  </Item>

ID

The item ID is required in update case of a quote item. In creation case, it is automatically generated by the system if not provided.

BuyerID

The item BuyerID can be specified, but is optional.

PostingDateTime

The item PostingDateTime is optional. If not provided in item creation case, it will be generated by the system.

ItemProduct

The ItemProduct can be specified by one of the following IDs: ProductInternalID, ProductBuyerID, ProductStandardID and ProductID.

ProductID is the so-called EnteredProductID which allows any of the IDs (ProductInternalID, ProductBuyerID or ProductStandardID).

If more than one IDs are provided, it shall be made sure that these IDs are available IDs of the same product.

ItemRequestedScheduleLine

With ItemRequestedScheduleLine the quantity and the requested schedule line date time can be provided.

In item creation case, if the quantity is not given, the quantity will be filled with minimum quantity defined in the product master data. If the DateTimePeriod is not given, it will be determined by the system.

The ID must be provided in item update case, but is optional in item creation case.

ItemProductRecipientParty

The ItemProductRecipientParty is required only if it is not the same as the ProductRecipientParty.

Specification of the ItemProductRecipientParty is the same as the ProductRecipientParty.

ItemSalesTerms

With ItemSalesTerms the cancellation reason code can be provided to cancel the customer quote item.

Remark: the given cancellation reason code must be available in the system.

ItemTotalValues

ItemTotalValues is not relevant for internal customer quote. However it is mandatory for external customer quote.

With the ItemTotalValues, the item NetAmount and the PricingSubtotals can be specified.

Multiple pricing subtotals can be given, however only TypeCodes with ListID '2' are allowed.

If the TotalValuesPricingSubtotalsCompleteTransmissionIndicator is set to true in item update case, the existing pricing subtotals in the quote item will be replaced by the given pricing subtotals.

Remark: all total values shall be provided in the same currency.

ItemPriceCalculation

ItemPriceCalculation is relevant only for customer quotes with internal pricing. They can be both internal quotes and external quotes.

With PriceCalculation, the item main price, main discount and price components can be created or updated.

Remark:

For update of price components, UUID of the price components is required.
The itemPriceComponentListCompleteTransmissionIndicator shall not be set to true for internal quotes ( 'true' means deletion of all existing price components. This can lead to issue when some of them are not deletable ).

ItemExternalPriceCalculation

ItemExternalPriceCalculation is relevant only for customer quotes with external pricing. They can be both internal quotes and external quotes.

Remark:

For price components, TypeCode is mandatory.
CalculatedAmount, InactivityReasonCode, ManuallyChangedIndicator, EffectiveIndicator and OriginCode are allowed only for external quotes.
For internal quotes, only prices are accepted ( Rate). CalculatedAmount, MajorLevelOrdinalNumberValue and MinorLevelOrdinalNumberValue are determined internally.
For update of price components, UUID of the price components is required.
The itemPriceComponentListCompleteTransmissionIndicator shall not be set to true for internal quotes ( 'true' means deletion of all existing price components. This can lead to issue when some of them are not deletable ).

ItemBusinessTransactionDocumentReference

The ItemBusinessTransactionDocumentReference is specified by ID, UUID, TypeCode, RoleCode and ItemID, ItemUUID of the referenced business document.

The ID and UUID donot need to be provided both. However one of them must be given. The same is for the ItemID and ItemUUID, one of them must be given (if relevant).

Allowed values for the RoleCode are 1 (Predecessor) and 2 (Successor).

More than one BusinessTransactionDocumentReference can be provided. If the itemBTDReferenceListCompleteTransmissionIndicator is set to true in item update case, the existing item business transaction document references in the quote item will be replaced by the given item business transaction document references.

Remark: if ItemBusinessTransactionDocumentReference is provided, the corresponding BusinessTransactionDocumentReference must also be provided.

Example for an internal reference (to opportunity)

   <ItemBusinessTransactionDocumentReference>
    <ID>4990</ID>
    <TypeCode>72</TypeCode>
    <ItemID>10</ItemID>
    <ItemTypeCode>43</ItemTypeCode>
    <RoleCode>1</RoleCode>
   </ItemBusinessTransactionDocumentReference>

Example for an external reference (to sales order in the external system QNQCLNT004)

   <ItemBusinessTransactionDocumentReference>
    <ID schemeID="QNQCLNT004">4990</ID>
    <TypeCode>114</TypeCode>
    <ItemID>10</ItemID>
    <ItemTypeCode>28</ItemTypeCode>
    <RoleCode>2</RoleCode>
   </ItemBusinessTransactionDocumentReference>

ItemText

With ItemText, item texts can be provided for specified TextTypeCode. A

Allowed TextTypeCode values are '10024' (Customer Information) and '10011' (Internal Comment).

If the textListCompleteTransmissionIndicator is set to true in quote update case, the existing texts in the quote will be replaced by the given texts.

Additionally the text creation date time can be given. The TextID can also be provided in quote update case, but is optional.

ItemAttachmentFolder

With ItemAttachmentFolder, item attachments can be provided.

The allowed attachment TypeCode for customer quote is '10001' (Standard attachment).

The allowed CategoryCode values are '2' (Document attachment) and '3' (Link attachment).

Multiple attachments can be provided within the AttachmentFolder. If the DocumentListCompleteTransmissionIndicator is set to true in item update case, the existing attachments in the quote item will be replaced by the given attachments.

The Document UUID can be provided in item update case, but is optional.

Examples

Simple quote creation

The following xml message requests creation of a new quote with one item.

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <CustomerQuote actionCode="01" ViewObjectIndicator="false">
  <BuyerID>111</BuyerID>
  <Name languageCode="EN">Quote20121228</Name>
  <BuyerParty>
   <BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
  </BuyerParty>
  <EmployeeResponsibleParty>
   <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
  </EmployeeResponsibleParty>
  <RequestedFulfillmentPeriod>
   <StartDateTime timeZoneCode="UTC">2014-05-31T13:20:00Z</StartDateTime>
   <EndDateTime timeZoneCode="UTC">2014-08-01T13:20:00Z</EndDateTime>
  </RequestedFulfillmentPeriod>
  <DeliveryTerms>
   <DeliveryPriorityCode>1</DeliveryPriorityCode>
   <Incoterms>
    <ClassificationCode>FOB</ClassificationCode>
    <TransferLocationName>HAMBURG</TransferLocationName>
   </Incoterms>
  </DeliveryTerms>
  <Item actionCode="01">
   <BuyerID>1</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0001</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">10</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2014-06-01T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2014-06-30T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemText actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <ContentText>Item Text for item 1</ContentText>
    <CreationDateTime>2012-12-28T12:00:00.1234567Z</CreationDateTime>
   </ItemText>
  </Item>
  <Text actionCode="01">
   <TextTypeCode>10024</TextTypeCode>
   <TextID/>
   <CreationDateTime>2012-12-28T12:00:00.1234567Z</CreationDateTime>
   <ContentText>Header Text</ContentText>
  </Text>
 </CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

Simple quote update

This xml message requests update of the customer quote 153 with the following changes:

change of the incoterms
change of the item 1 (ID 10) on Product and quantity
creation of item 2
change of the Customer Information text

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <CustomerQuote actionCode="02" ViewObjectIndicator="false"
 itemListCompleteTransmissionIndicator="true" textListCompleteTransimissionIndicator="false">
   <ID>153</ID>
  <DeliveryTerms>
   <Incoterms>
    <ClassificationCode>FOB</ClassificationCode>
    <TransferLocationName>BERLIN</TransferLocationName>
   </Incoterms>
  </DeliveryTerms>
  <Item actionCode="02">
   <ID>10</ID>
   <ItemProduct>
    <ProductID>MCF-0001</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">11</Quantity>
   </ItemRequestedScheduleLine>
  </Item>
  <Item actionCode="01">
   <BuyerID>2</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0036</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">20</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2014-06-01T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2014-06-30T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemText actionCode="01">
    <TextTypeCode>10024</TextTypeCode>
    <ContentText>New item </ContentText>
   </ItemText>
  </Item>
  <Text actionCode="02">
   <TextTypeCode>10024</TextTypeCode>
   <TextID/>
   <CreationDateTime>2012-12-28T12:00:00.1234567Z</CreationDateTime>
   <ContentText>The Quote has 2 items now</ContentText>
  </Text>
 </CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

external quote creation

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <CustomerQuote actionCode="01" ViewObjectIndicator="true">
  <BuyerID>101</BuyerID>
  <Name languageCode="EN">EXT-QUOTE-20130101</Name>
  <BuyerParty>
   <BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID>
  </BuyerParty>
  <SalesEmployeeParty>
   <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
   <MainIndicator>true</MainIndicator>
  </SalesEmployeeParty>
  <EmployeeResponsibleParty>
   <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID>
  </EmployeeResponsibleParty>

  <Item actionCode="01">
   <BuyerID>1</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0001</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">10</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2013-03-28T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2013-04-28T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemTotalValues actionCode="01">
    <NetAmount currencyCode="USD">1000</NetAmount>
   </ItemTotalValues>
  </Item>

  <TotalValues actionCode="01">
   <NetAmount currencyCode="USD">1000</NetAmount>
  </TotalValues>

 </CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

External quote update

This xml message requests update of the external quote 159 for the following changes:

change of the sales employee party
deletion of the item 10
creation of a new item
change of the total values

<n0:CustomerQuoteBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
 <CustomerQuote actionCode="02" ViewObjectIndicator="true"
  salesEmployeePartyListCompleteTransmissionIndicator="true">
  <ID>159</ID>
  <BuyerID>101</BuyerID>
  <Name languageCode="EN">EXT-QUOTE-20130101</Name>

  <SalesEmployeeParty>
   <BusinessPartnerInternalID>MC2854</BusinessPartnerInternalID>
   <MainIndicator>true</MainIndicator>
  </SalesEmployeeParty>

  <Item actionCode="03">
   <ID>10</ID>
   <ItemTotalValues actionCode="01">
    <NetAmount currencyCode="USD">1000</NetAmount>
   </ItemTotalValues>
  </Item>

  <Item actionCode="01">
   <BuyerID>2</BuyerID>
   <ItemProduct>
    <ProductID>MCF-0036</ProductID>
   </ItemProduct>
   <ItemRequestedScheduleLine>
    <Quantity unitCode="EA">50</Quantity>
    <DateTimePeriod>
     <StartDateTime timeZoneCode="UTC">2013-03-28T12:00:00.1234567Z</StartDateTime>
     <EndDateTime timeZoneCode="UTC">2013-04-28T12:00:00.1234567Z</EndDateTime>
    </DateTimePeriod>
   </ItemRequestedScheduleLine>
   <ItemTotalValues actionCode="01">
    <NetAmount currencyCode="USD">2000</NetAmount>
   </ItemTotalValues>
  </Item>

  <TotalValues actionCode="01">
   <NetAmount currencyCode="USD">2000</NetAmount>
  </TotalValues>

 </CustomerQuote>
</n0:CustomerQuoteBundleMaintainRequest_sync_V1>

Inbound Service CustomerQuoteProcessingManageCustomerQuoteIn

Overview

Public Solution Model

Documentation

Definition

Business Context and Use

Prerequisites

Constraints and Integrity Conditions

General Rules for Using this Web Service

Check Maintain Bundle vs. Maintain Bundle

Action Code

List Processing

Empty and Missing Elements

Communication Timeout

Message Header

Change State ID

Object Node Sender Technical Identifier

Response Message

More Information

General Information

Scenarios

Operation Manage Customer Quoter In Check Maintain as Bundle

Overview

Public Solution Model

Documentation

Definition

Business Context and Use

Operation Manage Customer Quote In Maintain as Bundle

Overview

Public Solution Model

Documentation

Definition

Business Context and Use

Structure

General information

ID

UUID

BuyerID

Name

ProcessingTypeCode

PostingDateTime

DataOriginTypeCode

ValidityPeriod

CompleteSalesQuoteIndicator

RequestConfirmationIssueIndicator

RequestExternalData

RequestedFulfillmentPeriod

SalesAndServiceBusinessArea

PrimaryQuoteIndicator

UpdateOpportunityIndicator

Parties

BuyerParty

EmployeeResponsibleParty

ProductRecipientParty

BillToParty

PayerParty

SalesEmployeeParty

SalesPartnerParty

SalesUnitParty

CompetitorParty

OtherParty

SellerParty

DeliveryTerms

PricingTerms

SalesTerms

CashDiscountTerms

BusinessTransactionDocumentReference

TotalValues

PriceCalculation

ExternalPriceCalculation

Text

AttachmentFolder

Item

ID

BuyerID

PostingDateTime

ItemProduct

ItemRequestedScheduleLine

ItemProductRecipientParty

ItemSalesTerms