Kontakt

Ansicht
Dokumentation

_ISISFICA_VKKICDAD - Set up Derivation Steps

_ISISFICA_VKKICDAD - Set up Derivation Steps

ABAP Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Enterprise Services for the business object InsuranceCollectionDisbursementAgreement (ICDA) contains data types that are known throughout the enterprise. If you want to use the relevant Enterprise Service to create or change insurance objects, you can derive parameters from the InsuranceCollectionDisbursementAgreement to the data specific to Collections/Disbursements for the insurance object.

In this Customizing activity you define the derivations for individual fields.

The source fields are available in the ICDA header data as well as the ICDA business partner data.

The following fields are available for use as target fields:

  • Fields for the insurance object-business partner relationship (the component names of the VKK_ICDA_DERIVE structure are shown in parentheses):
  • Account creation variant (CRTVAR)

  • Dunning variant (MVARI)

  • Correspondence variant (IS_COVAR)

  • Correspondence dunning procedure (CORR_MAHNV)

  • Incoming payment method (EZAWE_X)

  • Outgoing payment method (AZAWE_X_1, AZAWE_X_2, AZAWE_X_3, AZAWE_X_4, and AZAWE_X_5)

  • Open item grouping category (POGRU)

  • Open item summarization category (POVER)

  • Reserve and record payments on account indicator (XAKONTO)

  • Algorithm key (ALKEY)

  • Interest key (IKEY)

  • Interest calculation base period (INTPEROFF)

  • Interest calculation base period (INTPER)

  • Authorization group (AUGRP)

  • Invoicing type (FAART)

  • Base date for invoicing frequency (BASE_DATE)

  • Planning group (FDGRP)

  • Cash Management additional days (FDZTG)

  • Date up to which interest is calculated (INTTO)

  • Own bank details (EIGBV)

  • Master data group for Collections Management (CMGRP)

  • Collection strategy (STRAT)

  • Collections contact person (CPERS)

  • Withholding tax code for incoming payments (QSSKZ_E)

  • Withholding tax code for outgoing payments (QSSKZ_A)

  • Customer includes CI_DIMAIOBPAR and CI_DIMAIOBPAR2_DI for the direct input structure of the insurance object

  • You use CI-Include CI_ICDA_DERIVE_OUT_IO_P to add further direct input fields to the payment plan items. These must have the same names as those in direct input structure DIMA_A_DI.

  • Payment card fields (the component names of the VKK_ICDA_DERIVE structure are shown in parentheses):
  • Payment card category for incoming payments (CCTYP_INC): For example, you can derive this field from the payment card category for incoming payments (INC_PAYCARD_CATEGORY_CODE field) of the ICDA business partner item.

  • Payment card type for incoming payments (CCINS_INC): For example, you can derive this field from the payment card type for incoming payments (INC_PAYCARD_TYPE_CODE field) of the ICDA business partner item.

  • Payment card category for outgoing payments (CCTYP_OUT): For example, you can derive this field from the payment card category for outgoing payments (OUT_PAYCARD_CATEGORY_CODE field) of the ICDA business partner item.

  • Payment card type for outgoing payments (CCINS_OUT): For example, you can derive this field from the payment card type for outgoing payments (OUT_PAYCARD_TYPE_CODE field) of the ICDA business partner item.

You have defined a derivation strategy in the Customizing activity DS : SIMG._ISISFICA_VKKICDAS Define Derivation Strategy.

  1. Select the derivation strategy in this Customizing activity.
  2. Define the derivation steps. The following derivation step types are available:
  • Derivation rule: Define the source and target fields. Define the values for the source and target fields.

  • Table access: Determine the table and assign the respective source fields to the key fields. Furthermore, you assign the fields from the table to the relevant target fields.

  • Assignment: Create a source field and a target field. Assign the source field to the target field. Instead of assigning a source field, you can assign a constant to the target field.

  • Initialization: Select the target field that is to be initialized.

  • Enhancement: Define the source and target fields. In this step, the system processes the function module that is defined for event V364. The derivation of target fields from source fields then takes place in this function module.

  1. Set up the Derivation Strategy in the Customizing activity Set up Insurance Object Handling for your combination of the Feeder System for the Contract, the Type of Contract in the Feeder System, and the Subtype of the Contract in the Feeder System.
  • Incoming payment method (target field EZAWE_X): For example, the system can derive this field from the payment method for incoming payments (source field INC_PAYMENT_FORM_CODE) of the ICDA business partner item.
  • Outgoing payment method (target field AZAWE_X): For example, the system can derive this field from the payment method for outgoing payments (source field OUT_PAYMENT_FORM_CODE) of the ICDA business partner item. The four other outgoing payment methods can be derived accordingly with the target field AZAWE_X_2, and so on. , AZAWE_X_5 and source field OUT_PAYMENT_FORM_CODE_2, ... , OUT_PAYMENT_FORM_CODE_5.
  • Payment card category for incoming payments (target field CCTYP_INC): For example, the system can derive this field from the payment card category for incoming payments (source field INC_PAYCARD_CATEGORY_CODE) of the ICDA business partner item.
  • Payment card type for incoming payments (target field CCINS_INC): For example, the system can derive this field from the payment card type for incoming payments (source field INC_PAYCARD_TYPE_CODE) of the ICDA business partner item.






ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 8450 Date: 20240523 Time: 165946     sap01-206 ( 109 ms )