You are here: Transaction Rules > Transaction Elements > Suspense Element

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# Suspense Elements

## Description

The <Suspense> and <MultiSuspense> elements control the ability to apply suspense to an activity.

A transaction can have a <Suspense> element or a <MultiSuspense> element, but not both.

If a <Suspense> element is present in the transaction, a Suspense tab will be available on the Activity Details screen with a Suspense field and a suspense record will be written in AsSuspense when the activity processes.

If a <Multisuspense> element is present in the transaction, a Suspense tab will be available on the Activity Details screen with a Suspense section and multiple suspense records will be written in AsSuspense when the activity processes.

## Suspense Element/Attribute Table

Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<Suspense> | The start and end tags of the element. Cannot be used with <MultiSuspense> element. |  | Activity field containing the amount of the suspense that will be attached.
|  | AUTOENTRY | Yes – A suspense record is created for the amount of the element’s reference field. This value is also automatically attached. No – A suspense record must exist and be attached by the user to the activity.
OVERRIDABLE | Yes – Errors when received may be overridden by the user. No – Errors may not be overridden by the user. Ignore - Ignore errors
VALUE | Sufficient: The value of the suspense record must be at least the value of the activity field. Equals - The value of the suspense record must equal the value of the activity field.

## MultiSuspense Element/Attribute Table

Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<MultiSuspense> | The start and end tags of the element. This element is used so multiple suspense items can be attached to the Activity. Cannot be used with <Suspense> element |  | Activity field containing the total amount of suspense that will be attached.
FIELD | String
START | Integer Defines the minimum number of suspense items.
STOP | Integer Defines the maximum number of suspense items.

## XML Example

    <MultiSuspense START="0" STOP="3">BonusAmount</MultiSuspense>

Example Suspense Activity Detail Screen

###

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents