SAP ABAP IMG Activity BADI_EPIC_EBR_PRPS (BAdI: Bank Receipt Identification and Claiming)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-LOC (Application Component) Localization
     ⤷ ID-FI-EPIC-EBR (Package) Globalization: E-Payment Integration Bank Receipt
IMG Activity
ID BADI_EPIC_EBR_PRPS BAdI: Bank Receipt Identification and Claiming  
Transaction Code S_EBJ_45000059   (empty) 
Created on 20131122    
Customizing Attributes BADI_EPIC_EBR_PRPS   BAdI: Bank Receipt Identification and Claiming 
Customizing Activity BADI_EPIC_EBR_PRPS   BAdI: Bank Receipt Identification and Claiming 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EPIC_EBR_PRPS    

Use

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

You can use this BAdI during claiming and identifying bank receipts for the following purposes:

  • To define the logic the system uses to propose accounts for identifying bank receipts
  • To define the logic the system uses to propose items during claiming
  • To define how the system matches selected open items and bank receipts after you confirmed your selection during claiming

This BAdI is called in the following cases:

  • During bank receipt identification:
    • When the user chooses Automatic Identify under the Identify pushbutton on the Process Bank Receipts tab page
    • When the user chooses Propose Account in the dialog box that appears after the user selected Manual Identify
    • When the user chooses Propose Account on the Create Bank Receipt screen during bank receipt creation
  • During claiming bank receipts:
    • When the user chooses the Propose pushbutton on the Claim Bank Receipt screen
    • When the user chooses Confirm on the Claim Bank Receipt screen

This BAdI definition contains the following BAdI methods:

  • IDENTIFY_PRPS (Propose Accounts for Identifying)

    This BAdI method defines the key fields in the Electronic Bank Receipt Header (Structure) (EPIC_S_EBR_HDR) structure based on which the system searches for bank accounts in the payment transactions data of the partner master records during identification.

  • CLAIM_PRPS (Propose Items for Claiming)

    This BAdI method defines the rule that the system uses to select items for claiming after the user chooses the Propose pushbutton on the Claim Bank Receipt screen.

  • CLAIM_MAPPING (Map Items for Claiming)

    This BAdI method defines the rule that the system uses to map the selected open items and bank receipts to each other after the user confirms the selection on the Claim Bank Receipt screen.

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).

Activities

Example

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 EPIC_EBR_PRPS_IMP example implementation is available. This implementation works as follows:

  • Proposing accounts for identification: When the user chooses Propose Account during manual identification, or uses the automatic identification function, this implementation uses the values in the Company Code (BUKRS), House Bank (HBKID), and Account ID (HKTID) fields of the Electronic Bank Receipt Header (Structure) (EPIC_S_EBR_HDR) structure to find the corresponding values in the payment transactions master data of the customer or vendor. The user fills these fields on the Create Bank Receipts screen during bank receipt creation. If the system finds one record to match, it fills in the account type and account number information, or, in case of more matches, it proposes the accounts for selection in a dialog box.
  • Proposing items for claiming: When the user chooses the Propose pushbutton on the Claim Bank Receipt screen, this implementation uses the following logic to propose items for claiming depending on the selected proposal type:
    • Use Open Items:
      • The system searches for bank receipt transactions that could be claimed by the selected open items by checking the transaction date of the bank receipts and then the amount. The system checks the total amount of the selected open items and tries to select bank receipts whose total amount matches that. The possible bank receipts are sorted and displayed by transaction date, amount, and then document number. The best matches are selected in the Claimed column.
    • Use Receipts:
      • The system searches for open items to be mapped to the selected bank receipt transactions by checking the posting date of the open items and then the amounts. The system checks the total amount of the selected bank receipts and tries to select open items whose total amount matches that. The possible open items are sorted and displayed by posting date, amount, and then document number. The best matches are selected in the Claimed column.
    • Automatic Prpsl:
      • The system compares the total amounts of the two sides and picks the one that has the smaller amount. It selects all items from that side and searches for matches from the other side. The system searches for best matches by checking the posting date (in case of open items) or transaction date (in case of bank receipts) and then the amounts. The possible open items are sorted and displayed by posting/transaction date, amount, and then document number. The best matches are selected in the Claimed column.
  • Mapping items for claiming: When the user chooses Confirm on the Claim Bank Receipt screen, the system tries to map the selected bank receipts and open items to each other individually and displays the assignments and the claiming details in an ALV list. This implementation sorts items based on their transaction date (in case of bank receipts) or posting date (in case of open items) and maps bank receipts to open items based on their amounts.

    Mapping is based on your selection for proposal type. In case of mapping based on open items, for example, it works as follows. If, for an open item, there is a bank receipt with a matching amount, it maps that bank receipt to the open item. In case of more bank receipts with a matching amount, it maps the one with the earlier posting date. If there is no bank receipt with the same amount, but there is a bank receipt whose amount exceeds the amount of the open item, it maps the bank receipt and consumes only the relevant part from the bank receipt amount. The rest of the bank receipt amount can be mapped to another open item. If the system cannot find any bank receipt that could be mapped, it leaves the fields for bank receipts empty.

See also

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 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
BADI_EPIC_EBR_PRPS CN China
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20131122 
SAP Release Created in