Table Description
Liability Regeneration Request: The recreation of a previously canceled liability instrument.

A regenerated liability instrument be generated from an existing liability instruction.

Technical Notes

Note that currently in Curam, there is no functionality implemented to facilitate the regeneration of a Liability Instruction.
Relationship Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions.
Model Details
Location in Model: Logical View::MetaModel::Curam::Core::Reference Model::Financial::Entity Objects::LiabilityRegenerationRequest::LiabilityRegenerationRequest
Controlling File: core\model\Packages\Financial Manager Packages\LiabilityRegenerationRequest_cat.efx
Table Options
ALLOW_OPTIMISTIC_LOCKINGyes
Attributes (6)
AttributeStereotypeNullableDescriptionDomain DefinitionCodetableDDL Type
liabInstructionIDdetailsnoLiabilityInstructionID of the LiabilityInstruction which is to be regenerated.LIABILITY_INSTRUCTION_ID SVR_INT64
requestDatedetails Date on which the request for regeneration of the Instrument was received.CURAM_DATE SVR_DATE
reasonTextdetails Free text registered by the user to record the reason for the regeneration.REASON_TEXT SVR_STRING<200>
outcomeCodedetails Code value to denote whether the regeneration request has been approved or not. Populated from the RegenerationOutcome code table.REGENERATION_OUTCOME_CODERegenerationOutcomeSVR_STRING<10>
commentsdetails Free text registered by the User.COMMENTS SVR_STRING<300>
liabRegenerationIDkeynoUnique reference number assigned by the systemLIABILITY_REGEN_REQUEST_ID SVR_INT64
Foreign Keys (1)
ChildParent
LiabilityRegenerationRequest.liabInstructionIDLiabilityInstruction.liabInstructionID
Indices (1)
Index NameAttributes
LiabRegRequestIdxliabInstructionID
Operations (3)
OperationStereotypeOptionsDescriptionSQL
insertinsert Standard Operation 
modifymodifyOPTIMISTIC_LOCKING: yes
Standard Operation 
readread Standard Operation 
Related Pages (0)