applyAdjustments

Adjustments are like updates, except that they come from a balancing application and a separate set of presentment table columns is used to track them. Item inserts, deletes, moves, and updates are all done the same way as the apply updates request. The only difference is that the totals are applied to a different set of columns in the presentment table.

Once the adjustments are applied, they may affect the item counts and values for the batch (ICL). These statistical changes are applied to the following batch (ICL) totals:
  • ADJ_CREDITS
  • ADJ_DEBITS
  • ADJ_CREDIT_AMT
  • ADJ_DEBIT_AMT
The apply adjustments message content is identical to the apply updates message, except for the message type. The following table shows the fields that are needed to create an apply adjustments request.
Table 1. applyAdjustments Request
Field Description
Message Type The message type text for this message. The strings that can be used for the message type are:
  • AppBridgeConstants.MSGTYPE_APPLY_ADJUSTMENTS
  • applyAdjustments
Using the string that is defined in the AppBridgeConstants interface is the preferred method for setting the message type.
Unit of Work Batch (ICL) identifier. It is a long value and must be capable of being parsed as a long.
Payload Any transaction action bean type:
  • PaymentUpdateBean
  • PaymentInsertBean
  • PaymentDeleteBean
  • ImageUpdateBean
  • ModifyPaymentsBean
  • BlockMoveBean
  • BlockInsertBean
Each transaction action bean contains a payment ID and a set of name and value pairs that describe the item or transaction fields to modify.
Note: The name and value pairs are not meant for general use by an external application. Each transaction action bean provides individual setters for specifying the item or transaction parameters that can be modified. Do not attempt to use the name and value pair maps in any transaction action bean directly, because the bean setters provide a layer of data typing that the general application developer cannot know.