Hypertext: Object Class - Class to which a document belongs.
Document Name
EPIC_C_BCSV
Use
The technical settings of your bank may require that a bank communication comprises more than one step, that is, more than one pair of request and response messages. An example of such a multistep bank communication could involve a signature server: You first send an XML request message to the bank's signature server. The bank returns a digitally signed response message. In the second step of the communication, you send the digitally signed data to a different server. That server then sends a response message.
If you have bank communication types that have more than one step, enter the steps for each of these bank communication types in this Customizing activity. Your SAP ERP system then knows that it has to send several requests to the bank for each communication. Also enter the respective RFC destination, logon user, and character encoding set for each step.
Requirements
You have not entered an RFC destination, logon user or character encoding set for these bank communication types with multiple steps in the Define Bank Communication Details Customizing activity. If you entered values for these fields in the Define Bank Communication Details Customizing activity, the system will use the settings from this Customizing activity instead.
Hierarchy 
SAP_FIN (Software Component) SAP_FIN
FI-LOC (Application Component) Localization
ID-FI-EPIC-BACOM-BL (Package) Globalization: E-Payment Int. Bank Comm. Business Logic
IMG Activity 
Document 
History 
