Create Accounting Details

Create Accounting Details for a Registration

This section provides information on how this operation allows the user to create accounting detail(s) for registration through the following POST request:

http://[hostName]:[portNumber]/[api-context-root]/registrations/{id}/accountingdetails/create

Following is a resource representation of registrations:

  ...  ...
 "links": [
    {
      "href": "http://[hostName]:[portNumber]/[api-context-root]/generic/registrations/{id}",
      "rel": "self"
    },
    {
      "href": "http://[hostName]:[portNumber]/[api-context-root]/registrations/{id}/accountingdetails/create,
      "rel": "registration:createaccounting",
      "httpMethod": "POST"
    }
  ]
}

Payload

The payload should mandatorily contain the necessary information regarding the dynamic logic function.

{
  "createAccountingDetail"  : "Dynamic logic function code"
}

The system creates accounting detail line(s) and records an entry in the accounting detail grouping table.

This dynamic logic function must be of signature Create Accounting Detail for Registration or Create Accounting Detail with Dual for Registration. If it is of another signature, the error message FIN-IP-REGI-003 is returned.

Authorization

A user authorization configuration requires access to this operation. The relevant access restriction is registrations.createaccountingdetail IP.

Response

The response is the appropriate HTTP Status code defined in Response Messages.

Possible Message Codes

The possibility of the following message codes may return in response:

  • HTTP Status 204: When the registration is found, and the operation did not end up in error.

  • HTTP Status 404: Is returned if the registration is not found.

The following HTTP-specific errors can occur:

Table 1. Response Messages
Code Severity Message Text

FIN-IP-REGI-003

Fatal

Dynamic logic with code {0} is unknown or not of signatures Create Accounting Detail or Create Accounting Detail with Dual for registration.