AutoAdjust configuration

The following steps are necessary to configure AutoAdjust for processing adjustments:

Use the manage customer types page to define customer types.
A customer type is a one-character code that has an optional description. For more information about the manage customer types page, see Manage customer types page.
Define participants and associate a customer type with each participant. To associate a customer type with a participant, do the following steps:
Note: The customer type is optional and does not need to be assigned.
1. Go to the manage partners page to display the participants. For more information, see the links in the related information.
2. Select a participant from the list and view its details.
3. Display the attributes for this participant by selecting configure general attributes.
4. To change the customer type, edit the participant attributes.
Use the adjustment codes page to define or modify the adjustment codes.
The adjustment code is a two character code that is associated with an adjustment action. AutoAdjust comes with some predefined adjustment codes, which can be modified or deleted by the user. For more information about using the adjustment codes page, see Adjustment Codes page.
Use the adjustment actions page to associate an adjustment code with each adjustment action.
When an adjustment is made by a particular action, the corresponding adjustment code is used in the adjustment entry that is written to the database.
To associate an adjustment code with each adjustment action, do the following steps.
1. Go to the adjustment actions page. For more information about using the adjustment actions page, see Adjustment Actions.
2. Select an action from the list and view its details.
  The following adjustment actions are predefined for AutoAdjust:
  
  DBDL
  
  Duplicate bundle
  
  RBDL
  
  Rejected bundle
  
  ICLD
  
  Out of balance bundle
  
  NCI
  
  Nonconforming transaction
  
  TXOB
  
  Transaction balance
  
  IAD
  
  Item amount difference
3. Edit the adjustment action and then select its adjustment code from the list.
Use the customer type actions page to define the adjustment actions that are to be done for each customer type. AutoAdjust uses the adjustment actions to be done for a particular customer when it sets the balanced and adjusted flags for bundles, batches (ICLs), or both. Examples of how AutoAdjust uses the actions are shown in the following list.
- If item amount difference adjustments are being done, the balanced flag is not set until all items that have amount differences are adjusted.
- If item amount difference adjustments are not being done, the balanced flag can be set as soon as all exception items are adjusted.
- If nonconforming item adjustments are not being done, the adjusted flag can be set without all of the exception items adjusted.
If a specific participant does not have a customer type that is associated with it, use a value of blank or unspecified in the Unassigned actions field when actions are assigned. For more information about using the page, see Customer type actions.
Use the adjustment types page to define the grouping attributes for each adjustment code and customer type.
The adjustment types page is used to define the grouping behavior for a particular adjustment code and customer type combination. The adjustment code and customer type combination must be unique.
Note: If the grouping indicator is set to yes, AutoAdjust groups individual adjustments into a single adjustment entry if the number of adjustments exceeds the grouping threshold.
To define the grouping attributes for each adjustment code and customer type, do the following steps.
1. Go to the adjustment types page. For more information about using the adjustment types page, see Adjustment types or the online help.
2. Select an adjustment type from the list and view its details.
3. Edit the adjustment type and then set the group indicator to Yes or No. If this adjustment type is to be part of a group, do the following steps.
  1. Enter the threshold level in the Group Threshold field.
  2. In the Group Level field, select Batch or Segment.
  3. In the Group DTF Flag field, select Yes or No.
Use the adjustment error page to define the error text to be associated with each adjustment code and grouping indicator.
Default error fields are used if errors associated with the rejected segment or item are not found in the database. Gateway can be configured to assign error codes to items, segments, batches (ICLs), and transmissions as work is being loaded. It is these errors that are gathered and included with the adjustment.
To define the error text to be associated with each adjustment code and grouping indicator, do the following steps.
1. Go to the adjustment errors page. For more information about using the adjustment error page, see Adjustment errors or the online help.
2. Select an adjustment code from the list and view its details. If no code is available, or if a new code and error message is to be added, do the following steps.
  1. Click the Add Adjustment Error link.
  2. Select the adjustment code to be added from the Adjustment Code list.
  3. Indicate whether this code is part of a group that uses the Group Adjustment field.
  4. To finish adding the adjustment error, continue with step 7.c. The page is already in edit mode.
3. Edit the adjustment error. If needed, update the Use Error Description field and enter error messages in one or more of the fields.
  Note: If the Use Error Description field is set to Yes, the default error text is always used. If it is set to No, the default error text is used only if errors are not found in the database for the rejected segment or transaction.
Define the general system properties. For AutoAdjust, configure the following properties:

User Exit Classname

Package and class name of the AutoAdjust user exit.

Balancing Rule

Defines when to set the balance state on a batch or ICL.

Enable Business Rules

Indicates whether to call Business Rules for validation.
1. Go to the general properties page. For more information about using the general properties page, see General properties or the online help.
2. Use the edit icon to edit the general properties.
Configure the events needed to send messages to AutoAdjust.
The events that send messages to AutoAdjust as batches (ICLs) are loaded must be added to the Scheduler.xml file in Transaction Server. For more information about events, see Communicating with the Transaction Server.
Configure a listener in the Transaction Server listener profile to receive messages from AutoAdjust.
The Transaction Server has a listener profile, which defines the queues it monitors for messages from other applications. A new listener must be configured for AutoAdjust. For more information, see Transaction Server listener XML configuration.