Chargeback Messages 'Unable to credit full amount of charge', 'Error disbursing debit charges (over allocation)'
search cancel

Chargeback Messages 'Unable to credit full amount of charge', 'Error disbursing debit charges (over allocation)'

book

Article ID: 22057

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Description:

CA Clarity PPM v12.x

In the Admin Tool -> Chargebacks: Messages - I see the following messages on some transactions:

Error disbursing debit charges (over allocation).
Unable to credit full amount of charge.

How do I resolve these messages? I have configured my rules to debit and credit charges at 100%.

Here is the configuration of my Standard Debit Rule and my Credit Rule:

Admin Tool -> Standard Rule:

<Please see attached file for image>

Figure 1

Admin Tool -> Credit Rule:

<Please see attached file for image>

Figure 2

Solution:

STANDARD (OR PROJECT-SPECIFIC) DEBIT RULES:

Error disbursing debit charges (over allocation)

This message indicates that the Debit Rule detailed disbursements add up to more than 100%

If you are using 'Standard Rules', navigate to Admin Tool -> Chargebacks: Standard Rules (Debit Rules)

If you are using 'Project-specific Debit Rules', navigate to Main Application -> Projects -> Chargebacks: Debit Rules

Open one Debit Rule and examine the Debit Rule Details

If there is more than one 'detail' row of GL Account / Departments ; the total amount for all detail rows added together should equal 100% per fiscal period.

The "Charge To" (Debit) rules contain a Header record and one or more Detail record(s). The header record "snags" the financial transaction if the fields on the header record match with the fields on the financial record such as Input Type Code, Charge Code, Transaction Class, User Value 1, User Value 2.

The Debit Details record(s) charges the department for a percentage of the costs. In addition, the configuration of the detail record allows an association of a GL Account code to assist in reporting as many installations forward the "Charge To" (Debit) costs to another system for final processing.

To find out if the DEBIT RULE is over-allocated, you can modify the Standard or Project-specific Debit Rule Details portlet to show an Aggregation row that will 'sum' the PERCENTAGE values.

The steps below describe how to configure the portlet for Standard Debit Rules (the same configuration can be accomplished for Project-Specific Debit Rules in Project -> Chargebacks: Debit Rules tab)

  1. Admin Tool -> Standard Rules -> Select an existing Rule and navigate to the Debit Detail Properties

  2. [--Actions--] -> Configure -> Aggregation -> click 'Add' button and configure an aggregation row to 'sum' the percentage values.

    <Please see attached file for image>

    Figure 3

    <Please see attached file for image>

    Figure 4

    <Please see attached file for image>

    Figure 5

    <Please see attached file for image>

    Figure 6

To correct this configuration, calculate the allocation percentages per period for all detail rows to total 100%

<Please see attached file for image>

Figure 7

CREDIT RULES:

Unable to credit full amount of charge

This message indicates that the Credit Rule detailed disbursements add up to more than 100% (over-allocated)

Navigate to Admin Tool -> Chargebacks -> Credit Rules

Open one Credit Rule and examine the Credit Rule Details

If there is more than one 'detail' row of GL Account/Departments ; the total amount for all detail rows added together should equal 100% per fiscal period.

The Resource "Credit To" Rules contain a Header record and one or more Detail record(s). Like the "Charge To" Debit Rules - the Credit To header record "snags" the financial transaction if the fields on the header record match with the fields on the financial record such as Entity (required) Resource Location, Resource Department, Resource Class and Resource Transaction Class.

The Resource Credit Details record(s) credits the department for a percentage of the costs. In addition, the configuration of the detail record allows an association of a GL Account code to assist in reporting as many installations forward the "Credits" to another system for final processing.

To find out if the CREDIT RULE is over-allocated, you can modify the Credit Rule Details portlet to show an Aggregation row that will 'sum' the PERCENTAGE values.

The steps below describe how to configure the portlet for Credit Rules

  1. Admin Tool -> Credit Rules -> Select an existing Rule and navigate to the Credit Detail Properties

  2. [--Actions--] -> Configure -> Aggregation -> click 'Add' button and configure an aggregation row to 'sum' the percentage values.

    <Please see attached file for image>

    Figure 8

    <Please see attached file for image>

    Figure 9

    <Please see attached file for image>

    Figure 10

    <Please see attached file for image>

    Figure 11

    To correct this configuration, calculate the allocation percentages per period for all detail rows to total 100%

    <Please see attached file for image>

    Figure 12

Keywords: CLARITYKB, how-to, configuration, setup, cbk_errors.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component:

Attachments

1558718633350000022057_sktwi1f5rjvs16v0c.gif get_app
1558718631527000022057_sktwi1f5rjvs16v0b.gif get_app
1558718629664000022057_sktwi1f5rjvs16v0a.gif get_app
1558718627639000022057_sktwi1f5rjvs16v09.gif get_app
1558718625088000022057_sktwi1f5rjvs16v08.gif get_app
1558718623375000022057_sktwi1f5rjvs16v07.gif get_app
1558718621618000022057_sktwi1f5rjvs16v06.gif get_app
1558718619759000022057_sktwi1f5rjvs16v05.gif get_app
1558718617908000022057_sktwi1f5rjvs16v04.gif get_app
1558718615908000022057_sktwi1f5rjvs16v03.gif get_app
1558718614187000022057_sktwi1f5rjvs16v02.gif get_app
1558718612234000022057_sktwi1f5rjvs16v01.gif get_app