| Description | Query Appointment Activities |
| Name | QueryAppointmentActivityIn |
| 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 |
| Deploymnent Unit Description | Foundation |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Deprecated |
An interface to query appointment activity data.
The web service interface Query Appointment Activity enables you to connect external applications to your solution and to query and read appointment activities within your system. The web service interface is relevant if your company wants to access and manage aAppointment activity data from external applications.
The web service interface Query Appointment Activity offers the operation FindByElements.
Here is an example of a simple web service request to get all appointment activities with a certain subject name:
<n0:AppointmentActivityByElementsQuery_Sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <AppointmentActivitySelectionByElements> <SelectionByID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>*</LowerBoundaryIdentifier> <UpperBoundaryInternalID></UpperBoundaryInternalID> </SelectionByID> <SelectionByName> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryName>A2X Example*</LowerBoundaryName> <UpperBoundaryName></UpperBoundaryName> </SelectionByName> </AppointmentActivitySelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>25</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> </ProcessingConditions> </n0:AppointmentActivityByElementsQuery_Sync_V1>
Query 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 (external application) is responsible for ensuring reasonable sizes for mass operations.
The query processing conditions specify how to process a query with respect to the maximum number of hits to be returned.
Query request messages provide the following processing parameters:
Query hits maximum number value (element name QueryHitsMaximumNumberValue): Maximum number of hits to be returned by an inquiry.
Query hits unlimited indicator (element name QueryHitsUnlimitedIndicator): Indicates whether the maximum number of hits to be returned by an inquiry is unlimited or not.
Last returned object ID (element name LastReturnedObjectID): Identifies the last object returned by a previous inquiry.
Note: If QueryHitsUnlimitedIndicator = true, QueryHitsMaximumNumberValue must not be filled.
Query response messages provide the following elements:
Returned query hits number value (element name ReturnedQueryHitsNumberValue): The number of hits returned by an inquiry.
More hits available indicator (element name MoreHitsAvailableIndicator): Indicates whether there are more than ReturnedQueryHitsNumberValue hits matching the selection criteria or not.
Last returned object ID (element name LastReturnedObjectID): Identifies the last object returned by this inquiry.
Note: Processing conditions can be used for the paging of query results. However, it is crucial not to change the query selection parameters from request to request. Otherwise, the query result might change.
Query selection parameters are mainly exposed as select options or ranges with an inclusion/exclusion code, interval boundary type code, lower boundary value, and upper boundary value.
The inclusion/exclusion code (element name InclusionExclusionCode) specifies the inclusion or exclusion of a set into a result set.
| Inclusion Exclusion Code | Description |
|---|---|
| E | Excluding |
| I | Including |
The interval boundary type code (element name IntervalBoundaryTypeCode) is used to describe intervals by their boundaries. Depending on the operator, the lower boundary value or both boundary values are relevant.
| Interval Boundary Type Code | Name | Description | |
|---|---|---|---|
| 1 | Equal to | Single value | = X |
| 3 | Between | Interval with open lower and open upper boundary | (X, Y) |
| 6 | Less than | Interval with unlimited lower and open upper boundary | < X |
| 7 | Less Than or Equal to | Interval with unlimited lower and closed upper boundary | <= X |
| 8 | Greater Than | Interval with open lower and unlimited upper boundary | > X |
| 9 | Greater Than or Equal to | Interval with closed lower and unlimited upper boundary | = X |
Requested elements (element name RequestedElements) enable web service consumer to reduce the size of query response messages. Therefore, transmission and response times are reduced, thus avoiding timeouts.
Requested elements contain transmission request codes for controlling the transmission of corresponding query response node elements.
The transmission request codes are modeled as xml attributes following the syntax: <element name>TransmissionRequestCode.
The prefix <element name> is equivalent to the name of the node element in the response message to which the transmission request code applies.
| Transmission Request Code | Name | Description |
|---|---|---|
| 1 | Complete Structure | The node element and all its elements, its child node elements and all their elements will be returned. |
| 2 | Complete Node | The node element and all its elements will be returned. |
| 3 | Node with Key Elements | The node element and its key elements will be returned (not supported by all web service interfaces). |
| 4 | Excluded Node | The node element and its child node elements will not be returned. |
The transmission request code is optional. If no transmission request code is modeled or provided by the service consumer, then the following rules apply:
If no transmission request code is provided at all, then the response message contains all data.
If the transmission request code of the parent node element is 1, then its sub-node elements for which no transmission request code is specified are defaulted by 1.
If the transmission request code of the parent node element is 2 or 3, then its sub-node elements for which no transmission request code is specified are defaulted by 4.
If the transmission request code of the parent node element is 4, then its sub-node elements are not returned anyway.
The structure of the query response message consists of three parts:
A business document-specific part containing the returned business documents
Processing conditions
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:
Find Appointment Activity
With a certain party
With a certain name
Etc.
Example to find Appointment activites with a certain activity party:
<n0:AppointmentActivityByElementsQuery_Sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <AppointmentActivitySelectionByElements> <SelectionByActivityPartyBusinessPartnerInternalID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryInternalID>MDEC9785</LowerBoundaryInternalID> <UpperBoundaryInternalID></UpperBoundaryInternalID> </SelectionByActivityPartyBusinessPartnerInternalID> </AppointmentActivitySelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>25</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> </ProcessingConditions> <RequestedElements AppointmentActivityTransmissionRequestCode="1"> </RequestedElements> </n0:AppointmentActivityByElementsQuery_Sync_V1>
| Description | Find appointment activities |
| Name | FindByElements |
| Synchronous | yes |
| Release Status | Deprecated |
A query to find appointment activities.
The request message of the operation FindByElements contains the QueryByElements that groups all possible selection parameters.
| Selection Parameter | Remark |
|---|---|
| SelectionByIdentifier | Selection by ID |
| SelectionByActivityPartyBusinessPartnerInternalID | Selection by internal Business Partner ID of the Activity Party |
| SelectionByName | Selection by name (subject) |
| SelectionByCreatedDateTime | Selection by creation date and time |
| SelectionByLastChangeDateTime | Selection by last change date and time |
| SelectionByReportedDateTime | Selection by reported date and time (start date and time if available) |
| SelectionByBusinessPartnerInternalID | Selection by internal Business Partner ID independent of any party role |
The response contains the list of found appointment activities, log items, and processing conditions.
For parties like the ProcessorParty, EmployeeResponsibleParty, etc., the business partner internal ID is returned. Other IDs are currently not supported.
Show full documentation
Show full documentation