Loans (Part 7) List of events after clicking "Save" button

Loans (Part 6) List of events during creation

Event R721 Restrict Contracts during creation of disconnection / reconnection order

In one of our implementation, we create disconnect order in background by calling FM 'ISU_S_DISCDOC_CHANGE', and we have troubles in deciding which devices to be disconnected and some devices are not even exist in the itab XY_DVALOBJ (BAPI Definition ISU_SERVORD_EDCN, Method SET_ORDERCODE_DISCONNECT) for you to choose.

SAP use a unique way to find out Contracts that can be disconnected. Basically SAP will check contracts that are listed in the open overdue items against dunning activities (FKKMAKT), and then check against Dunning History (FKKMAZE), if records exist, the contract can be disconnected. Thus, sometimes when you reverse the dunning and then re-run it again, some other devices are available for you to choose again, it's kind of magic. Lol~

Anyway, this can be resolved by enhancing event R721, you can either refresh itab T_DISC_EVER, so that all contracts are taken into consideration, or, define your own logic to include more contracts to T_DISC_EVER.

Technical Information:
Program: SAPLES34
Include Program: LES34F46
Form: DCORD_DARK_PBO
Then,
FM 'ISU_DISCDOC_ENVIRONMENT_SELECT'
Then,
FM 'ISU_GET_EVER_DISC_RELEVANT'
Then,
FM 'ISU_DB_GET_POS_DISC_RELEVANT'

Loans (Part 5) EK25, EK26, and EK27

EK25

Functionalities:

1. Enter BP Number or Contract Account Number, posting parameters, loan installment parameters and loan parameters to create loan
2. Loan Recipient and Out Payment Account
   
   • Contract Account / Business Partner to which the outgoing loan payment is posted. Loans granted can be paid out to:
   • The customer who will pay back the loan. This is also the customer for whom the repayment plan is created.
   • A third party. This is usually the case if the loan is granted for the purchase of a subsidized device, such as a heat pump, or a subsidized service, such as insulation measures. In this case, the loan should be paid directly to the supplier or service provider concerned.

EK26, EK27

Functionalities:

1. In change mode, you can perform the following activities:
• Deactivate Loan Repayment Plan
• Make changes to:
• Automatic Payment Lock Reason (P)
• Dunning Lock Reason (D)
• Interest Lock Reason (I)
• Clearing Lock Reason (C)
• Alternative Business Partner for Payments
• Payment Method
• Bank Details ID of Payee
• Alternative Payment Card ID in Document
• Exclude from dunning run
• Notes for document
• Save the changes and create letter
2. System Menu Environment provides few options:
• Source Receivables (Account Display) brings you to Account Balance Screen (FPL9)
• Interest Supplement or Interest Documents bring you to a list with loan interest information, click on any of them will launch t-code FPE3
• Installment Plans Business Partner or Contract Account will call FM 'FKK_S_INSTPLAN_GETLIST' to show all loans belong to this business partner or Contract Account

Debug FQ Events

In SAP IS-U, most of the FICA and Billing related enhancements are using FQ-Events. To debug/ find out what FQ Events to use for certain transaction, use the following steps:
1. In command field, enter /h

2. When Debugger Controls Session is launched, set break point for  FM 'FKK_FUNC_MODULE_DETERMINE '.

3. Continue and Debugger will stop at FM 'FKK_FUNC_MODULE_DETERMINE '.

4. I_FBEVE is the FQ Event Number, and at the end of this FM, T_FBSTAB will contains all the FMs that will be called under this event. You can get more information of this event via command FQEVENTS.

Loans (Part 4) Event 2900

Event: 2900 Loan: Calculate Repayment Plan
Sample FM: FKK_SAMPLE_2900_NEW


The function module processed at event 2900 calculates a repayment plan for a loan on the basis of the transfer parameters.


The module creates the repayment plan in table TFKKLOAN and returns it to the calling program.
Field FAEDN of table FKKLOAN contains the due dates of the individual loan installments. This module calculates the fields INTEREST (interest amount), REPAYMENT (repayment amount), ANNUITY (Annuity = interest amount + repayment amount) for the individual due dates.


Make sure that the condition INTEREST + REPAYMENT = ANNUITY is filled for all due dates.
In addition, the total of the amounts in the field REPAYMENT must agree with the total loan (import parameter I_LOANAMOUNT).


Notes:

1. Monthly Duration = 30 days
2. IF interval type = monthly and the interval = 1. The formula is
• Loan Monthly Payment Amount = [ rate + ( rate / { [ (1 + rate ) ^ months ] - 1 } ) ] * principal
• rate = annual percentage rate / 1200   
3. ELSE
• Get estimate roughly by triangle hypothesis - total interest amount
• Total Interest Amount = [ ( principal /2 ) * rate * ( duration / 360 ) ] 
• Payment Amount per Interval = [ Total Interest Amount + Principal Amount ] / Number of Installments

FPL9's Line Item Description (Part 3)

Sometimes if the description of the list in FPL9 is missing. May be it is due to the configuration via the following path.
The "Description in Co. Code" field is the one that displayed on FPL9 screen.

FPL9's Line Item Description (Part 2)

CALL FUNCTION 'ISU_GET_TRANSACTION_TEXT'
EXPORTING
x_applk = p_postab-applk
x_spras = p_langu
x_bukrs = p_postab-bukrs
x_sparte = p_postab-spart
x_hvorg = p_postab-hvorg
x_tvorg = p_postab-tvorg
IMPORTING
h_votxt = p_postab-votxt.

This is how SAP get the text and display on the basic list in t-code FPL9

FPL9's Line Item Description (Part 1)

SAP get the line item description via FM 'ISU_ACC_DISP_BASIC_LIST_1205'

Program: SAPLFKL9
Include Program: LFKL9FS0
Form: SELEKTION_AUSFUEHREN_END

Then,

Program: SAPLFKL9
Include Program: LFKL9U08
Function: FKK_LINE_ITEMS_ADD_INFORMATION

Loans (Part 3)

Define Loan Categories

This IMG activity allows creation of default values for a loan category. These default values are proposed when a corresponding loan is created.

Initial Screen:

Table: TEK060T - Installment Plan and Loan Categories


Second Screen:

Table: TEK060A - Loan Categories


Installment Interval: the length of the intervals between the installments. The system determines the due dates of the installments using the start date, the installment interval, and the interval category.

Interval Type: the interval between installments. The system determines the due date for installments from the start date, the installment inervals, and the interval type. Standard Values:
1 = Days
2 = Weeks
3 = Months
4 = Every 2 Weeks

Sub-transaction for items due in return payment plan: In some application areas, this indicator determines parameters such as the interest key as well as the due dates. You cannot change the main transaction - it is determined via the internal main transaction 0085. In contrast to the installment plan where you cannot change the sub-transaction for the installments, here you can use a separate sub-transaction.

Sub-transaction for credit posting from loans: When you enter a loan repayment plan, the system automatically triggers the posting of the available credit. The sub-transaction to be used can be defaulted here.

Sub-transaction for posting receivables from loans: Once a loan repayment plan has been entered, this automatically triggers the posting of the receivable to the amount of the available credit. This receivables posting forms the basis of the loan repayment plan. The sub-transaction to be used can be defaulted here.

Loans (Part 2) EK09

Define Specifications for Loans

This IMG activity allows you to store the document types which are proposed when a loan is created. The required document types must be created before configuring this.

SREL_GET_NEXT_NEIGHBORS (Part 2)

Tables involved:

1. SRRELROLES - Object Relationship Service: Roles

• Enter Object Key (OBJKEY), if possible pass in object type (OBJTYPE) as well.
• Get Type of role (ROLETYPE)  and the Role GUID (ROLEID)

2. ORBRELTYP - Object Relationship Binary Link Type

• Stores the relationship between 2 roles
• Pass Type of Role (SRRELROLES- ROLETYPE) to either ROLE_A or ROLE_B

3. ORTBRELTYP - Text table of ORBRELTYP

4. SMZB_BINREL - Object Relationship Service: Generic Binary Links

• Depends on what table is specified in ORBRELTYP- DBTABLE
• If Type of Role (SRRELROLES-ROLETYPE) exists in ORBRELTYP-ROLE_A, pass SRRELROLES-ROLEID to SMZB_BINREL-ROLE_A and vice versa.
• Get Either ROLE_A or ROLE_B

5. Back to SRRELROLES, pass SMZB_BINREL-ROLE_A or ROLE_B to SRRELROLES-ROLEID, and you will get the object key of the other object

 

Other useful Tables:

• ORROLETYP: Object Relationship Service object role types

• Return Description of Object Role

• TOJTB: Business object repository: Basic data

• Return the Business Object  Information

Loans (Part 1)

Menu Path: Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Business Transaction -> Loans

This function is not suitable for Insurance Company.

SAP IS-U allows you to define:

• Specifications for Loans
• Loan Categories