Skip to Content

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).

sepa_cust.JPG

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.sepa_form1.JPG

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.

sepa_form2.JPG

sepa_form3.JPG

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

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

    1. Ashok Pattnaik Post author

      Hi,

      you need to maintain the texts in SO10, alternatively you can maintain in text modules(transaction: SMARTFORMS) and assign the the SO10 text / text module to smartform. The standard structure SEPA_MANDATE is filled in runtime which can be referred directly in SO10 text as well.

      (0) 

Leave a Reply