Swift Integration Package for PI

[Former Member]

Hi

I'm trying to configure the PI File Adapter to process the attached example inbound FIN files.

I know very little about Swift messages, but I have tried both adapter modules localejbs/swift/FINConversionToSWIFTModule and  localejbs/swift/FINConversionFromSWIFTModule with a standard PI File Adapter, with no joy.

With  localejbs/swift/FINConversionToSWIFTModule, I get error     'com.sap.xi.swift.ParserException: Parameter sender reference is missing'

With  localejbs/swift/FINConversionFromSWIFTModule, I get error 'com.sap.xi.swift.ParserException: Message does not start with character '0x1f'

Can anyone please make a suggestion on how I can process these files through PI and into ECC6 system?

Thanks in advance.

Example1.fin.zip

Example2.fin.zip

[Former Member · Accepted solution]

Hi Andy,

These files are already in text format. If you need to process these into ECC then you just create another scenario (File to Proxy) to process these files. If these are acknowledgement files, you can use the ECC service CollectivePaymentOrderNotification_In to process them into the bank monitor report.

The adapter modules delivered in the SWIFT Integration Package do the following:

localejbs/swift/FINConversionToSWIFTModule - FIN MT Messages (txt) to SWIFT XMLv2 files

localejbs/swift/FINConversionFromSWIFTModule - SWIFT XMLv2 files to FIN MT Messages (txt)

Hope that helps.

[Former Member · Accepted solution]

Thanks Erwin.

So is there no requirement to convert these files into XML in PI, and they can be processed in their current format by  ECC service CollectivePaymentOrderNotification_In.

Is that correct?

[Former Member · Accepted solution]

Well, as I mentioned previously, you will need a separate custom scenario to process these files ( file to proxy ). I assume that these are bank acknowledgments,  and based on my experience, they are specific to each bank. You have to roll your own scenario in order to use the CPON service. That entails building your bank specific structures and mapping this to the CPON service.

The SWIFT Integration Package is only provided to help in converting the Swift Alliance Access XMLv2 files to the corresponding SWIFT MX or MT files and vice-versa.

[Former Member · Accepted solution]

ok, so I need to develop something bespoke in PI  to convert these ack files to XML, in order to then call a server proxy in ECC6.  Correct?

[Former Member · Accepted solution]

Yes, that would be correct.

[Former Member · Accepted solution]

Thanks Erwin.  I'm still unsure how this works though. 

Normally (for server proxies), I would define an Inbound Interface in PI, and then run SPROXY to generate the ABAP objects in ECC.  Then we add code within the generated ABAP class to process the data.
 
But how does this work with Enterprise Services?  Do we still need to manually define the interface in PI and then generate the Proxy as before? 

[Former Member · Accepted solution]

You can refer to my answer in the similar question below http://scn.sap.com/message/13357371.

You can refer to the step by step wiki here. The XI content that you'll be looking for in SWDC is for XI CONTENT SAP_APPL <version>.

Depending on your ECC version, the inbound enterprise service should be already in your system. Look for the server proxy with name 'CollectivePaymentOrderNotification_In'. So you just need to import the SAP provided XI content then you can start developing your own scenario using the CPON service.

[Former Member · Accepted solution]

That's great, thank you!

One more question please:

"Look for the server proxy with name 'CollectivePaymentOrderNotification_In"

Im not sure where I need to look for this. Is there a transaction code to use?

Thanks again for your help.

[Former Member · Accepted solution]

Yeah, use SE80 for Enterprise Objects or if you have already imported the XI content for SAP_APPL in your PI ESR then you should be able to see it in SPROXY as well under SAP APPL and namespace http://sap.com/xi/APPL/Global2 .

[Former Member · Accepted solution]

ok, but isn't this just a view over the ESR in PI? 
So obviously I can generate a server proxy from any inbound interface definition that exists in the ESR, and the result will be some ABAP objects/ structures generated in ECC6.
 
But I'm still missing something.... do we then need to do some ABAP coding inside the proxy-generated ABAP classes, in order to execute the Enterprise Service that I want to call?

[aashish_sinha · Accepted solution]

HI,

Have a look into blow threads for my answers. you will come to know about a solution related to E-Banking.

http://scn.sap.com/message/13357238#13357238

Regards

Aashish Sinha

[Former Member · Accepted solution]

Ah  .... by switching to 'Local View' in SE80 E.S. Browser, I can see CollectivePaymentOrderNotification_In is there, and a proxy exists.

Maybe I just need to install the XI content and then use the inbound interface...... 

[Former Member · Accepted solution]

Hi Erwin,

I have requirement to convert mt101(txt) to swift xmlv2 file in PI7.31

Can i use the localejbs/swift/FINConversionToSWIFTModule for this requirement ?

I am not find the document for the use of above adapter module and it's use.

Regards

Upendra

[former_member51178]

Hi Andy,

did you solve a problem with com.sap.xi.swift.ParserException: Parameter sender reference is missing?

I've got the same one, appreciate your help

[baskar_gopalakrishnan2]

You might want to check OSS note 1064419 for configuration details.

[Former Member]

Hi.  I has already checked note 1064419.

In section '3.3 Receiving Status Messages using FIN', it suggests that no Adapter Modules other than callSapAdapter are used.

I don't understand this, because the files are not XML format.