As explained in my last post, many standalone check print solutions integrated with Oracle E-business suite require only a fixed position text file of check data.
The third party software takes care of the layout and presentation of the document.
In order to fulfil this requirement, we have to:
1)- Define the structure of the fixed position Check file required by the third party software.
2)- Understand the XML file created for Payment Disbursements.
This article describes the steps to launch an html page from an Apps form, using Forms Personalizations. In this example, the html is an Apex (Application Express) page.The first step is to navigate into the form from which you want to launch an html page. Then you navigate further via the menu ::Help::Diagnostics::Custom::Forms Personalizations.Create an additional menu entry, as shown:and
There has been a few questions on the BI Publisher OTN forums recently around creating cheque (check) print files in ASCII format:
This is because many 3rd party cheque printing solutions (e.g. Bottomline / Paybase) only require an ASCII file of cheque data. The 3rd party software then takes care of the layout of the cheque, signatures and security markings etc.
Yesterday, a new Whitepaper called Best Practices for Adopting E-Business Suite Release 12 appeared on Metalink. This document, written by Anne Carlson "offers practical advice from professionals
in Oracle’s Support, Consulting, IT, and Development organizations on how to do a Release 12 implementation or upgrade".