Create a project expense resource

post

/fscmRestApi/resources/11.13.18.05/projectExpenseResources

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Expense Amount
    Amount allocated in the project for the expense resource.
  • Title: Name
    Maximum Length: 240
    Display name of the resource.
  • Title: Project ID
    Unique identifier of the project associated with the resource assignment. To identify the project, provide a value only for this attribute, or any one of the Project Number or the Project Name attribute. Project is mandatory when creating an assignment.
  • Title: Project Name
    Maximum Length: 240
    Name of the project.
  • Title: Project Number
    Maximum Length: 25
    Alphanumeric identifier of the project.
  • Title: Resource ID
    Unique identifier of the project enterprise resource.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : projectExpenseResources-item-response
Type: object
Show Source
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    Indicates the resource who created the row of data.
  • Title: Creation Date
    Read Only: true
    Date when the row of data was created.
  • Title: Expense Amount
    Amount allocated in the project for the expense resource.
  • Title: Last Updated Date
    Read Only: true
    Date when the record was last edited.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    Indicates who last edited the record.
  • Links
  • Title: Name
    Maximum Length: 240
    Display name of the resource.
  • Title: Project Currency Code
    Read Only: true
    Maximum Length: 15
    Default Value: USD
    The code for the currency used in the project. The currency code is a three-letter ISO code associated with a currency.
  • Title: Project ID
    Unique identifier of the project associated with the resource assignment. To identify the project, provide a value only for this attribute, or any one of the Project Number or the Project Name attribute. Project is mandatory when creating an assignment.
  • Title: Project Name
    Maximum Length: 240
    Name of the project.
  • Title: Project Number
    Maximum Length: 25
    Alphanumeric identifier of the project.
  • Title: Project Resource ID
    Read Only: true
    Unique identifier of the project resource.
  • Title: Resource ID
    Unique identifier of the project enterprise resource.
Back to Top

Examples

The following example shows how to create a project expense resource by submitting a POST request on the REST resource using cURL.

curl --user ppm_cloud_user -X POST -d @example_request_payload.json --header "Content-Type: application/json" https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectExpenseResources

Request Body Example

The following shows an example of the request body in JSON format.

{
"Name" : "Construction",
"ProjectId" : "300100185240389",
"ExpenseAmount" : "1500"
}

Response Body Example

The following shows an example of the response body in JSON format.

{
"ProjResourceId": 300100211649582,
"ProjectId": 300100211613856,
"ResourceId": 300100033414520,
"Name": "Construction",
"ExpenseAmount": 1500,
"CreatedBy": "Carlton.Baugh",
"CreationDate": "2020-12-09T06:43:45+00:00",
"LastUpdatedBy": "Carlton.Baugh",
"LastUpdateDate": "2020-12-09T06:43:45.335+00:00",
"ProjectCurrencyCode": "USD",
"ProjectName": "test 1207 1124",
"ProjectNumber": "test 1207 1124",
"links":
-0: {
"rel": "self"
...
}
}
Back to Top