Description | Query Purchase Orders |
Name | QueryPurchaseOrderQueryIn |
Namespace | http://sap.com/xi/A1S/Global |
Process Component Description | Purchase Order Processing |
Process Component Name | PurchaseOrderProcessing |
Process Component Namespace | http://sap.com/xi/AP/Purchasing/Global |
Deployment Unit Description | Purchasing |
Endpoint Activation | By Scoping of Process Component | Operations |
Release Status | Released |
An interface to query Purchase Orders from a source system.
The web service Interface ‘Query PurchaseOrderQuery In’ enables you to connect external applications to your SAP Business By Design system and to query Purchase Orders in your system. The web service interface ‘Query PurchaseOrderQuery In’ is relevant if your company wants to access Purchase Orders data from external applications.
Purchase orders (PO) can be created manually in the Purchase Orders view of the Purchase Requests and Orders work center
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 in 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 | Logical Operator |
---|---|---|---|
1 | Equal to | Single Value | =X |
2 | Between(Excluding upper boundary) | Interval with closed lower and open upper boundary | [X, Y) |
3 | Between | Interval with open lower and open upper boundary | (X, Y) |
4 | Between (excluding both boundaries) | Interval with open lower and open upper boundary | (X, Y) |
5 | Between (excluding lower boundary) | Interval with open lower and closed 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 |
Transmission Request Code in RequestedElements specifies which elements shall be returned
Code | Description |
---|---|
1 | The node element, all its elements and its child node elements and all their elements shall be returned. |
2 | The node element and all its elements shall be returned. |
3 | The node element and its key elements shall be returned. |
4 | The node element and its child node elements shall not be returned. |
Before a query is executed on Purchase Orders , instance of Purchase Orders has to be created and maintained first.
Action codes represent an instruction to the recipient of the web service request to process transmitted message node elements.
The action code to be used is ‘QUERY_BY_ELEMENTS’.
Optional leaf elements in request messages that are not transmitted within a web service request are not considered while querying. So any value of missing parameters would meet the comparison.
Query operation is stateless synchronous web service operation. 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.
The structure of the request message type consists of two parts:
• Selection parameters for the query
• Processing conditions. This specifies the limit on the output i.e number of records returned. You can also specify if you want unlimited number of records.
Many external applications consuming web services have special requirements and restrictions regarding the format of WSDLs. Some external applications require service definition WSDLs describing the web service signature. This is normally sufficient for the creation of static client-side proxies. Other external applications, normally those that do not create static client-side proxies, require binding WSDLs including the endpoint definition and authentication policy information.
In both cases, it may be the case that the external application imposes special restrictions on the structure or the size of WSDLs.
Microsoft InfoPath requires binding WSDLs and considers elements with the attribute "minOccurs=0" as "mandatory". However "minOccurs=0" means "optional" in SAP web services. In order to circumvent this problem, the WSDL must be saved locally and an additional attribute "nillable=true" must be added to make a query parameter optional for Microsoft InfoPath.
For very small clients such as mobile devices, the size of the WSDL itself may become a problem. In most cases the client only requires a very small part of the signature, but due to the complexity of the WSDL they may end up with long runtime during serialization of the request or deserialization of the response. In order to circumvent this problem, the WSDL must be saved locally and the optional parts of the signature have to be removed before the WSDL is imported or static client-side proxies are generated.
External applications have to take into account that web service request and response message types can be enhanced with additional elements and attributes. Enhancements can be created by SAP, SAP partners, and key users. Enhancements of request message types are always optional elements or attributes. The SAP system does not require the external application to provide values in the request. Enhancements of response message types can contain mandatory elements or attributes. The external application must be able to process the extended response successfully.
XML element and attribute names are always stable. Technical definitions of data types can be enhanced in a compatible way. This may result in changed data type names. External applications can rely on XML element names and attribute names, but should not rely on data type names.
Note: You can download the WSDL file for any web service here:
• Application and User Management work center -> Input Output Management -> Communication Arrangement.
• User Management work center -> Service Explorer view.
You can find the documentation of the global data types in the SAP Community Network: Go to http://scn.sap.com/docs/DOC-17516 and click View Document.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
• Find Purchase Orders based on certain set of information like parties, location etc.
This finds the Purchase Order that has life cycle status between 1 to 6.
<n0:PurchaseOrderSimpleByElementsQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseOrderSimpleSelectionByElements> <SelectionByPurchaseOrderLifeCycleStatusCode> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <LowerBoundaryPurchaseOrderLifeCycleStatusCode>1</LowerBoundaryPurchaseOrderLifeCycleStatusCode> <UpperBoundaryPurchaseOrderLifeCycleStatusCode>6</UpperBoundaryPurchaseOrderLifeCycleStatusCode> </SelectionByPurchaseOrderLifeCycleStatusCode> </PurchaseOrderSimpleSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <QueryHitsMaximumNumberValue>100</QueryHitsMaximumNumberValue> </ProcessingConditions> </n0:PurchaseOrderSimpleByElementsQuery_sync>
Description | Find purchase orders |
Name | FindSimpleByElements |
Synchronous | yes |
Release Status | Released |
QueryPurchaseOrderIn interface allows to query on existing purchase Orders in the system.
The request message of the QueryByElements contain two parts: Body and Processing Conditions. Body comprises of the various parameters on which Purchase Orders can be queried. Details on these parameters is discussed in the following sub-sections. Processing conditions controls the execution of query. For example you can specify if you want a certain number of records as output or unlimited records should be shown.
The response message contain the header level relevant attributes of Purchase Order along with the Processing conditions. The processing condition here indicates that how many records are returned and are there any more records existing which meet the criteria but not fetched.
The search can contain complex criteria instead of having simple equation. You can get results based on ‘equal to’ or a Range or Less than or greater than logical operations. These type codes should be specified in the request message.
The web service ‘Query PurchaseOrderQuery In’ offers the operation QUERY_BY_ELEMENTS.
Example : Retrieves purchase orders which are in status between 1 (In Preparation) to 6 (Sent).
Web service request
<n0:PurchaseOrderSimpleByElementsQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseOrderSimpleSelectionByElements> <SelectionByPurchaseOrderLifeCycleStatusCode> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <LowerBoundaryPurchaseOrderLifeCycleStatusCode>1</LowerBoundaryPurchaseOrderLifeCycleStatusCode> <UpperBoundaryPurchaseOrderLifeCycleStatusCode>6</UpperBoundaryPurchaseOrderLifeCycleStatusCode> </SelectionByPurchaseOrderLifeCycleStatusCode> </PurchaseOrderSimpleSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <QueryHitsMaximumNumberValue>2</QueryHitsMaximumNumberValue> </ProcessingConditions> </n0:PurchaseOrderSimpleByElementsQuery_sync>
Web service response
<n0:PurchaseOrderSimpleByElementsResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAS05B6BFBB03520E661520:804"> <PurchaseOrder> <PurchaseOrderID>39</PurchaseOrderID> <PurchaseOrderUUID>00163e06-5908-1ed5-99d6-96fe12d4c7c3</PurchaseOrderUUID> <SystemAdministrativeData> <CreationDateTime>2015-09-29T14:17:06Z</CreationDateTime> <CreationIdentityUUID>00300571-cc0f-02db-bcaf-2a0658a6c1e7</CreationIdentityUUID> <LastChangeDateTime>2015-09-29T14:47:51Z</LastChangeDateTime> <LastChangeIdentityUUID>00300571-cc0f-02db-bcaf-2a0658a6c1e7</LastChangeIdentityUUID> </SystemAdministrativeData> <OrderedDateTime timeZoneCode="EST">2015-09-29T14:38:01Z</OrderedDateTime> <CurrencyCode>USD</CurrencyCode> <TotalNetAmount currencyCode="USD">18200.0</TotalNetAmount> <PartyBuyerPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC10000</PartyID> </PartyBuyerPartyKey> <PartySellerPartyKey> <PartyTypeCode>147</PartyTypeCode> <PartyID>MC3333</PartyID> </PartySellerPartyKey> <ApprovalStatusCode>3</ApprovalStatusCode> <DeliveryProcessingStatusCode>1</DeliveryProcessingStatusCode> <InvoiceProcessingStatusCode>1</InvoiceProcessingStatusCode> <InvoicingStatusCode>1</InvoicingStatusCode> <PurchaseOrderConfirmationStatusCode>9</PurchaseOrderConfirmationStatusCode> <PurchaseOrderDeliveryStatusCode>1</PurchaseOrderDeliveryStatusCode> <PurchaseOrderLifeCycleStatusCode>2</PurchaseOrderLifeCycleStatusCode> <DataOriginTypeCode>1</DataOriginTypeCode> </PurchaseOrder> <PurchaseOrder> <PurchaseOrderID>40</PurchaseOrderID> <PurchaseOrderUUID>00163e06-5908-1ed5-99d6-aeae41bd67eb</PurchaseOrderUUID> <SystemAdministrativeData> <CreationDateTime>2015-09-29T14:22:18Z</CreationDateTime> <CreationIdentityUUID>00300571-cc0f-02db-bcaf-14864da6c27f</CreationIdentityUUID> <LastChangeDateTime>2015-09-29T14:42:58Z</LastChangeDateTime> <LastChangeIdentityUUID>00300571-cc0f-02db-bcaf-14864da6c27f</LastChangeIdentityUUID> </SystemAdministrativeData> <OrderedDateTime timeZoneCode="EST">2015-09-29T14:38:51Z</OrderedDateTime> <CurrencyCode>USD</CurrencyCode> <TotalNetAmount currencyCode="USD">11800.0</TotalNetAmount> <PartyBuyerPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC10000</PartyID> </PartyBuyerPartyKey> <PartySellerPartyKey> <PartyTypeCode>147</PartyTypeCode> <PartyID>MC3333</PartyID> </PartySellerPartyKey> <ApprovalStatusCode>3</ApprovalStatusCode> <DeliveryProcessingStatusCode>1</DeliveryProcessingStatusCode> <InvoiceProcessingStatusCode>1</InvoiceProcessingStatusCode> <InvoicingStatusCode>1</InvoicingStatusCode> <PurchaseOrderConfirmationStatusCode>9</PurchaseOrderConfirmationStatusCode> <PurchaseOrderDeliveryStatusCode>1</PurchaseOrderDeliveryStatusCode> <PurchaseOrderLifeCycleStatusCode>2</PurchaseOrderLifeCycleStatusCode> <DataOriginTypeCode>1</DataOriginTypeCode> </PurchaseOrder> <ResponseProcessingConditions> <ReturnedQueryHitsNumberValue>2</ReturnedQueryHitsNumberValue> <MoreHitsAvailableIndicator>true</MoreHitsAvailableIndicator> <LastReturnedObjectID>00163E0659081ED599D6AEAE41BD67EB</LastReturnedObjectID> </ResponseProcessingConditions> <Log/> </n0:PurchaseOrderSimpleByElementsResponse_sync>
Structure of the request message has the following parameters based on which purchase orders can be searched:
Element | Remark |
---|---|
SelectionBySearchText | You can specify anything in this text and if this text exists for any Purchase Order it will show up in result |
ID | Id of the Purchase Order |
SystemAdministrativeDataCreationDateTime | Creation date of Purchase Order |
SystemAdministrativeDataLastChangedDateTime | Last changed date of Purchase Order |
CreationBusinessPartnerCommonPersonName | Name of the Purchaser who created the Purchase Order |
LastChangeBusinessPartnerCommonPersonName | Name of the employee who updated the PO last |
TypeCode | TypeCode of the Purchase Order value is 001 |
CurrencyCode | Currency of Purchase Order |
OrderedDateTime | Date when the Purchase Order was sent to supplier |
SupplierCommonBusinesspartnerFormattedName | Supplier name in Purchase Order |
Name | Purchase Order text |
TotalNetAmount | Total value of Purchase Order |
BuyerPartyKeyPartyID | Company ID of Purchase Order |
EmployeeResponsiblePartyKeyPartyID | Purchaser in Purchase Order |
PartyResponsiblePurchasingUnitPartyKeyPartyID | Purchasing Unit in Purchase Order |
PartySellerPartyKeyPartyID | Supplier Id in Purchase Order |
Approval Status | Approval related status of Purchase Order. It could be 1 Not Started 2 Approval not Necessary 3 In Approval 4 Approved 5 Rejected 6 In Revision 7 Withdrawn. |
DeliveryProcessingStatus | The status of processing the delivery of Purchase Order. It could be 1 Not Started 2 Partially 3 Delivered 4 Not relevant or Completed. |
InvoiceProcessingStatus | Status of processing the invoicing on Purchase Order. It could be 1 Not started 2 In Process 3 Finished 4 Not Relevant 5 Interrupted. |
DelievryStatusCode | The status of delivery. It could be 1 Not started 2 Partially delivered 3 Delivered 4 Not Relevant. |
PurchaseOrderConfirmationStatusCode | The status of Purchase Order Acknowledgment. It could be 1 No Acknowledgment Received 2 Deviation in Acknowledgment 3 Receipt Acknowledged 4 Rejected 5 Partially Rejected 6 Partially Acknowledged 7 Acknowledged 8 New Acknowledgment Expected 9 No Acknowledgment Expected |
PurchaseOrderLifeCycleStatusCode | The life cycle status of Purchase Order, it could be 1 In Preparation 2 In Approval 3 In Revision 4 Rejected 5 Not Yet Acknowledged 6 Sent 7 Acknowledgment Received 8 Canceled 9 Follow-Up Document Created 10 Finished. |
ItemAccountingCodingBlockTYpe | The type of accounting object of Purchase Order item |
ItemAccountingCodingBlockDistributionItemCostCentreId | Cost center of item |
ItemAccountingCodingBlockDistributionItemProjectReferenceProjectId | Project to which PO Item is accounted |
ItemAccountingCodingBlockDistributionItemSAlesOrderReferenceID | Sales Order to which Item is accounted to |
ItemDeliveryPeriod | The delivery start and end dates of Purchase Order Item. |
ItemDescription | The Product description |
ItemDirectMaterialIndicator | Whether the item is a stock material or not |
ItemFollowUpPurchaseOrderConfirmationRequirementCode | The status of Follow Up Purchase Order Confirmation. It could be 01 Required 02 Expected 03 Optional 04 Not Expected 05 Forbidden. |
ItemLocationShipToLocationID | Ship to location of Purchase Order item |
ItemPartyProductRecipientPartyKeyPartyID | Recipient of the product |
ItemPartyServicePerformerPartyKeyPartyID | ServiceAgent in the Purchase Order item |
ItemProductCategoryID | Product category of the Purchase Order Item |
ItemProductProductRequirmentSpecificationKey | Product Requirements Specification ID of Product |
ThirdPartyDealIndicator | If the Purchase Order Item has process type third party |
ItemTypeCode | Type of Purchase Order Item, It could be 18 Material 19 Service 20 Limit 84 Expense. |
BusinessTransactionDocumentrefernce* | Reference to related document like Contract, Purchase Request etc. |
Code | Remark |
---|---|
1 | In Preparation |
2 | In Approval |
3 | In Revision |
4 | Rejected |
5 | Not Yet Acknowledged |
6 | Sent |
7 | Acknowledgment Received |
8 | Canceled |
9 | Follow-Up Document Created |
10 | Finished |
Code | Remark |
---|---|
1 | Not Started |
2 | Approval not Necessary |
3 | In Approval |
4 | Approved |
5 | Rejected |
6 | In Revision |
7 | Withdrawn |
Code | Remark |
---|---|
1 | Not Started |
2 | In Process |
3 | Finished |
4 | Not Relevant |
5 | Interrupted |
Code | Remark |
---|---|
1 | Not Started |
2 | In Process |
3 | Finished |
4 | Not Relevant |
5 | Interrupted |
Code | Remark |
---|---|
1 | Not Invoiced |
2 | Partially Invoiced |
3 | Invoiced |
4 | Not Relevant |
Code | Remark |
---|---|
1 | Not Delivered |
2 | Partially Delivered |
3 | Delivered |
4 | Not Relevant |
Code | Remark |
---|---|
1 | No Acknowledgment Received |
2 | Deviation in Acknowledgment |
3 | Receipt Acknowledged |
4 | Rejected |
5 | Partially Rejected |
6 | Partially Acknowledged |
7 | Acknowledged |
8 | New Acknowledgment Expected |
9 | No Acknowledgment Expected |
Element | Remark |
---|---|
PurchaseOrderID | Purchase Order ID |
SystemAdministrativeData | System Administrative Data which include the creation and last changed date time |
OrderedDateTime | Ordered date time of the PO |
CurrencyCode | Currency Code |
TotalNetAmount | Total Net Amount of the PO |
PartyBuyerPartyKey | the buying company |
PartyResponsiblePurchasingUnitPartyKey | The Purchaser who is requesting the purchasing document |
PartySellerPartyKey | The supplier to whom the purchase document is raised |
ApprovalStatusCode | Approval Status of the PO |
DeliveryProcessingStatusCode | Delivery Processing Status Code |
InvoiceProcessingStatusCode | Invoice Processing Status Code |
InvoicingStatusCode | Invoicing Status Code |
OrderDeliveryStatusCode | Order Delivery Status Code |
PurchaseOrderConfirmationStatusCode | Purchase Order Confirmation Status Code |
PurchaseOrderDeliveryStatusCode | Purchase Order Delivery Status Code |
PurchaseOrderLifeCycleStatusCode | Purchase Order Life Cycle Status Code |
BusinessTransactionDocumentReferenceGoodsAndServiceAcknowledgementID | Business Transaction Document Reference Goods And Service Acknowledgment ID |
BusinessTransactionDocumentReferencePurchasingContractID | Business Transaction Document Reference Purchasing Contract ID |
BusinessTransactionDocumentReferenceInternalRequestID | Business Transaction Document Reference Internal Request ID |
BusinessTransactionDocumentReferenceOutboundDeliveryID | Business Transaction Document Reference Outbound Delivery ID |
BusinessTransactionDocumentReferencePurchaseRequestID | Business Transaction Document Reference Purchase Request ID |
DataOriginTypeCode | Data Origin Type Code |
Example 1: Retrieves purchase orders based on supplier ID. MC2000 as a supplier ID in selection.
Web service request
<n0:PurchaseOrderSimpleByElementsQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseOrderSimpleSelectionByElements> <SelectionByPartySellerPartyKeyPartyID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundarySellerPartyID>MC2000</LowerBoundarySellerPartyID> </SelectionByPartySellerPartyKeyPartyID> </PurchaseOrderSimpleSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <QueryHitsMaximumNumberValue>2</QueryHitsMaximumNumberValue> </ProcessingConditions> </n0:PurchaseOrderSimpleByElementsQuery_sync>
Web service response
<n0:PurchaseOrderSimpleByElementsResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAS05B6BFBB03520E661520:804"> <PurchaseOrder> <PurchaseOrderID>58</PurchaseOrderID> <PurchaseOrderUUID>00163e06-66fe-1ed5-bdb3-a372e37747e9</PurchaseOrderUUID> <SystemAdministrativeData> <CreationDateTime>2016-03-29T10:59:06Z</CreationDateTime> <CreationIdentityUUID>00145ef5-88e6-02db-bcae-74ea799f1856</CreationIdentityUUID> <LastChangeDateTime>2017-11-15T10:20:44Z</LastChangeDateTime> <LastChangeIdentityUUID>00300571-ce9b-1ddd-8dc5-f2f399b055fa</LastChangeIdentityUUID> </SystemAdministrativeData> <OrderedDateTime timeZoneCode="EST">2016-03-29T10:59:07Z</OrderedDateTime> <CurrencyCode>USD</CurrencyCode> <TotalNetAmount currencyCode="USD">92.0</TotalNetAmount> <PartyBuyerPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC10000</PartyID> </PartyBuyerPartyKey> <PartySellerPartyKey> <PartyTypeCode>147</PartyTypeCode> <PartyID>MC2000</PartyID> </PartySellerPartyKey> <ApprovalStatusCode>2</ApprovalStatusCode> <DeliveryProcessingStatusCode>3</DeliveryProcessingStatusCode> <InvoiceProcessingStatusCode>3</InvoiceProcessingStatusCode> <InvoicingStatusCode>3</InvoicingStatusCode> <PurchaseOrderConfirmationStatusCode>9</PurchaseOrderConfirmationStatusCode> <PurchaseOrderDeliveryStatusCode>3</PurchaseOrderDeliveryStatusCode> <PurchaseOrderLifeCycleStatusCode>10</PurchaseOrderLifeCycleStatusCode> <DataOriginTypeCode>1</DataOriginTypeCode> </PurchaseOrder> <PurchaseOrder> <PurchaseOrderID>82</PurchaseOrderID> <PurchaseOrderUUID>00163e07-3d62-1ed7-acde-d475413f2505</PurchaseOrderUUID> <SystemAdministrativeData> <CreationDateTime>2017-10-17T04:50:53Z</CreationDateTime> <CreationIdentityUUID>00163e07-3d66-1ee7-acde-9fab1c37b735</CreationIdentityUUID> <LastChangeDateTime>2017-10-17T04:50:53Z</LastChangeDateTime> <LastChangeIdentityUUID>00163e07-3d66-1ee7-acde-9fab1c37b735</LastChangeIdentityUUID> </SystemAdministrativeData> <OrderedDateTime timeZoneCode="GMTUK">2017-10-17T04:50:54Z</OrderedDateTime> <CurrencyCode>USD</CurrencyCode> <TotalNetAmount currencyCode="USD">430.0</TotalNetAmount> <PartyBuyerPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC10000</PartyID> </PartyBuyerPartyKey> <PartyResponsiblePurchasingUnitPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC64850</PartyID> </PartyResponsiblePurchasingUnitPartyKey> <PartySellerPartyKey> <PartyTypeCode>147</PartyTypeCode> <PartyID>MC2000</PartyID> </PartySellerPartyKey> <ApprovalStatusCode>2</ApprovalStatusCode> <DeliveryProcessingStatusCode>1</DeliveryProcessingStatusCode> <InvoiceProcessingStatusCode>1</InvoiceProcessingStatusCode> <InvoicingStatusCode>1</InvoicingStatusCode> <PurchaseOrderConfirmationStatusCode>9</PurchaseOrderConfirmationStatusCode> <PurchaseOrderDeliveryStatusCode>1</PurchaseOrderDeliveryStatusCode> <PurchaseOrderLifeCycleStatusCode>6</PurchaseOrderLifeCycleStatusCode> <BusinessTransactionDocumentReferenceInternalRequestID>101</BusinessTransactionDocumentReferenceInternalRequestID> <BusinessTransactionDocumentReferencePurchaseRequestID>32</BusinessTransactionDocumentReferencePurchaseRequestID> <DataOriginTypeCode>8</DataOriginTypeCode> </PurchaseOrder> <ResponseProcessingConditions> <ReturnedQueryHitsNumberValue>2</ReturnedQueryHitsNumberValue> <MoreHitsAvailableIndicator>true</MoreHitsAvailableIndicator> <LastReturnedObjectID>00163E073D621ED7ACDED475413F2505</LastReturnedObjectID> </ResponseProcessingConditions> <Log/> </n0:PurchaseOrderSimpleByElementsResponse_sync>
Example 2: Retrieves purchase order data based on purchase order ID.
Web service request
<n0:PurchaseOrderSimpleByElementsQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseOrderSimpleSelectionByElements> <SelectionByID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryID>58</LowerBoundaryID> </SelectionByID> </PurchaseOrderSimpleSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>true</QueryHitsUnlimitedIndicator> </ProcessingConditions> </n0:PurchaseOrderSimpleByElementsQuery_sync>
Web service response
<n0:PurchaseOrderSimpleByElementsResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAS05B6BFBB03520E661520:804"> <PurchaseOrder> <PurchaseOrderID>58</PurchaseOrderID> <PurchaseOrderUUID>00163e06-66fe-1ed5-bdb3-a372e37747e9</PurchaseOrderUUID> <SystemAdministrativeData> <CreationDateTime>2016-03-29T10:59:06Z</CreationDateTime> <CreationIdentityUUID>00145ef5-88e6-02db-bcae-74ea799f1856</CreationIdentityUUID> <LastChangeDateTime>2017-11-15T10:20:44Z</LastChangeDateTime> <LastChangeIdentityUUID>00300571-ce9b-1ddd-8dc5-f2f399b055fa</LastChangeIdentityUUID> </SystemAdministrativeData> <OrderedDateTime timeZoneCode="EST">2016-03-29T10:59:07Z</OrderedDateTime> <CurrencyCode>USD</CurrencyCode> <TotalNetAmount currencyCode="USD">92.0</TotalNetAmount> <PartyBuyerPartyKey> <PartyTypeCode>200</PartyTypeCode> <PartyID>MC10000</PartyID> </PartyBuyerPartyKey> <PartySellerPartyKey> <PartyTypeCode>147</PartyTypeCode> <PartyID>MC2000</PartyID> </PartySellerPartyKey> <ApprovalStatusCode>2</ApprovalStatusCode> <DeliveryProcessingStatusCode>3</DeliveryProcessingStatusCode> <InvoiceProcessingStatusCode>3</InvoiceProcessingStatusCode> <InvoicingStatusCode>3</InvoicingStatusCode> <PurchaseOrderConfirmationStatusCode>9</PurchaseOrderConfirmationStatusCode> <PurchaseOrderDeliveryStatusCode>3</PurchaseOrderDeliveryStatusCode> <PurchaseOrderLifeCycleStatusCode>10</PurchaseOrderLifeCycleStatusCode> <DataOriginTypeCode>1</DataOriginTypeCode> </PurchaseOrder> <ResponseProcessingConditions> <ReturnedQueryHitsNumberValue>1</ReturnedQueryHitsNumberValue> <MoreHitsAvailableIndicator>false</MoreHitsAvailableIndicator> <LastReturnedObjectID>00163E0666FE1ED5BDB3A372E37747E9</LastReturnedObjectID> </ResponseProcessingConditions> <Log/> </n0:PurchaseOrderSimpleByElementsResponse_sync>
Release | Change Description | Details |
1805 | Documentation change | Service Interfaces and Operation, Request message content changes, Example payload updates |