Description | Query Purchase Requests |
Name | QueryPurchaseRequestQueryIn |
Namespace | http://sap.com/xi/A1S/Global |
Process Component Description | Purchase Request Processing |
Process Component Name | PurchaseRequestProcessing |
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 Request from a source system.
The web service Interface ‘Query Purchase Request Query In’ enables you to connect external applications to your SAP Business By Design system and to query Purchase Request in your system. The web service interface ‘Query Purchase Request Query In’ is relevant if your company wants to access Purchase Request data from external applications.
The Purchase Requests view in the Purchase Requests and Orders work center allows you to process and monitor all purchase requests.
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 Request , instance of Purchase Request 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 ‘FindSimpleByElements’.
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. Please open the Web Services document in a new window.
Possible scenarios include the following:
• Find Purchase Request based on certain set of information like parties, location etc.
This finds the Purchase Request that has ID between 4447 to 4450 with maximum as 10.
<n0:PurchaseRequestQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseRequestsSelectionByElements> <SelectionByID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>4447</LowerBoundaryIdentifier> <UpperBoundaryIdentifier>4450</UpperBoundaryIdentifier> </SelectionByID> </PurchaseRequestsSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>10</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:PurchaseRequestQuery_sync>
Description | Find purchase requests |
Name | FindSimpleByElements |
Synchronous | yes |
Release Status | Released |
QueryPurchaseRequestQueryIn Interface allows to query on existing purchase request items 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 requests Items 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 Purchase Request Query In’ offers the operation FindSimpleByElements.
Example: Retrieves purchase requests by id between 1 to 100
Web service request
<n0:PurchaseRequestQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseRequestsSelectionByElements> <SelectionByID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>1</LowerBoundaryIdentifier> <UpperBoundaryIdentifier>100</UpperBoundaryIdentifier> </SelectionByID> </PurchaseRequestsSelectionByElements> <ProcessingConditions> <QueryHitsMaximumNumberValue>10</QueryHitsMaximumNumberValue> <QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:PurchaseRequestQuery_sync>
Structure of the request message has the following parameters based on which purchase request items can be searched.
Element | Remark |
---|---|
ID | ID of the Purchase Request |
SearchText | You can specify anything in this text and if this text exists for any Purchase Request it will show up in result |
SystemAdministrativeDataCreationDateTime | Creation date of Purchase Order |
SystemAdministrativeDataLastChangeDateTime | Last changed date of Purchase Request |
CreationBusinessPartnerCommonPersonNameFamilyName | Family Name of the Purchaser who created the Purchase Request |
CreationBusinessPartnerCommonPersonNameGivenName | Given Name of the Purchaser who created the Purchase Request |
LastChangeBusinessPartnerCommonPersonNameFamilyName | Family Name of the employee who updated the Purchase Request last |
LastChangeBusinessPartnerCommonPersonNameGivenName | Given Name of the employee who updated the Purchase Request last |
PartyBuyerPartyKeyPartyID | Company ID of Purchase Request |
PartyBuyerPartyKeyPartyTypeCode | Company party Type Code |
PartyEmployeeResponsiblePartyKeyPartyTypeCode | Purchaser in Purchase Request |
PartyEmployeeResponsiblePartyKeyPartyID | Purchaser Party Type Code |
PartyResponsiblePurchasingUnitPartyKeyPartyTypeCode | Purchasing Unit in Purchase Request |
PartyResponsiblePurchasingUnitPartyKeyPartyID | Purchasing Unit Party Type Code |
PartySellerPartyKeyPartyTypeCode | Supplier ID of Purchase Request |
PartySellerPartyKeyPartyID | Supplier Party Type Code |
ItemAccountingCodingBlockTypeCode | The type of accounting object of Purchase Request item |
ItemAccountingCodingBlockDistributionItemAccountingDeterminationExpenseGroupCode | A coded representation of a group of expense types from the perspective of an identical or similar determination of an account in accounting. |
ItemAccountingCodingBlockDistributionItemCostCentreID | Cost center of item |
ItemAccountingCodingBlockDistributionItemIndividualMaterialKeyProductTypeCode | Product Type Code of Item |
ItemAccountingCodingBlockDistributionItemIndividualMaterialKeyProductIdentifierTypeCode | Product Identifier Type Code of Item Product |
ItemAccountingCodingBlockDistributionItemProjectReferenceProjectID | Project ID of Item |
ItemAccountingCodingBlockDistributionItemProjectReferenceProjectName | Project Name of Item |
ItemAccountingCodingBlockDistributionItemProjectReferenceProjectElementID | Project Element ID of Item |
ItemAccountingCodingBlockDistributionItemProjectReferenceProjectElementName | Project Element Name of Item |
ItemAccountingCodingBlockDistributionItemSalesOrderReferenceID | Sales Request to which Item is accounted to |
ItemDeliveryPeriodEndDateTime | The delivery start dates of Purchase Request Item. |
ItemDeliveryPeriodStartDateTime | The delivery end dates of Purchase Request Item. |
ItemDirectMaterialIndicator | Whether the item is a stock material or not |
ItemLocationShipToLocationID | Ship to location of Purchase Request item |
ItemPartyProductRecipientPartyKeyPartyID | Recipient of the product |
ItemPartyProductRecipientPartyKeyPartyTypeCode | Recipient Party Type Code |
ItemPartyRequestorPartyKeyPartyID | Requester of purchasing |
ItemPartyRequestorPartyKeyPartyTypeCode | Requester party type code |
ItemPartyServicePerformerPartyKeyPartyID | ServiceAgent in the Purchase Request item |
ItemPartyServicePerformerPartyKeyPartyTypeCode | ServiceAgent Party Type Code |
ItemProductProductCategoryIDKeyProductCategoryInternalID | Product Category ID |
ItemProductProductKeyProductID | Product ID Key |
ItemProductProductRequirementSpecificationKeyRequirementSpecificationID | Product Requirements Specification ID of Product |
ItemThirdPartyDealIndicator | Indicator is the representation of a situation that has exactly two mutually exclusive Boolean values |
ItemTypeCode | Type of Purchase RequestItem |
BusinessTransactionDocumentReferencePurchasingContractID | Contract ID of Purchase Request Item |
Supplier_CommonBusinessPartnerFormattedName | Supplier Common Formatted Name |
ItemProductDescription | Product Description of item product |
ItemPreferredSupplier | Prefer Supplier of purchase request item |
ConsistencyStatus | Indicator for where the consistency check is processed automatically after every change |
FollowUpDocumentStatus | A PurchaseRequestFollowUpDocumentStatusCode is a coded representation of the PurchaseRequest related to its follow-up document. |
CancellationStatusCode | A CancellationStatusCode is a coded representation of the status of a cancellation. |
ShoppingCartID | Shopping Cart ID of Purchase Request ID |
SalesOrderID | Sales RequestID of Purchase Request Item |
ProjectPurchaseRequestID | Project Purchase Request ID of Purchaser Request Item |
PurchaseProposalID | Purchase Proposal ID of Purchase Request Item |
PurchaseOrderID | Purchase RequestID of Purchase Request Item |
Code Value | Description |
---|---|
1 | Check Pending |
2 | Inconsistent |
3 | Consistent |
Code Value | Description |
---|---|
1 | No Follow-up |
2 | Purchase Order Created |
3 | RFQRequest Created |
4 | Contract Created |
5 | Scheduling Agreement Created |
Code Value | Description |
---|---|
1 | Not Canceled |
2 | Cancellation Requested |
3 | Cancellation Discarded |
4 | Canceled |
5 | Partially Canceled |
6 | Partial Cancellation Requested |
The response consists of root and item level element of Purchase Request. Following are the major attributes in result
Element | Remark |
---|---|
ID | Purchase Request ID |
ItemID | Purchase Request Item ID |
DirectMaterialIndicator | Direct Material Indicator |
ThirdPartyIndicator | Third Party Indicator |
ItemType | Item Type |
Quantity | Quantity |
DeliveryStartDateTime | Delivery Start Date Time |
DeliveryEndDateTime | Delivery End Date Time |
ItemReleaseQuantity | Item Release Quantity |
ItemOpenQuantity | Item Open Quantity |
ItemNetAmount | Item Net Amount |
ItemNetUnitPrice | Item Net Unit Price |
ItemGrossUnitPrice | Item Gross Unit Price |
ProductID | Product ID |
ProductDescription | Product Description |
ProductCategoryID | Product Category ID |
ProductSpecificationID | Product Specification ID |
SupplierPartNumber | Supplier Part Number |
ShipToLocationID | Ship To Location ID |
SiteLocationID | Site Location ID |
CompanyID | Company ID |
RequesterParty | Requester Party |
ReceipientParty | Recipient Party |
EmployeeResponsible | Employee Responsible |
PurchasingUnit | Purchasing Unit |
PreferredSupplierID | Preferred Supplier ID |
SupplierID | Supplier ID |
ServiceAgentID | Service Agent ID |
ContractReferenceID | Contract Reference ID |
ContractReferenceItemID | Contract Reference Item ID |
CreatedOnDateTime | Purchase Request Created On Date Time |
ChangedOnDateTime | Purchase Request Changed On Date Time |
CreatedByGivenName | Purchase Request Created By Given Name |
ItemAccountingCodingBlockDistribution | Item Accounting Coding Block Distribution |
ConsistencyStatusCode | Consistency Status Code of Purchase Request |
FollowUpDocumentStatusCode | Follow Up Document Status Code of Purchase Request |
CancellationStatusCode | Cancellation Status Code |
ItemTextCollection | Item Text Collection |
ItemAttachmentFolder | Item Attachment Folder |
Example 1 : Retrieves purchase request based on purchase request ID
Web service request
<n0:PurchaseRequestQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseRequestsSelectionByElements> <SelectionByID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>12</LowerBoundaryIdentifier> </SelectionByID> </PurchaseRequestsSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>true</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:PurchaseRequestQuery_sync>
Web service response
<n0:PurchaseRequestQueryResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TASC47B0F9FB8D906EA083C:804"> <PurchaseRequest> <ID>12</ID> <UUID>00163e07-3d6a-1ee7-ad9b-af875edd3077</UUID> <Item> <ItemID>1</ItemID> <ItemUUID>00163e07-3d6a-1ee7-ad9b-afba5421b077</ItemUUID> <ThirdPartyIndicator>true</ThirdPartyIndicator> <ItemType>18</ItemType> <Quantity unitCode="EA">1.0</Quantity> <DeliveryStartDateTime>2017-10-20T00:00:00Z</DeliveryStartDateTime> <DeliveryEndDateTime>2017-10-21T00:00:00Z</DeliveryEndDateTime> <ItemReleaseQuantity unitCode="EA">1.0</ItemReleaseQuantity> <ItemOpenQuantity unitCode="EA">1.0</ItemOpenQuantity> <ItemNetAmount currencyCode="USD">0.0</ItemNetAmount> <ItemNetUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemNetUnitPrice> <ItemGrossUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemGrossUnitPrice> <ProductID>AXUS-M934</ProductID> <ProductDescription languageCode="EN">Laptop</ProductDescription> <ProductCategoryID>320-10</ProductCategoryID> <SiteLocationID>AXUS-1000</SiteLocationID> <CompanyID>AXUS-C127</CompanyID> <RequesterParty>3824</RequesterParty> <ReceipientParty>3824</ReceipientParty> <EmployeeResponsible>MC0678</EmployeeResponsible> <PurchasingUnit>ICSP-1100</PurchasingUnit> <CreatedOnDateTime>2017-10-19T14:55:14Z</CreatedOnDateTime> <ChangedOnDateTime>2017-10-19T14:55:14Z</ChangedOnDateTime> <CreatedByGivenName>Anunax Astamadi</CreatedByGivenName> <ItemAccountingCodingBlockDistribution> <ValidityDate>2017-10-19</ValidityDate> <CompanyID>AXUS-100000</CompanyID> <LanguageCode>EN</LanguageCode> <TotalAmount currencyCode="USD">0.0</TotalAmount> <TotalQuantity unitCode="EA">1.0</TotalQuantity> <AccountingCodingBlockAssignment> <Percent>100.0</Percent> <Amount currencyCode="USD">0.0</Amount> <Quantity unitCode="EA">1.0</Quantity> <AccountingCodingBlockTypeCode>PRO</AccountingCodingBlockTypeCode> <ProjectTaskKey> <TaskID>CPSO37</TaskID> </ProjectTaskKey> <ProjectReference> <ProjectID>CPSO37</ProjectID> <ProjectUUID>00163e07-3d62-1ed7-ad80-cdefaf8e12a1</ProjectUUID> <ProjectName>PSO test</ProjectName> <ProjectElementID>CPSO37</ProjectElementID> <ProjectElementUUID>00163e07-3d62-1ed7-ad80-cdefaf8e12a1</ProjectElementUUID> <ProjectElementName>PSO test</ProjectElementName> </ProjectReference> </AccountingCodingBlockAssignment> </ItemAccountingCodingBlockDistribution> <ConsistencyStatusCode>3</ConsistencyStatusCode> <FollowUpDocumentStatusCode>1</FollowUpDocumentStatusCode> <CancellationStatusCode>1</CancellationStatusCode> </Item> <Item> <ItemID>2</ItemID> <ItemUUID>00163e07-3d6a-1ee7-ad9b-afba54217077</ItemUUID> <ThirdPartyIndicator>true</ThirdPartyIndicator> <ItemType>18</ItemType> <Quantity unitCode="EA">1.0</Quantity> <DeliveryStartDateTime>2017-10-20T00:00:00Z</DeliveryStartDateTime> <DeliveryEndDateTime>2017-10-21T00:00:00Z</DeliveryEndDateTime> <ItemReleaseQuantity unitCode="EA">1.0</ItemReleaseQuantity> <ItemOpenQuantity unitCode="EA">1.0</ItemOpenQuantity> <ItemNetAmount currencyCode="USD">0.0</ItemNetAmount> <ItemNetUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemNetUnitPrice> <ItemGrossUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemGrossUnitPrice> <ProductID>10000040</ProductID> <ProductDescription languageCode="EN">AHT COMBI 75</ProductDescription> <ProductCategoryID>50-10</ProductCategoryID> <SiteLocationID>AXUS-1000</SiteLocationID> <CompanyID>AXUS-C127</CompanyID> <RequesterParty>MC0678</RequesterParty> <ReceipientParty>3824</ReceipientParty> <EmployeeResponsible>MC1986</EmployeeResponsible> <PurchasingUnit>MC64850</PurchasingUnit> <CreatedOnDateTime>2017-10-19T14:55:14Z</CreatedOnDateTime> <ChangedOnDateTime>2017-10-19T14:55:14Z</ChangedOnDateTime> <CreatedByGivenName>Anunax Astamadi</CreatedByGivenName> <ItemAccountingCodingBlockDistribution> <ValidityDate>2017-10-19</ValidityDate> <CompanyID>AXUS-100000</CompanyID> <LanguageCode>EN</LanguageCode> <TotalAmount currencyCode="USD">0.0</TotalAmount> <TotalQuantity unitCode="EA">1.0</TotalQuantity> <AccountingCodingBlockAssignment> <Percent>100.0</Percent> <Amount currencyCode="USD">0.0</Amount> <Quantity unitCode="EA">1.0</Quantity> <AccountingCodingBlockTypeCode>PRO</AccountingCodingBlockTypeCode> <ProjectTaskKey> <TaskID>CPSO37-1</TaskID> </ProjectTaskKey> <ProjectReference> <ProjectID>CPSO37</ProjectID> <ProjectUUID>00163e07-3d62-1ed7-ad80-cdefaf8e12a1</ProjectUUID> <ProjectName>PSO test</ProjectName> <ProjectElementID>CPSO37-1</ProjectElementID> <ProjectElementUUID>00163e07-3d68-1ee7-ad9b-9d8636aac526</ProjectElementUUID> <ProjectElementName>t1</ProjectElementName> </ProjectReference> </AccountingCodingBlockAssignment> </ItemAccountingCodingBlockDistribution> <ConsistencyStatusCode>3</ConsistencyStatusCode> <FollowUpDocumentStatusCode>1</FollowUpDocumentStatusCode> <CancellationStatusCode>1</CancellationStatusCode> </Item> <Item> <ItemID>3</ItemID> <ItemUUID>00163e07-3d6a-1ee7-ad9b-afba54219077</ItemUUID> <ThirdPartyIndicator>true</ThirdPartyIndicator> <ItemType>18</ItemType> <Quantity unitCode="EA">1.0</Quantity> <DeliveryStartDateTime>2017-10-20T00:00:00Z</DeliveryStartDateTime> <DeliveryEndDateTime>2017-10-21T00:00:00Z</DeliveryEndDateTime> <ItemReleaseQuantity unitCode="EA">1.0</ItemReleaseQuantity> <ItemOpenQuantity unitCode="EA">1.0</ItemOpenQuantity> <ItemNetAmount currencyCode="USD">0.0</ItemNetAmount> <ItemNetUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemNetUnitPrice> <ItemGrossUnitPrice> <Amount currencyCode="USD">0.0</Amount> <BaseQuantity unitCode="EA">1.0</BaseQuantity> <BaseQuantityTypeCode>EA</BaseQuantityTypeCode> </ItemGrossUnitPrice> <ProductID>AXUS-M934</ProductID> <ProductDescription languageCode="EN">Laptop</ProductDescription> <ProductCategoryID>320-10</ProductCategoryID> <SiteLocationID>AXUS-1000</SiteLocationID> <CompanyID>AXUS-C127</CompanyID> <RequesterParty>3824</RequesterParty> <ReceipientParty>3824</ReceipientParty> <EmployeeResponsible>MC0678</EmployeeResponsible> <PurchasingUnit>ICSP-1100</PurchasingUnit> <PreferredSupplierID>1000190</PreferredSupplierID> <SupplierID>1000190</SupplierID> <CreatedOnDateTime>2017-10-19T14:55:14Z</CreatedOnDateTime> <ChangedOnDateTime>2017-10-19T14:55:14Z</ChangedOnDateTime> <CreatedByGivenName>Anunax Astamadi</CreatedByGivenName> <ItemAccountingCodingBlockDistribution> <ValidityDate>2017-10-19</ValidityDate> <CompanyID>AXUS-100000</CompanyID> <LanguageCode>EN</LanguageCode> <TotalAmount currencyCode="USD">0.0</TotalAmount> <TotalQuantity unitCode="EA">1.0</TotalQuantity> <AccountingCodingBlockAssignment> <Percent>100.0</Percent> <Amount currencyCode="USD">0.0</Amount> <Quantity unitCode="EA">1.0</Quantity> <AccountingCodingBlockTypeCode>PRO</AccountingCodingBlockTypeCode> <ProjectTaskKey> <TaskID>CPSO37-1</TaskID> </ProjectTaskKey> <ProjectReference> <ProjectID>CPSO37</ProjectID> <ProjectUUID>00163e07-3d62-1ed7-ad80-cdefaf8e12a1</ProjectUUID> <ProjectName>PSO test</ProjectName> <ProjectElementID>CPSO37-1</ProjectElementID> <ProjectElementUUID>00163e07-3d68-1ee7-ad9b-9d8636aac526</ProjectElementUUID> <ProjectElementName>t1</ProjectElementName> </ProjectReference> </AccountingCodingBlockAssignment> </ItemAccountingCodingBlockDistribution> <ConsistencyStatusCode>3</ConsistencyStatusCode> <FollowUpDocumentStatusCode>1</FollowUpDocumentStatusCode> <CancellationStatusCode>1</CancellationStatusCode> </Item> <SystemAdministrativeData> <CreationDateTime>2017-10-19T14:55:14Z</CreationDateTime> <CreationIdentityUUID>00163e07-3d6a-1ee7-ad80-aa4ff476323a</CreationIdentityUUID> <LastChangeDateTime>2017-10-19T14:55:14Z</LastChangeDateTime> <LastChangeIdentityUUID>00163e07-3d6a-1ee7-ad80-aa4ff476323a</LastChangeIdentityUUID> </SystemAdministrativeData> </PurchaseRequest> <ProcessingConditions> <ReturnedQueryHitsNumberValue>3</ReturnedQueryHitsNumberValue> <MoreHitsAvailableIndicator>false</MoreHitsAvailableIndicator> <LastReturnedObjectID>00163E073D6A1EE7AD9BAFBA5421B077</LastReturnedObjectID> </ProcessingConditions> <Log/> </n0:PurchaseRequestQueryResponse_sync>
Example 2: Retrieves purchase requests based on Suppliers
Web service request
<n0:PurchaseRequestQuery_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <PurchaseRequestsSelectionByElements> <SelectionByPartySellerPartyKeyPartyID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundarySellerPartyID>MC2000</LowerBoundarySellerPartyID> </SelectionByPartySellerPartyKeyPartyID> <SelectionByPartySellerPartyKeyPartyID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundarySellerPartyID>MC4000</LowerBoundarySellerPartyID> </SelectionByPartySellerPartyKeyPartyID> </PurchaseRequestsSelectionByElements> <ProcessingConditions> <QueryHitsUnlimitedIndicator>true</QueryHitsUnlimitedIndicator> <LastReturnedObjectID/> </ProcessingConditions> </n0:PurchaseRequestQuery_sync>
Release | Change Description | Details |
1805 | Documentation change | Service Interfaces and Operation,Structure of request message and response message, Example of payload updates |