Do you have any question about this error?
Message type: E = Error
Message class: BV - Customer Measurement
Message number: 270
Message text: El usuario representado &1 no existe en el sistema lógico &2
A (chargeable) substituted user in the same logical system must be
specified for a (free-of-charge) substitute. The substituted user
&V1& in the logical system &V2& was not found.
Technical background: The system searched the log tables USZBVSYS in
the central system for the user &V1& in &V2&, where the states "A"
(system call for deletetion started), "D" (system assignment of the
user deleted) and "X" (to be deleted) are not accepted.
Termination.
Specify an existing substituted user.
If you believe that the substituted user &V1& must exist in logical
system &V2&, it might help to distribute this user again from the
central system to the child system, to obtain a correct entry in the
log table USZBVSYS. You can then repeat the classification as
substitute.
El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
BV270
- El usuario representado &1 no existe en el sistema lógico &2 ?Get instant SAP help. Start your 7-day free trial now.
BV269
El sistema &1 no está asignado al usuario o no forma parte de GCU
¿Qué causa este problema? The user classification for system &1 cannot be used, because The system is not a child system of a CUA landscape The...
BV268
Modelo GCU no válida
¿Qué causa este problema? The system has discovered an inconsistency in your model of the the Central User Administration (CUA)Respuesta del sistem...
BV271
Para el tipo de usuario &1 no está permitido indicar una versión especial
¿Qué causa este problema? The specification of a special version is not permitted for user type &V1&. Technical background: The central sys...
BV272
Versión especial &1 desconocida en sistema secundario &2
¿Qué causa este problema? Special version &V1& in not known in the child system &V2&. A cause of this could be that the central sys...
Haga clic en este enlace para buscar todos los mensajes de SAP.