Customer Statement Report converted from PLD to CR - extra datasource issue

Question

Hi All,
We've come across an issue where we have used the Crystal Converter to convert a PLD layout of the Customer Statement (Collection) Report to a CR layout (done via CR 2008 using the 8.8 standard integration).
The layout converted fine and we've got most standard fields working and showing the correct values etc. However we had a requirement to also bring in the Original Document Amount into the layout (which is not a standard PLD field unfortunately!) and we had to do it via an extra datasource based on a pretty straightforward view we created in that company database - which contained columns CardCode, DocName (which was the transaction type + number e.g. IN 12345) and of course, DocTotal.
We then added the datasource (via ADO connection) and linked the DocName to the Reference field that is already present in the standard layout and contains the same data as our cutom DocTotal - and remarkably, this actually produced the correct results - i.e. we managed to get the Original Document Amount to appear in the lines of the statement together with the open invoice balance, reference, posting date, due date etc - however this seems to affect the other areas of the layout - and we lose the header and footer information completely; whilst retaining only the lines level information.
We've tried a few things such as linking the CardCode to a header field as well but it doesn't seem to bring the rest of the layout back. So in a nutshell, as soon as we bring that extra field in from the added datasource, we get the correct original document amount appearing in the lines but that's all we see in a print preview - the line level data of the statement. The header and footer information disappears.
And here is the big question - any thoughts on this and has anybody experienced a similar problem in an integrated CR? We think it may possibly be due to the extra datasource - perhaps the 8.8 - CR integration doesn't know how to handle the additional datasource AND it's own standard datasource (which is referencing the PLD fields) properly yet?
Thoughts please because I'm sure this will turn into a common issue sometime soon.
Edited by: Mohsen Qureshi on Jul 2, 2010 11:04 AM

Answer 1

Hi Mohsen,
Perhaps you are able to help me.
I have successfully converted the SAP system 'Customer Collection Report (One Page per Customer)' PLD into Crystal using the Crystal converter. I now run my customer ageing report in SAP, however, when i print preview the Crystal layout, the "detail" section of the report repeatedly displays the "text" label of each field. I'm assuming this is because the system PLD for the collection report, does not use database fields for the detail/repetetive area - instead it uses text fields to pull through fields such as document no etc etc.
I would have throught that a crystal conversion from an untouched system layout would have worked, but it hasn't.
My question - Did you have to perform any additional work to the crystal report after the conversion?
Any suggestions or tips on how to get the system  would be greatly appreciated.
Thanks in advance,
George Kantzavelos