on 11-22-2013 5:42 PM
Hi Guys,
I have a scenario to receive a file from a FILE system and integrate it with SAP ECC system (for which I am using proxy communication).
I did create a sender communication channel with file content conversion. (Shown settings I made)
Qn 1. Can anybody do help me with the to set up the Parameters for Recordset ("DisbMessage").
Qn 2. Other question how will my settings work for those lines which are highlighted in bold and italics?
File format looks like below.
{1:XXXXXXXXXXXX}{2:XXXXXXXXXXXXXXX}{3:{XXXXXXXXXXXXXXX}}{4:
:20:12333333
:21R:ABC123123
:28D:5/6
:50H:/1111111
ENTITY NAME
ENTITY STREET
ENTITY CITY
ENTITY COUNTRY
:52A:SAMPLE111
:30:SAMPLE222
:21:SAMPLE333
:32B:USD111,11
:57A:SAMPLE555
:59:/66666
BENEFICIARY NAME
BENEF STREET
BENEF CITY
BENEF COUNTRY
:70:SAMPLE6666
:71A:TEST
-}
I already did the set the parameters like below:-
DisbMessage.fieldSeparator ':'
DisbMessage.beginSeparator ':'
DisbMessage.fieldNames Number, Name
DisbMessage.endSeparator 'nl'
Hope my question is clear. If not, please let me know. I can make it more detail. Expecting an prompt response.
Hi Krishna,
MT101 is a Swift format message, this cannot be parsed through standard File adapter.
Check if B2B add on is supporting MT101 format.
Refer these threads:
http://scn.sap.com/thread/3426790
http://scn.sap.com/thread/3200555
This link http://scn.sap.com/thread/1804480 tells to use a ABAP code to achieve the requirement.
Regards,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Pranav.
I know that there are B2B adapters which can accept 101 message format.
The situation here is I don't have that adapters in my client space. Available adapter is provided by only third parties, I believe. And moreover we are having here SAP PI 7.1 version.
Additionally, even though I am getting this file in 101 format, it is not mandatory to have it accepted as it is. This file format is using by Sender which we need to map with Custom tables/applications not with any SAP Standard.
Now coming back to current context, Is there any way to read it with available options of file adapter.
Please correct me if I went wrong anywhere and convey your opinion on my thoughts.
Hi Krishna,
We had a similar situation in our project. After trying different methods, we asked Source bank to send files in pain format than MT101.
Pain is almost an xml format, we mapped using the pain xsd to trigger CPON proxy, It will be a normal scenario with pain xsd.
But it all depends on the source system acceptance. Good luck.
Regards,
Pranav
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.