Business Trends
Query Projects in SAP Business ByDesign using SOAP UI
This web service is used to query projects. It has the FindProjectByElements operation which is used to query for one or more instances of the project based on the query filter parameters passed.
| Description | Query Projects |
| Name | QueryProjectIn |
| Process Component Name | ProjectProcessing |
| Operation | Find Projects |
FindProjectByElements is an operation to query the project data by the selection elements passed in the request.
You can query based on the below elements;
| SelectionByElements | UI Element |
|---|---|
| SelectionByResponsibleUnitID | Responsible Unit ID |
| SelectionByProjectID | Project ID |
| SelectionByProjectName | Project Name |
| SelectionByProjectType | Project Type |
| SelectionByCustomerID | Customer ID |
| SelectionByRequestingUnitID | Requesting Unit ID |
| SelectionByBillableIndicator | Billable Indicator |
| SelectionByIntercompanyIndicator | Intercompany Indicator |
| SelectionByResponsibleEmployeeID | Person Responsible ID |
Note:
Billable indicator takes the values ‘True’ or ‘False’. To query for projects that are billable, set the value for field IntervalBoundaryTypeCode under the tag SelectionByBillableIndicator to ‘True’.
Mandatory Fields:
- In the ProcessingConditions tag, the QueryHitsUnlimitedIndicator field is mandatory, which takes the values ‘True’ or ‘False’.
- IntervalBoundaryTypeCode field is a mandatory field in each of the selection tags. This field takes the values as given in the generic document
Constraint:
- If a large volume of data is to be retrieved, the consumer must implement the retrieval logic in batches. The data can be limited by using QueryHitsMaximumNumberValue field in the ProcessingConditions tag.
- For the selection fields, in each SelectionField tag, the field InclusionExclusionCode takes the values ‘E’ Or ‘I’.
- E- Excluding
- I- Including
Project Types:
The project types provided by SAP are:
| Project Type Code | Value |
|---|---|
| 10 | Cost collecting project |
| 20 | Direct cost project |
| 21 | Marketing project |
| 22 | Strategic sourcing project |
| 23 | Research and development project |
| 24 | Customer project w/o sales integration |
| 25 | Customer project with sales integration |
| 26 | Multi-customer project |
| 27 | Intercompany Project |
Examples:
Example for using various query paramaters
Query projects based on Project ID:
<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:glob=”http://sap.com/xi/SAPGlobal20/Global”>
<soapenv:Header/>
<soapenv:Body>
<glob:ProjectByElementsQuery>
<ProcessingConditions>
<QueryHitsMaximumNumberValue>20</QueryHitsMaximumNumberValue>
<QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator>
</ProcessingConditions>
<ProjectSelectionByElements>
<SelectionByProjectID>
<InclusionExclusionCode>I</InclusionExclusionCode>
<IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
<LowerBoundaryProjectID>COC1</LowerBoundaryProjectID>
</SelectionByProjectID>
</ProjectSelectionByElements>
</glob:ProjectByElementsQuery>
</soapenv:Body>
</soapenv:Envelope>`
Query projects based on Responsible Unit ID:
<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:glob=”http://sap.com/xi/SAPGlobal20/Global”>
<soapenv:Header/>
<soapenv:Body>
<glob:ProjectByElementsQuery>
<ProcessingConditions>
<QueryHitsMaximumNumberValue>20</QueryHitsMaximumNumberValue>
<QueryHitsUnlimitedIndicator>false</QueryHitsUnlimitedIndicator>
</ProcessingConditions>
<ProjectSelectionByElements>
<SelectionByResponsibleUnitID>
<InclusionExclusionCode>I</InclusionExclusionCode>
<IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode>
<LowerBoundaryRespUnitID>A1110</LowerBoundaryRespUnitID>
</SelectionByResponsibleUnitID>
</ProjectSelectionByElements>
</glob:ProjectByElementsQuery>
</soapenv:Body>
</soapenv:Envelope>`