# Save Rev Rec Contract

Save Rev Rec Contract

Endpoint: POST /rest/2.0/REVREC_CONTRACT
Version: 1.0
Security: JWT

## Header parameters:

  - `sessionId` (string, required)

## Request fields (application/json; charset=utf-8):

  - `brmObjects` (object)

  - `brmObjects.Id` (string, required)
    Id: Primary key

  - `brmObjects.AccountId` (integer)
    Account

  - `brmObjects.Name` (string, required)
    Rev Rec Contract

  - `brmObjects.Created` (string)
    System controlled field: Date and time the record was created

  - `brmObjects.Updated` (string)
    System controlled field: Date and time the record was last updated

  - `brmObjects.CreatedUserId` (string)
    System controlled field: Id of the user that created the record

  - `brmObjects.UpdatedUserId` (string)
    System controlled field: Id of the last user that updated the record

  - `brmObjects.Status` (string)
    Contract Status: Contract Status can either be Current or Superseded. Current contracts have not been prospectively modified. When a contract is Current, it is eligible to be edited or modified. Contracts that have been prospectively modified have effectively been superseded, and are thus locked from further edits or modifications.

  - `brmObjects.CurrentActiveContract` (integer)
    Current Active Contract: When a contract has been prospectively modified, the original contract is early terminated and prospectively replaced with an associated new rev rec contract. The Current Active Contract represents the most recent rev rec contract in a string of contracts that have been prospectively modified.

  - `brmObjects.OriginalContract` (integer)
    Original Contract: When a contract has been prospectively modified, the original contract is early terminated and prospectively replaced with an associated new rev rec contract. The Original Contract represents the oldest contract in a string of contracts that have been prospectively modified.

  - `brmObjects.SupersededBy` (integer)
    Superseded By: When a contract has been prospectively modified, a contract is terminated and prospectively replaced with an associated new rev rec contract. The new rev rec contract created as a result of the prospective contract modification represents the 'Superseded By' contract relative to the contract it replaced.

  - `brmObjects.Supersedes` (integer)
    Supersedes: When a contract has been prospectively modified, a contract is terminated and prospectively replaced with an associated new rev rec contract. The old contract that was early terminated and replaced as a result of the prospective contract modification represents the 'Supersedes', whereby the new contract 'supersedes' the old one.

  - `brmObjects.StartDate` (string)
    Start Date

  - `brmObjects.EndDate` (string)
    End Date

  - `brmObjects.ContractGLStatus` (string)
    Contract GL Status: There are two statuses available for Rev Rec Contracts including:DRAFTACTIVATEDWhen a contract is in DRAFT status, changes can be made to the contract that do not trigger any changes to the GL. When a contract status is set to ACTIVATED, the changes made to the contract are processed on the GL.

  - `brmObjects.EditModifyContract` (string)
    Edit or Modify Contract: Changes can be made to rev rec contracts using different methods. This field lets the user choose if the assignment of the account product to an existing rev rec contract is an accounting contract modification or an edit of the contract that does not constitute a contract modification in accordance with accounting standards.

  - `brmObjects.ContractModificationDate` (string)
    Date of Contract Modification: This is the accounting date of the contract modification in accordance with accounting standards.

  - `brmObjects.ContractModificationMethod` (string)
    Contract Modification Method: When 'Modify Contract' is selected, there are two methods of modification available to select.Prospective: The prospective modification method results in the rev rec contract to be early terminated and superseded by a new rev rec contract created by the system.Cumulative Catch-Up: The cumulative catch-up method results in changes in the current rev rec contract along with catch-up revenue recognition journal entries booked without a new rev rec contract being created.

## Response 200 fields (application/json):

  - `retrieveResponse` (object)

  - `retrieveResponse.Id` (string)
    Id: Primary key

  - `retrieveResponse.AccountId` (integer)
    Account

  - `retrieveResponse.Name` (string)
    Rev Rec Contract

  - `retrieveResponse.Created` (string)
    System controlled field: Date and time the record was created

  - `retrieveResponse.Updated` (string)
    System controlled field: Date and time the record was last updated

  - `retrieveResponse.CreatedUserId` (string)
    System controlled field: Id of the user that created the record

  - `retrieveResponse.UpdatedUserId` (string)
    System controlled field: Id of the last user that updated the record

  - `retrieveResponse.Status` (string)
    Contract Status: Contract Status can either be Current or Superseded. Current contracts have not been prospectively modified. When a contract is Current, it is eligible to be edited or modified. Contracts that have been prospectively modified have effectively been superseded, and are thus locked from further edits or modifications.

  - `retrieveResponse.CurrentActiveContract` (integer)
    Current Active Contract: When a contract has been prospectively modified, the original contract is early terminated and prospectively replaced with an associated new rev rec contract. The Current Active Contract represents the most recent rev rec contract in a string of contracts that have been prospectively modified.

  - `retrieveResponse.OriginalContract` (integer)
    Original Contract: When a contract has been prospectively modified, the original contract is early terminated and prospectively replaced with an associated new rev rec contract. The Original Contract represents the oldest contract in a string of contracts that have been prospectively modified.

  - `retrieveResponse.SupersededBy` (integer)
    Superseded By: When a contract has been prospectively modified, a contract is terminated and prospectively replaced with an associated new rev rec contract. The new rev rec contract created as a result of the prospective contract modification represents the 'Superseded By' contract relative to the contract it replaced.

  - `retrieveResponse.Supersedes` (integer)
    Supersedes: When a contract has been prospectively modified, a contract is terminated and prospectively replaced with an associated new rev rec contract. The old contract that was early terminated and replaced as a result of the prospective contract modification represents the 'Supersedes', whereby the new contract 'supersedes' the old one.

  - `retrieveResponse.StartDate` (string)
    Start Date

  - `retrieveResponse.EndDate` (string)
    End Date

  - `retrieveResponse.ContractGLStatus` (string)
    Contract GL Status: There are two statuses available for Rev Rec Contracts including:DRAFTACTIVATEDWhen a contract is in DRAFT status, changes can be made to the contract that do not trigger any changes to the GL. When a contract status is set to ACTIVATED, the changes made to the contract are processed on the GL.

  - `retrieveResponse.EditModifyContract` (string)
    Edit or Modify Contract: Changes can be made to rev rec contracts using different methods. This field lets the user choose if the assignment of the account product to an existing rev rec contract is an accounting contract modification or an edit of the contract that does not constitute a contract modification in accordance with accounting standards.

  - `retrieveResponse.ContractModificationDate` (string)
    Date of Contract Modification: This is the accounting date of the contract modification in accordance with accounting standards.

  - `retrieveResponse.ContractModificationMethod` (string)
    Contract Modification Method: When 'Modify Contract' is selected, there are two methods of modification available to select.Prospective: The prospective modification method results in the rev rec contract to be early terminated and superseded by a new rev rec contract created by the system.Cumulative Catch-Up: The cumulative catch-up method results in changes in the current rev rec contract along with catch-up revenue recognition journal entries booked without a new rev rec contract being created.

## Response 400 fields (application/json):

  - `error` (string)
    Bad request

  - `message` (string)
    Bad request

## Response 401 fields (application/json):

  - `error` (string)
    Unauthorized

  - `message` (string)
    Unauthorized

## Response 404 fields (application/json):

  - `error` (string)
    Not found

  - `message` (string)
    Not found

## Response 429 fields (application/json):

  - `error` (string)
    Too many requests

  - `message` (string)
    Too many requests

## Response 500 fields (application/json):

  - `error` (string)
    Internal error

  - `message` (string)
    Internal error