Ansicht
Dokumentation

EPIC_RELATED - Prerequisites for the Customizing for Electronic Payment Integration

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Before you make the settings in the Customizing activities specific to Electronic Payment Integration, make the necessary settings in the Customizing activities listed below and create the necessary ABAP repository objects for your bank-specific communication types.

Payment Release List

The Electronic Payment Integration solution for processing items to be paid uses back-end functions and tables from the Payment Release List (PRL). This means you must make settings in the Customizing for the PRL:

1. Define an Electronic Payment Integration application for the PRL in the Define Applications Customizing activity.
2. Activate the Payment Release List (PRL) in the Activate Payment Release List Customizing activity.
3. Activate the EPIC application for the PRL in the Activate Application Customizing activity. Once you have activated the EPIC application, you cannot use the Payment Release List screens to process items. This prevents inconsistencies in the database.

You can also define approval levels and disable standard clearing, reversing, and editing functions for open items that are being processed in the Electronic Payment Integration application. To do that, make settings as follows:

1. Define the approval levels for payment item statuses in the Define Approval Levels Customizing activity. For example:

Approval level	Status
0	“In Preparation” or “Approval Pending”
1	“Approval Pending”
2	“Released for Payment”

1. Disable clearing and reversal functions for the required approval levels in the Disable Clearing and Reversal for Approval Levels Customizing activity.
2. Disable editing open items for the required approval levels in the Disable Document Changes for Approval Levels Customizing activity.

Payment Program

1. Create the DMEE format trees needed to send files to your house banks. These formats must be of the PAYM type. To do this, you use the DMEEtransaction.
2. Make the necessary settings for payment medium formats from the Payment Medium Workbench (PMW). To do so, you make the settings in the following Customizing activities in the Customizing for Financial Accounting under Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Make Settings for Payment Medium Formats from Payment Medium Workbench:
1. Create Payment Medium Formats. Ensure that in the Program control group box, the Mapping using DME engine field is selected.
2. Adjust Note to Payee
3. Assign Payment Medium Format and Note to Payee to Payment Method. Ensure that in the Payment medium group box the Use payment medium workbench radio button is selected. Enter the name of your PMW format in the Format field.
4. Create/Assign Selection Variants

For the following steps, you make settings in the relevant Customizing activities for Financial Accounting under Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments. Alternatively, you can use the FBZP transaction.

1. Set Up All Company Codes for Payment Transactions
2. Set Up Paying Company Codes for Payment Transactions
3. Set Up Payment Methods for Each Country/Region for Payment Transactions
   
   
4. Set Up Payment Methods per Company Code for Payment Transactions
5. Set up your house banks for payment transactions (Customizing activity: Define House Banks/Bank Account).
6. Set up bank determination for payment transactions (Customizing activity: Set Up Bank Determination for Payment Transactions).

For more information, see https://help.sap.com -> SAP ERP Central Component -> SAP ERP Central Component -> Financials -> Financial Accounting (FI) -> Accounts Payable -> FI Accounts Receivable and Accounts Payable -> Payments -> Executing the Payment Program -> Payment Medium Workbench (-> Data Medium Exchange Engine).

Bank Communication

For each type of bank communication, for example, sending a payment file or a query about an account balance, for each of your house banks, implement the following objects in your own namespace using the respective functions of the SE80 transaction:

• An implementing class that has the IF_EPIC_BANK_COMM_IMPL interface delivered in the ID-FI-EPIC-BACOM-BL package with this solution. This interface has the following methods:

• CREATE_REQUEST

• PROCESS_RESPONSE

• ADJUST_HTTP_REQUEST (for example, for adding HTTP header fields to the message)

• ACCESS_HTTP_RESPONSE (for example, for reading additional HTTP header fields)

You must implement all of these methods. Note that, if you only want to implement coding for the CREATE_REQUEST and PROCESS_RESPONSE methods, you still must implement the other two methods empty, that is, without coding.

• The following structures, as needed, for each implementing class:

• Structure with Dialog Parameters for Bank Communication

• Output Table Structure for Bank Communication

• Structure with (Other) Parameters for Bank Communication

• Structure with (Other) Results for Bank Communication

• Mapping for creating and processing the necessary bank-specific messages. You can do this mapping using, for example, XSLT transformations or the Data Medium Exchange Engine (DMEE) format trees.

• Any additional data elements needed for dialog or result parameters that are to be displayed on the Electronic Payment Integration (China) screen.

If you need additional messages for your implementations, create them using the SE91 transaction.

To enable a connection to each of your house bank's communication clients, set up the respective Remote Function Call (RFC) destinations using the SM59 transaction.

2

2

2

2

RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 9068 Date: 20240523 Time: 184356     sap01-206 ( 110 ms )