Ansicht
Dokumentation
12735 - Sending an IDOC from SAP to a bank via ftp
ABAP Short Reference General Data in Customer MasterThis documentation is copyright by SAP AG.
Sending an IDOC from SAP to a bank via ftp
Hi Steven.Not sure whether this would work for you, but I have done it on our
system a few times.
Create a PF with a record length being the maximum length of a line
in the IDOC in the IFS. Then FTP the IDOC from the IFS to the PF (on
the same system), i.e. FTP LOOPBACK...
Then check the data in the PF and confirm whether it looks as it
should. If the record length is still a problem, then try and let
the FTP from the IFS document CREATE the PF when doing the PUT. I
found that creating the PF first with a fixed record length was a
better option (personally).
Hope it helps!
Regards,
Des.
--- In DoNotReply@consolut.eu, "Steven Glennie"
<eiglenniZn...> wrote:
> Thanks for the info Volker, but unfortunatley we have already been
> down that route and although it produces the spaces it also puts
in
> an end of record / line character when the file is sent by ftp.
Only
> the *fixed produced multiple lines, the others like *CRLF just
> produced the one line in the physical file.
>
> When we send the file by ftp direct from the IFS it works
perfectly,
> but this is unencrypteed and the encryption sofware only works
with
> physical files.
>
> Jim's method was new to me but made each line of file populated
with
> spaces up to the record length. The problem we have is that it is
> varaible length records.
>
> Does anyone know if it is possible to send idocs to a library
> instead of the IFS.
>
> With regards
>
> Steven
>
> > this problem is well-known. It is just the point, that blanks at
> the
> > end are skipped what is nórmally no issue. You could add the CR
> > and/or LF in the library table already.
> > ... at least with this trick I solved it the last time.
> >
> > Regards
> >
> > Volker
> > --- In DoNotReply@consolut.eu, "Steven Glennie"
> <eiglenniZn...>
> > wrote:
> > > Hello All,
> > >
> > > We have an R/3 4.6C system which is on a 740-12 way EBCDIC
> system
> > > and we are having issues with IDOCS and encryption software
> called
> > > COMPRESS.
> > >
> > > The IDOC is sent from SAP to the IFS directory on an AS/400,
but
> > > COMPRESS will only accept files from a library. To overcome
this
> we
> > > have been using the CPYFRMSTMF command. After the COMPRESS
> utility
> > > has encrypted the file it is then sent by ftp to Citibank.
> > >
> > > The problem is that the file does not retain spaces in fields
> that
> > > have a record with no entries in the last field. We tried
using
> the
> > > parameter ENDLINFMT (*CRLF) on the CPYFRMSTMF command which
did
> > keep
> > > the spaces intact it then put the whole record onto one single
> > line.
> > > This single line only contained the first 5000 characters as
> this
> > is
> > > what was specified as the record length when we created the
> > physical
> > > file. We then tried the ENDLINFMT (*FIXED) which seemed to
work
> > > better as it retained the spaces and when viewed with DSPPFM
> looked
> > > much better as it contained all the IDOC entries, but alas
> CITIBANK
> > > said that the file was fine for the first 5000 charaters and
> then
> > > the file had an error "IDOC file format invalid - Failed to
> process
> > > due to incorrect syntax after Segment <E2IDKU4>.
> > >
> > > The problem may be down to the fact that we have an ebcdic
> system.
> > I
> > > even tried ftping to '127.0.0.1' and using the put command to
> move
> > > the file from the IFS to the library but it did not retain the
> > > spaces.
> > >
> > > We would appreciate any help you can give me on this, even
> > > alternative solutions. I had thought about trying to send the
> IDOC
> > > directly to library on the AS/400 but I don't know if this is
> > > possible.
> > >
> > > Best regards,
> > >
> > > Steven Glennie
> > > NACCO
Durban Tours - Südafrika Safari
CL_GUI_FRONTEND_SERVICES - Frontend Services TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5333 Date: 20240420 Time: 075230 sap01-206 ( 3 ms )
