Adjust project costs
/fscmRestApi/resources/11.13.18.05/projectCosts/{projectCostsUniqID}/action/adjustProjectCosts
Request
-
projectCostsUniqID(required): string
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.
-
Effective-Of:
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. -
Metadata-Context:
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".
-
REST-Framework-Version:
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.
- application/vnd.oracle.adf.action+json
object
-
AdjustmentType: string
Type of adjustment that is to be performed on the project cost. You must enter a value for either this attribute or AdjustmentTypeCode to perform a project cost adjustment. A list of valid values is defined in the lookup PJC_ADJUSTMENT_TYPE.
-
AdjustmentTypeCode: string
Code that identifies the type of adjustment that is to be performed on the project cost. You must enter a value for either this attribute or AdjustmentType to perform a project cost adjustment. A list of valid values is defined in the lookup PJC_ADJUSTMENT_TYPE.
-
BillableFlag: boolean
Determines whether the destination project cost transaction is billable. Only applicable when performing Split adjustments on contract projects.
-
BurdenCostCreditAccountCombinationId: number
Code combination identifier of the burden cost credit account.
-
BurdenCostDebitAccountCombinationId: number
Code combination identifier of the burden cost debit account.
-
BurdenedCostCreditAccountCombinationId: number
Code combination identifier of the burdened cost credit account.
-
BurdenedCostDebitAccountCombinationId: number
Code combination identifier of the burdened cost debit account.
-
CapitalizableFlag: boolean
Determines whether the destination project cost transaction is capitalizable. Only applicable when performing Split adjustments on capital projects.
-
Comment: string
Comment entered for the project cost.
-
ContractId: number
Identifier for the destination contract.
-
ContractName: string
Name of the destination contract.
-
ContractNumber: string
Number of the destination contract.
-
ExpenditureType: string
A classification of cost that is assigned to each project cost. Expenditure types are grouped into cost groups (expenditure categories) and revenue groups (revenue categories).
-
ExpenditureTypeId: number
Identifier of the expenditure type.
-
FundingSourceId: number
Identifier for the destination funding source.
-
FundingSourceName: string
Name of the destination funding source.
-
FundingSourceNumber: string
Number of the destination funding source.
-
HoldInvoiceFlag: boolean
Determines whether the destination project cost transaction is withheld from invoice generation. Only applicable when performing Split adjustments on contract projects.
-
HoldRevenueFlag: boolean
Determines whether the destination project cost transaction is withheld from revenue recognition. Only applicable when performing Split adjustments on contract projects.
-
Justification: string
User-entered justification for an adjustment.
-
ProjectId: number
Identifier of the destination project.
-
ProjectName: string
Name of the destination project.
-
ProjectNumber: string
Number of the destination project.
-
ProjectRoleId: number
Identifier of the project role associated with the project cost. You must include either the ProjectRoleId or ProjectRoleName attribute to adjust the project role value on a project cost transaction. If you include both attributes, the value for the ProjectRoleId attribute is used and the ProjectRoleName value is ignored.
-
ProjectRoleName: string
A classification of the relationship between a person and the project associated with the project cost, such as Consultant or Technical Lead. You must include either the ProjectRoleId or ProjectRoleName attribute to adjust the project role value on a project cost transaction. If you include both attributes, the value for the ProjectRoleId attribute is used and the ProjectRoleName value is ignored.
-
Quantity: number
Quantity entered on the project cost.
-
RawCostCreditAccountCombinationId: number
Code combination identifier of the raw cost credit account.
-
RawCostDebitAccountCombinationId: number
Code combination identifier of the raw cost debit account.
-
RawCostInTransactionCurrency: number
Project cost in the transaction currency that is directly attributable to the work performed.
-
TaskId: number
Identifier for the destination task.
-
TaskName: string
Name of the destination task.
-
TaskNumber: string
Number of the destination task.
-
TransactionCurrency: string
Code for the currency in which the project cost was incurred.
-
TransactionCurrencyCode: string
The currency in which the project cost was incurred.
Response
- application/json
- application/vnd.oracle.adf.actionresult+json
Default Response
object
-
result(required): string
Response that indicates if the adjustment on the project cost was successful.
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 accountsin 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." }