Transaction General Pane

Update required and optional transaction processing features from this pane. There are two required sections: Transaction and Effective Date, which are automatically added. The following sections are optional and can also be added.

  • Values Block

  • Withholding

  • Valuation

  • Suspense

  • Membership

  • Multi-suspense
  • Transitions

  • ValueFinancialEntry

The optional sections can be configured via the wizard when a new transaction is created or edited via Edit Transaction General from the right-click menu.

Expand or Collapse Sections on General Pane

Sections of the General Pane can be expanded or collapsed by clicking the box on the left side of the section. The box contains a plus sign plus sign on sections of general pane when the section is collapsed. Click the plus sign to expand the section. The box contains a minus sign minus sign on transaction section of general pane when the section is expanded. Click the minus sign to collapse the section.

Transaction Section

There are four fields that can be updated in the Transaction section on the General Pane.

  • Type: The transaction type can be updated from this drop down box.

  • Status: The transaction status can be updated from this drop down box.

  • Processing order: Update the processing order by entering a new value in the processing order field. The Time Line button will open a window, which will display a list of all transactions and their processing order.

  • NAV Correction: This should be set to Yes for all financial transactions.

Effective Date Section

All of the effective date attribute values can be updated from the Effective Date section on the General Pane.

  • Status: Select Enabled or Disabled. If blank, no status attribute will appear in the XML source.

  • Type: Select SQL, System or blank.

    • If SQL, then a box will appear to the right of the Properties information with a space for the user to enter a SQL query.

    • If System, then Value field should be disabled. Effective date should default to system date.

    • If blank, use the Value attribute field to enter the value for the effective date.

  • Title: Enter a title for the Effective Date.

  • Value: Only used when Type=blank. This field allows user to select a specific value from the Market Maker calendar for the activity effective date.

  • Business Day: Select Yes or No. If Yes, the system checks to see if the current system date was a business day and if not, bumps it to the next business day for the Market Maker’s calendar. If No, the system leaves the date unchanged. If blank, the BUSINESSDATE attribute will not appear in the XML.

Effective Date section with SQL selected

Effective Date Section with SQL Selected

Optional Sections

The optional sections will have a green plus sign next to the name if the section contains information. Click the plus sign to open the section and update information. If the plus signs are greyed out, then that indicates that the sections are empty. Please see the XML Configuration Guide for a list of all elements, attributes and values needed for configuration.

  • Values Block: Creates a section on the Activity Detail screen that displays the current policy fund values. The section is display only.

  • Withholding: Allows for the configuration of the Withholding functionality.

  • Valuation: Calls the valuation engine to run valuation processing.

    • Effective Date NUV Must Exist: If this box is checked, the Unit Values (NUVs) as of the activity’s Valuation Date must be present in order for the activity to process at all. If there are no Unit Values, the system displays an error message stating NUV’s Missing (Effective Date).
    • System Date NUV Must Exist: If the box is checked, Unit Values as of the System Date must be present in order for the activity to process at all. If no Unit Values are present, the system displays an error message stating NUV’s Missing (System Date). If the box is unchecked for a variable product and NUV’s do not exist for the System Date, but Unit Values are present for the Valuation Date, the activity will process in its entirety, except for the calculation of Gain/Loss. The Activity List screen will display a lightning bolt icon next to the activity with a status of Gain/Loss Pending until Unit Values are added for the System Date. After Unit Values have been entered for the System Date and either the lightening bolt is clicked again or Cycle is run, the Activity Status will change to Active and Gain/Loss will have been calculated.
    Important   For Fixed products, this should never be checked.

  • Suspense: Displays and controls the suspense field inside the activity.

  • MultiSuspense: Defines the multi-suspense attribute values. The currencies of each suspense item must match the premium currency selected on the activity in OIPA.

  • Membership: Allows for the Membership section to be expanded and enabled. This section allows for the details relevant to the class membership calculation process to be entered on the Membership table.
    • ClassGroupType: this is used to determine the Class Group type of membership calculation. The drop down box will be populated with the CodeValue defined on the AsCode table for CodeName AsCodeClassGroupType.
    • DisplayMembershipClass: this is used to specify the Class Membership types to display. The default value for this field will be blank. When blank is selected the DISPLAYMEMBERSHIPCLASS element is not added.
    • WriteMembership: this indicates if membership records will be written to the database. Users can enter Yes, No or have the option to enter field or math variable names equal to Yes or No. When a value is entered a WriteMembership element will be added to the transaction XML. If blank, then no element will be added.
    • EffectiveFromDate: define the Effective From date of the membership calculation. Users can enter the string literal, SystemDate. Users also have the option to enter field or math variable names equal to a valid date. When a value is entered, an EffectiveFromDate element will be added to the transaction XML. If blank, no element will be added.
    • EffectiveToDate: define the Effective To date of the membership calculation. Users can enter the string literal, SystemDate. Users also have the option to enter field or math variable names equal to a valid date. When a value is entered, an EffectiveFromDate element will be added to the transaction XML. If blank, no element will be added.

  • Transitions: Provides the ability to automatically update the effective date of an activity as a way to transfer Gain/Loss to the client. If this checkbox is selected, two fields are enabled: Method and AdvanceToSystemDate. Two tags are also added to the XML Source with default values: <Transitions> and <Queue>.

    • Method: Valuation is the only option for this drop down box. This is a required attribute that tells what validation is driving the Queue determination.

    • AdvanceToSystemDate: This is an auto-complete text field that accepts a literal value of Yes or No. This auto-complete text box will load all field names and math variable names that are text datatype. This field will also resolve copybooks contained within the transaction. When not entering literal Yes or No values the user must select a field name or math variable name that holds a valid value of Yes or No. Entry in this field is optional.

Steps to Add or Remove Sections in the General Pane

  1. Check-out the transaction’s XML file.

  2. Right-click on the transaction's XML file.

  3. Select Edit Transaction General.

  4. Check or uncheck XML section checkboxes.

  5. Save and check-in the transaction.