Error importacion abap:
Hello i got this message in the import abap phase
import_mnonitor.log
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SASACONT1' import package:
/usr/sap/SOL/SYS/exe/run/R3load -ctf I /instaladores/export/D51036442/DATA_UNITS/EXP3/DATA/SASACONT1.STR /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL SASACONT1.TSK ORA -l SASACONT1.log
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'REPOSRC' import package:
/usr/sap/SOL/SYS/exe/run/R3load -ctf I /instaladores/export/D51036442/DATA_UNITS/EXP1/DATA/REPOSRC.STR /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL REPOSRC.TSK ORA -l REPOSRC.log
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SACONT01' import package:
/usr/sap/SOL/SYS/exe/run/R3load -ctf I /instaladores/export/D51036442/DATA_UNITS/EXP2/DATA/SACONT01.STR /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL SACONT01.TSK ORA -l SACONT01.log
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'REPOSRC' import package into database:
/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SASACONT1' import package into database:
/usr/sap/SOL/SYS/exe/run/R3load -i SASACONT1.cmd -dbcodepage 4103 -l SASACONT1.log -stop_on_error
TRACE: 2010-03-13 14:14:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SACONT01' import package into database:
/usr/sap/SOL/SYS/exe/run/R3load -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error
ERROR: 2010-03-13 15:26:28 com.sap.inst.migmon.LoadTask run
Loading of 'SACONT01' import package is interrupted with R3load error.
Process '/usr/sap/SOL/SYS/exe/run/R3load -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error' exited with return code 2.
For mode details see 'SACONT01.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
import_monitor_java.log
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142ifx-20090909 (JIT enabled)
J9VM - 20090908_41946_LHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
Import Monitor jobs: running 1, waiting 29, completed 0, failed 0, total 30.
Loading of 'SAPNTAB' import package: OK
Import Monitor jobs: running 0, waiting 29, completed 1, failed 0, total 30.
Import Monitor jobs: running 1, waiting 28, completed 1, failed 0, total 30.
Import Monitor jobs: running 2, waiting 27, completed 1, failed 0, total 30.
Import Monitor jobs: running 3, waiting 26, completed 1, failed 0, total 30.
Loading of 'SACONT01' import package: ERROR
Import Monitor jobs: running 2, waiting 26, completed 1, failed 1, total 30.
Import Monitor jobs: running 3, waiting 25, completed 1, failed 1, total 30.
Loading of 'SASACONT1' import package: ERROR
SACONT01.log
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20100313141454
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 21:39:36
/usr/sap/SOL/SYS/exe/run/R3load -ctf I /instaladores/export/D51036442/DATA_UNITS/EXP2/DATA/SACONT01.STR /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL SACONT01.TSK ORA -l SACONT01.log
(RTF) ########## WARNING ###########
Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
/usr/sap/SOL/SYS/exe/run/R3load: job completed
/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20100313141454
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20100313141454
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 21:39:36
/usr/sap/SOL/SYS/exe/run/R3load -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
Similar Messages
-
error analysis as in ST22 TRANSACTION:
AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
ATTACHED IS MY PROGRAM
REPORT ZVXR0303
LINE-COUNT 60(3)
LINE-SIZE 132
MESSAGE-ID VN.
Tables: VBEP, VBAP, NAST.
DATA: BEGIN OF HEADER,
ORDER(15) VALUE 'ORDER',
LINE(5) VALUE 'LINE',
MATERIAL(14) VALUE 'MATERIAL',
DUE(15) VALUE 'DUE (MAD)',
CREATED(10) VALUE 'CREATED',
QTY(10) VALUE 'QUANTITY',
KEY(5) VALUE 'KEY',
TYPE(5) VALUE 'TYPE',
END OF HEADER.
DATA: Begin of IDAT OCCURS 0,
VBELN LIKE VBAP-VBELN,
POSNR LIKE VBAP-POSNR,
werks LIKE VBAP-WERKS,
cuobj LIKE vbap-CUOBJ,
MBDAT LIKE vbep-mbdat,
ERDAT LIKE VBAP-ERDAT,
MATNR LIKE VBAP-MATNR,
KWMENG LIKE VBAP-KWMENG,
QTY TYPE I,
END of IDAT.
class cl_abap_char_utilities definition load.
constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
DATA: t_record(1000) TYPE C.
DATA: C_KWMENG(20) TYPE C.
data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
DATA: BEGIN OF TKOMCON OCCURS 50.
INCLUDE STRUCTURE CONF_OUT.
DATA: END OF TKOMCON.
DATA: iKEY TYPE I,
offset TYPE I,
KeyTypeLOC TYPE I,
KeyNumberLOC TYPE I,
type(15) TYPE C.
select-options: sVBELN FOR VBEP-VBELN obligatory,
sMAD FOR VBEP-MBDAT obligatory,
sERDAT FOR VBAP-ERDAT,
sMATNR FOR VBAP-MATNR,
sWERKS FOR VBAP-WERKS,
sKWMENG FOR VBAP-KWMENG.
SELECT
vbap~vbeln
vbap~POSNR
vbap~werks
vbap~cuobj
VBEP~MBDAT
VBAP~ERDAT
VBAP~MATNR
VBAP~KWMENG
INTO CORRESPONDING FIELDS of IDAT
FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
AND vbepposnr = vbapposnr )
WHERE BMENG > 0
AND vbep~MBDAT IN sMAD
AND VBEP~VBELN in sVBELN
AND VBAP~werks IN sWERKS
AND VBAP~ERDAT IN sERDAT
AND VBAP~MATNR IN sMATNR
AND VBAP~KWMENG IN sKWMENG
AND VBAP~ABGRU = SPACE.
APPEND IDAT.
ENDSELECT.
PERFORM TOP-OF-PAGE.
if sy-batch = 'x'.
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER t_record TO OUTFILE.
endif.
IF SY-SUBRC = 0.
LOOP at IDAT.
write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
REFRESH TKOMCON.
CALL FUNCTION 'VC_I_GET_CONFIGURATION'
EXPORTING
INSTANCE = idat-cuobj
LANGUAGE = NAST-SPRAS
TABLES
CONFIGURATION = TKOMCON
EXCEPTIONS
OTHERS = 4.
LOOP AT TKOMCON
WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
KeyTYPELOC = 0.
keynumberloc = 2.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
Else.
Offset = 0.
DO.
IF offset <= 9.
offset = offset + 1.
If TKOMCON-ATWRT+Offset(1) = ':'.
KeyTypeLOC = Offset + 1.
KeyNumberLOC = Offset + 3.
EXIT.
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
IDAT-KWMENG = TKOMCON-ATWRT(3).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDIF.
CLOSE DATASET OUTFILE.
FORM OUT-OF-RANGE-FOUND *
FORM OUT-OF-RANGE-FOUND.
WRITE: / IDAT-VBELN.
WRITE: 10 IDAT-POSNR.
WRITE: 20 IDAT-MATNR.
WRITE: 35 IDAT-MBDAT.
WRITE: 50 IDAT-ERDAT.
WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
WRITE: 85 'Consecutive'.
ELSE.
WRITE: 85 'Specific'.
ENDIF.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
TYPE = 'Consecutive'.
ELSE.
TYPE = 'Specific'.
ENDIF.
* PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
IDAT-VBELN
IDAT-POSNR
IDAT-MATNR
IDAT-MBDAT
IDAT-ERDAT
C_KWMENG
TKOMCON-ATWRT+KeyTypeLOC(6)
TYPE
INTO t_record SEPARATED BY tab.
if sy-batch = 'x'.
TRANSFER t_record TO OUTFILE.
endif.
ENDFORM.
FORM TOP-OF-PAGE *
FORM TOP-OF-PAGE.
WRITE: / 'ORDER'.
WRITE: 10 'LINE'.
WRITE: 20 'MATERIAL'.
WRITE: 35 'DUE (MAD)'.
WRITE: 50 'CREATED'.
WRITE: 65 'QTY'.
WRITE: 75 'KEY'.
WRITE: 85 'TYPE'.
PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
header-ORDER
header-LINE
header-MATERIAL
header-DUE
header-CREATED
header-QTY
header-KEY
header-TYPE
INTO t_record SEPARATED BY tab.
ENDFORM.
THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
Sales Order 1250000 TO 2250000
MAD 01/18/2005 TO 03/02/2005
Material LOCK9250FR TO LOCK9250XF
PLANT 4500
IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
ANY HELP WOULD BE GREATLY APPRECIATED
THANKS.HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Occurred on 09/29/2005 at 14:33:21
Unable to interpret "04:" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "ZVXR0303" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was
not caught, which
led to a runtime error. The reason for this exception is:
The program attempted to interpret the value "04:" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Integers are represented in ABAP using a sequence of digits and, in some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[mantissa]E[sign][exponent]
[whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"ZVXR0303" or "ZVXR0303"
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "grrsap54"
Network address.......... "10.80.96.102"
Operating system......... "HP-UX"
Release.................. "B.11.11"
Hardware type............ "9000/800"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "grrsap54"
Database type............ "ORACLE"
Database name............ "D01"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Aug 28 2005 20:25:49"
Created in............... "HP-UX B.11.00 A 9000/800"
Database version......... "OCI_920 "
Patch level.............. "88"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 050
User................ "NSHAKER"
Language key........ "E"
Transaction......... "SE38 "
Program............. "ZVXR0303"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "ZVXR0303" in
"START-OF-SELECTION".
The main program was "ZVXR0303 ".
The termination occurred in line 156 of the source code of the (Include)
program "ZVXR0303"
of the source code of program "ZVXR0303" (when calling the editor 1560).
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
001260 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001270 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001280 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001290 ?
001300 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001310 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
001320 ? PERFORM OUT-OF-RANGE-FOUND.
001330 ? ENDIF.
001340 ? ENDIF.
001350 ? Else.
001360 ? Offset = 0.
001370 ? DO.
001380 ? IF offset <= 9.
001390 ? offset = offset + 1.
001400 ? If TKOMCON-ATWRT+Offset(1) = ':'.
001410 ? KeyTypeLOC = Offset + 1.
001420 ? KeyNumberLOC = Offset + 3.
001430 ? EXIT.
001440 ? ENDIF.
001450 ? ELSE.
001460 ? EXIT.
001470 ? ENDIF.
001480 ? ENDDO.
001490 ?
001500 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001510 ?
001520 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001530 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001540 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001550 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
? IDAT-KWMENG = TKOMCON-ATWRT(3).
001570 ? PERFORM OUT-OF-RANGE-FOUND.
001580 ? ENDIF.
001590 ? ENDIF.
001600 ? ENDIF.
001610 ? ENDLOOP.
001620 ? ENDLOOP.
001630 ? ENDIF.
001640 ? CLOSE DATASET OUTFILE.
001650 ?
001660 ? *----
001670 ? * FORM OUT-OF-RANGE-FOUND *
001680 ? *----
001690 ? * ........ *
001700 ? *----
001710 ? FORM OUT-OF-RANGE-FOUND.
001720 ?
001730 ? WRITE: / IDAT-VBELN.
001740 ? WRITE: 10 IDAT-POSNR.
001750 ? WRITE: 20 IDAT-MATNR.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 44
SY-TABIX 7 SY-DBCNT 1
SY-FDPOS 4 SY-LSIND 0
SY-PAGNO 2 SY-LINNO 18
SY-COLNO 94 SY-PFKEY
SY-UCOMM SY-TITLE Out of Range Keys
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
Chosen variables
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
%_SPACE
2
0
SY-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
TKOMCON-ATWRT 04:XF1260
333543333222222222222222222222
04A861260000000000000000000000
KEYNUMBERLOC 5
0000
0005
SYST-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
SY-LDBPG SAPDB__S
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
IKEY 1260
000E
004C
KEYTYPELOC 3
0000
0003
SY ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
SVBELN IBT00012500000002250000
44533333333333333333333
92400012500000002250000
IDAT-KWMENG ########
00000000
0000000C
TKOMCON-ATWRT+0(3) 04:
333
04A
SYST ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
OUTFILE /usr/users/ftpsapfi/locks_540318
2777277677267776766266667533333322222222
F532F53523F64031069FCF3B3F54031800000000
... + 40
2222222222
0000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_Move" of the SAP
Basis System, specifically in line 529 of the module
"//bas/640_REL/src/krn/runt/abmove1.c#6".
The internal operation just processed is "MOVE".
The internal session was started at 20050929142552.
Active calls in SAP kernel
( 0) 0x4000000001751924 CTrcStack2 + 0x2bc dw.sapD01_DVEBMGS00
( 1) 0x4000000001751658 CTrcStack + 0x18 dw.sapD01_DVEBMGS00
( 2) 0x4000000001db7478 rabax_CStackSave__Fv + 0x100 dw.sapD01_DVEBMGS00
( 3) 0x4000000001dc3abc ab_rabax + 0x1e1c dw.sapD01_DVEBMGS00
( 4) 0x4000000001b44cb4 ab_cnverr__FiPcPCvN21T2 + 0x18c dw.sapD01_DVEBMGS00
( 5) 0x40000000016c96f8 ab_Move + 0x1910 dw.sapD01_DVEBMGS00
( 6) 0x40000000016d4434 ab_jmove__Fv + 0x384 dw.sapD01_DVEBMGS00
( 7) 0x4000000001022348 ab_extri__Fv + 0x17a0 dw.sapD01_DVEBMGS00
( 8) 0x4000000001726dc8 ab_xevent__FPCc + 0x38 dw.sapD01_DVEBMGS00
( 9) 0x40000000019f7efc ab_trigg__Fv + 0x94 dw.sapD01_DVEBMGS00
(10) 0x40000000019dc9ec ab_run + 0xc4 dw.sapD01_DVEBMGS00
(11) 0x4000000000f65e0c N_ab_run + 0x14 dw.sapD01_DVEBMGS00
(12) 0x4000000000f5fa88 dynpmcal + 0x198 dw.sapD01_DVEBMGS00
(13) 0x4000000000f5d500 dynppai0 + 0x830 dw.sapD01_DVEBMGS00
(14) 0x4000000000f5b8b4 dynprctl + 0x43c dw.sapD01_DVEBMGS00
(15) 0x4000000000f56728 dynpen00 + 0x2118 dw.sapD01_DVEBMGS00
(16) 0x400000000102f1b4 Thdynpen00 + 0x69c dw.sapD01_DVEBMGS00
(17) 0x400000000102e1e4 TskhLoop + 0x523c dw.sapD01_DVEBMGS00
(18) 0x4000000001022f50 tskhstart + 0x1e0 dw.sapD01_DVEBMGS00
(19) 0x4000000000dce3c4 DpMain + 0x484 dw.sapD01_DVEBMGS00
(20) 0x40000000022784cc nlsui_main + 0x14 dw.sapD01_DVEBMGS00
(21) 0x4000000000a39534 main + 0x14 dw.sapD01_DVEBMGS00
(22) 0xc00000000000a588 $START$ + 0xa0 /usr/lib/pa20_64/dld.sl
List of ABAP programs affected
Type Program Gen. Date Time Load Size
Prg ZVXR0303 09/29/2005 14:25:42 39936
Prg SAPMSSY0 05/01/2005 00:21:19 66560
Prg SAPMSSYD 06/05/2002 17:09:33 16384
Prg SAPFSYSCALLS 02/14/2002 14:22:47 6144
Prg RSDBRUNT 06/13/2004 00:43:20 226304
Typ RSSCR / / : m:15 5120
Prg RSDBSPBL 01/07/2003 18:47:02 59392
Prg SAPDB__S 02/14/2002 14:22:47 15360
Typ VARID 05/12/1997 16:51:30 4096
Prg %_CSYDB0 02/14/2002 14:22:46 28672
Prg RSDBSPVA 09/06/2005 22:54:22 112640
Prg SAPLSVAR 09/06/2005 22:57:28 625664
Typ VARIS 05/12/1997 15:27:21 2048
Typ RSVAMEMKEY 05/07/1997 13:07:49 2048
Prg RSDBSPMC 06/05/2002 17:09:26 66560
Typ DDSHDESCR 09/03/1997 03:05:16 3072
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ RSSELINT 04/04/1995 16:12:37 2048
Prg SAPLICON 03/12/2004 06:57:52 23552
Prg %_CICON 02/14/2002 14:22:46 65536
Prg SAPLSABE 02/14/2002 14:22:47 11264
Prg SAPLSECU 05/23/2005 14:04:05 64512
Typ RSSUBINFO 10/14/1999 22:01:03 3072
Prg %_CRSDS 02/14/2002 14:22:46 8192
Typ RSDSEXPR 08/20/1998 10:57:18 2048
Prg SAPLDSYA 02/14/2002 14:22:47 39936
Prg SAPFSDS1 01/07/2003 18:32:17 47104
Typ TDCLD 11/02/1998 09:51:35 5120
Prg SAPLSDOD 04/30/2005 22:53:50 39936
Typ DOKIL 05/12/1997 16:46:17 3072
Prg SAPCNVE 02/14/2002 14:22:47 6144
Prg SAPLLANG 02/14/2002 14:22:47 8192
Typ T002 02/14/1998 10:24:58 2048
Typ RSEXFCODE 08/13/1997 12:52:57 1024
Prg SAPFSPOR 03/13/2004 19:20:44 12288
Prg SAPLOMCV 05/01/2005 00:14:10 16384
Prg CL_EXITHANDLER================CP 06/13/2004 00:40:58 26624
Prg SAPLSEXV 09/06/2005 22:55:26 107520
Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 05/01/2005 00:21:35 33792
Typ SXS_ATTR 08/20/2001 12:23:27 4096
Typ V_EXT_ACT 11/09/2000 14:27:05 2048
Typ SXC_EXIT 11/09/2000 14:23:43 2048
Prg CL_EX_BADI_MATN1==============CP 05/01/2005 00:14:04 22528
Prg IF_EX_BADI_MATN1==============IP 06/13/2004 00:48:55 4096
Typ TMCNV 02/24/1999 03:33:25 3072
Prg SAPLSCNT 02/14/2002 14:22:47 24576
Typ DYCBOX 08/20/1998 11:16:53 2048
Prg SAPLSVSM 01/07/2003 18:35:45 22528
Prg SAPLSGUI 01/09/2003 17:15:12 31744
Prg SAPLSTTM 05/01/2005 00:24:04 75776
Prg SAPLSBDC 05/23/2005 14:05:19 38912
Prg CL_DATAPROVIDER===============CP 02/14/2002 14:22:46 40960
Prg %_CCNTL 02/14/2002 14:22:46 13312
Typ OBJ_RECORD 02/14/1998 08:30:43 2048
Prg SAPLSTUP 05/23/2005 14:03:46 65536
Prg SAPLCNDP 05/23/2005 14:05:47 167936
Prg SAPFGUICNTL 01/09/2003 17:18:52 20480
Prg SAPLOLEA 05/23/2005 14:03:56 79872
Prg SAPLSFES 09/06/2005 22:53:55 191488
Prg SAPLSPLUGIN 02/14/2002 14:22:48 6144
Typ ARFCRDATA 11/09/2000 14:04:16 6144
Prg SAPLGRFC 02/14/2002 14:22:47 13312
Typ SWCBCONT 11/15/2000 17:55:11 3072
Typ OLE_VERBS 04/04/1995 16:02:20 2048
Typ OLE_PA 04/04/1995 16:02:19 2048
Prg SAPSHDTV 03/12/2004 06:40:27 28672
Typ SSCRTEXTS 09/03/1997 03:12:33 3072
Typ SSCRFIELDS 05/13/1997 12:54:26 4096
Prg CL_GUI_PROPS_CONSUMER=========CP 01/07/2003 18:26:56 26624
Prg SAPLTHFB 09/06/2005 22:52:48 306176
Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 02/14/2002 14:22:46 33792
Prg CL_GUI_DATAMANAGER============CP 05/01/2005 00:20:36 70656
Prg CL_ABAP_CHAR_UTILITIES========CP 05/01/2005 00:14:49 11264
Prg RSDBSPVD 05/01/2005 00:15:44 73728
Typ RVARI 03/30/1998 09:40:50 4096
Typ RSVARIVDAT 04/04/1995 16:12:54 2048
Typ VBEP 01/27/2003 16:50:17 10240
Typ VBAP 09/15/2005 11:15:36 44032
Prg SAPLCEI0 09/22/2005 14:34:40 936960
Typ API_VALUE 02/20/1998 08:46:47 2048
Prg SAPLCUEV 06/07/2001 18:26:56 10240
Prg SAPLSUNI 06/13/2004 00:42:30 131072
Typ TFDIR 07/29/1998 19:49:08 3072
Prg %_CIBCO2 03/13/2004 14:32:13 12288
Typ IBINCOM 06/01/1999 11:56:27 3072
Typ IBINCONF 06/01/1999 11:56:27 2048
Typ IBSTCONF 06/01/1999 11:56:28 1024
Prg SAPLCUCB 05/23/2005 15:20:17 192512
Typ TCUIBSPECIAL 06/07/2001 17:50:37 1024
Prg %_CIBXX 03/13/2004 14:38:45 49152
Typ BAL_S_MSG 12/04/2000 13:04:01 6144
Prg CX_CBASE_ERROR================CP 01/27/2003 16:58:10 10240
Typ SCX_SRCPOS 11/09/2000 14:12:15 2048
Typ BAL_S_CONT 11/02/1998 09:43:07 2048
Typ BAL_S_PARM 12/04/2000 12:45:14 3072
Typ BAL_S_CLBK 11/02/1998 09:43:07 2048
Prg CX_STATIC_CHECK===============CP 02/14/2002 14:22:47 8192
Prg CX_ROOT=======================CP 02/14/2002 14:22:47 9216
Prg CL_CBASE======================CP 05/23/2005 15:19:44 87040
Typ T371G 04/29/1998 10:42:48 2048
Prg SAPLIBCO 03/13/2004 15:32:40 269312
Prg %_CIBCO 03/13/2004 14:38:45 11264
Prg SAPLIBXX 03/13/2004 14:38:46 11264
Prg SAPLIBIBF 03/13/2004 14:38:46 179200
Prg %_CIBIB 03/13/2004 14:38:45 18432
Prg SAPLIBINF 06/12/2004 22:20:22 415744
Prg %_CIBIN 03/13/2004 15:32:40 48128
Prg CL_IBASE_STRUC================CP 06/07/2001 19:59:10 106496
Prg %_CIBST 03/13/2004 14:38:45 37888
Prg CL_IBASE_STRUC_BUF============CP 06/07/2001 19:59:10 89088
Prg CL_IBASE_STRUC_STAT===========CP 06/07/2001 19:59:10 8192
Prg CL_IBASE_STRUC_BUF_IBSTREF====CP 06/07/2001 19:59:10 35840
Prg %_CIBCO1 03/13/2004 14:38:45 14336
Typ IBINVAL 09/18/2001 10:02:52 2048
Prg SAPLIBCU 03/13/2004 14:38:46 12288
Prg SAPLIBCUT 06/07/2001 18:27:19 12288
Typ T371B 05/14/1998 22:58:43 2048
Typ V_IBINR 03/13/2004 15:32:40 5120
Typ V_IBINR_CM 03/13/2004 15:32:40 5120
Prg CL_IBASE_SERVICE==============CP 06/07/2001 19:59:10 13312
Prg CL_IBASE_T371D_BUF============CP 06/07/2001 19:59:10 12288
Typ T371D 08/27/1999 18:19:44 2048
Prg CL_IBASE_R3_MATERIAL==========CP 05/23/2005 15:08:24 59392
Typ MARA 05/23/2005 15:08:18 22528
Typ MAKT 08/28/1997 08:52:19 2048
Typ ICON 01/03/1996 15:34:02 3072
Prg CL_ABAP_TYPEDESCR=============CP 05/01/2005 00:20:10 21504
Prg CL_ABAP_ELEMDESCR=============CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_DATADESCR=============CP 03/12/2004 07:16:33 14336
Prg CL_ABAP_REFDESCR==============CP 03/12/2004 07:17:23 16384
Prg CL_ABAP_STRUCTDESCR===========CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_COMPLEXDESCR==========CP 03/12/2004 07:16:33 13312
Prg CL_ABAP_TABLEDESCR============CP 03/12/2004 07:17:23 17408
Prg CL_ABAP_CLASSDESCR============CP 03/12/2004 07:17:23 23552
Prg CL_ABAP_OBJECTDESCR===========CP 03/12/2004 07:17:23 25600
Prg CL_ABAP_INTFDESCR=============CP 03/12/2004 07:16:33 19456
Prg CL_ABAP_SOFT_REFERENCE========CP 03/29/2001 16:42:12 7168
Prg CL_ABAP_REFERENCE=============CP 02/14/2002 14:22:46 6144
Prg IF_EX_CM_BADI_VERSION=========IP 01/07/2002 16:09:04 3072
Prg %_CABAP 01/07/2003 18:31:23 23552
Typ SXS_INTER 11/30/1998 15:55:16 2048
Prg CL_EX_CM_BADI_VERSION=========CP 05/01/2005 00:14:04 13312
Prg %_CSXRT 06/13/2004 00:40:55 11264
Prg CL_EXIT_MASTER================CP 06/13/2004 00:40:58 13312
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ SXC_IMPSWH 11/09/2000 14:23:44 2048
Prg CL_IM_CM_BADI_VERSION_DEF=====CP 04/17/2002 11:01:00 6144
Prg SAPLASTAT_TRIG 02/14/2002 14:22:47 11264
Typ ASTAT_TYP2 11/10/1998 05:35:18 2048
Prg IF_CM_BASELINE================IP 05/23/2005 15:08:24 9216
Prg IF_IBASE_IBOF_TREE_OBJECT=====IP 05/23/2005 15:08:24 5120
Prg IF_IBASE_INSTALL==============IP 06/07/2001 20:08:54 4096
Prg IF_IBASE_MATERIAL=============IP 06/07/2001 20:08:54 3072
Prg IF_IBASE_OBJECT===============IP 06/07/2001 20:08:54 4096
Prg SAPLBOMA 02/14/2002 14:15:40 10240
Typ IONRA 03/12/2004 02:09:40 23552
Typ IBIBCOM 08/30/2001 17:56:57 4096
Typ IBIB 03/13/2004 14:32:13 5120
Prg CL_IBASE_STRUC_SERVICE========CP 06/07/2001 19:59:10 17408
Prg CL_CU_CBASE_ENQUEUE_CORE======CP 06/07/2001 19:58:59 11264
Prg CL_CU_CBASE_ENQUEUE===========CP 06/07/2001 19:58:59 16384
Typ T371F 06/01/1999 12:00:49 2048
Typ V_IBIN_SYVAL 03/13/2004 15:32:41 4096
Typ IBIN 09/18/2001 10:02:52 6144
Typ IBINOWN 02/01/2000 14:56:07 2048
Prg CL_IBASE_T371F_BUF============CP 06/07/2001 19:59:11 8192
Prg CL_IBASE_STRUC_FILT_02========CP 06/07/2001 19:59:10 11264
Prg CL_IBASE_STRUC_FILT===========CP 06/07/2001 19:59:10 10240
Typ IBST 09/18/2001 10:02:52 4096
Typ IBST 09/18/2001 10:02:52 4096
Typ IBSTREF 04/15/1998 00:20:43 2048
Typ IBSTREF 04/15/1998 00:20:43 2048
Prg IF_CBASE_E====================IP 06/07/2001 20:08:25 3072
Prg %_CCXTAB 02/14/2002 14:22:46 6144
Prg SAPLCUCQ 09/15/2005 11:15:38 79872
Typ CUCO 09/18/2001 10:02:34 18432
Typ CUCO_OBJ 09/18/2001 10:02:34 18432
Prg SAPLCLCA 09/06/2005 23:33:29 68608
Typ TCLA 03/13/2004 14:10:20 5120
Typ TCLAO 08/13/1997 13:57:22 4096
Prg SAPLCUOB 05/23/2005 14:31:35 31744
Typ INOB 09/03/1997 03:20:02 4096
Prg SAPLCLSE 05/23/2005 14:32:26 167936
Prg %_CCC01 05/01/2005 00:34:57 53248
Typ TABLEKEY 07/06/1998 21:01:06 2048
Typ KSSK 09/18/2001 10:02:58 3072
Prg SAPLCLEF -
SAP Ecc6.0 Installation error during ABAP Import Phase 20 of 24
While I am installing SAP ECC 6.0 with Original DVD. I am getting some Issues.
I had finished upto 4 stpes . and after that IMPORT ABAP, showing error in " Log files are written to C: Program files:sapinst......"
Please Retry , View Log & Stop.
I am clicking Retry again it will be come same issue. Please Let me know.
Log Files Name - "ABAP Processors of Instances SID\DVEMGS00"Still I am getting same problem in mine SAP ECC6.0 Installation.
In Abap Instance Phase 20 of 24. Error in ABAP Instance. I check the mmc.
Disp+work is in Gray Color. Remainiing Server Green Color. After Few minutes it will stopped in Work Process.
Still Going Installation for same Process.
Let me know. -
Error "Error in ABAP statement when processing an internal table. table."
Hello,
I am facing the error when tried for GR from SRM portal for my shopping cart and for others created shopping cart. The error is
"Error in ABAP statement when processing an internal table. table."
I have the central receipient role. Couold any body assist me?
Thanks,
PijushHi Harish,
Execute the query in RSRT and check whether you have any short dump is in ST22. This would give a clear idea at what might have gone wrong.
Another thing is to check whether the code for the variable is fine in the user exit.
Hope this helps.
Bye
Dinesh -
How to avoid time out error in abap program
How to avoid time out error in abap program
based on performance wise i want please helpTimeout occurs when a statement exceeds its time limit.To avoid this we need to tune the statements.
I can give give you few tips for tune a select stament.
1.The order of the feilds in the select statement should be same as the order of fields in the database table.
2.It is always advisible to use the key fields when you are using the where clause.
3. Sort the internal table while using the for all entreis statements.
4.Use index in where clause if necessary.
5.When you have a read statement user binary search but before this a sort statement should be there.
6. Check your program with the Tcode ST05 and check which statement takes much time based on that tune that. -
Inbound queue error"XI Error APPLICATION_ERROR.ABAP: Queue stopped"
Hi,
In SMQ2 ,we have received inbound queue error "XI Error APPLICATION_ERROR.ABAP: Queue stopped".When activate queue error is not going.So please advice.
Thanks,
PraveenHello Mr,
Have a look into SAP Notes: 824554, 906435, 783515, 910649, 706563.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
To be more helpful, can you post here complete error log? -
How to check syntax errors in ABAP Queries
HI Guys,
How to check syntax errors in ABAP queries, Can please provide the T-Codes.
Advande thanks to everybody.
Thanks,
GourisankarHi
with these you can check syntax errors and performance points
Hi
these all are doing t he same thing that is checking the program for better performance
Tools for Performance Analysis
Run time analysis transaction SE30
SQL Trace transaction ST05
Extended Program Check (SLIN)
Code Inspector ( SCI)
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Extended Program Check
This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
reward if usefull -
Error message "ABAP/4 error during dynamic assign" on Contact Log creation.
Hi,
We are getting an error message "ABAP/4 error during dynamic assign beyond program bounds" displayed while creating contact log using transaction "BCT0".
Please suggest what can be the cause of the error message and how we can remove this.
Regards,
AnkurDear Andrea,
The problem should be caused by obsolete entry in table TFAWX.
Please use the following report for deleting this entry (test before in your TEST System) :
report ztfawx_delete.
tables tfawx.
select single * from tfawx where prog = 'SAPLBAS0'
and bldgr = '0110'
and mnum = 23
and bfeld = '$GENERAL'.
if sy-subrc = 0.
delete tfawx.
endif.
Buona Giornata
Mauro -
Error: The ABAP/4 Open SQL array insert results in duplic in EWM
Hi Friends,
During outbound process in EWM, my completed EWM delivery gets stuck in SMQ1 with error "The ABAP/4 Open SQL array insert results in duplic". I performed following checks and found all the ok. Please help me with your insights.
- Checked the Master data Products, Business Partners,are CIFed properly. Yes they are done properly.
- Checked if inbound is stuck in same way. But its not.
- Checked if there is any enhancement stopping in ECC. There is some enhancement in Document_save in ECC outbound delivery which I got it commented. Still the problem is same.
Please suggest what could be the root cause.
Thanks
TrivediHi Rushikesh,
I checked all Number ranges (O/D in EWM and ECC, HU and Batches). All are ok. I tried taking help of ABAPer to see if any Run time errors occuring but no use.
Regards,
Trivedi -
Error in ABAP XSLT transformation
Hi,
Im trying to upload some data from XML to abap. But Im getting an error while transforming xml data to internal table.
Here are the details.
XML:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- Edited by XMLSpy® -->
<?xml-stylesheet type="text/xsl" href="ABAP1.xsl"?>
<conceptRevDecisionXml>
<projectInfo>
<projectId>P000755</projectId>
<stage>CON</stage>
<country>Ethiopia</country>
<region>AFRICA</region>
<teamleader>Priya Agarwal</teamleader>
<teamleaderfirstname>Priya</teamleaderfirstname>
<teamleaderlastname>Agarwal</teamleaderlastname>
<actionType>X</actionType>
</projectInfo>
</conceptRevDecisionXml>
XSLT: Transformation
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sapxsl="http://www.sap.com/sapxsl"
>
<xsl:strip-space elements="*"></xsl:strip-space>
<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<PROJID>
<xsl:apply-templates select="//conceptRevDecisionXml"></xsl:apply-templates>
</PROJID>
</asx:values>
</asx:abap>
</xsl:template>
<xsl:template match="conceptRevDecisionXml">
<xsl:for-each select="projectInfo">
<xsl:value-of select="projectId"></xsl:value-of>
<xsl:value-of select="stage"></xsl:value-of>
<xsl:value-of select="country "></xsl:value-of>
<xsl:value-of select="region"></xsl:value-of>
<xsl:value-of select="teamleader"></xsl:value-of>
<xsl:value-of select="teamleaderfirstname"></xsl:value-of>
<xsl:value-of select="teamleaderlastname"></xsl:value-of>
<xsl:value-of select="actionType"></xsl:value-of>
</xsl:for-each>
</xsl:template>
</xsl:transform>
Once I run the program...Im getting an error saying...ABAP XML Formatting error in XML node..
Im new to ABAP-XML parsing..Pls help me where Im going wrong..
Thanks in advance.
Regards,
PriyaHi Priya,
you can try with the below,
1) Create a local ITAB with the structure of the XML,
TYPES: BEGIN OF t_data,
projectid TYPE char30,
stage TYPE char30,
country TYPE char30,
region TYPE char30,
teamleader TYPE char30,
teamleaderfirstname TYPE char30,
teamleaderlastname TYPE char30,
actiontype TYPE char30,
END OF t_data.
2) Create an XSLT prog in "STRANS" with the below code,
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<L_DATA>
<xsl:apply-templates select="//projectInfo"/>
</L_DATA>
</asx:values>
</asx:abap>
</xsl:template>
<xsl:template match="projectInfo">
<conceptRevDecisionXml>
<PROJECTID>
<xsl:value-of select="projectId"/>
</PROJECTID>
<STAGE>
<xsl:value-of select="stage"/>
</STAGE>
<COUNTRY>
<xsl:value-of select="country"/>
</COUNTRY>
<REGION>
<xsl:value-of select="region"/>
</REGION>
<TEAMLEADER>
<xsl:value-of select="teamleader"/>
</TEAMLEADER>
<TEAMLEADERFIRSTNAME>
<xsl:value-of select="teamleaderfirstname"/>
</TEAMLEADERFIRSTNAME>
<TEAMLEADERLASTNAME>
<xsl:value-of select="teamleaderlastname"/>
</TEAMLEADERLASTNAME>
<ACTIONTYPE>
<xsl:value-of select="actionType"/>
</ACTIONTYPE>
</conceptRevDecisionXml>
</xsl:template>
</xsl:transform>
3) Call the transformation as shown below,
CALL TRANSFORMATION zxslt_project ---> "Name of the XSLT prog created above
SOURCE XML l_xml_str ---> Source XML string
RESULT l_data = l_data. ---> ITAB as in step 1 above
Regards,
Chen -
IDOC-XI-FILE Scenario: Error in ABAP Mapping
Dear All,
I am working on IDOC-XI-Flat FIle scenario in which I am using ABAP Mapping as per document "How To Convert an IDoc-XML
structure to a flat file and vice versa in XI 3.0".
I created one customized Idoc for this. The Idoc is reacing XI but its flat file is not getting created. Its giving me following error:
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_PACKING_LIST (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I have also gone thru threads posted for the same topic earlier but still I am not been to resolve this error.
Please help me out in resolving this error.
Regards,
N.JainHI,
Log saying that, u have problem in the mapping program.
i.e Z_ABAP_MAPPING_PACKING_LIST
the problem is due declaration of data.
i hope that, you have some methods.
those are declared under intialization section in mapping program.
please use start of selection before the method.
other wise, it will come under intilization section.
warm regards
mahesh. -
SRM Installation error during abap import
Hi SAP Gurus,
This is the error during the ABAP Import.
>>>Import_Monitor.log
INFO: 2007-10-07 14:25:17
Import Monitor is started.
CONFIG: 2007-10-07 14:25:17
Application options:
dbCodepage=4103
dbType=ORA
extFiles=yes
importDirs=C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3
installDir=C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS
jobNum=3
loadArgs= -stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-10-07 14:25:17
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-10-07 14:25:17
List of packages with views: 'SAPVIEW'.
TRACE: 2007-10-07 14:25:17 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
INFO: 2007-10-07 14:25:17 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2007-10-07 14:25:18
Data codepage 1100 is determined using TOC file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-10-07 14:25:18
Version table 'SVERS' is found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-10-07 14:25:18
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
TRACE: 2007-10-07 14:25:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
INFO: 2007-10-07 14:28:04 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC.TSK ORA -l SAPSSEXC.log
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL1.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1.TSK ORA -l SAPAPPL1.log
TRACE: 2007-10-07 14:28:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL0.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0.TSK ORA -l SAPAPPL0.log
TRACE: 2007-10-07 14:28:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
TRACE: 2007-10-07 14:28:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error
TRACE: 2007-10-07 14:28:19 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error
INFO: 2007-10-07 14:38:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is successfully completed.
TRACE: 2007-10-07 14:39:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2007-10-07 14:39:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2\DATA\SAPAPPL2.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2.TSK ORA -l SAPAPPL2.log
TRACE: 2007-10-07 14:39:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error
INFO: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
TRACE: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-10-07 14:40:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSSRC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
TRACE: 2007-10-07 14:40:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
INFO: 2007-10-07 14:41:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2007-10-07 14:41:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-10-07 14:41:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPPOOL.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
TRACE: 2007-10-07 14:41:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
INFO: 2007-10-07 14:42:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
ERROR: 2007-10-07 14:42:38 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSPROT.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
TRACE: 2007-10-07 14:42:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDOCU.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
TRACE: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
TRACE: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
ERROR: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSDOCU.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-07 14:42:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSPROT.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSLEXC.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
TRACE: 2007-10-07 14:43:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPCLUST.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
TRACE: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
TRACE: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
ERROR: 2007-10-07 14:43:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error' exited with return code 2.
For mode details see 'SAPCLUST.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2007-10-07 14:43:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSLOAD.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
TRACE: 2007-10-07 14:43:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDDIM.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
TRACE: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
TRACE: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
ERROR: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSLOAD.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-07 14:43:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDDIM.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDFACT.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
TRACE: 2007-10-07 14:44:17 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPDODS.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
TRACE: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
TRACE: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-07 14:44:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDFACT.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPUSER.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
TRACE: 2007-10-07 14:44:47 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAP0000.STR" "C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
TRACE: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
TRACE: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
INFO: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
INFO: 2007-10-07 14:44:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
INFO: 2007-10-08 08:15:14
Import Monitor is started.
CONFIG: 2007-10-08 08:15:14
Application options:
dbCodepage=4103
dbType=ORA
extFiles=yes
importDirs=C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP2;C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3
installDir=C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS
jobNum=3
loadArgs= -stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-10-08 08:15:14
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-10-08 08:15:14
List of packages with views: 'SAPVIEW'.
TRACE: 2007-10-08 08:15:14 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
INFO: 2007-10-08 08:15:15 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SRM05\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2007-10-08 08:15:15
Data codepage 1100 is determined using TOC file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-10-08 08:15:15
Version table 'SVERS' is found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-10-08 08:15:15
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\Documents and Settings\joseph.f.n.quinto\Desktop\SRM Files\51032234\EXP3\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error
TRACE: 2007-10-08 08:15:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
ERROR: 2007-10-08 08:15:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:15:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSPROT.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:15:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-10-08 08:15:44 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
TRACE: 2007-10-08 08:15:45 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
ERROR: 2007-10-08 08:15:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error' exited with return code 2.
For mode details see 'SAPCLUST.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:15:49 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSLOAD.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:15:49 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSDOCU.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-10-08 08:16:14 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
TRACE: 2007-10-08 08:16:15 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2007-10-08 08:16:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDDIM.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:16:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDFACT.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-10-08 08:16:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\SR1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2007-10-08 08:16:44
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-10-08 08:16:44
9 error(s) during processing of packages.
INFO: 2007-10-08 08:16:44
Import Monitor is stopped.
Please let me know your thoughts.
Points will be given.Hi Joseph,
Pls remove any spaces in names of Export Dir Dump Location e.g. SRM files make it SRM_files etc and restart the installation.
Hope this is useful
Regards
Umesh -
OBJEC_OBJEC REF NOT FOUND,UNCAUGHT EXCEPTION ERRORS IN ABAP WEBDYNPRO
Hi Folks,
We ve been facing with a weird issue that while we were trying to access the (node in Objective setting and appraisals) configure performance management process ,getting an dump as
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_FPM_EXCEPTION
Date and Time 01.10.2009 14:08:12
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_FPM_EXCEPTION' was raised, but it was not caught anywhere
along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_FPM_MESSAGE_MANAGER========CP' has to be
terminated.
Information on where terminated
Termination occurred in the ABAP program "CL_FPM_MESSAGE_MANAGER========CP" -
in "IF_FPM_MESSAGE_MANAGER~RAISE_T100_EXCEPTION".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 20
of the (Include) program "CL_FPM_MESSAGE_MANAGER========CM00H".
The termination is caused because exception "CX_FPM_EXCEPTION" occurred in
procedure "IF_FPM_MESSAGE_MANAGER~RAISE_T100_EXCEPTION" "(METHOD)", but it was
neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "CL_FPM_MESSAGE_MANAGER========CP "; its source
code begins in line
| 1 of the (Include program "CL_FPM_MESSAGE_MANAGER========CM00H ".
HERE ANOTHER ERROR DUMP WE GET
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception CX_SY_REF_IS_INITIAL
Date and Time 29.09.2009 21:33:39
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "/1BCWDY/ENNJ6GYA7WNKNW5ZMH3D==CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Information on where terminated
Termination occurred in the ABAP program "/1BCWDY/ENNJ6GYA7WNKNW5ZMH3D==CP" -
in "PREPARE_NAVIGATION".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 1859
of the (Include) program "/1BCWDY/B_ENNJ8K41U5ETCV51ASVN".
Termination occurred in a Web Dynpro application
Web Dynpro Component FPM_OIF_COMPONENT
Web Dynpro Controller CNR_VIEW
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "PREPARE_NAVIGATION" "(METHOD)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "/1BCWDY/ENNJ6GYA7WNKNW5ZMH3D==CP "; its source
code begins in line
| 1685 of the (Include program "/1BCWDY/B_ENNJ8K41U5ETCV51ASVN ".
Techies please through some light on the above eerors
RegardsHello,
Before using the Predefined Performance Management Process you have to generate a template using the IMG activity "Configure Template for Performance Management Process" under
Personnel Management->Personnel Development->Objective Setting and Appraisals->Settings for Predefined Performance Management Process
After that a process must be configured using the IMG activity "Edit Performance Management Process"
Beefore generating a template and process, we highly recommend that you import all notes listed as related notes to sap note 1239426 since they all fix issues in the Predefined performance management.
Check also the notes below, they helped fix similar dump for other customers.
1284562 Columns missing when you generate a template
1239426 Business function HCM_OSA_CI_1 (and related notes)
1239427 Business function CA_HAP_CI_1
1295544 Error when generating categories
Hope this help
Sarah -
Hello Experts,
Have anyone tried ABAP Docs 2.1 tool in SAP version 4.7?
While installing the tool, i found some issues for which i need some clarifications.
Is the ABAP Docs tool only applicable for Ecc 6.0 and above? Since the documentation of this tool has all the screen shots of ECC 6.0 system.
I have tried it in SAP version 4.7. While executing "ABAP Docs 2.1 Cockpit" transaction, it goes for a short dump, stating that SAP_BOOL (data type used in public section of class ZFLC_ALV_GRID_GC) is not available. SAP_BOOL data type doesnot exist in SAP v4.7. But it is available in SAP ECC 6.0. I have checked it.
What are the pros and concerns to be taken care, when i need to install the tool in SAP v4.7? What are all the issues i will face other than the error SAP_BOOL?
Please help me with your valuable suggestions.
Thanks and Best Regards,
SureshNo proper responses.
-
BODS 3.2: Error opening ABAP file while trying to read ECC table
I have an ABAP data flow where I'm trying to read an ECC table (I'm following the DS 3.2 tutorial on "Extracting SAP Application Data"). I have the ECC datastore store set up with the following:
ABAP execution option = Generate and Execute
Data transfer method = Shared directory
Working directory on SAP server =
A\interfaces\D11\110 (SAP app server)
Application path to the shared directory =
A\interfaces\D11\110 (SAP app server)
Generated ABAP directory =
B\opt\ds\ds32dev1\transfer_ABAP (DS server)
However, when I run the job I get the following error:
R3C-150301 12/2/2011 1:54:41 PM Error opening file <//B/opt/ds/ds32dev1/transfer_ABAP/zcustdim.aba>.
I have verified the DS userid has read/write access to the Generated ABAP directory. Any ideas on what I'm doing wrong?
Thanks...Hi Brad, Sorry Tushar,
I see the discussion has moved on (to the second page ) Still the below should apply. Please give a look and see if it explains things.
It looks like a permission issue creating the file if I'm not wrong.
http://wiki.sdn.sap.com/wiki/display/EIM/How+to+execute+the+ABAP
point 3.
It will be the abap script that will write the file into the folder you added in the DataStore.
You can even goto the folder the abap code is in and search for the path in there.
Here a good example for windows from the wiki
http://wiki.sdn.sap.com/wiki/display/EIM/shared_directory+transport+method
with this important sentence:
However it has to be made certain that the OS user running the ABAP has the
permission to write there, and the user running the job requires read
permissions one the directory and the created file. What OS user is writing the
file? It is the user running the entire SAP instance. And who is reading the
file? The user running the DI service
So:
The working directory = where the SAP user = the user that is running the SAP installation is instructed to write the .dat file. The folder is probably local to the SAP installation?
Shared folder is for the JobServer to pick up that file. Same physical directory ...but this time from the DS user prospective. Is the JobServer on the same machine or does the folder have to be mapped?
Keep in mind that for a job server on Windows, Windows shares with \\<server>\path are OK, but I don't believe there is any other network drive mechanism, so no NFS paths in the <server>:/ or trying // etc.
Regards
Norbert
P.S. In production you should then switch to "execute" instead of load and execute and an ftp server instead of shared folders.
Maybe you are looking for
-
Some clients print, some don't
Server is PPC running OS X Server 10.4.11. Clients are OS X 10.4.11 or 10.5. Users are enabled for print in WGM, Server Admin says Print Services are on. Epson printer is connected to the server. Some of the clients can print to the shared printer. S
-
Putting Time Machine preferences back in tool bar
I had to do an erase and install then restore my data with Time Machine. It"s no longer showing in the tool bar and there is no box to check. Does anyone know how I can get it to show? I hate having to open the preferences pane if I want to check on
-
New PAGES won't lauch and open prior pages documents. What's the solution?
-
since installing new itunes iam unable to edit or change artwork in libary
-
I need Oracle Apps DBA in Cali
I need someone who is an Oracle App's DBA with RAC/Linux implementation experience for a f/t gig in California's central valley (between Fresno and Bakersfield) for a very nice and big family-owned company. The pay and benefits are super (LA/SF rates