Description | Manage Task Activities |
Name | ManageTaskActivityIn |
Namespace | http://sap.com/xi/A1S/Global |
Process Component Description | Activity Management |
Process Component Name | ActivityManagement |
Process Component Namespace | http://sap.com/xi/AP/FO/Activity/Global |
Deployment Unit Description | Foundation |
Endpoint Activation | By Scoping of Process Component | Operations |
Release Status | Released |
An interface to migrate activity task data from a source system or file.
The Web service interface Manage Activity Task In enables you to connect external applications to your SAP system and to create and edit activity tasks in your system. The web service interface Manage Activity Task In is relevant if your company wants to access and manage activity task data from external applications.
The web service interface Manage Activity Task In offers the operations MaintainBundle and CheckMaintainBundle.
Here is an example of a simple web service request:
<n0:TaskActivityBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa000c68</ID> </BasicMessageHeader> <ActivityTask actionCode="01"> <Name>Meeting Preperation</Name> <PriorityCode>1</PriorityCode> <InformationSensitivityCode>1</InformationSensitivityCode> <ScheduledPeriod> <StartDateTime timeZoneCode="CET">2012-06-28T12:00:00.0000000Z</StartDateTime> <EndDateTime timeZoneCode="CET">2012-06-30T12:00:00.0000000Z</EndDateTime> </ScheduledPeriod> <Text actionCode="01"> <TextTypeCode>10002</TextTypeCode> <ContentText>Meeting Preparation for a new customer</ContentText> <CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime> </Text> <ProcessorParty> <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID> </ProcessorParty> <EmployeeResponsibleParty> <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID> </EmployeeResponsibleParty> <MainActivityParty> <BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID> </MainActivityParty> </ActivityTask> </n0:TaskActivityBundleMaintainRequest_sync_V1>
Existence of referenced master data or business documents:
Employee, customer, and so on to name processor, or employee responsible for related customers
Campaigns or other business documents to reference
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 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. |
05 | Remove; the system deletes the node element. If the node element does not exist, the system does not send an error message. |
06 | No Action; the system does not change the node element. |
Default action code: 04 (Save).
Note: Action code 04 (Save) creates business documents if the system could not 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, in order to avoid accidental creation of duplicate business documents.
The processing of node elements with cardinality > 1 (for example a list of descriptions in different languages or a list of telephone numbers) can be controlled using List Complete Transmission Indicators (LCTI). The LCTI indicates whether a list of node elements is completely transmitted. 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 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 removed. If no node element is transmitted, the complete list is 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.
Optional leaf elements in request messages that are not transmitted within a web service request are not changed in corresponding business documents.
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 causes communication timeouts. The web service consumer is responsible for ensuring reasonable sizes of data for mass operations.
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.
Using change state identifier (element name ChangeStateID), external applications can enforce 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.
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>
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
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
Create a Task
The MaintainBundle operation is used to create a task activity for an employee
Update a Task
The MaintainBundle operation is used to update existing task activity to set the completion rate
Here is an example web service request to create a task activity by employee MC2471 which is related to a customer MC9785:
<n0:TaskActivityBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa000c68</ID> </BasicMessageHeader> <ActivityTask actionCode="01"> <Name>Meeting Preperation for Customer (Silverstar) MC9785</Name> <PriorityCode>1</PriorityCode> <InformationSensitivityCode>1</InformationSensitivityCode> <Text actionCode="01"> <TextTypeCode>10002</TextTypeCode> <ContentText>Meeting Preparation for a new customer</ContentText> <CreationDateTime>2006-03-28T12:00:00.1234567Z</CreationDateTime> </Text> <ProcessorParty> <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID> </ProcessorParty> <EmployeeResponsibleParty> <BusinessPartnerInternalID>MC2471</BusinessPartnerInternalID> </EmployeeResponsibleParty> <MainActivityParty> <BusinessPartnerInternalID>MC9785</BusinessPartnerInternalID> </MainActivityParty> </ActivityTask> </n0:TaskActivityBundleMaintainRequest_sync_V1>
When the employee has confirmed a completion rate of 50%, the task activity can be updated as follows:
<n0:TaskActivityBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa021c99</ID> </BasicMessageHeader> <ActivityTask actionCode="02"> <UUID>00163e02-8b2e-1ed1-aeaa-6d7e616e72fd</UUID> <CompletionPercent>50</CompletionPercent> </ActivityTask> </n0:TaskActivityBundleMaintainRequest_sync_V1>
Attention: The party ID and party role are not unique keys for a party instance. Thus, for parties with 1:n cardinality, in case of updates (change and delete) the CompleteTransmissionIndicator needs to be set and the whole list of updated parties has to be provided that should replace the existing list of parties.
Example data for ReferenceParty:
List of existing ReferenceParty to be changed:
MCP6049
MCPB9785
MCPC9785
What do we want to achieve?
Delete party MCP6049
Keep party MCPB9785
Change party MCPC9785 -> MCP17101
Add party MCP17102
Add party MDECP9786
Due to the fact that no unique identification of a party instance is possible using party ID and party role, the referencePartyListCompleteTransimissionIndicator is to be set to "true". Then the behavior will be as follows: The list of parties is completely transmitted. Hence, all parties that are not transmitted are removed. If no party is transmitted, the complete list is removed.
In the following example, the desired list of parties is to be provided:
MCPB9785
MCP17101
MCP17102
MDECP9786
The respective XML document to achieve this looks like the following:
<n0:TaskActivityBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa000c68</ID> </BasicMessageHeader> <ActivityTask actionCode="02" referencePartyListCompleteTransimissionIndicator="true"> <ID>325</ID> <ReferenceParty> <BusinessPartnerInternalID>MCPB9785</BusinessPartnerInternalID> </ReferenceParty> <ReferenceParty> <BusinessPartnerInternalID>MCP17101</BusinessPartnerInternalID> </ReferenceParty> <ReferenceParty> <BusinessPartnerInternalID>MCP17102</BusinessPartnerInternalID> </ReferenceParty> <ReferenceParty> <BusinessPartnerInternalID>MDECP9786</BusinessPartnerInternalID> </ReferenceParty> </ActivityTask> </n0:TaskActivityBundleMaintainRequest_sync_V1>
In case a new party instance has to be appended to the existing list of parties, this can be achieved by just providing the new party and setting the ListCompleteTransimissionIndicator to "false".
Example data:
List of existing parties:
MCP6049
MCPB9785
MCPC9785
What do we want to achieve?
Keep MCP6049
Keep MCPB9785
Keep MCPC9785
Add MCP8300
Add MCP60500
In the following example, just the list of new parties has to be provided:
MCP8300
MCP60500
The respective XML document to achieve this looks like the following:
<n0:TaskActivityBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>00000000000102dcade9bcb0aa000c68</ID> </BasicMessageHeader> <ActivityTask actionCode="02" referencePartyListCompleteTransimissionIndicator="false"> <!-- append new party instances with LCTI = "false" --> <ID>325</ID> <ReferenceParty> <BusinessPartnerInternalID>MCP8300</BusinessPartnerInternalID> </ReferenceParty> <ReferenceParty> <BusinessPartnerInternalID>MCP60500</BusinessPartnerInternalID> </ReferenceParty> </ActivityTask> </n0:TaskActivityBundleMaintainRequest_sync_V1>
Description | Maintain task activities |
Name | MaintainBundle |
Synchronous | yes |
Release Status | Released |
No documentation available.
Description | Check task activities |
Name | CheckMaintainBundle |
Synchronous | yes |
Release Status | Released |
No documentation available.