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?
Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial DirectorFor 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?
This was first published in May 2010
Join the conversationComment
Share
Comments
Results
Contribute to the conversation