Create an inbound interface framework: Guidelines needed

[Former Member]

Hi ,

I need to create an bespoke interface framework monitor (and data processing logic) using file transfers (Not using XI ).

Plan is to make the legacy system dump data files on some SAP server(I guess AL11 can show me the files). Then I need to pick the file and process the data and produce an error log. All the incoming, processed or errorred file details need to be displayed on some bespoke interface monitor

What I am looking for is some guidance and helpful tips which could guide me about how to create a bespoke interface monitor.

I would really appreciate if you have any documentation with table structure details, functon modules etc details or just some plan advise on how to start the design of this interface monitor.

Thanks

Shirin

[Former Member]

I had to use one like that once. Had no access to codes though, but I can remember more or less how it works.

I remember there were four Z tables. One was the master, where every interface (inbound or outbound) should be registered before being able to be executed (this check were done under the incapsulated code of the functions). Second was responsible for registering processing data (each time an inferface was processed), like how many records were processed, valid processed transactions, etc. Third was to record history data, which user executed the interface, etc.

The last one were used to record restart data, in case some problem happened when processing interfaces.

Interface processings where identified by timestamp. So the generated files where named like INTNAME.<timestamp>, so that the file names not be too confused, or could not be overwritten.

There were function modules resposible for the actions: Init interface, Load Datafiles, Insert BDCData, Call Bapi, Move Datafiles, Done Inteface.

Also there were an include you could use in some programs, containing some macros that would help on log creation / messaging.

This was some of the framework's architecture.