| Description | Manage Opportunities |
| Name | ManageOpportunityIn |
| Namespace | http://sap.com/xi/AP/CRM/Global |
| Process Component Description | Opportunity Processing |
| Process Component Name | OpportunityProcessing |
| Process Component Namespace | http://sap.com/xi/AP/CRM/Global |
| Deployment Unit Description | Customer Relationship Management |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to replicate opportunity data from a source system or file to a target system.
The Manage Opportunity In inbound service interface groups operations that receive imported and structured opportunity data from a source, such as a system or a file. This data is replicated or migrated to a target system either for a single opportunity or for several opportunities in a bundle.
The web service interface Manage Opportunity In offers the operations MaintainBundle and CheckMaintainBundle.
Here is an example of a simple web service request:
Show full documentation
Show full documentation
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0ab000c99</ID>
</BasicMessageHeader>
<Opportunity actionCode="01">
<ObjectNodeSenderTechnicalID>9B6B11DA-A126-4ADA-8DA7-35FB32751A54</ObjectNodeSenderTechnicalID>
<ChangeStateID>20130304073654.7493750</ChangeStateID>
<Name>A2X Test Opp</Name>
<PriorityCode>3</PriorityCode>
<GroupCode>0023</GroupCode>
<OriginTypeCode>001</OriginTypeCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
<SalesForecast>
<ExpectedRevenueAmount currencyCode="USD">100</ExpectedRevenueAmount>
<ExpectedProcessingDatePeriod>
<StartDate>2013-03-03</StartDate>
<EndDate>2013-04-04</EndDate>
</ExpectedProcessingDatePeriod>
</SalesForecast>
<SalesCycle>
<SalesCycleCode>001</SalesCycleCode>
<SalesCyclePhaseCode>001</SalesCyclePhaseCode>
</SalesCycle>
<ProspectParty>
<PartyID>MC9785</PartyID>
<ContactPerson/>
</ProspectParty>
<EmployeeResponsibleParty>
<PartyID>mc2471</PartyID>
</EmployeeResponsibleParty>
</Opportunity>
</n0:OpportunityBundleMaintainRequest_sync>
Existence of referenced business data:
The following business data are only referenced and will not be created by the service operations. They must already exist in the system already at the time the web service is called:
Business partners and related projections like prospects, employees, etc.
Products, Materials, Services
Campaigns
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
Create Opportunity
The MaintainBundle operation is used to create an opportunity.
Update Opportunity
The MaintainBundle operation is used to update an opportunity.
Delete Opportunity
The MaintainBundle operation is used to delete opportunity as well.
An example of a web service request to create an opportunity, specifying the mandatory and the Party information:
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0ab000c99</ID>
</BasicMessageHeader>
<Opportunity actionCode="01">
<ObjectNodeSenderTechnicalID>9B6B11DA-A126-4ADA-8DA7-35FB32751A54</ObjectNodeSenderTechnicalID>
<ChangeStateID>20130304073654.7493750</ChangeStateID>
<Name>A2X Test Opp</Name>
<PriorityCode>3</PriorityCode>
<GroupCode>0023</GroupCode>
<OriginTypeCode>001</OriginTypeCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
<SalesForecast>
<ExpectedRevenueAmount currencyCode="USD">100</ExpectedRevenueAmount>
<ExpectedProcessingDatePeriod>
<StartDate>2013-03-03</StartDate>
<EndDate>2013-04-04</EndDate>
</ExpectedProcessingDatePeriod>
</SalesForecast>
<SalesCycle>
<SalesCycleCode>001</SalesCycleCode>
<SalesCyclePhaseCode>001</SalesCyclePhaseCode>
</SalesCycle>
<ProspectParty>
<PartyID>MC9785</PartyID>
<ContactPerson/>
</ProspectParty>
<EmployeeResponsibleParty>
<PartyID>mc2471</PartyID>
</EmployeeResponsibleParty>
</Opportunity>
</n0:OpportunityBundleMaintainRequest_sync>
An example of creating an opportunity with the Party and the Item Product information:
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID>00000000000102dcade9bcb0ab000c99</ID>
</BasicMessageHeader>
<Opportunity actionCode="01">
<ObjectNodeSenderTechnicalID>9B6B11DA-A126-4ADA-8DA7-35FB32751A54</ObjectNodeSenderTechnicalID>
<ChangeStateID>20130304073654.7493750</ChangeStateID>
<Name>A2X Test Opp</Name>
<PriorityCode>3</PriorityCode>
<GroupCode>0023</GroupCode>
<OriginTypeCode>001</OriginTypeCode>
<LifeCycleStatusCode>1</LifeCycleStatusCode>
<SalesForecast>
<ExpectedRevenueAmount currencyCode="USD">100</ExpectedRevenueAmount>
<ExpectedProcessingDatePeriod>
<StartDate>2013-03-03</StartDate>
<EndDate>2013-04-04</EndDate>
</ExpectedProcessingDatePeriod>
</SalesForecast>
<SalesCycle>
<SalesCycleCode>001</SalesCycleCode>
<SalesCyclePhaseCode>001</SalesCyclePhaseCode>
</SalesCycle>
<ProspectParty>
<PartyID>MC9785</PartyID>
<ContactPerson/>
</ProspectParty>
<EmployeeResponsibleParty>
<PartyID>mc2471</PartyID>
</EmployeeResponsibleParty>
<Item actionCode = "01">
<Quantity unitCode="ea">4</Quantity>
<ItemProduct>
<MaterialInternalID>MCF-0001</MaterialInternalID>
</ItemProduct>
</Item>
</Opportunity>
</n0:OpportunityBundleMaintainRequest_sync>
An example of updating an opportunity with the basic information:
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID/> </BasicMessageHeader> <Opportunity actionCode="02"> <ObjectNodeSenderTechnicalID/> <ChangeStateID/> <ID>45</ID> <Name>A2X Test Opp Modified</Name> </Opportunity> </n0:OpportunityBundleMaintainRequest_sync>
An example of updating an opportunity with the Sales Cycle and the Sales Forecast information:
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<ID/>
</BasicMessageHeader>
<Opportunity actionCode="02">
<ObjectNodeSenderTechnicalID/>
<ChangeStateID/>
<ID>45</ID>
<Name>A2X Test Opp Re-modified</Name>
<PriorityCode>1</PriorityCode>
<GroupCode>0023</GroupCode>
<OriginTypeCode>001</OriginTypeCode>
<LifeCycleStatusCode>2</LifeCycleStatusCode>
<SalesForecast>
<ExpectedRevenueAmount currencyCode="USD">100</ExpectedRevenueAmount>
<ExpectedProcessingDatePeriod>
<StartDate>2013-03-03</StartDate>
<EndDate>2013-04-04</EndDate>
</ExpectedProcessingDatePeriod>
</SalesForecast>
<SalesCycle>
<SalesCycleCode>001</SalesCycleCode>
<SalesCyclePhaseCode>001</SalesCyclePhaseCode>
</SalesCycle>
</Opportunity>
</n0:OpportunityBundleMaintainRequest_sync>
An example of deleting an opportunity:
<n0:OpportunityBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID/> </BasicMessageHeader> <Opportunity actionCode="03"> <ObjectNodeSenderTechnicalID/> <ChangeStateID/> <ID>43</ID> </Opportunity> </n0:OpportunityBundleMaintainRequest_sync>
| Description | Maintain opportunities |
| Name | MaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To maintain one or more opportunities using imported and structured data.
The Manage Opportunity In Maintain as Bundle inbound operation maintains one or more opportunities based on the opportunity data. This data is replicated or migrated from a source, a system or a file, to a target system.
| Description | Check opportunities |
| Name | CheckMaintainBundle |
| Synchronous | yes |
| Release Status | Released |
To check whether one or more opportunities can be maintained using imported and structured data.
The Manage Oppportunity In Check Maintain as Bundle inbound operation checks whether one or more opportunities can be maintained in the target system, based on the opportunity data received from a source, a system or a file.