Hi Nitin,
Yes, I am using detach parameters in the sender channel and it is split into two files, but as some kind of algorithm or signature. However, the two files are exactly same. My input file is as above as per my message yesterday.
It is converted by the module to: (from rwb)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:SWIFT_payload_parFile xmlns:ns0="http://sap.com/xi/SWIFT">
<payload>PD94bWwgdmV................................................
..............................................................dW1lbnQ+</payload>
<parFile>PD94bWwgdmV................................................
...............................................................dW1lbnQ+</parFile>
</ns0:SWIFT_payload_parFile>
It is then split into two messages in the mapping as:
<?xml version="1.0" encoding="UTF-8"?>
<ns1:SWIFT_payload xmlns:ns1="http://sap.com/xi/SWIFT">
<payload>PD94bWwgdmV8....................WduYXR1cmU+PC9CQUNTRG9jdW1lbnQ+</payload>
</ns1:SWIFT_payload>
and
<?xml version="1.0" encoding="UTF-8"?>
<ns1:SWIFT_parFile xmlns:ns1="http://sap.com/xi/SWIFT">
<parFile>PD94bWwgdmV......................WduYXR1cmU+PC9CQUNTRG9jdW1lbnQ+</parFile>
</ns1:SWIFT_parFile>
However, when the files are written by the two receiver channels, Payload file is same as the input file i.e.,
<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!--Generated by Oracle Repots version 10.1.2.3.0 -->
<AddresseeInformationname="xxxxx" />
<ServiceLicenseInformationuserName="xxxxx" userNumber="xxxxxx" /></ReturnedCreditItem>
-<ReturnedCreditItem ref="xxxxx" uacName="xxxx" transCode="RA"returnCode="5" returnDescription="No account" valueOf="xxxx.xx"currency="GBP">
</ReturnedCreditItem>
-<ReturnedCreditItem ref="xxxxxx" uacName="x" transCode="RA"returnCode="0" returnDescriptionxxxx="Invalid details"valueOf="xxx.00" currency="GBP">
</ReturnedCreditItem>
</OriginatingAccountRecord>
</OriginatingAccountRecords>
</Advice>
</ARUCS>
</Data>
<SignatureMethod>Vanilla</SignatureMethod>
<Signature>MIILOgYJKoZIhvcNAQcCoIIL.............................................................................................................................................................................................................................................AeJFj00rBp5io5dWa0fX4YAcSWYxinQ2ufLVgA==</Signature>
</BACSDocument>