SAP ABAP IMG Activity EPIC_RELATED (Prerequisites for the Customizing for Electronic Payment Integration)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-LOC (Application Component) Localization
     ⤷ ID-FI-EPIC-GEN (Package) Globalization: E-Payment Integration Generic Topics
IMG Activity
ID EPIC_RELATED Prerequisites for the Customizing for Electronic Payment Integration  
Transaction Code S_EBS_44000366   (empty) 
Created on 20110124    
Customizing Attributes EPIC_RELATED   Prerequisites for the Customizing for Electronic Payment Integration 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EPIC_RELATED    

Use

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.

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 DMEE transaction.
  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.

  3. Set Up All Company Codes for Payment Transactions
  4. Set Up Paying Company Codes for Payment Transactions
  5. Set Up Payment Methods per Country for Payment Transactions
  6. Set Up Payment Methods per Company Code for Payment Transactions
  7. Set up your house banks for payment transactions (Customizing activity: Define House Banks/Bank Account).
  8. 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:
  • 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.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
EPIC_RELATED CN China
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG EPIC_RELATED 0 HLA0009204 Accounts Payable 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20111114 
SAP Release Created in 606