You are here: Business Rules > Attached Rules > DeliveryRequirements

Oracle® Insurance XML Configuration Guide Release 9.4.1.0 E23637_01

# DeliveryRequirements

## Description

Delivery Requirements business rule defines the fulfillment criteria of the activity’s requirements via its date fields. The rule must be attached to a transaction and be listed in the TransactionBusinessRulePacket of the transaction.

DeliveryRequirements Element/Attribute Table
Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<DeliveryRequirements> | The opening and closing tag of the DeliveryRequirements business rule. |  |
| PROCESSONCOMPLETE | Optional: "Yes": Automatically sets the ActivityEffectiveDate of the attached activity to the latter of the CloseDate [where the status is not “05” (Cancelled)], or the ActivityEffectiveDate. Date used can be overridden by the NewActivityDate attribute. "No": the activity's effective date will stay at its original value (default).
NEWACTIVITYDATE | Optional: MathVariable or Field; datatype: Date Sets the new activity effective date to this value once all requirements are complete. The attribute should accept any date value so long as it is not earlier than the activity’s current effective date. If used, PROCESSONCOMPLETE must be set to “Yes”.
<RequiredDates> | Required, Repeatable; Defines the date fields that are required |  |
| TYPE | Required: Identifies the relationship that multiple dates have to one another in order to fulfill the requirement. "AND": All fields identified must be populated and equal to or less than the system’s date in order for the requirement to be met. "OR": As long as one of the fields identified is populated and equal to or less than the system’s date, the requirement is met.
<RequiredDate> | Required, Repeatable Identifies an individual date field to be tested for requirement fulfillment. |  | RequestedDate DueDate ReceivedDate WaivedDate OpenDate CloseDate

## XML Example

    <DeliveryRequirements PROCESSONCOMPLETE=”Yes” NEWACTIVITYDATE=”Activity:DateField”>>

    <RequiredDates TYPE="AND">

    <RequiredDate>OpenDate</RequiredDate>

    <RequiredDate>CloseDate</RequiredDate>

    </RequiredDates>

    </DeliveryRequirements>

## Schema

    <DeliveryRequirements>

    <RequiredDates TYPE="[OR|AND]">

    <RequiredDate>RequestedDate</RequiredDate>

    <RequiredDate>DueDate</RequiredDate>

    <RequiredDate>ReceivedDate</RequiredDate>

    <RequiredDate>WaivedDate</RequiredDate>

    </RequiredDates>

    </DeliveryRequirements>

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

Open table of contents