Decision Message Processing

The administrative returns node performs these tasks, in the order listed. It is assumed there is no change to the sample.
  1. Before the first table look up , the repairable and reviewable flags are checked. If either is set to true, the node exits.
  2. The return customers table is searched using the depositor ID. If it is not found, the node exits.
  3. The return reasons table is checked for any flag set to true. If none are found, the node exits.
    1. For the first true flag found, the return reason is set and the rest are ignored.
    2. The endpoint is cleared so a failed look up in the next table results in the ibmNprEndpoint field being returned to the client as an empty string.
  4. The return endpoints table is searched for the endpoint. If found, the return endpoint overwrites the ibmNprEndpoint field.
Note: If ibmNprReturnReason was set, it is returned to the client regardless of the results.
Figure 1 shows how a transaction is processed in the administrative returns node.
Figure 1. Administrative Returns Workflow
gpy_izwc_adminretworkflow.jpg