Show TOC

 Payment Plan Interface (Transfer Category 121)

This document contains information that you must take note of when transferring data to the payment plan interface.

The examples show you how the individual fields are to be filled, under certain conditions.

Data Transfer Tool

Transferring payment plan data takes place – as for master data – using the Direct Input procedure (see Transferring Data from Legacy or Operational Systems ). The transfer category is 121.

Identifying the Payment Plan Items (POSNR Field)

All payment plan items (PPIs) must be assigned to an insurance object-partner relationship (exceptions: G/L transfer posting, business case reversal). The individual items that belong to a relationship must be differentiated by a sequence number. The following two options are available:

  • You can enter a number in the POSNR field – this must be unique for each insurance relationship.

  • You can leave the POSNR field empty; in this case, a number is determined in the Collections/Disbursements system.

    Note Note

    For PPIs that you change or reverse, you must specify the item with an entry in the POSNR field.

    End of the note.
Partner/Contract Supplement

In the interface, the system determines the partner from the contract, and vice versa, if one of the two fields is empty and unique determination is possible. You can overwrite the determined value in exit V015.

Master Data and Transaction Data for One-Time Disbursement Transactions

You can transfer master data (CPD partner) and transaction data in one step for one-time disbursement transactions. The document must be posted to an existing insurance object-partner relationship, whereby the system enters the CPD partner in the document as the alternative payer or alternative payment recipient, and also enters the data for the CPD partner for each individual payment plan document. On this basis, Collections/Disbursements creates a partner in the background.

Note Note

Note: This partner does not have to be assigned to an insurance object.

End of the note.
Customer Checks

You can define your own checks in exit V070. In case of errors, you cannot work with the ABAP expression MESSAGE but you must fill a specific error table instead.

You can find an example for this in the VKKSA2_DI_CHECK_V070 function module.

Document Categories

Every PPI must be supplied with a document category and filled with certain fields dependent on this. The document category controls further processing of the items in the area of debit entries ( Execute Payment Plans function) in the Collections/Disbursements system. It corresponds to a payment plan item category (or subitem category).

The following table shows in which cases document categories are to be defined. This means that cases are also taken into account for which one-time documents are transferred, as opposed to PPIs in the actual sense.

You want to transfer the following:

Assign the following document category (BLTYP field) and further attributes as appropriate:

PPI from which a document is created in the debit entry.

20

One-time document flag (PSNGL field = “X”)

A PPI from which one or more open items are created in FS-CD, according to the payment plan.

20 with PSNGL= [Space]

PPIs that are not to be posted in the system (for freely customer-initiated payments, Reserve and Record Payments on Account flag)

21

Payment plan subitems that occur when using a payment plan with individual distribution. Open items are created 1:1 in FS-CD from these PPIs.

30

Subledger transfer posting:

You want to make a transfer posting between contract accounts.

22, 32

General ledger transfer posting:

You want to make a transfer posting between G/L accounts.

23
RFC Module ISCD_SCPOS_MAINTAIN

  • The function and parameters for the module are described in the system.