This topic includes additional information about getting a BP list.
Company-level BP Record
To get company level BP record information, do not send projectNumber parameter. If you send project number and the BP exists at company level then you will get an error that BP name is not correct.
Single Record BP
To get Single Record BP you need a record number populated on to the record. If you do not have a record number populated then getBPRecord will return back the structure of the BP.
filterCondition
If you cannot send filterCondition and filter values currently then it is recommended that these be set to "null." If you want to filter out the records that you want to retrieve then you can use this element. If you want to include more than one filter condition then following this syntax
<_filterCondition>fieldname=value && fieldname=value<_filterCondition>
You can add custom field clause through filters.
Example
end_date=04-13-2005, && record_no=uas-1200
If condition value is string (ex: ABC Inc) then value should be entered as follows <_filterCondition>Vendor Name=’ABC Inc’</_filterCondition>. Observe that the value has single quotes. Only equal to "=" operation is supported right now.
Note: If errors are present when evaluating the basic filter condition system will ignore it, but if there are errors in custom filter condition field names and values, system will return an empty list. All condition fields are evaluated using AND. If the combination has only basic fields and it has an error in processing all the records will be returned.
filterNames
The Filter name will contain list of elements that you want to see as part of output XML. Ex: If you want to see project name and project number as output then include projectname and projectnumber.
filterValues, and filterNames are not supported as part of Web services for this release.
This service can be used for both Project (Standard) and Shells of cost code type CBS and Generic.
li_group_name
Use the <li_group_name> tag to specify group names. This tag is applicable to all BPs that support Summary line items other than Summary Payment Application BPs of Base Commit, Change Commit and Payment Applications.
Behavior Specific to Summary Payment Application SOV Type BPs
Note: The information is applicable to Base Commit, Change Commit, and Payment Application Business Processes of Summary Payment Application SOV Type BPs.
When this method is used for the above mention BPs, the response file will contain Cost Allocation details for various Line Items.