Batch (ICL) update bean

This bean is the primary facility for applying changes to a batch (ICL) in the Transaction Server.

The payload class name of the batch (ICL) update bean is com.ibm.paydir.ima.txacc.app.bridge.PresentmentUpdateBean.

Use the bean to modify the batch (ICL) condition code or update the user field.
Note: The update batch (ICL) request fails if the specified batch (ICL) is absent.
When queried, the batch (ICL) update bean returns UPDATE_PRESENTMENT as its update code. It can be queried for the batch (ICL) ID that is affected by the update by using the following accessor method: 
public  long  getPresentmentId()
The caller can use the mutator methods that are shown in the following table to configure the batch (ICL) update bean.
Table 1. UPDATE_PRESENTMENT request
Method name Takes data type Description
setCondition Short Updates the batch (ICL) condition code:
  • Accepted is 0
  • Rejected is 1
setOverrideable Boolean Updates the condition is overrideable indicator.
setOverridden Timestamp Updates the condition is overridden indicator.
setOverriddenBy Sting Updates the condition is overridden by ID.
setUserField String Updates the user field.
setIsnAllocated Timestamp Updates the ISN allocated state.
setIcreExtracted Timestamp Updates the ICRE extracted state.
setMcreExtracted Timestamp Updates the MCRE extracted state.
setValidated Timestamp Updates the validated state.
setIqa Timestamp Updates the IQA state.
setBalanced Timestamp Updates the balanced state.
setRepaired Timestamp Updates the repaired state.
setReviewed Timestamp Updates the reviewed state.
setDupDetected Timestamp Updates the duplicate detected state.
setDupReviewed Timestamp Updates the duplicate reviewed state.
setAdjusted Timestamp Updates the adjusted state.
In addition, the user can add their own fields to the presentment user table. The user fields can have any of the primary database types.
Note: The presentment user table has a foreign key to the presentment table, which might restrict the fields that can be added.
The batch (ICL) update bean supports updating the user fields by these methods:
  • setUserData ( String name, Timestamp val )
  • setUserData ( String name, short val )
  • setUserData ( String name, byte val )
  • setUserData ( String name, char val )
  • setUserData ( String name, Object val )

The setUserData Java™ method is overloaded to accept the various data types for the user field value. The value supplied for a user field must use the data type that conforms to its database definition. For example, to update a field with the database data type SMALLINT, use the method that accepts a short.

Use the method that accepts an Object as the value to update user field with data types not supported by the methods listed. For example, to update a field with the database data type BIGINT, call setUserData with the Java primitive type of long. The long primitive value is converted to an Object.

For presentment table updates, the Transaction Server generates an SQL statement based on the collection and attempts to update the batch (ICL) as specified. Updating total counts and amounts is not supported. Modifying the states can cause the events to start. Any modifications to the states might be ignored, if the state is already at the requisite enablement.