Skip to end of metadata
Go to start of metadata

Prozess Overview


The validation sheet provides a detailed overview to decide whether a claim is valid. The validation sheet uses BPS planning integration and contains a detailed structure for validation including ausal factors.


If the validatation sheet is enabled the claim amounts must be entered using the validation sheet. The claim resolution tree disables the amount fields.

On inserting the amount in the validation sheet planning table the amounts are updated in the claim resulution tree accordingly. This is done with the 'transfer to spends' button.


The correct validation sheet is determined from the validation profile assigned to the trade promotion.



The validation sheet needs to be enabled for the claim transaction type. This is done with the following customizing:


Customer Relationship Management
Basic Settings
Define Transaction Types



The validation profile is defined in the following customizing:


Customer Relationship Management
Claims Management
Define Validation Profile


This also holds holds the reference to the BPS planning profiles using the planning profile group. The PPG for the validation sheet is defined in the following customizing:


Customer Relationship Management
Claims Management
Define Planning Profile Groups



Known Issues


Validation sheet planning table not displayed


A new claim is created and a TP is assigned, on opening the validation sheet to enter the amounts, the assigned planning layouts are not opened:



The underlying planning cube is defined as read only cube, hence the planning object cannot be locked. This is not a real locking conflict but is caused by the definition of the InfoCube. The cube is obviously defined as exclusive read cube – once the cube is in read mode planning cannot be performed. The cube needs to be in write mode so planning can be performed. This is further documented in the following SAP note:


555849 - Definition of exclusive read cube


This is one of the weakness in the design of the CRM planning integration, caused by the very way BPS handles locking. The locks set by BPS will prevent to lock the same data in another BPS, or BW-IP session. Locks set by BPS will not prevent locking or updating of the data by core BW processes.


  • No labels