|
#1
|
|||
|
|||
Error Amigos ABAP - Noda me Resulta es Urgente
Err.tmpo.ejec. CONVT_CODEPAGE
Excep. CX_SY_CONVERSION_CODEPAGE Fecha y hora 15.01.2010 03:29:32 Texto breve A character set conversion is not possible. ¿Qué ha sucedido? At the conversion of a text from codepage '4102' to codepage '1100': - 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 'ZPRO_004' 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 1. 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 "FILE_TABITE" "(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 '4102' or '1100' 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 405900 405900rw-rw-rw-201001140831002010011503293220100115032932") 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" "ZPRO_004" or "ZPRO_004" "FILE_TABITE" 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 "FILE_TABITE" "(FORM)", or its possible occurrence must be declared in the RAISING clause of the procedure. To prevent the exception, note the following: Propiedades fichero /home/anonimo/CI_ITEMS Autorizaciones rw-rw-rw- Modificado el 15.01.2010 03:29:32 Último acceso 14.01.2010 08:31:00 Última modif.status 15.01.2010 03:29:32 Tam. 405900 Byte Posición actual 405900 Entorno sistema SAP-Release 700 Application server... "servicio_1" Network address...... "20.20.20.10" Operating system..... "AIX" Release.............. "5.3" Hardware type........ "00C3948E4C00" Character length.... 16 Bits Pointer length....... 64 Bits Work process number.. 45 Shortdump setting.... "full" Database server... "iansamysap1_1" Database type..... "ORACLE" Database name..... "PRD" Database user ID.. "SAPPRD" Char.set.... "C" SAP kernel....... 700 created (date)... "Nov 18 2008 21:27:59" create on........ "AIX 2 5 005DD9CD4C00" Database version. "OCI_102 (10.2.0.2.0) " Patch level. 185 Patch text.. " " Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*" SAP database version. 700 Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6" Memory consumption Roll.... 16192 EM...... 75417264 Heap.... 0 Page.... 32768 MM Used. 63363128 MM Free. 3668840 Usuario y transacción Client.............. 200 User................ "ADMIN" Language key........ "S" Transaction......... " " Program............. "ZPRO_004" Screen.............. "SAPMSSY0 1000" Screen line......... 6 Info posición de cancelación Termination occurred in the ABAP program "ZPRO_004" - in "FILE_TABITE". The main program was "ZPRO_004 ". In the source code you have the termination point in line 804 of the (Include) program "ZPRO_004". The program "ZPRO_004" was started as a background job. Job Name....... "ZPRO_004" Job Initiator.. "ADMIN" Job Number..... 03001401 The termination is caused because exception "CX_SY_CONVERSION_CODEPAGE" occurred in procedure "FILE_TABITE" "(FORM)", but it was neither handled locally nor declared in the RAISING clause of its signature. The procedure is in program "ZPRO_004 "; its source code begins in line 801 of the (Include program "ZPRO_004 ". Lín. Txt.fte. 774 * IF P_UNIX NE SPACE. 775 * TRANSFER TABFACP2 TO P_FACTU LENGTH 92. 776 * ENDIF. 777 * APPEND TABFACP2. 778 *ENDFORM. " FILE_TABFACP 779 *&---------------------------------------------------------------------* 780 *& Form FILE_TABFACI 781 *&---------------------------------------------------------------------* 782 *FORM FILE_TABFACI. 783 * TABFACI-FIN = '|'. 784 * IF P_UNIX NE SPACE. 785 * TRANSFER TABFACI TO P_FACTU LENGTH 92. 786 * ENDIF. 787 * APPEND TABFACI. 788 *ENDFORM. " FILE_TABFACI 789 *&---------------------------------------------------------------------* 790 *& Form FILE_TABPED 791 *&---------------------------------------------------------------------* 792 FORM FILE_TABPED. 793 IF P_UNIX NE SPACE. 794 TRANSFER TABPED TO P_PEDID LENGTH 39. 795 ENDIF. 796 APPEND TABPED. 797 ENDFORM. " FILE_TABPED 798 *&---------------------------------------------------------------------* 799 *& Form FILE_TABITE 800 *&---------------------------------------------------------------------* 801 FORM FILE_TABITE. 802 IF P_UNIX NE SPACE. 803 >>>>> TRANSFER TABITE TO P_ITEMS LENGTH 197. 805 ENDIF. 806 APPEND TABITE. 807 ENDFORM. " FILE_TABITE 808 *&---------------------------------------------------------------------* 809 *& Form FILE_TABPLA 810 *&---------------------------------------------------------------------* 811 FORM FILE_TABPLA. 812 IF P_UNIX NE SPACE. 813 TRANSFER TABPLA TO P_PLANE LENGTH 53. 814 ENDIF. 815 APPEND TABPLA. 816 ENDFORM. " FILE_TABPLA 817 *&---------------------------------------------------------------------* 818 *& Form FILE_TABHIS 819 *&---------------------------------------------------------------------* 820 FORM FILE_TABHIS. 821 IF P_UNIX NE SPACE. 822 TRANSFER TABHIS TO P_HISTO LENGTH 66. 823 ENDIF. Contenido campos sistema Nom. Val. SY-SUBRC 0 SY-INDEX 0 SY-TABIX 1110 SY-DBCNT 7 SY-FDPOS 0 SY-LSIND 0 SY-PAGNO 0 SY-LINNO 1 SY-COLNO 1 SY-PFKEY SY-UCOMM SY-TITLE Interfaz de Pago proveedores SY-MSGTY I SY-MSGID SF SY-MSGNO 616 SY-MSGV1 ZPRO_004 SY-MSGV2 RE SY-MSGV3 ES SY-MSGV4 SY-MODNO 0 SY-DATUM 20100115 SY-UZEIT 030017 SY-XPROG SAPLSYST SY-XFORM SYSTEM_HOOK_OPEN_DATASET Llamadas/Eventos activos Nº Cl. Programa Include Lín. Nom. 3 FORM ZPRO_004 ZPRO_004 804 FILE_TABITE 2 FORM ZPRO_004 ZPRO_004 597 CARGA_PEDIDOS 1 EVENT ZPRO_004 ZPRO_004 339 START-OF-SELECTION Nom. Val. Nº 3 Cl. FORM Nom. FILE_TABITE P_UNIX X 0 0 5 8 SYST-REPID ZPRO_004 0000000000000000000000000000000000000000 0000000000000000000000000000000000000000 5554533322222222222222222222222222222222 A02FF00400000000000000000000000000000000 P_ITEMS /home/anonimo/CI_ITEMS 0000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000 2666626666666244545445222222222222222222222222222 F8FD5F1EFE9DFF39F945D3000000000000000000000000000 TABITE 450052806600010 I28250000183 SELLO½MECANICO½SI 2000 ½430½½D 1½¾”½½½½½02049001GR 28 201 0000000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 333333333333333243333333333322222254444B44444444B54233332B333BB423BB1BBBBB33333333452332222333 450052806600010092825000018300000035CCFDD531E93FD39020000D430DD401DEDDDDDD02049001720280000201 |
#2
|
|||
|
|||
Note 570051 - CX_SY_CONVERSION_CODEPAGE exception during TRANSFER
Hola:
Encontre esta nota en SAP, espero que te ayude. Summary Symptom An CX_SY_CONVERSION_CODEPAGE exception is triggered when data is written to a file using TRANSFER even though the file was opened with OPEN DATASET ... IGNORING CONVERSION ERRORS. Other terms Conversion error, multibyte code page, multibyte characters Reason and Prerequisites When data is written to files, characters may have to be converted because the file exists in a code page other than the code page used internally by the system that is running (system code page).Errors can naturally occur during conversion, for example, the character may not exist in the corresponding target code page or a character is invalid. In the latter, it may be a case that a field contains a truncated multibyte character in a multibyte code page because, for example, the field was not large enough to hold all of the character bytes. Errors detected during conversion result in the CX_SY_CONVERSION_CODEPAGE exception. You can prevent the exception from being triggered by using the IGNORING CONVERSION ERRORS addition with the OPEN DATASET. Due to a programming error, you cannot prevent the exception from being triggered in the case of truncated multibyte characters. Solution A patch is available. Patch comment: TRANSFER of broken characters 6.20 patch level: 463 Header Data Release Status: Released on: 11.11.2002 08:46:58 Master Language: Alemán Priority: Category: Primary Component: BC-ABA-LA Affected Releases |
#3
|
|||
|
|||
A ver si no he entendido mal, esto es una interfase
Lo que te esta diciendo el dump es que en el fichero (o cualquier otro contenedor de datos ) que viene de la interfase hay algun caracter que no puede interpretar Tienes que averiguar cual es el caracter que no puede interpretar y te esta dando el dump, para ello puedes ir a la transaccion SCP visualizar el codepage origen y el codepage destino y ver que caracteres existen en el origen que no estan en el destino Para corregir esto se puede hacer de varias maneras Si es posible y no afecta en los ficheros destino cuando abras el dataset hazlo con ENCODING DEFAULT para ver si asi se lo traga Si lo anterior no funciona lo que tendras que hacer es tratar el fichero origen y eliminar los caracteres que sean invalidos, hace poco alguien en este foro expuso un problema parecido en el que cuando venia una e con acento en el fichero le daba un dump, la solucion fue tratar la cadena y eliminar (o sustituir ) el caracter invalido Si quieres ver una manera de sustituir caracteres invalidos de una cadena echa un vistazo a este post |
#4
|
|||
|
|||
Continua El Error Pero En Otra Lugar
PUEDO EJECUTAR EL Z, PERO ME SALE UN MENU CON UNOS BOTENES
EDITAR Y GUARDAR, SI LOS PRESIONO ME SALE ESTO.- 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 and therefore caused a runtime error. 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/'. (further information about the file: "X 162 4096rwxrwxrwx201001151316022010011509412520100115094125") Falta tratamiento de excepción de sistema Programa ZUNIXEDI Posición desencadenante de excepción Programa ZUNIXEDI Include ZUNIXEDI Línea 61 Nombre módulo START-OF-SELECTION +++++++++++++++++++++++++++++++++++++++++++++++++++++ 31 INITIALIZATION. 32 PROGRAM = 'C:\WINDOWS\NOTEPAD.EXE'. 33 FILETEMP = 'C:\WINDOWS\TEMP\SAPTEMP.TXT'. 34 STATUS = '0'. 35 36 START-OF-SELECTION. 37 38 *------------------------UNIX-->PC-------------------------------------* 39 * SUBMIT ZUNIX-PC 40 * WITH INFILE = INFILE 41 * WITH OUTFILE = 'C:\WINDOWS\TEMP\SAPTEMP.TXT' 42 * WITH MENSAJE = 'NO' 43 * AND RETURN. 44 45 IF STATUS <> '0'. 46 INFILE = INFILE2. 47 OUTFILE = OUTFILE2. 48 ENDIF. 49 50 *{ REPLACE SBXK900051 1 51 *\ OPEN DATASET INFILE FOR INPUT IN TEXT MODE. "MESSAGE MSG_TEXT. 52 OPEN DATASET INFILE FOR INPUT IN TEXT MODE encoding default. 53 *"MESSAGE MSG_TEXT. 54 *} REPLACE 55 56 IF SY-SUBRC NE 0. 57 MESSAGE A703 WITH INFILE. 58 ENDIF. 59 60 DO. >>>> READ DATASET INFILE INTO ARCHIVO. 62 IF SY-SUBRC NE 0. 63 EXIT. 64 ENDIF. 65 APPEND ARCHIVO. 66 ENDDO. 67 68 CALL FUNCTION 'WS_DOWNLOAD' 69 EXPORTING 70 FILENAME = FILETEMP 71 FILETYPE = 'ASC' 72 IMPORTING 73 FILELENGTH = LARGO 74 TABLES 75 DATA_TAB = ARCHIVO 76 EXCEPTIONS 77 FILE_OPEN_ERROR = 01 78 FILE_WRITE_ERROR = 02 79 INVALID_FILESIZE = 03 ******************************************************* Anál.errores An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_FILE_OPEN', was not caught in procedure "UNIX_PC" "(FUNCTION)", 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: The file with the name "/home/anonimo/" cannot be opened because it is already open . Falta cláusula RAISING en interface Programa SAPLZ001 Include LZ001U01 Línea 1 Tp.módulo (FUNCTION) Nombre módulo UNIX_PC Posición desencadenante de excepción Programa SAPLZ001 Include LZ001U01 Línea 27 Tp.módulo (FUNCTION) Nombre módulo UNIX_PC 1 FUNCTION UNIX_PC. 2 *"---------------------------------------------------------------------- 3 *"*"Interfase local 4 *" IMPORTING 5 *" VALUE(INFILE) 6 *" VALUE(OUTFILE) 7 *" VALUE(TYPE) 8 *" EXCEPTIONS 9 *" UNIX_FILE_OPEN_ERROR 10 *" WS_INVALID_FILESIZE 11 *" WS_INVALID_TABLE_WIDTH 12 *" WS_INVALID_TYPE 13 *" WS_NO_BATCH 14 *" WS_UNKNOWN_ERROR 15 *"---------------------------------------------------------------------- 16 17 DATA: BEGIN OF ARCHIVO OCCURS 100, 18 LINEA(560) TYPE C, 19 END OF ARCHIVO. 20 *{ INSERT PRDK901812 3 21 constants MAXLINES type I value 500. 22 data: lineas type i, 23 flag type i, 24 modo(1) type c. 25 *} INSERT 26 >>>> OPEN DATASET INFILE FOR INPUT IN TEXT MODE ENCODING DEFAULT. " MESSAGE MSG_TEXT. 28 29 IF SY-SUBRC NE 0. 30 RAISE UNIX_FILE_OPEN_ERROR. 31 ENDIF. 32 33 *{ DELETE PRDK901812 1 34 *\ DO. 35 *\ READ DATASET INFILE INTO ARCHIVO. 36 *\ IF SY-SUBRC NE 0. 37 *\ EXIT. 38 *\ ENDIF. 39 *\ APPEND ARCHIVO. 40 *\ ENDDO. 41 *\ 42 *\ CALL FUNCTION 'DOWNLOAD' 43 *\ EXPORTING 44 *\ FILENAME = OUTFILE 45 *\ FILETYPE = TYPE 46 *\ TABLES ****************************************************** |
#5
|
|||
|
|||
nombre erroneo
Hola, me da la impresion de que no le estas indicando el nombre del fichero, es decir lo que le esta llegando a la instruccion open data set es:"/home/anonimo/" Que es una carpeta. lo que debe de llegar es el nombre de un fichero, es decir "/home/anonimo/mifichero.txt"
Saludos.
__________________
el tema esta en hacer la pregunta correcta... |
Herramientas | Buscar en Tema |
Desplegado | |
|
|