Generic Deenvelope service MX example, expected results

Expect the following results from the Generic Deenvelope service MX example:

• The translation map generates three customer credit transfer transactions.
• The result of the translation map is the same format as the cstmr_cdttrf_flat.dat input file used for the sample WebSphere Transformation Extender map for the Sterling B2B Integrator Generic Envelope service for MX.
• Compliance check performed against the MX document prior to execution of the translation map indicates two valid and one invalid (first of the three transactions), within the SWIFT MX message.
• The failure is due to an invalid currency code on element IntrBkSttlmAmt currency attribute.
• The entry for transaction instruction identification, instrID, exists in both the ProcessData and Correlation tables.