Decision Basis

You can use the decision basis (DBA) to centrally manage a structured collection of general data for an applicant, such as personal data, employer, income, sickness-related absences and so on and make this data available to the decision subprocesses such as the eligibility and entitlement check.

You can use DBA modeling to define decision basis types to define the applicant data required for the respective social service or benefit program. You can use customer-defined check rules to perform a two-stage data check (consistency check, verification) on the decision basis data. Active DBA data, which has therefore been successfully checked, is available for the decision subprocesses that are performed in the social service plan.

(See Decision Basis).

Composite Calculation

You can use the composite gross entitlement calculation (known as the composite calculation) to enter and process benefits for several beneficiaries in a single social service plan. The composite calculation supports the legal requirement for a specific entitlement calculation logic to be used for individuals in relationships (such as married couples in a joint household). This produces a composite decisionin which eligibility periods and benefit entitlements are divided up as decision units for each beneficiary.

(See Composite Calculation).

Extended Processing of Customer Messages

The functions for processing customer messages have been extended. These functional enhancements now give you the option of defining the number of error messages and the error type (such as error, warning or information) without restriction for your customer implementations. Extended error processing references your BAdI implementations; BRFplus-based error processing has not changed.

The function enhancement does not affect your existing customer implementations with error messsages from the ABAP statement MESSAGE ... RAISING error occured.