ABAP mappingclass warning

Hi.
I get warnings on lines in my mapping class.
FIELD-SYMBOLS <ls_structcomp> TYPE abap_compdescr.
Class *****, Method IF_MAPPING~EXECUTE (E) Package "*****" cannot use object "TYPE ABAP TYPE" from package "SABP_TYPES" in any of the following ways: "USE object or type"
CALL METHOD cl_abap_tabledescr=>describe_by_data_ref
EXPORTING
p_data_ref = lr_mast
RECEIVING
p_descr_ref = lr_typedesc.
Class *****, Method IF_MAPPING~EXECUTE (E) Package "*****" cannot use object "CLAS CL_ABAP_TYPEDESCR CLAS" from package "SABP_RTTI" in any of the following ways: "USE object or type"
Have plenty of more warnings. Have I missed something in my package that I put the class in?
I get the warnings in one system and not in an other system.
I have not created the package my self in the systems.
BR
Kalle

Hi Kalle,
Could you please share the solution for the mentioned problem?
Did you add any reference of package SABP_RTTI to your package?
Thanks in advance!!
Regards,
Saurabh

Similar Messages

ABAP Program Warning

Hi Experts,
I got below error when checking an ABAP program, which was generated in maintaining datasouce with RSA6.
Description:
Type Group RSFH
In Unicode programs, the "-" character canot appear in names, as it does here in the name "RSFH_C_TFMETHODE-TEST".
Any input will be very appreciated.
Thanks,
Bill

Hi
It should be Warning Message, not an error i think.. Which Version of SAP you are working...
Still you can Execute the Program, as if its only Warning..
You can see that in the Attributes of the Program..
If it has a Program name , then goto SE38 -> give program name -> select Attributes Radio button.-> display....
You can see that is unicode enabled or not....
\[removed by moderator\]
Edited by: Jan Stallkamp on Jul 9, 2008 8:27 AM

ABAP Unit Warning: The instrumentation of testclass ... is not complete

Hi guys,
if just wondering why I'm getting this stupid The instrumentation of testclass <LCL_MY_UNIT_TEST> is not complete". It would be nice if someone has the answer.
Thanks
Christian
Message was edited by: Christian Lahmer
Message was edited by: Christian Lahmer

Sorry..Christian..Wish i could help..Refer this link..
It may be useful..
http://help.sap.com/saphelp_nw04/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm

Warning while downloading an Excel file from WD ABAP

Hi folks,
In one of requirements, Client wants to download all the data that is appearing on the screen ( WD ABAP Application ) to an Excel with a layout in different manner.
We achieved this with Simple Transformations.
Now the question is while downloading the excel file, the framework/other is throwing an Warning like
" The file you are trying to open, 'info.xls', is in a different format than specified by the extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now? "
Note: All the users of my client are using MS Office 2002 / 2003.
I am using the following code........!
*------ Call Transformation for Excel OUTPUT
CALL TRANSFORMATION ZEXCEL_OUTPUT
      SOURCE
             t_dates     = t_dates
             t_info        = t_info
      RESULT XML l_xml_string.
REPLACE ALL OCCURRENCES OF '<?xml version="1.0" encoding="utf-16"?>' l_xml_string WITH '<?xml version="1.0"?><?mso-application progid="Excel.Sheet"?>'.
**-- Call Function Module for converting string data to XSTRING
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
    EXPORTING
      text           = l_xml_string
      mimetype = 'application/xml'
    IMPORTING
      buffer      = l_xml_xstring
    EXCEPTIONS
      failed   = 1
      OTHERS   = 2.
CALL METHOD cl_wd_runtime_services=>attach_file_to_response
    EXPORTING
      i_filename       = 'info.xml'
      i_content        = l_xml_xstring
      i_mime_type   = 'application/vnd.ms-excel'.
With this code I am generating a file of type XML SPREADSHEET 2003. While opening this file I am getting the above message which the user unwanted......
Can any one help me on this -
> How to avoid this warning?
Thanks and Regards,
Aneel Danda
Edited by: danda aneel on Jul 13, 2010 1:43 PM

Firstly, Thanks for Your quick Response, Thomas.
Even though what ever may be the file name I am passing either info.xml or Info.xls , In error info.xls is coming.
Kindly provide me an alternative on this XML doesn't seem like it would match the 'application/vnd.ms-excel'.
what is the supported format.?
Similarly, It is not considering the UTF-8 / UTF-16 for xml.........same result is appearing in the output.
Edited by: danda aneel on Jul 14, 2010 7:52 AM

Warning in WD ABAP Table - Master Column Mapping deprecated

Hi ,
I am getting a warning 'Master Column Mapping deprecated' in a WD ABAP component while activating it .
Can anybody suggest what I have to do to solve this issue .
Best Regards
Sid

Hi,
Could you please tell me how to take Row Arrangement in Master Column?
Cheers
Harkesh Dang

Warning assigning 0 to BA... in ABAP syntax check on DELETE itab statement

Hello,
I didn't see an answer to that question in the forum/internet, nor in SAP notes, so I post it.
I have a 7.01 system, and this code:
TYPES : BEGIN OF ts_record,
          carrid    TYPE S_CARR_ID,
          employees TYPE p,
        END OF ts_record.
TYPES tt_record TYPE SORTED TABLE OF ts_record
      WITH UNIQUE KEY carrid.
DATA lt_record TYPE tt_record.
DELETE lt_record WHERE employees = 0.
The syntax check sends the following warning and places the cursor on the number "0" of the DELETE statement:
Assigning "0" to "BA" could result in data loss. It is therefore not
possible to optimize the LOOP. The components and values should have
identical types The types have identical types
Same thing if I make the internal table hashed or non-unique.
The warning is removed only if I replace 0 by a data object of same type as EMPLOYEES, or if I make the internal table standard.
Do you now why, I mean what is the intrinsec kernel algorithm that would make something slow? (and why a "data loss"?, what is "BA", is it a wrong translation or something else?)
Thank you
Sandra

Hi Gautham,
So, it would mean something like "hey do you know you could access the internal table by using = on the key fields and it will be optimized", like a kind of advertisement, but sent only in a few cases, I don't see why in other ones they are not sent... Hopefully we don't have this warning with READ TABLE. Maybe this warning is more useful in 7.02 with secondary index... ( BTW could somebody test if the warning is sent in 7.02 systems? )
In German, I get a better message I think, so "BA" is a bug:
Die Zuweisung von "0" nach "EMPLOYEES" ist potentiell nicht
verlustfrei. Es sind deshalb keine Optimierungen beim LOOP möglich.
Bitte eine identische Typisierung bei Komponenten und Werten benutzen.
which is google-translated:
The assignment of "0" after "EMPLOYEES" is potentially not
without loss. It is therefore not possible to use optimizations for LOOP.
Please identical components and typing in values.
which seems a better translation.
Hi Maximilian,
you're right, <= keeps the warning from being displayed, that's fun!
Well, I guess the warning is not very welcome, I hope that will be changed in the future!
Thanks for your valuable answers
Sandra
Edited by: Sandra Rossi 1 minute later
One more question: Is there a way to suppress this warning from the syntax check?

Warning message in ALV report

Hi Experts,
In ALV report i am getting warning like
" Field string LS_HEADER is not referenced statically"
Actually i declared this field as "DATA: ls_header TYPE slis_listheader.".
How to correct this warning message.
Thanks in advance.
Thanks,
Madhu.

Dear Madhu,
You are not using LS_HEADER statically that you have defined in the program. You will get a warning message since you have defined a field that you have not referenced statically.
Are you using this field dynamically? You can delete/comment the code if you are not using it statically and dynamically.
Moved the thread ABAP forum. Post your queries in relevant forums to get efficient answers.
Regards,
Naveen

Error while accesing ABAP web dynpro application

Hi Experts,
We are getting warning symbol on web page status bar, when we are accessing the ABAP web dynpro application
only first page of application is getting loaded and when we click on page it is showing error on status bar and we can perform any thing.
once we double click on warning icon,
below details are coming:
Line: 1491
Char: 3
Error: Object Expected
Code: 0
URL: url of the ABAP web dynpro application
This scenario is occuring for many ABAP WD application for a client.
Please guide how to solve this issue?
Thanks!
Piyush

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

EHP4 Upgrade ABAP+JAVA stack

Hi SDN Team,
We are in the proceess of EHP4 upgrade,now we are at the road map configuration where we got stuck,I is looking for JAVA sca files in XML file but could not found the same and it throw an error,
Trouble Ticket Log
===============
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: SE1
Hostname...........: NA00SAPSAND02
Install directory..: g:/usr/sap/SE1
Upgrade directory..: G:\EHPI\EHPI\java
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
More information can be found in the log file G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
We have added the system in SMSY and download the stack properly and I could see SCA files listed in XML file but still iam stuck the above error
PREPARE_JSPM_QUEUE_CSZ_02
===========================
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter inputFile=EHPComponents.xml
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jul 27, 2010 3:48:22 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jul 27, 2010 3:48:22 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jul 27, 2010 3:48:22 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jul 27, 2010 3:48:22 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Info]:                      com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
Jul 27, 2010 3:48:22 AM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jul 27, 2010 3:48:22 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.141.
Jul 27, 2010 3:48:22 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
Not sure what to do now.please advise.
Regards
Uday

Hi Uday,
> Jul 27, 2010 3:48:22 AM [Warning]:    >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Warning]:    >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Info]:                      >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of >stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
> Jul 27, 2010 3:48:22 AM [Error]:                       >com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception >has occurred during the execution of the phase.
> Jul 27, 2010 3:48:22 AM [Error]: >com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) >[Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no >components for this system.
I can see in the log that stack xml you are using is not for the system to whom you are upgrading. That is the reason system is rejecting stack file. Please check above extract of logs.
I would suggest you to please generate stack xml file for this system from MOPZ after correctly configuring SMSY and use it. Then your problem will be resolved.
Thanks
Sunny

SAP ERP 2005 SR 2 IDES installation error in step "Run ABAP Reports"

Hello,
I'm installing SAP ERP 2005 SR 2 IDES on Win2003 R2 SP2 and Oracle 10.2 to create a test-system for my diploma thesis.
During the step "Import ABAP" I got the following message:
object_checker.log
ERROR: 2008-05-21 20:50:38
1 objects have error/ignore/execute or unknown status in the task lines.
Invalid objects are saved in 'invalid_objects.txt' file.
invalid_objects.txt
package object type action status
SAPDFACT ?N pkey create
but the installation went on until "Run ABAP Reports".
Warnings and Errors in sapinst.log are:
WARNING 2008-05-27 15:09:36
Execution of the command "C:\usr\sap\IMP\SYS\exe\uc\NTI386\stopsap.exe name=IMP nr=00 SAPDIAHOST=imperia-sap" finished with return code -1. Output:
STOPSAP: execution of C:\usr\sap\IMP\SYS\exe\uc\NTI386\sapntwaitforhalt.exe name=IMP nr=00 SAPDIAHOST=imperia-sap 3600 failed
Details are written to C:\Programme\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\stopsap.log
WARNING 2008-05-27 15:09:36
Could not stop instance 'DVEBMGS00' of SAP system IMP.
WARNING 2008-05-27 15:09:38
Connect to message server (imperia-sap/3900) failed: NIECONN_REFUSED.
WARNING[E] 2008-05-27 15:12:05
FSL-06002 Error 1060 (Der angegebene Dienst ist kein installierter Dienst.) in execution of a 'OpenService' function, line (266), with parameter (sapccmsr.00).
WARNING[E] 2008-05-27 15:21:42
FRF-00007 Unable to open RFC connection.
ERROR 2008-05-27 16:30:15
FRF-00025 Unable to call function. Error message: connection closed without message (CM_NO_DATA_RECEIVED) .
INFO 2008-05-27 16:30:19
RFC connection closed.
ERROR 2008-05-27 16:30:45
MUT-03025 Caught ERfcExcept in Modulecall: connection closed without message (CM_NO_DATA_RECEIVED).
ERROR 2008-05-27 16:30:47
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Full log of today is available at [http://pastebin.com/f43531f97]
Has anyone an idea how I can finish this installation?
Thx
Daniele

It seems that the system did not come up and thus the RFC call fails.
What´s the output of
dev_w0
dev_disp
(in the ...work directory)?
Markus

SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903

Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\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: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.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): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.

Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain.

Program _____.MDS not registered..PI 7.1 EHP 1-MDM 7.1 Integration-ABAP API

Hi,
I am on the way of integrating ABAP API in PI 7.1 EHP 1 with MDM 7.1
I installed MDM ABAP API in PI system.
In transaction MDMAPIC, created MDM Server Connection with default port, DBMS Hosts and MDM Repository.
After I did the above tasks, I tested the RFC Connection, But its failed with the following error.
Connection Test MDM_API_GEN_DEFIANCEDEP
Connection Type TCP/IP Connection
Logon     Connection Error
Error Details     Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67
Error Details     ERROR: program DEFIANCEDEP.MDS not registered
Error Details     LOCATION: SAP-Gateway on host DEFIANCEDPI / sapgw00
Error Details     DETAIL: TP DEFIANCEDEP.MDS not registered
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 87
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1714
Error Details     RETURN CODE: 679
Error Details     SUBRC: 0
Error Details     RELEASE: 711
Error Details     TIME: Sat Mar 12 13:53:55 2011
Error Details     VERSION: 2
Appreciated if replied with the proper resolution at the earliest.
Thanks in Advance
Pradeep Shetty

Hi Kanstantsin Chernichenka,
Thanks for your reply.
I tried the given suggestion. And even restarted the PI and MDM system.
Still, I am facing the same problem.
My allow.ip file contains
122.183.187.24;
122.183.187.25;
115.242.211.112;
115.184.2.47;
My MDS.ini file contents are
[MDM Server]
XCS Ini Version=1
Accelerator Dir=E:\usr\sap\MDM\MDS02\mdm\accelerators
Log Dir=E:\usr\sap\MDM\MDS02\log
Report Dir=E:\usr\sap\MDM\MDS02\mdm\reports
Archive Dir=E:\usr\sap\MDM\MDS02\mdm\archives
Distribution Root Dir=E:\usr\sap\MDM\MDS02\mdm\distributions
Transport Dir=E:\usr\sap\MDM\MDS02\mdm\transport
Modifications Dir=E:\usr\sap\MDM\MDS02\mdm\modifications
Lexicon Dir=E:\usr\sap\MDM\MDS02\exe\Lexicons\
Extra DBConnection Validation=True
Log SQL Errors=True
String Resource Dir=E:\usr\sap\MDM\MDS02\exe\LangStrings\
Stemmer Install Dir=E:\usr\sap\MDM\MDS02\exe
Wily Instrumentation=False
Wily Instrumentation Level Threshold=10
SLD Registration=True
Skip Unchanged Records=False
Autostart=0
MDS Ini Version=1
RELEASE\UseAssert=True
Tracing Level=3
LogViewer Format Logging=False
LogViewer Format Tracing=False
Trusted SAP Systems=DPI
TrustFiles Dir=E:\usr\sap\MDM\MDS02\config
Max Threads Per Operation=Auto
Lock Account After Failed Password Attempts=5
Lock Account Duration=1800
Minimal Password Length=5
Password Expiration Days=90
Password Expiration Warning=7
Disable Read Access To Corrupt Repositories=False
MDS Scone=
Log SQL Modifications=False
Maximum DBMS Bind Count=512
Oracle\Dll=OCI.DLL
Allow Console to Retrieve Files=True
Oracle Tablespace Files=1
Default Interface Language Code=eng
Default Interface Country Code=US
Client Ping Timeout Minutes=0
Inactive Client Timeout Minutes=30
Value Retrieval Threshold=0
Protect Family Nodes With Locked Data=False
Number Of Stemmers Per Language=2
TrexDllPath=
Import Slice Size=2048
Bulk Import Silo=True
Safe Silo Mode=False
Enable Change Stamp Logging=False
Always Verify DBMS Connection Before Executing SQL Statements=False
Disable Read Access To Repositories That Require Restart=False
Family Retrieval Threshold=30000
Enable Client Dictionaries=False
Restricted Url For Client Export=
Index_Page_Margin=10
Default Slice Size=500
Default Slice Wait Time MS=300
Enable Slicing For Non-Bulk Operations=False
Multithreaded Matching=True
SAP RFC Gateways=
[MDM Server\Databases\MDM_1MDMORCL_5_3_4_3]
Port=2345
Login=SYSTEM
Password+=ES066H2NVHDCFSJ206LJ9I995SLBVSA21OMQPM0
Stemmer Language=
Stemmer Variant=
Valid Keyword Chars=abcdefghijklmnopqrstuvwxyz0123456789
Max Large Text Length=250000
Number of Rows Per Fetch=100
Max Initial MB to Retain=4
Max Send Failure MB to Retain=4
Workflow Detailed Report=False
Mail Server=
Mail SMTP Timeout=1
Here I am requesting you to send your valuable feedback at the earliest.
Thanks
Pradeep Shetty

Import ABAP error in ERP 2005 SR2 IDES installation

Hi Experts
               I am trying to install the SAP ERP 2005 SR2 ( OS is 2003 and Database is Oracle 10g )IDES which i downloaded from the SAP market place and got
the following error at the IMPORT ABAP task
INFO 2008-02-20 14:19:37
Output of C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2008-02-20 14:31:07
Execution of the command "C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103.
Output: java version "1.4.2_16"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)Java HotSpot(TM)
Client VM (build 1.4.2_16-b05, mixed mode)Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERRORImport Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
ERROR 2008-02-20 14:31:07
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-02-20 14:31:07
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW
CreateDBandLoad|ind|ind|ind|ind|10|0|NWABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor
was executed with status ERROR .
can anyone help me to fix this error. Installation of ECC 6.0 with SQL SERVER 2005 was done fine.
Thanking you
Regards
Mrudul

Hi Mrudul,
   Understood you have downloaded the completed IDES SAP 2005 SR2 package, i have also downloaded it several months ago, but i found the package not full good when i prepare to install it last week, 3 of 35 Exp unpackage CRC32 error(51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar) when unpackage them, can you do me a favor to share me the 3 rar files? As the original download address have been obsoleted away service.sap.com, i can tell you my FTP site to store them.
51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar
Or 51032413_3\EXP3\DATA\SAPAPPL1.009 & SAPAPPL1.010
12/17/2006 02:32 AM     1,048,576,000 SAPAPPL1.009
12/17/2006 02:42 AM       954,643,456 SAPAPPL1.010
Tks!
Best rds,
Jeff
msn: [email protected]

Error while installing the java add-on on abap system

Dear All,
We are trying to install java add-on with EP on present ABAP system, but getting struck up with error as below at creating java users (sapjsf) in central instance installation phase.
ENVIRONMENT:
ECC6.0
WIN 2003
KERNEL 136
SUPPORT PACK LEVEL AT 13
NETWEAVER 2004S SR1.
DB- ORACLE
error: ( usercheck.log)
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
error: (sapinst.log)
WARNING 2008-08-11 15:00:00
Execution of the command "C:\usr\sap\B60\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\lib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\sharedlib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install" -c sysnr=00 -c ashost=sapserver -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with return code -1. Output:
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
INFO 2008-08-11 15:00:00
Removing file C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\dev_UserCheck.
ERROR 2008-08-11 15:00:00
CJS-30197 . For more details see output of logfile:
ERROR 2008-08-11 15:00:00
FCO-00011 The step createJSF with step key |NW_Addin_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|8|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0|createJSF was executed with status ERROR .
Please help us out at your earliest convenience.
Thanks and warm regards,

Dear Samrat Dangeti ,
Thanks.
Inst version: 701.
JDK version: 1.4.2_13
Regards,

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

ABAP mappingclass warning

Similar Messages

Maybe you are looking for