To find tracked processes according to specific criteria, such as header, properties, or tracking ID details.
Entity Type |
Service Operation |
Software Component Version |
SCEMSRV 7.01 |
released |
|
TrackedProcessSimpleByElementsQueryResponse_In |
|
http://sap.com/xi/EM/Global |
|
SCM-EM-MGR-CON |
|
Web Service Definition (Back End) |
/SAPTRX/TRACKEDPROCESSSIMPLEBY |
inbound |
|
synchronous |
|
no |
|
not applicable |
|
true |
The Find Tracked Process by elements inbound operation searches for tracked processes that match specific search criteria.
Consider a purchasing scenario that begins with the creation of a purchase order for a material. The purchase order can be created with reference to a purchase requisition, or it can be created without reference to any prior document. If the purchase order is subject to a tracked process, the progress of the purchase order (from creation through to payment) can be tracked at line item level.To determine if a tracked process exists for this purchasing scenario, you can search all available tracked processes using the Find Tracked Process by elements operation. This operation returns tracked processes that match the criteria specified, such as header, properties, or tracking ID. The details of an individual process can be investigated using the Read Tracked Process operation.
An individual tracked process can be queried using the Read Tracked Process operation.
For more information about related operations, see the Tracked Process business object.
You use the Find Tracked Process by elements operation to search tracked processes in the back-end system, according to the input values defined. The tracked process selection entity code is required for all tracked process queries.
In addition, the input values for this operation can include the following tracked process data:
Header
Event notification header
Control properties
Information properties
Extension properties, these properties are relevant for query performance
Status
Expected event
Tracking ID
The input values can be provided from the back-end system, for example, when an expected event is created, or when a tracked process is created. The input values can also be provided from a tracked process event notification.
Consider a procurement scenario, where a user would like to determine what tracked processes exist for a specific range of buyer–specific criteria. The user can specify the tracked process selection entity code, and a range of other known details, as follows:
Purchase order number
Procurement status
Acknowledgement status
Alternatively, a user can query tracked processes using a range of supplier–specific criteria. The user specifies the tracked process selection entity code, and a range of other known details, as follows:
Purchase order number
Procurement status
Acknowledgement status
Sales order number
Note that value ranges and wildcards can be used.
For each tracked process where a matching item is found, the operation returns the universally unique identifier (UUID). If no tracked process fits the selection criteria, an information message is returned.
The operation returns an error in the following cases:
If selection criteria are defined that do not correspond to attributes in the back-end system.
If the tracked process selection entity code is not supported in the back-end system.
TrackedProcessSimpleByElementsQueryMessage_sync
TrackedProcessSimpleByElementsResponseMessage_sync
For more information about SAP implementation requirements, see the Tracked Process business object.
The BAdI: Query Event Handler (/SAPTRX/SE_EH_QUERY) Business Add-In (BAdI) is available for this operation.