Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
ashokpattnaik1
Explorer
0 Kudos

This document describes development steps for SEPA mandate form output. In this approach, no need to do tedious translation of smartfom (in SE63) to trigger output in multiple languages.

Standard Smartform: SEPA_MANDATE is copied to customized Smartform : ZSEPA_MANDATE. The new form name needs to be assigned in SEPA customization (transaction FI_APAR_SEPA_CUST).

Copy the smart style SEPA_MANDATE_STIL to ZSEPA_MANDATE_STIL and assign it to new smartform ZSEPA_MANDATE (in form attributes).

Upload the logo in SE78 transaction and replace it in LOGO window.

Replace the texts with SO10 text or Text module. Keep the ‘Language’ field blank. The standard text will be called dynamically based on the language passed from application. Maintain the standard texts in intended language in SO10 transaction.

As per standard SEPA functionality, the mandate is triggered in payer’s language (Language field in ‘sender’ tab of mandate master data).

2 Comments