Hey All,
I was wondering if anyone has downloaded the help file with the 2005 DTW? I downloaded it this morning and it does not have the same appendix info that the 2004 file has. That file contained descriptions of all the templates in great detail, including table names, field desc etc..
Anyone know if there is similiar info available for 2005?
Hi Lara
totaly agree with you, they have changed the SBO 2005 data transfer workbench totaly but they haven't given us a help file. The file for the DTW 2005 is useless.
I'd also like to see a answer from SAP regarding this.
Laura,
As you have noticed the DTW 2005 help file is much different from the 2004 DTW Help file. The net-net is that the 2005 DTW closely follows the conventions of the SAP Business One objects as outlined in the DI API Help file as far as what you can and can not do, properties, constraints, etc. Because of this, the documentation other than the functions of the DTW are not listed in the DTW Help file like they used to be and have to be looked up in the DI API Help or the Schema documentation that is also part of the 2005 SDK Help file. The issue with the 2004 documentation for the DTW was that we were duplicating information that was already stated in other areas. What we tried to do here is use one common set of documentation since the DTW needs and therefore uses the DI API for importing data. The though was for the detailed information about objects and properties, to use the existing DI API help. There is no other document beyond what comes with the DTW 2005 and the SDK Help.
Hope that helps,
Eddy
Hi Edward Neveux
We appreciate your answer and your reasoning. The only problem is if you look at the current DI API document it is focused more at programming and how to use it. Many consultants are not qualified in sdk and do not have a clear understanding on programming.
The help that came from 2004 dtw was a lot more helpfull from a consultant view. Now it's basicaly helpful for implementation consultants that have done programming which is very few here. Has that DI API file been made a lot more descriptive to take this into count?
How are we meant to cope with this short coming?
Add a comment