Skip to end of metadata
Go to start of metadata

 

Different application create different posting transactions. Each posting transaction contains different value categories that update different key figures. The following gives an overview about various posting transactions and the underlying value categories grouped by the application that is triggering the fund posting.

 

Fund Postings from TPM

 

Trade Promotions with Funds Management Integration create a Fund Usage object. The Fund Postings are created against the FU created for the TP.

 

Reserve Budget

 

The 'Reserve Budget' Posting is triggered from the trade promotion object. The TP appears as reference ID in the Fund Posting Header.

 

Depending on the TP status the 'Reserve Budget' posting contains the following value categories.

 

Prereserved

 

When the trade promotion gets approved the 'Reserve Budget' posting is created with value category '20 Prereserved':

 

Reserved

 

When the trade promotion gets approved the 'Reserve Budget' posting is created with value category '21 Reserved': 

Any 'prereserved' amount gets reversed on reserving the amount.

 

Fund Postings from Claims Management

 

Claims Management triggers the following Fund Postings. This is depending on the claim items status. When having claims with reference to a TPM object, such as deduction claims and invoice claims, the claim fund postings are generated against the TPM Fund Usage. For Claims without TP reference, such as direct payments, a Fund Usage from type 'Claim' will be created, and the fund postings are created against that FU.

 

Update Claim

 

The 'Update Claim' Posting is triggered from the claim object. The Claim ID appears as reference ID in the Fund Posting Header.

 

Depending on the claim item status the 'Update Claim' posting contains the following value categories.

 

Pending Claim

 

When the Claim item gets the status 'to be approved' the validated amount in the claim is posted as value category '31 Pending Claim':

 

Approve Claim

Release to Settle

 

When the Claim item gets the status 'approved' the validated amount in the claim is posted as value categories '32 Approved Claim' and '40 Released to Settle':

Any 'pending claim' amount gets reversed on approving the claim.

 

When the claim gets cancelled the '32 Approved Claim' and '40 Released to Settle' value categories get reversed.

In case the cancelled claim was already settled a 'Cancel Settlement' posting is triggered as well.

Settle Claim

 

The 'Settle Claim' Posting is triggered from the Claim Settlement. The Settlement ID appears as reference ID in the Fund Posting Header.

The 'Settle Claim' posting contains the following value categories.

 

Settled

Expensed

 

When the Claim gets settled the settlement amount is posted as value categories '41 Settled' and '44 Expensed':

Any 'released to settle' amount gets reduced by the settled amount.

 

In case there are accruals available in the fund usage the '48 Accrual Balance' is posted and the '44 Expensed' gets the delta amount posted.

 

Cancel Settlement

 

The 'Cancel Settlement' Posting is triggered from cancelling a Claim Settlement. The Settlement ID appears as reference ID in the Fund Posting Header.

When the settlement is cancelled the '41 Settled' value category is reversed and the '40 Released to Settle' , the '44 Expensed' or  '48 Accrual Balance' get posted again:

  

Fund Postings in the MDF Scenario

 

Reserve Budget

 

The 'Reserve Budget' posting is created from the Reservation created against an MDF Initiative Element. The Reservation appears as reference ID in the Fund Posting Header.

Depening on the Reservation status the value categories Prereserved and Reserved are posted.

 

Update Claim

 

Claims in the MDF Scenario create 'Update Claim' Fund Postings. The MDF Claim ID appears as reference ID in the Fund Posting Header.

Depending on the MDF Claim item status the value categories 'Pending Claim', 'Approve Claim' and 'Release to Settle' are posted.

 

Fund Postings from Accrual Load

 

Accruals are built in CRM with running the Accruals Load reports for either CRM or ECC Accruals in the following order:

 

CRM Accruals:

RCRM_FM_ACL_ACCRUAL_UPLOAD_SV: Uploads sales volumes from ERP to CRM
RCRM_FM_ACL_ACCRUAL_RUN: Calculates accruals
RCRM_FM_ACL_ACCRUAL_POSTING_FM: Posts accruals

 

ECC Accruals:

RCRM_MKTPL_TPM_EXT_ACCRUALS: Updates ECC accruals to CRM FM

 

Executing the report, or scheduing the same as a background job result in the following fund posting transactions.

 

Accrue

 

The 'Accrue' Fund Posting is triggered by executing the accruals load job. The job ID appeas as reference ID in the fund posting header.

 

The 'Accrue' fund posting contains the following value categories.

 

Accrual Balance

Expensed

 

The accrual job posts the value categories '48 Accrual Balance' and '44 Expensed.

 

Troubleshooting

 

The fund posting header (showing the fund posting) data is stored in table CRMD_FM_FPO_HEAD, wheras the items (showing the value categories) are stored in table CRMD_FM_FPO_ITEM. Checking the table entries may help to figure out any missing or duplicated fund postings. 

 

There are several reports existing for correcting known inconsistencies:

 

Fund Posting Inconsistencies

 

 

  • No labels