SAP ABAP IMG Activity SIMG_CFMEUNUOFDICASH (Electronic Account Statement Entry)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
IMG Activity
ID SIMG_CFMEUNUOFDICASH Electronic Account Statement Entry  
Transaction Code S_ALR_87007683   IMG Activity: SIMG_CFMEUNUOFDICASH 
Created on 19981222    
Customizing Attributes SIMG_CFMEUNUOFDICASH   Electronic Account Statement Entry 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMEUNUOFDICASH    

Electronic Account Statement Entry

General information

In Real Estate Management you can use the following for the electronic processing of incoming payments and returned debit memos:

  • Account statement entry with different data formats (for instance, Multicash, DTAUS)
  • Account statement entry using a bank procedure (DTAUS format only)

Both procedures are based on the standard function "Electronic Account Statement Entry" in Financial Accounting (FI). The account statement entry consists of three steps:

  • File import
  • Analysis of the note to payee for each line item
  • Corresponding postings

Real Estate Management is linked to this FI standard function, for example, to assign an incoming payment to a rental agreement. The following describes the steps in detail.

File import

This step is the same as the standard FI procedure. Start the program via the following menu path: Accounting -> Real Estate Management -> Rental management -> Rental accounting ->

Incoming payments -> Account statement entry

or Country specifics -> Bank procedure

Important Customizing settings:

Make the FI Customizing setting for the electronic account statement entry:

  1. Enter the house bank and the corresponding house bank accounts
  2. Enter the posting rules
  3. Assign the posting rules to external transactions (the external transactions for the bank procedure are composed of the entries in the 7A and 7B fields of the C-records. For example, if field 7A = '52' and field 7B = '000', the external transaction is '52 000')
  4. Define posting specifications for posting areas 1 (bank posting) and 2 (customer posting):

Example for returned debit memo (posting rule 0009):
Area 1
Posting type: 1 (Post to G/L account)
Document type: DZ
Debit: Posting key 40 Cash disbursement
Credit: Posting key 50 Bank
Area 2
Posting type: 7 (Clear subledger account in debit)
Document type: DZ
Debit: blank
Credit: Posting key 50 Cash disbursement

For more information, refer to the corresponding chapter of the FI Implementation Guide.

Analysis of the note to payee

There are a number of standard and application-specific interpretation algorithms available for analysing the note to payee of a line item.

In order to assign incoming payments and returned debit memos, standard FI (interpretation algorithm 001) carries out a search for a document number or a reference document number of the open item or debit memo document.

The tenant normally does not know the document number; this means he/she will indicate the rental agreement number as the assignment criterion in the "Note to payee" field, or else enter an account number that is uniquely assigned to his/her rental agreement in the case of the bank procedure. In order to interpret the data differently from the standard FI procedure, you have to use one of these two Real Estate-specific interpretation algorithms:

050: First the FI standard search according to document number or reference document number is carried out. If it is unsuccessful, the Real Estate-specific search (Module: ANALYSE_VW_RE) is carried out. Any incoming payments that are not assignable here are posted to a rejection account.

051: Here the Real Estate-specific search is started directly. Any unassignable incoming payments are posted to a rejection account. Therefore, if you expect other items besides incoming payments for rental agreements, you should use algorithm 050.

If you wish to implement your own extended logic for finding items or rental agreements, you can use interpretation algorithm 000 (customer-specific user exit):

  1. Create a report ZXF01U01 of type I (Include). You may use report RFVIKA01 as a reference. The report calls the function module ANALYSE_VW_RE.
  2. Call transaction CMOD.
  3. Create a project and give it any name.
  4. Choose "SAP enhancements" and enter the name FEB00001.
    Activate the project.

While the account statement data is being evaluated, the user exit is called. This module contains the program that you have created as an include. You can adjust program ZXF01U01 as necessary, for example by making it call your own module with your own logic instead of the standard function module ANALYSE_VW_RE. The report ZXF01U01 is with the user's namespace and can therefore be changed by you as required. However, you may not change the module ANALYSE_VW_RE since this is an SAP object.

Important Customizing settings:

You can specify the algorithm you want to use in FI Customizing. (refer to

Allocate external transactions to posting rules)

In the "Rental Accounting" section of the RE Implementation Guide you can also define flow types and account determination for nonassignable incoming payments.

Corresponding postings

Incoming payments:

If an incoming payment was assigned to a rental agreement, the system searches for the customer open items for this rental agreement. If their sum is greater than the incoming payment, the open items are sorted according to rules that you define in Customizing. Once they are sorted, the open items are cleared one by one until the incoming payment has been used up. In the case of an incoming payment that is too large, you can specify in Customizing whether a new residual item or an unqualified advance payment is to be posted. If the incoming payment could not be assigned, it is posted to a rejection account.

Returned debit memos:

Using the document number of the clearing document, found in the Note to payee field, the system searches for the original receivables. Once they are found, the clearing is reversed and a new amount consisting of the original open item and any bank charges is charged to the customer.

Important Customizing settings:

Choose the sorting criteria for the open items (refer to

Determine incoming payment control) and specify a processing type (refer to

Assign Transactions incoming payment 02, outgoing payment 01)

For the handling of returned debit memos you have to set the corresponding flow types for flow categories 3RET and 3GEB. For more information, refer to Assign Flow Types to Flow Categories.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMEUNUOFDICASH 0 I090004600 Real Estate Management 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981222 
SAP Release Created in