SAP ABAP IMG Activity FVD_BILL_REM_DERIVE (BAdI: Interface for Determining Remittance Code)
Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   FS-CML (Application Component) Loans Management
     FVVD_PER_DEFAULT (Package) Default: Persistence Layer
IMG Activity
ID FVD_BILL_REM_DERIVE BAdI: Interface for Determining Remittance Code  
Transaction Code S_AEN_10000935   (empty) 
Created on 20050406    
Customizing Attributes FVD_BILL_REM_DERIVE   BAdI: Interface for Determining Remittance Code 
Customizing Activity FVD_BILL_REM_DERIVE   BAdI: Interface for Determining Remittance Code 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FVD_BILL_REM_DERIVE    

Use

This business add-in (BAdI) is used in the Loans Management component.

By calling this BAdI method you can output the remittance codes valid for your loans and their descriptions in plain text, and adjust them to suit the requirements of your organization.

For each loan contract there are different remittance codes to which the borrower sends checks and coupons in order to fulfill his payment obligations. This means that the remittance codes for regular payment installments are different from those used to make payoffs.

The standard implementation FVD_BILL_REM_STANDAR is intended for the remittance code. This implementation specifies the remittance code for regular payment installments for a loan and is part of the regular billing process.

To be able to use this implementation, you need to have programmed the relevant method for reading remittance codes (GET_REMITTANCE_DATA) according to the requirements made by the application determining the remittance code of a lockbox provider.

The return parameters returned to the billing functions are address and bank details of the lockbox provider.

Requirements

Standard settings

The Business Add-In is not activated in the standard system. Sample code exists for the BAdI method. The BADI is filter-dependent.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

See also

SAP Library -> Financials -> SAP Banking -> Loans Management -> Position Management -> Periodic Processing -> Billing.

Methods

Read Remittance Code

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional 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 FVD_BILL_REM_DERIVE 0 HLA0100092 Receivables/Payment Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050419 
SAP Release Created in 600