SwiftNet Interface without BCM- SOAP to SFTP Scenario through SIPS Package in SAP PO 7.5

[vskvelu]

We have been working on SAP PO 7.5- Banking Integration- SwiftNet Outgoing Payments Interface from S4/HANA to third party system. We have done the POC with SIPS (SAP Integration package for SWIFT) through File to File transfer and it is able to split both Payload and PAR file in SIPS mapping (Getting the source file name and poplated the same in target Payload and PAR file with .PAR extension). It is working as expected. Now, We have switched the scenario to use Webservice(SOAP) to SFTP due to some reason. We have used the Standard Swift Interface name to trigger Webservice from S4/HANA to third party SFTP Server. From S4/HANA- Receiving the actual file as Attachment and in PO 7.5 System using PayloadSWAP bean to use the attachment file as Main payload and replacing the main document (It is used in the first module in the SOAP Channel). In this case, We are able to trigger the message from S4/HANA and split both Payload and PAR file accordingly through SIPS mapping. But couldn't get the actual source file name while uploading both Payload and PAR file in the target system. Hence encountering an issue "Null pointer exception while loading from the local variable Filename" . We have also found that there is a SAP note 1919169 for Enhancement of compatibility with other adapters. As suggested in the note, We have declared FilenamePropNamespace = http://sap.com/xi/XI/System/SOAP FilenamePropName = (Not sure what needs to be passed here) in the associated channel. We are stuck at this point since how to retrieve actual source filename using sender SOAP adapter. Since it is a SAP Standard interface, No mapping and customization is possible. Could anyone check and help on this request. Your help is much appreciated.

[MichalKrawczyk · Accepted solution]

hi,

>>>Since it is a SAP Standard interface, No mapping and customization is possible.

Why not ? It's PI you can change anything as long as you know what you're doing...

add a java mapping which will only set the Filename (to anything for a start) and check,

Best Regards,

Michal Krawczyk

[vskvelu]

Thank you very much Michal for the quick response. This issue has been resolved now. Earlier, The customized scenario doesn't work with Proxy communication from S4/HANA System due to missing SAP Standard namespace message type error message. After your answer, We have used Web service method and it worked well. then I was using Java mapping to get the filename dynamically and able to populate the same in target system through File channel ASMA option.