1. REST API for Oracle Fusion Cloud Project Management
  2. Tasks
  3. Project Costs

Adjust project costs

post

/fscmRestApi/resources/11.13.18.05/projectCosts/{projectCostsUniqID}/action/adjustProjectCosts

Adjust existing project costs after reviewing them.

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Project Costs resource and used to uniquely identify an instance of Project Costs. The client should not generate the hash key value. Instead, the client should query on the Project Costs collection resource in order to navigate to a specific instance of Project Costs to get the hash key.
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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.
Supported Media Types
Request Body - application/vnd.oracle.adf.action+json ()
Root Schema : schema
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Body ()
Root Schema : schema
Type: object
Show Source
Back to Top

Examples

The following example shows how to adjust project costs 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/vnd.oracle.adf.action+json" https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectCosts/7861598

Request Body Example

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

{ "name":"adjustProjectCosts", "parameters": [ {"AdjustmentType": "Update Accounts"}, {"RawCostDebitAccountCombinationId": 122865}, {"BurdenCostCreditAccountCombinationId": 122865}, {"BurdenCostDebitAccountCombinationId": 122865}, {"BurdenedCostCreditAccountCombinationId": 122865} ] }

Response Body Example

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

{ "result": "The project cost with transaction number 7861598 was adjusted and as a result the following project costs were created with transaction numbers: 7876610." }

Request Body Example

The following shows an example of the request body to transfer to a new expenditure type which is not rate based in JSON format. 

{ "name":"adjustProjectCosts", "parameters": [ {"AdjustmentType": "Transfer"}, {"ExpenditureType": "Airfare"} ] }

Response Body Example

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

{ "result": "The project cost with transaction number 7861598 was adjusted and as a result the following project costs were created with transaction numbers: 7876610." }

Request Body Example

The following shows an example of the request body to transfer to a new expenditure type which is rate based in JSON format. 

{ "name":"adjustProjectCosts", "parameters": [ {"AdjustmentType": "Transfer"}, {"ExpenditureType": "Administration"}, {"Quantity": 50} ] }

Response Body Example

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

{ "result": "The project cost with transaction number 7861598 was adjusted and as a result the following project costs were created with transaction numbers: 7876610." }

Request Body Example

The following shows an example of the request body to transfer to a new project, task and expenditure type in JSON format. 

{ "name":"adjustProjectCosts", "parameters": [ {"AdjustmentType": "Transfer"}, {"ProjectId": 300100166942329}, {"TaskId":100100082734576 }, {"ExpenditureTypeId": 300100148008012} ] }

Response Body Example

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

{ "result": "The project cost with transaction number 7952956 was adjusted and as a result these project costs were created with transaction numbers 7953010." }

Request Body Example

The following shows an example of the request body to set a billable expenditure item to non billable in JSON format. 

{ "name": "adjustProjectCosts", "parameters": [ { "AdjustmentType": "Set to nonbillable" } ] }

Response Body Example

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

{ "result": "The project cost was adjusted." }
Back to Top