Difference between revisions of "Plugin: SEPA"
From iDempiere en
(Created page with "right * '''Creator:''' Patric Massing from Hans Auler GmbH, Germany. * '''Current Version:''' 2.1 * '''License:''' [http://www.gnu.org/licenses/gp...") |
CarlosRuiz (talk | contribs) (remove dead w4grb extension) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
* '''Source:''' [http://bitbucket.org/red1/de.aulersipel.sepapaymentexport PaymentExport] | * '''Source:''' [http://bitbucket.org/red1/de.aulersipel.sepapaymentexport PaymentExport] | ||
* '''Reviewed by: ''' [[User:Red1|Red1]] ([[User talk:Red1|talk]]) 23:52, 22 June 2015 (CEST) | * '''Reviewed by: ''' [[User:Red1|Red1]] ([[User talk:Red1|talk]]) 23:52, 22 June 2015 (CEST) | ||
| − | * '''DB Change:''' Payment | + | * '''DB Change:''' Payment Export Class defined in Bank/Cash>Account window to use: 'org.aulersipel.util.as1SEPAPaymentExport'. |
[[Image:BankAccountExportClass.png]] | [[Image:BankAccountExportClass.png]] | ||
__FORCETOC__ | __FORCETOC__ | ||
| Line 12: | Line 12: | ||
== Description == | == Description == | ||
*Banks today process big volume of transactions using a standard XML format to import the payments to be relayed to the recipient accounts. | *Banks today process big volume of transactions using a standard XML format to import the payments to be relayed to the recipient accounts. | ||
| − | *In Germany it is the SEPA format. | + | *In Germany it is the SEPA format, defined in a custom class, called by the PaymentExport process in *Piere ERP. |
*This fragment plugin works under the host plugin of org.idempiere.ui.zk | *This fragment plugin works under the host plugin of org.idempiere.ui.zk | ||
*Just install it in OSGI or via Felix Console to your idempiere-server and start it. | *Just install it in OSGI or via Felix Console to your idempiere-server and start it. | ||
| − | *Once it is active it will be seen as 'Fragment' and that means it will process | + | *Once it is active it will be seen as 'Fragment' and that means it will be used in the PaymentExport process. |
| + | *Tested in production use by the sponsor company group with partners in Germany and Luxemburg. | ||
| + | *As a fragment plugin, this custom export handling is easily decoupled or maintained with no impact to the core ERP. | ||
| − | = | + | =Template Fragment= |
| − | + | [[Image:FragmentPluginPaymentExport.png|550px|right]] | |
| − | + | *This fragment can be a good sample to reuse to make new fragments | |
| − | + | *Fragments are needed as extension to core plugins without modifying core. | |
| − | + | *This particular fragment fulfills classloader by core plugin by providing the class as its single payload. | |
| − | + | *In this example, the fragment merely loads the defined class in the window above during WPayPrint. | |
| + | *The fragment class as1SEPAPaymentExport implements PaymentExport interface which defines a single method exportToFile. | ||
If you want to provide additional comments, please use the [[Talk:Plugin:_SEPA|Discussion page]] or | If you want to provide additional comments, please use the [[Talk:Plugin:_SEPA|Discussion page]] or | ||
| Line 30: | Line 33: | ||
[[Category:Available_Plugins]] | [[Category:Available_Plugins]] | ||
| + | [[Category:User Manual ]] | ||
| + | [[Category:Financial accounting]] | ||
| + | [[Category:Bank Cashbook]] | ||
| + | [[Category:Accounting]] | ||
Latest revision as of 11:50, 23 April 2019
- Creator: Patric Massing from Hans Auler GmbH, Germany.
- Current Version: 2.1
- License: GPLv2 - Free as in Freedom not Free Lunch
- JIRA Ticket: IDEMPIERE-1546.
- Source: PaymentExport
- Reviewed by: Red1 (talk) 23:52, 22 June 2015 (CEST)
- DB Change: Payment Export Class defined in Bank/Cash>Account window to use: 'org.aulersipel.util.as1SEPAPaymentExport'.
Description
- Banks today process big volume of transactions using a standard XML format to import the payments to be relayed to the recipient accounts.
- In Germany it is the SEPA format, defined in a custom class, called by the PaymentExport process in *Piere ERP.
- This fragment plugin works under the host plugin of org.idempiere.ui.zk
- Just install it in OSGI or via Felix Console to your idempiere-server and start it.
- Once it is active it will be seen as 'Fragment' and that means it will be used in the PaymentExport process.
- Tested in production use by the sponsor company group with partners in Germany and Luxemburg.
- As a fragment plugin, this custom export handling is easily decoupled or maintained with no impact to the core ERP.
Template Fragment
- This fragment can be a good sample to reuse to make new fragments
- Fragments are needed as extension to core plugins without modifying core.
- This particular fragment fulfills classloader by core plugin by providing the class as its single payload.
- In this example, the fragment merely loads the defined class in the window above during WPayPrint.
- The fragment class as1SEPAPaymentExport implements PaymentExport interface which defines a single method exportToFile.
If you want to provide additional comments, please use the Discussion page or please also visit our contribution list at AulerSipel.
