Database Table: CasePaymentSuspension
| Case Payment Suspension:
A suspension of a payment on a case.
If a payment exceeds the maximum payment limit the entire payment instrument is suspended. If suspended, manual approval of the payment by a supervisor must take place before payment can be issued. The maximum payment amount is stored against the delivery pattern for a Curam product.
This table holds a type of case event. Events are displayed in an events calendar for viewing by the user.
Example The maximum payment amount for Product X is specified as $1000.
User Ronan Rooney submits a case where the payment amount is $1050. The payment is suspended and a notification is sent to his supervisor to review and approve the payment.
Technical Notes Optimistic locking is not required for this table as the data is never modified.
|
|
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions.
|
|
|
| Location in Model: | Logical View::MetaModel::Curam::Core::Reference Model::Case::Entity Objects::Case Payment Suspension::CasePaymentSuspension |
| Controlling File: | core\model\Packages\Case\Case Payment Suspension_cat.efx |
| ALLOW_OPTIMISTIC_LOCKING | no |
| Attribute | Stereotype | Nullable | Description | Domain Definition | Codetable | DDL Type |
| casePaymentSuspensionID | key | no | This is the unique ID assigned to each Case Payment Suspension record. | CASE_PAYMENT_SUSPENSION_ID | | SVR_INT64 |
| caseID | details | no | The ID of the case to which this Case Payment Suspension record is related. | CASE_ID | | SVR_INT64 |
| suspensionDate | details | | The date on which the payment suspension was applied. | CURAM_DATE | | SVR_DATE |
| details | | The reason this Payment Suspension was applied. | COMMENTS | | SVR_STRING<300> |
|
| Index Name | Attributes |
| CasePaymSuspIdx | caseID |
|
| Operation | Stereotype | Options | Description | SQL |
| insert | insert | | Standard Operation | |
| read | read | | Standard Operation | |
|
