Ansicht
Dokumentation

/BSNAGT/V_STAPUS - Maintain Static EBICS Users

/BSNAGT/V_STAPUS - Maintain Static EBICS Users

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this activity, you define static EBICS users that can be used by SAP Multi-Bank Connectivity to send messages through EBICS.

In scenarios in which SAP Multi-Bank Connectivity connects to banks using EBICS, EBICS users are required for sending messages to the banks. Two EBICS users are usually required in such a scenario.

Static EBICS users are used in scenarios where there are no approval users, but where you must define EBICS users to be able to send messages via EBICS, for example, if the messages are created by the file pickup function.

The static EBIC users you define here are sent as values for the extended header parameters EBICS.USER_1 and EBICS.USER_2 in the MBC message.

When you define an entry for a static EBICS user, specify the following message header fields:

  • Sender ID
  • Receiver ID
  • Message type
  • Origin

For a simpler configuration, you can also leave one or more of these fields empty. In this case, an empty field is a wildcard.

For each static EBICS user entry, assign the extended header parameter EBICS.USER_1 or EBICS.USER_2 and the relevant EBICS user known to the bank






BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 1380 Date: 20240328 Time: 190317     sap01-206 ( 30 ms )