Do you have any question about this error?
Message type: E = Error
Message class: SCTS_AIM - Messages for the AIM meta data repository
Message number: 060
Message text: Conflicto de modo de bloqueo (&2 <-> &3) p.tabla &1 con AIM de tp.SOBJ &4
For each after import method (AIM), the owner has to declare all tables
the AIM reads from or writes to. Furthermore, for each of these tables,
the owner of the AIM or XPRA has to declare if and how the content of
these tables is protected against write access by the productive
application running in parallel with the ZDO upgrade. The owner provides
this information by assigning a "LOCK_MODE" to each of these tables. The
possible values of the LOCK_MODE and their meanings are described
<DS:DE.OB_LOCK_MODE>here.</>
El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.
If different AIMs or XPRAs declare access to the same table and useIn a ZDO upgrade, the tables cannot be correctly classified. This can
lead to a failure of the upgrade.
Adjust the LOCK_MODE values for table &V1&.
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
SCTS_AIM060
- Conflicto de modo de bloqueo (&2 <-> &3) p.tabla &1 con AIM de tp.SOBJ &4 ?Get instant SAP help. Start your 7-day free trial now.
SCTS_AIM059
Conflicto de modo de bloqueo (&2 <-> &3) p.tabla &1 con entrada SLAPI &4
¿Qué causa este problema? For each after import method (AIM), the owner has to declare all tables the AIM reads from or writes to. If an AIM calls ...
SCTS_AIM058
Ningún ajuste de modo bloq.P -> X neces. No hay tablas con modo bloq.P.
¿Qué causa este problema? During a ZDM upgrade, some database tables can be accessed by both the productive application and the after-import method...
SCTS_AIM061
Conflicto de modo de bloqueo (&2 <-> &3) p.tabla &1 con entrada SLAPI &4
¿Qué causa este problema? For each after import method (AIM), the owner has to declare all tables the AIM reads from or writes to. If an AIM calls ...
SCTS_AIM062
Modo de bloqueo no definido para tabla &1 en metadatos de API &2
¿Qué causa este problema? The metadata object of an API &V2& to be called by an after-import method (AIM) has been created. Table &V1&a...
Haga clic en este enlace para buscar todos los mensajes de SAP.