Kontakt

Ansicht
Dokumentation

Broker Collections ( RELNISCD_472_BROKER )

Broker Collections ( RELNISCD_472_BROKER )

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Broker Collections

Use

You can find the following new developments in Broker Collections for Release 4.72 of SAP for Insurance.

Integration

Broker collections and the functions for transferring coinsurance shares are now integrated: The broker can transfer coinsurance shares independently, as well as transferring the shares for the respective insurers. The broker does not transfer the total collected amount to the leading company, but just the share for the leading company.

Master Data

The new Broker Transfers Coinsurance Shares flag has been introduced for the broker contract.

Customizing Settings

The Basic Settings IMG activity for broker collections now contains both new flags, Broker Dunning Status Active and Brokers Transfer Coinsurance Shares.

Broker Report

Selection Fields

As the classification key has been introduced as a new criterion for the document, the length of the selection fields in the broker report (IBROSTMP-SELV1, ..., IBROSTMP-SELV5) has been extended to 35 characters. If you use the file interface for creating broker reports, as well as the BAPIs for broker reports, you have to adjust the interfaces accordingly.

Broker Report Proposal

The Proposal for Broker Report function in Broker Report Processing now contains the new Postprocess Proposal Online flag. If the flag is set you can manually postprocess the proposal determined by the system, meaning that items can be deactivated, clearing amounts can be changed and new items can be additionally selected. The system then uses the changed proposal to construct the broker report items.

Checking Open Items

The new release of broker report processing now contains the new Check Open Items function. This allows you to check all broker report items to see whether the information about open items, stored for the broker report item, still corresponds to the current status in the system. If this is not the case, the information about the open item is adjusted to match the current system status and the clarification code is set accordingly. You can use event V525 (Archiving Generic Tax Report Shadow Table: Sort Fields) to make further adjustments to the change determined by the system.

Late Payments

In broker report processing, you can now levy surcharges for late payments. To do this, you have to define an appropriate function module, using event 104 (Clearing: Surcharges for Late Payment). You can set the surcharges manually in processing for open items for a broker report item. If you also use the Proposal for Item function, the system automatically suggests proposals. The surcharges are added to the suggested amount for a broker report. The Value Date field in the broker report item is used to calculate the surcharges, and if it is not filled, the system does not calculate any surcharges.

Example
If an open item for 100 EUR is selected in an broker report item, and a surcharge of 2 EUR is levied manually, the system expects a reported amount of 102 EUR from the broker.
If the broker actually pays 102 EUR and a clarification code with the Post according to proposal posting rule is used, the customer item is fully cleared; the system posts 102 EUR to the broker account, as well as 2 EUR to a revenue account for payment surcharges defined in Customizing.

Authorization View

You can now adjust the authorization view for a user in broker collections, which is determined as standard with the references to the user master record for business object BUSISI0002, using event V575 (Broker Report: User Authorization).

New Events

V525: Check open items

V527: Decide whether the broker transfers the coinsurance shares for an item

V575: Adjust authorization view in broker collections

BAPIs

The BAPIs in broker collections have been adjusted as follows for the new release:

  • Transfer of coinsurance shares is integrated:
  • Broker Transfers Coinsurance Shares flag for Collect BAPI

  • Broker Transfers Coinsurance Shares flag for the Creation and Change BAPIs

  • Extension of Detail BAPIs

  • Interest for late payments:
  • AMOUNT_LATE_PYMT field in the BAPIBROKREPSELITEMC structure. In this field, you can define a surcharge for late payment (for the open items for the item), when creating broker report items.

  • AMOUNT_LATE_PYMT field in the BAPIBROKREPSELITEM structure. The field is used for the detailed view of open items for a broker report item.

  • Check authorization view for user:
  • NO_AUTH_CHECK flag. If this is set, no authorization checks are executed on the authorization view for the user currently logged on. If it is not set, the authorization checks are executed.

File Interface

The file interface for creating broker reports has been extended with the Broker Transfers Coinsurance Shares field.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

You can find further information about the new flags in broker collections in the release note on Insurance-Specific Dunning for Release 4.72.






General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7202 Date: 20240601 Time: 234511     sap01-206 ( 117 ms )