2007 Oct 18 9:10 AM
Hi,
What tools/techniques would you suggest for moving Campus Management historical data (student master data, modules, events, bookings, grades)? I found batch input recording as the only feasible option so far (in LSMW) as there are no standard interfaces (BAPIs, IDOCs) for Campus Management there. Alas, recording works only for some areas. For instance, it's not possible to create a recording to fill academic calendar periods. The only alternative, as I understand, would be to write an ABAP conversion program. Any good tutorials on that?
Also, where can I find documentation, which tables/objects correspond to the actual end-user functionality? For example, I'm curious where the bookings are stored on the physical table level.
Thanks
Janek
2007 Oct 18 9:56 AM
Hi Janek,
There are delivered interfaces which we recommend... batch input is usually not recommended. I suggest that you start with the Data Transfer Guideline
http://service.sap.com/higher-ed
Services -> Background Material -> "CM 4.71 Data Transfer for Campus Management"
Best regards
Joachim
2007 Oct 18 9:56 AM
Hi Janek,
There are delivered interfaces which we recommend... batch input is usually not recommended. I suggest that you start with the Data Transfer Guideline
http://service.sap.com/higher-ed
Services -> Background Material -> "CM 4.71 Data Transfer for Campus Management"
Best regards
Joachim
2007 Oct 18 10:51 AM
Hi Joachim,
Thanks for the link. It's a good overview, which in general concludes that... there are no consistent tools for data transfer for Campus Management ) Or at least they are too risky to use. Warnings plastered everywhere about ensuring data consistency before using them. E.g. the document talks that it's not advisable to import objects that cannot be maintained through PP01. While event booking assignments indeed can't be edited through PP01.
Also, they talk that batch input is a feasible data transfer option especially when it certainly ensures data consistency, etc. So it somewhat contradicts with your point of batch input being "not recommended".
Useful lists of infotypes and tables, though.
Regarding ABAP functions mentioned in the document: I can access and run (test) them through SE37 but how should I use them for the actual data transfer? Should I write a standalone ABAP program that calls these functions and feeds data in a loop? They are not standalone tools/programs, as I understand.
Janek
2007 Oct 18 11:27 AM
Hi Janek,
Ok, maybe one should be more precise sometimes - batch input indeed is a viable option as it runs throught the standard checks. However in the most critical areas exactly those full business checks take a lot of time and thus the batch input isn't the best choice for a massive load of complex data. In addition for some processes the UI is optimized for the user and not for batch input and thus some controls have limitations with using batch input. If for your data transfer batch input works there is no reason not to use it.
The data transfer guideline has some generic recommendations as well gives advise for each particular data group. The generic recommendations may not fully apply for every data group, but should help to make decisions for those areas which you need to cover in addition. PP01 has not been enabled for those cases where there is a high risk of creating inconsitencies in maintaing data seperetaly from running it through a regular process.
Usually you would indeed write an ABAP report to import the data. This is also adviseable to have control on the comitt-process, roll-back etc..
Regards
Joachim