Manual Confirmation Message Generation Processing
After successful validation and authorization of the Manual Confirmation input by user, the confirmation message generation is done.
A gpi Confirmation message gets generated if the 'gpi Agent' flag is 'Yes'. Otherwise, a Universal confirmation message gets generated.
In case of gpi Confirmation message, the Field 111 in Block 3 is populated with a value of '001' [Value is taken from SWIFT gpi Static preference maintenance (PXDGPIST) ]. The value population for other fields is same as done for Universal confirmation message generation.
Once a gpi/Universal confirmation message is generated successfully, the 'Confirmation Status' value is updated as 'Generated' if the previous status is 'Ungenerated' or blank and 'Confirmation Type' is marked as 'Interim' or 'Reject' or 'Credit' depending on the confirmation message generated.
In the gpi Confirmations sub screen, the field 'Generation Type ''Generation Mode' is marked as 'Manual'.
| Status Code | Status / Reject Reason | Inbound Cross Border | Inbound Fedwire | Pass-through Fedwire |
|---|---|---|---|---|
| ACCC | NA | Applicable | Applicable | Not Applicable |
| RJCT | Any Reject Reason code | Applicable | Applicable | Applicable |
| ACSP | G000 | Not Applicable | Not Applicable | Not Applicable |
| ACSP | G001 | Not Applicable | Not Applicable | Applicable |
| ACSP | G002 | Applicable | Applicable | Applicable |
| ACSP | G003 | Applicable | Applicable | Applicable |
| ACSP | G004 | Applicable | Applicable | Applicable |
Note:
The manual gpi/Universal confirmation message can be generated even if the gpi/Universal confirmation message generation preference is 'Automatic' in SWIFT gpi Host preferences maintenance (PXDGPIPF) based on the transaction status. E.g. An interim confirmation can be generated before OBPM generates the same during EOD.Parent topic: gCCT Confirmations - MT 199