Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 524
Message text: Datos volumen negocios no borrados, es posible actualiz.vol.neg.doble
You have requested the retrospective compilation of statistics for all
relevant invoices received. Data that is to be retrospectively updated
and data that has already been upated is processed.
For the current document, the update is not retrospective. Instead,
business volume data is recompiled. As you have not asked the system to
delete the business volume data, data is liable to be updated twice.
The system will allow the updating of the condition record in order to
permit a selective recompilation of the statistics.
If you want to carry out a selective recompilation of statistics,
ensure that the operative data (version '000') in the LIS structures
for this arrangement are deleted first. This means that data is not
updated twice.
If you only want to carry out updates for missing or retrospective
data, set the <LS>Supplementary business volume update </> indicator on
the selection screen.
Please also refer to the documentation for this indicator.
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
MN524
- Datos volumen negocios no borrados, es posible actualiz.vol.neg.doble ?Get instant SAP help. Start your 7-day free trial now.
MN523
Reg.condición contenido en las condiciones documentos
Mensaje autoexplicativo Dado que SAP cree que este mensaje de error específico 'se explica por sí mismo', no se ha proporcionado más información. ...
MN522
Registro condición creado posteriorm., no registrado en condic.documento
¿Qué causa este problema? The condition was entered in the system retrospectively, with a validity start date that is earlier than, or identical to...
MN525
No existe ningún historial de pedido para doc.compras &, posición &
¿Qué causa este problema? No purchase order history exists for purchasing document &V1&, item &V2&, which means that the system fou...
MN526
Registro de condición divergente de la fecha de actualización
¿Qué causa este problema? The update for document &V2&, item number &V3&, has already been carried out for a condition record (inte...
Haga clic en este enlace para buscar todos los mensajes de SAP.