- Previous: WBS Automation
- Up: WBS Automation
- Next:
WBS/WBE creation
This API allows to create WBS and/or WBE element in SAP.
#### Request URI
#### Request Structure
#### Request Example
#### Response Example
Project/WBS Creation
WBE Creation
## Error cases
The errors are categorized with the following code:
Example of resubmission request:
API field | Type | Description | Mandatory | Technical Details |
project |
||||
id |
String | SAP project definition id | N | Needed to add new WBE to a particular project |
description |
String | Project description | N | |
portfolio |
String | SAP portfolio code related to the project | N | Example: "GSC" for Global Supply Chain |
investmentArea |
String | Investiment Area to which the project is linked | N | |
location |
String | Global or Local project | N | If global project than send "GLOB", otherwise send the local regional code (example "AMER" for America) |
fiscalYear |
String | Fiscal year to which the project is in scope | N | Format: YYYY |
externalProjectNumber |
String | Number of the Demand associated to the project | N | Format: YYYY |
wbs (0..∞) |
||||
description |
String | WBS description | N | |
companyCode |
String | SAP Company code | N | |
program |
String | Project Program to which the project is affiliated | N | |
platform |
String | Platform involved in the project | N | |
wbe (0..∞) |
||||
description |
String | WBE description | N | |
type |
String | Spending type | N | Opex or Capex |
companyCode |
String | SAP Company code id | N | |
costCenterResponsible |
String | Cost Center actually responsible for the WBE | N | |
investmentProfile |
String | SAP investiment profile code related to the WBE | N | Needed only for Capex. Accepted values: "Z00001" for Software License, "Z00002" for Consulting Services, "Z00108" for Hardware |
subArea |
String | subArea related to the WBE | N | |
subAccountDescription |
String | subAccount description related to the WBE | N | |
serviceNowNumber |
String | Service Now id of the WBE | N | |
costCenter |
String | Cost Center related to the WBE | N | |
rechargedCompanyCode |
String | SAP company code associated with the cost plan | N | |
spendingCategory |
String | Recurring fee or one-shot payment | N | For one-shot payment, send "ONESHOT", otherwise leave it blank |
functionalArea |
String | Functional Area related to the WBE | N | Needed only for Opex. Accepted value: "0090" |
goLiveDate |
String | Planned go-live date | N | Format "YYYYMMDD" |
#### Response Structure
API field | Type | Mandatory | Description | |
ResponseType |
||||
status |
String | Y | Possible status returned: "Success" or "Error" | |
code |
String | N | In case of error, an error code is returned. See table below for details about error code and possible action | |
message |
String | Y | In case of error, this field provides a description of the error. Otherwise it notifies a successful transaction. | |
project |
Returned only in case of Success | |||
id |
String | N | Project Id created/updated | |
description |
String | Project description | N | |
wbs (0..∞) |
||||
id |
String | N | WBS Id created/updated | |
description |
String | N | WBS description | |
wbe (0..∞) |
||||
id |
String | N | WBE Id created/updated | |
description |
String | N | WBE description |
Code | Description | Actions |
WBS-001 | This indicates a generic error occurred anywhere during the integration. | Before resubmit the request, it is suggested to check on SAP if the project has been already created in order to avoid duplicates. |
WBS-002 | Error occurred during first data saving in SAP. | Since this step is failing, after fixing the error cause, it is possible to resubmit the request. |
WBS-003 | Error occurred in a following steps, after saving some data on SAP | Since the project, WBS and WBE have been already created, do not resubmit the request, otherwise a duplicate will be created on SAP. To avoid duplicates, the WBE id created at a previous step must be send in the request so that it won't be created again in SAP. |
- Previous: WBS Automation
- Up: WBS Automation
- Next:
0 Comments
Please sign in to post a comment.