MUNDOSAP

Regresar   MUNDOSAP > DESARROLLO > Programación ABAP IV
Nombre de Usuario
Contraseña
Home Descargas Registrar FAQ Miembros Calendario Buscar Temas de Hoy Marcar Foros Como Leídos




 
Respuesta
 
Herramientas Buscar en Tema Desplegado
  #1  
Viejo 13/01/10, 18:10:17
braschilester
 
Mensajes: n/a
Unhappy Error Desarrollo de Interfaz

Err.tmpo.ejec. CONVT_CODEPAGE
Excep. CX_SY_CONVERSION_CODEPAGE
Fecha y hora 13.01.2010 16:07:59



Texto breve
A character set conversion is not possible.



¿Qué ha sucedido?
At the conversion of a text from codepage '4110' to codepage '4102':

- a character was found that cannot be displayed in one of the two
codepages;
- or it was detected that this conversion is not supported

The running ABAP program 'ZUNIXFBR' had to be terminated as the conversion
would have produced incorrect data.

The number of characters that could not be displayed (and therefore not
be converted), is 9. If this number is 0, the second error case, as
mentioned above, has occurred.



¿Qué puede hacer?
Please make a note of the actions and input which caused the error.
-

To resolve the problem, contact your
SAP system administrator.

With transaction ST22 for the ABAP dump analysis, you can analyze and
administrate termination messages, or store them for a longer time
period.

If you were requested by the application to enter a codepage, the
termination may be avoided after the restart of the application if you
enter a different codepage.

If characters could not be converted: Please use transaction SCP to
analyse the codepages used by you. Search for characters you wanted to
convert, which are not entered in the table. (If you changed a codepage,
you can use transaction SP12 to invalidate the character set buffer
(CCC).

You find further help tools to codepages in transaction SNLS.

Anál.errores
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_CODEPAGE', was not
caught in
procedure "COLLECT_DATA" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Characters are always displayed in only a certain codepage. Many
codepages only define a limited set of characters. If a text from a
codepage should be converted into another codepage, and if this text
contains characters that are not defined in one of the two codepages, a
conversion error occurs.

Moreover, a conversion error can occur if one of the needed codepages
'4110' or '4102' is not known to the system.

If the conversion error occurred at read or write of screen, the file
name was '/home/anonimo/CI_ITEMS'. (further information about the file: "X 198
400554rw-rw-rw-201001131055432010011303543720100113090642")



Notas para corregir errores

If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:

"CONVT_CODEPAGE" "CX_SY_CONVERSION_CODEPAGE"
"ZUNIXFBR" or "ZUNIXFBR"
"COLLECT_DATA"


If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

The exception must either be prevented, caught within proedure
"COLLECT_DATA" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:

Info posición de cancelación
Termination occurred in the ABAP program "ZUNIXFBR" - in "COLLECT_DATA".
The main program was "ZUNIXFBR ".

In the source code you have the termination point in line 165
of the (Include) program "ZUNIXFBR".
The termination is caused because exception "CX_SY_CONVERSION_CODEPAGE"
occurred in
procedure "COLLECT_DATA" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.

The procedure is in program "ZUNIXFBR "; its source code begins in line
151 of the (Include program "ZUNIXFBR ".
Responder Con Cita
  #2  
Viejo 13/01/10, 19:01:06
mystic_soul mystic_soul is offline
Member
 
Fecha de Ingreso: sep 2007
Mensajes: 76
es un problema de unicode..

donde tengas open dataset, pone..

OPEN DATASET archivo FOR INPUT (o OUTPUT, depende de lo que tengas) IN ... MODE ENCODING DEFAULT

Espero que te sea util..

Saludos!
Responder Con Cita
  #3  
Viejo 13/01/10, 19:33:25
braschilester
 
Mensajes: n/a
Question Gracias Amigo

Te puedo enviar a un mail el desarrollo me ayudas donde pls..soy pollo

gracias

Responder Con Cita
  #4  
Viejo 13/01/10, 19:36:25
mystic_soul mystic_soul is offline
Member
 
Fecha de Ingreso: sep 2007
Mensajes: 76
si, no hay problema! lo que si, hoy no te lo puedo contestar, pero para mañana, seguro!



Saludos!
Responder Con Cita
  #5  
Viejo 13/01/10, 19:40:07
braschilester
 
Mensajes: n/a
Cool Amigo ok,,gracias

mira ,,dando una vuelta el codigo lo tiene pero asi.


906 * OPEN DATASET p_items FOR OUTPUT IN TEXT mode encoding default.
Responder Con Cita
  #6  
Viejo 13/01/10, 19:43:44
braschilester
 
Mensajes: n/a
Wink Todo esto tiene con OPEN DATASET

841 *\ OPEN DATASET p_items FOR OUTPUT IN TEXT MODE.
854 OPEN DATASET P_ITEMS FOR OUTPUT IN BINARY MODE.
866 * OPEN DATASET P_ITEMS IN TEXT MODE FOR OUTPUT ENCODING NON-UNICODE.
879 * OPEN DATASET P_ITEMS IN TEXT MODE FOR OUTPUT ENCODING UTF-8.
895 OPEN DATASET p_items FOR OUTPUT IN LEGACY TEXT mode code page '1100'.
906 * OPEN DATASET p_items FOR OUTPUT IN TEXT mode encoding default.
Responder Con Cita
  #7  
Viejo 13/01/10, 19:48:37
mystic_soul mystic_soul is offline
Member
 
Fecha de Ingreso: sep 2007
Mensajes: 76
ok! lo mas probable que el error se encuentre en la linea 895..

primero proba reemplazar en la linea 895, lo que dice 'code page 1100' por 'encoding default'..

y luego fijate en la linea 854, de ponerle al final ENCODING DEFAULT..


Avisame a ver que tal salio!

Saludos!
Responder Con Cita
  #8  
Viejo 13/01/10, 19:52:31
braschilester
 
Mensajes: n/a
Cool Muchissssiiiiiiiiiimas gracias

Te pasaste probare,,gracias
Responder Con Cita
  #9  
Viejo 13/01/10, 19:54:55
mystic_soul mystic_soul is offline
Member
 
Fecha de Ingreso: sep 2007
Mensajes: 76
de nada! cualquier cosa tenes mi mail!

Saludos!
Responder Con Cita
  #10  
Viejo 01/09/10, 19:09:40
Ariel-StaFe Ariel-StaFe is offline
Senior Member
 
Fecha de Ingreso: nov 2007
Localización: Santa Fe - Argentina
Mensajes: 321
Mismo error pero en READ DATASET

Estimados
Se aplica la misma solucion para el DUMP en la línea con el Read Dataset ?
READ DATASET v_header INTO hcont. ?
Tendria que agregar para que quede
READ DATASET v_header INTO hcont IN TEXT MODE ENCODING DEFAULT. ?
Gracias
Responder Con Cita
Respuesta


Herramientas Buscar en Tema
Buscar en Tema:

Búsqueda Avanzada
Desplegado

Reglas de Mensajes
no puedes crear nuevos temas
no puedes responder temas
no puedes adjuntar archivos
no puedes editar tus mensajes

El código vB está On
Las caritas están On
Código [IMG] está On
Código HTML está Off
Saltar a Foro


Husos Horarios son GMT. La hora en este momento es 03:41:20.


www.mundosap.com 2006 - Spain
software crm, crm on demand, software call center, crm act, crm solutions, crm gratis, crm web