Do you have any question about this error?
Message type: E = Error
Message class: AJ - Billing program
Message number: 762
Message text: La consommation calculée est trop élevée.
The consumption calculated in billing for register &v2&, device &v1&,
is too high. The calculated consumption is larger than the maximum
consumption that can be entered in the internal field for saving
consumption. This error has been generated to avoid a runtime error.
The
high level of consumption was calculated by multiplying the meter
reading difference by billing factors. The difference is taken from the
meter reading &v3& and the previous meter reading &v4&. The meter
reading difference is either too large, for example, due to an
undesired meter overflow, or the billing factors are too big.
Billing is terminated.
Check the meter
readings and the billing-relevant factors (billing factor, meter factor,
calorific value and gas volume correction). If you really want to bill
consumption of this size, choose another billing dimension with a
reduced absolute amount (for example, GWh instead of kWh), or divide the
billing period into smaller units so that the consumption to be billed
is reduced for each billing period.
Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.
Extrait du message d'erreur du système SAP. Copyright SAP SE.
AJ762
- La consommation calculée est trop élevée. ?Get instant SAP help. Start your 7-day free trial now.
AJ761
Il existe des initiateurs du calcul pour le profil &1
Quelle est la cause de ce problème? Calculation triggers already exist for formula profile &v1& for the period &v2& to &v3&...
AJ760
Il manque l'ordre de facturation dans le document de calcul de fact. &1.
Quelle est la cause de ce problème? In the billing order for installation &v2&, billing document &V1& is entered as a document tha...
AJ763
Nom d'opérande ne peut pas contenir les caractères spéciaux "*" et ","
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
AJ764
Impossible de supprimer l'index d'extraction car archivage déjà lancé
Quelle est la cause de ce problème? You cannot delete extraction index &v1& because archiving has already been prepared or executed for at ...
Cliquez sur ce lien pour rechercher tous les messages SAP.