[4358] in sapr3-soft
FI: e-Banking Inbound and Outbound Interface
daemon@ATHENA.MIT.EDU (Kenneth @ BTM Singapore)
Thu Nov 4 08:50:13 1999
To: sapr3-soft@MIT.EDU
Date: 4 Nov 1999 07:48:05 -0600
From: "Kenneth @ BTM Singapore" <kensoh@pacific.net.sg>(by way of SAP Moderator <sap-request@realtimeusa.com>)
Message-Id: <7vs2ql$p3h@nexus.netconcepts.com>
Hi all,
I am in electronic banking app development and I would
appreciate it if someone could advise me on the following:
We intend to develop an interface between our e-banking
front-end and R3. By visiting the SAP site I realized the
following:
1. Inbound statements can be achieved via:
(a) Multicash - but no certification is available.
(b) MT940
(c) IDoc
2. Outbound payment can be achieved via IDoc only.
My questions are:
1. Is there a support for outbound payment in MT100 ?
2. When it is mentioned that "MT" format is supported,
does it mean file import and export of "tagged" file
and not the CSV or delimited file ?
e.g. MT tagged file:
:20:Field-1 Content
:25:Fled-2 Content
:32:Field-3 Content
e.g. CSV file:
Field1,Field-2,Field3
By and large, import/export in PC are usually CSV-based.
I am just curious if I am on the right track to implement our
e-banking application to import and export tagged files.
i.e. if tagged file approach is used, for inbound interface,
my application will export the tagged file in MT940 and expect
R3 to accept. For outbound interface, my application would
expect the MT100 tagged file from R3.
CSV is common in PC file import/export but I am not too
sure if it is correct to implement tagged file import/export as
it is a less efficient and cumbersome method ?
Please help and cc: kensoh@pacific.net.sg
Thanks and regards,
Kenneth
