SAP ABAP IMG Activity EPIC_USB_VALIDATION (BAdI: Security Token Validation Control)
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_USB_VALIDATION BAdI: Security Token Validation Control  
Transaction Code S_EBJ_45000018   (empty) 
Created on 20130715    
Customizing Attributes EPIC_USB_VALIDATION   BAdI: Security Token Validation Control 
Customizing Activity EPIC_USB_VALIDATION   BAdI: Security Token Validation Control 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EPIC_USB_VALIDATION    

Use

This Business Add-In (BAdI) is used in the E-Payment Integration China (FI-LOC-EPI-CN) component.

You can use this BAdI to implement security check points during the processing of items to be paid using the Electronic Payment Integration for China (EPIC) application. The Electronic Payment Integration framework can check if a security token is in use and if the data on the security token (for example, a PIN) is accurate. The framework also can prompt the user to enter a PIN.

This BAdI can be called during two processes:

  • Bank communication when a user tries to send a payment file from the Process Items tab page or start a bank communication from the Query Bank tab page, for example, to query a bank account balance.
  • Approval process when a user tries to approve, for example, the payment of an open invoice item on the Appprove Items tab page.

This BAdI definition contains the Validate User with Security Token (VALIDATE_WITH_SECURITY_TOKEN) BAdI method.

This BAdI method checks which type of action the user wants to perform. If the action is related to bank communication, the method checks the usage category of the communication to be triggered. The method also checks which items in the FPRL_ITEM table are involved.

When a security token check is necessary based on these input parameters, the method displays a dialog box that allows the user to enter a PIN. If the PIN is correct, the user can then continue with the action. If the PIN is incorrect, corresponding messages are displayed.

Requirements

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder(transaction SE18).

If there is no active implementation for this BAdI, the system uses the code in the CL_EPIC_SECURITY_STD_FALLBACK class.

Activities

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.

For this BAdI, the CL_EPIC_SECURITY_IMPL example implementation is available. This implementation makes the security token checks based on the following procedure:

  1. The user tries to perform one of the actions that is checked, either sending a bank communication or approving an item.
  2. The implementation checks if a security token is available on the client side.
  3. If the security token is available, the implementation compares the series number of the security token on the client side with the information stored in the database.
  4. If the series numbers match, the implementation displays a dialog box that allows the user to input a PIN.
  5. The implementation reads the password that corresponds to the PIN from the security token.
  6. The implementation compares this password with the encrypted password in the database. If the password is correct, the implementation allows the Electronic Payment Integration framework to continue the processing.

Example

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
EPIC_USB_VALIDATION CN China
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG EPIC_USB_VALIDATION 0 HLA0009200 Financial Accounting 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20130726 
SAP Release Created in