However, migrating the SAPscript to Smart Form (I think we need to change the driver program by copying it to a custom driver program) will require more time when compared to developing the same in SAPscript.
How advantageous is developing this in Smart Forms when compared to SAPscripts? Is it possible that this development can be migrated to Smart Forms?
For instance, the SAPscript tool is relatively unforgiving (i.e., no 'undo' capability, awkward table handling, client-dependent, etc.) and ongoing maintenance is much tougher as a result. Thus, in my experience, even if the initial maintenance investment in a Smart Form is higher, it often will be cheaper in the long run. And sometimes you can leverage an existing Smart Forms template, which is not an exact fit, but gets you 20 to 30% of what you need. Depending on your precise form requirements, this sometimes can be easier than migrating an SAPscript form and dealing with all the associated clean-up.
In your case, I would probably "bite the bullet" and build the Smart Form. I would take a close look at print program RLB_INVOICE and the invoice Smart Form template, as well as print program RVADIL01 and SAPscript form SD_INVOICE_LIST, to see which is a better starting point in light of your requirements. Obviously, every situation is different, but when it comes down to it, wouldn't you rather build something that is easier to support?
Dig Deeper on SAP workflow development
Related Q&A from Mark Smithson
An SAP user is looking to fix an error with a packing slip print-out in an SAP Smart Form. Continue Reading
An SAP user is trying to align a barcode in the center of a defined window on an SAP Smart Form. Continue Reading
The SAP-provided Smart Form purchase order template is hard to locate and install, and may require the assistance of the Basis team, but it's worth ... Continue Reading