Queries related to ABAP Programs migration to SAP ECC 6.0

We are planning to re-implement SAP using SAP ECC 6.0 We are currently using SAP R3 Version 4.7
Regarding migration of existing ABAP Programs and data, I have some queries which may kindly be answered by any of the experts of this forum.
1. I have heard that SAP ECC 6.0 or SAP Netweaver 7.0 will never support BDC programs. To upload data into SAP, BAPI is the preferred option. Is that true?
2. In ABAP Programming, relational operator < (less than), > (greater than), <= (less than or equal to) etc are not supported by SAP Netweaver 7.0. In stead, operator contants LT, GT, LE etc must be used. Other wise, SAP reports syntax error. Is thar true?
3. Screens (Dynpros) have been fully programmed in ABAP Objects in almost all programs related to functional modules (SD,MM,PP,FI/CO etc) in SAP ECC 6.0. Is that true?
4. Programs written in SAP R/3 Version 4.7 will report syntax errors when that program is compiled as it is in SAP Netweaver. Is that true?
I request you to kindly reply for these four queries at the earliest.
Thanking you,
K. RANGARAJAN
ABAP Programmer

SAP ECC6.0 will be supporting BDC programs too.But ,apart from this there are other options like LSMW ,BAPI, ECATT tool
which serves the same purpose . It doesnot mean that SAP wont support BDC.
Coming to relational operators u can use both of them but preferred is operator contants LT, GT, LE.
If there are any obsolete statements or any Obsolete function modules used in version4.7 U will get syntax errors or unicode errors.
Regards,
Lakshman.

Similar Messages

Call ABAP Program from outside SAP

Hi all,
How can I call an ABAP program from outside SAP, for example from a C++ executable, a .NET assembly or a JAVA package ? Are their "adapters" provided by SAP for this ?
Angela

Hi Angela,
as mho already stated:
For external connections to ABAP, the sap-proprietary "remote function call (RFC)" is a common way.
SAP delivers an RFC-library for this, and for some development environments SAP even offers a connector on top of this library to make connectivity more easy (SAP Java Connector, SAP Business Connector, SAP Connector for Microsoft .Net). An RFC is always starting function modules in ABAP, not ABAP programs, and these function modules need the attribute "remote-enabled".
(Remark: in the context of SAP NetWeaver Process Integration, SAP offers adapters for connectivity, also for ABAP systems.)
For ABAP systems on basis code line 6.20 and above, the remote-enabled function modules can externally be used as web services.
Information on RFC can be found in the SAP Help Portal http://www.help.sap.com, e.g. [RFC Call - Example Program|http://help.sap.com/saphelp_nw04/helpdata/en/3d/733760ccb411d2b4550060941936e3/frameset.htm]. A search in SDN provides links to the Help Portal as well.
>
Angela GALACY wrote:
> For example, what if I develop an EJB inside NetWeaver, will I be able to access this from any J2EE client ?
This part is beyond the ABAP question, and my guess is pretty simple: like on any other J2EE server.
Regards, Boris

ABAP Programming Error with SAP HR IMG

Hi,
I am new to this site and I have a question. Recently, I had the "Vanilla SAP System" installed on a harddrive for my laptop. I am studying for the SAP HR Consultant Certification.
However, the system doesn't have the training DB and I have to start with implementing a project through the IMG. Yesterday, I received an error message (below) when I go to the application component sectin to add on Pers. Administration, Countries, etc).
Can anyone direct me to someone in Atlanta that may be able to take a look at this for me?
I was working on my computer and I get to a certain point in my customizing activity and I get this error msg:
Runtime errors RFCGUI_unexpected_data
The termination occurred in the ABAP program SAPMSSYO in %_CTL_OUTPUT
The main program was SAPLS_IMG_TOOL_5
The termination occurred in line 30 of the source code of the (Include) program <SYSINI> of the source code of program <SYSINI> (when calling the editor 300)
There is more to the error message and I would have to perform the activity to let the person see the message. Not unless they can tell what's wrong by the error above.

Hi Pradeep,
If it was resolved, please let me know the resolution.
Thanks,
Srivijay

Re-use of ABAP Program ID from SAP Application in BODS 4.0

Objective:
1. We have used ABAP Program ID in DataStage 7.5. For example, ZDSYE001
2. The above ABAP Program ID is residing in SAP Application Server.
3. Now we need to use the same ABAP Program ID [ZDSYE001] in SAP BODS 4.0
=====================================================================
ISSUE/ERROR:
1. In SAP BODS 4.0, we create a Datastore for SAP Application with all the configuration details.
2. We are able to view external metadata for tables but not for ABAP Program ID.
3. For ABAP Program ID, we are getting below error while using Extractor Object in Datastore to get the ABAP program ID:
Cannot import the extractor<name=ZDSYE001>
Error creating RFC Fuction<Z_AW_EXTRACTOR_IMPORT>:<RFC_ABAP_EXTRACTION-Exception Key:FU_NOT_FOUND,SYS-MSGTY:E,SY-MSGID:FL,SY-MSGNO: 046)>.Notify Customer Support (BODI-1116153)
=======================================================================
Please provide your inputs ASAP

Hi,
Please check this wiki pages for more information on how to solve your issue:
http://wiki.sdn.sap.com/wiki/display/BOBJ/ReleasingExtractorsforusebytheODP+API
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=217449812
Hope it helps,
Pedro

OS Migration of SAP ECC 6.0 system and SID needs to be changed.

Hi Folks ,
               I need a small help ,
               here i need to migrate SAP ECC 6.0 EHP 7 from SUSE Linux to AIX and SID is also going to change from ABC to XYZ
               so what is the proposed plan for it
               1. we have to built the target system first ... and go with the import or
               2. after export and import we have to go for SID change ...

Hi Reagan ,
In homogeneous system copy its possible , its possible to change SID when you are importing but is it possible for heterogeneous copy to change the SID
here the file system is built with target SID (eg : usr/sap/XYZ , sapmnt/XYZ , oracle/XYZ)
or we have to create the symlinks like oracle/ABC-->oracele/XYZ and then we have to delete the symlinks and change the SID

How to recover deleted program / smartform from sap ecc 6.0

Hi
whats tcode or how can we revert back our delted program or smartform,
can we do it form their object?
Best regards,
dushyant.

Dushyant,
Check whether the program is in TRDIR table or not,if it is there then it will be available else you need to talk to basis guys.
If the program is there and you want to revert to previous version then go to version management and select the version number and then click on the button RETRIEVE.
Smartforms don't haver the concept of version management and hence it is always advisable to download the smartform and then go ahead with the changes.If in case you want to revert to pervious version then you can upload the downloaded smartform and get back the previous version.
K.Kiran.

ABAP Programming Help

Hello All,
I am very new to ABAP programming and i want to learn ABAP. For this i am using following link
http://help.sap.com/saphelp_470/helpdata/en/fc/eb2c46358411d1829f0000e829fbfe/frameset.htm
But this document does not contains any walkthroughs or How to Section, so that beginner can start programming.
Do you have any such material related to only programming steps.
Thanks in advance,
Prashant

Pls follow the below link:
http://www.itcserver.com/blog/2006/06/24/the-structure-of-an-abap-program/
http://help.sap.com/saphelp_470/helpdata/en/fc/eb2c46358411d1829f0000e829fbfe
Please check also the foll links to start learning ABAP.
http://help.sap.com/
http://www.sapgenie.com/abap/
http://www.sappoint.com/abap.html
http://cma.zdnet.com/book/abap/index.htm
http://www.sap-img.com
http://www.sappoint.com
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://sap.ittoolbox.com
Please visit this link. I hope this will help you a lot.
LINK : http://sapabap.iespana.es/sapabap/manuales/learnabap/
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
https://www.sdn.sap.com/irj/sdn/developerareas/abap
Pls reward appropriate points.

Can we make ABAP program as executable file

Hi All,
I have query related to abap program.
Can we make ABAP program as .exe file or .bat file..
If yes then what is the procedure to do the same.
I would really appreciate if anyone can suggest something on this.
Regards
Prabhat

No you can not. Why? Because ABAP is a proprietary language developed by SAP which only runs in the ABAP runtime environment.
Regards,
Rich Heilman
PS.
Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.
Spread the wor(l)d!
Message was edited by: Rich Heilman

How can i get access code to create ABAP Program ?

hi guys ,
How can i get access code for creating ABAP Program in my System.
I am using SAP IDES 4.6 Version
Please Help me out .
Regards
Raghu

Hi Raghu,
- license your system (http://service.sap.com/licensekey)
- create a developer key (http://service.sap.com/sscr)
- create a key for your ABAP program (httP://service.sap.com/sscr)
Markus

Backup ABAP Programs

Hi Everyone,
I need your help.
I am working on a tool that can backup the ABAP source codes and tables.
I am using the READ REPORT to get the source code and store the result in a text file,
my question is, if I want to give this tool to a client , what kind of authorization a user need to be able
to run the tool and backup all the ABAP programs of the SAP system ?
Can any ABAP developer use the "READ REPORT" and read the source code written by
other ABAP developer ?
Thanks

REPORT zdownload.
TABLES: trdir.
SELECT-OPTIONS name FOR trdir-name NO INTERVALS.
PARAMETERS: path TYPE c LENGTH 50 DEFAULT 'C:\USERS\SCHWAB\PROGRAMS'.
START-OF-SELECTION.
LOOP AT name.
 PERFORM download_program USING name-low.
ENDLOOP.
FORM download_program
FORM download_program USING value(i_name) LIKE trdir-name.
DATA: BEGIN OF lt_data_tab OCCURS 0,
 line(72),
 END OF lt_data_tab,
 l_filename TYPE string.
CONCATENATE path '\' i_name '.TXT' INTO l_filename.
READ REPORT i_name INTO lt_data_tab.
IF lines( lt_data_tab ) = 0.
 MESSAGE e001(uc) WITH TEXT-TK0.
ENDIF.
CALL METHOD cl_gui_frontend_services=>gui_download
 EXPORTING
 filename = l_filename
 CHANGING
 data_tab = lt_data_tab[]
 EXCEPTIONS
 OTHERS = 0.
IF sy-subrc <> 0.
 MESSAGE e001(uc) WITH TEXT-K01.
ENDIF.
ENDFORM. "download_program
AT SELECTION-SCREEN ON name.
check name-low <> space.
SELECT SINGLE * FROM trdir WHERE name = name-low.
IF sy-subrc <> 0.
 MESSAGE e001(uc) WITH TEXT-K02.
ENDIF.

How to Lock ABAP Program

Hi all,
I am using a module pool program,
I want to ristrict the access of program to single user at a time.
can some one give me some clues about program locks.
Regards,
Gaurav Sood.

Hi
Locking All Users
Sometimes it is useful to be able to lock all the users out of a client; for instance, during a client copy (you can also do this with tp locksys, but you have to issue that command from the OS level, and then you can only use DDIC or SAP* to log on). You can use this program to lock out all users except yourself.
This program (un)locks all the users in a client, except for the current user, and the SAP* user. You might want to add somthing like SELECT-OPTIONS EXEMPTUS FOR USR02-BNAME to allow a list of usernames not to be processed.
Un/Lock all users in a client
*& Report YUSRLOCK *
REPORT YUSRLOCK MESSAGE-ID Z1 .
TABLES: USR02.
PARAMETERS: LOCK AS CHECKBOX, LISTLOCK AS CHECKBOX.
DATA: UFLAGVAL TYPE I, LOCKSTRING(8) TYPE C.
---- Authorization check -
AUTHORITY-CHECK OBJECT 'ZPROG_RUN' ID 'PROGRAM' FIELD SY-CPROG.
IF SY-SUBRC <> 0.
IF SY-SUBRC = 4.
MESSAGE E000 WITH SY-CPROG. "some message about authorization check failure
ELSE.
MESSAGE E005 WITH SY-SUBRC. "some message about authorization check failure
ENDIF.
ENDIF.
IF LISTLOCK = 'X'.
WRITE:/ 'List all locked users: '.
SELECT * FROM USR02 WHERE UFLAG = 64.
WRITE: / USR02-BNAME.
ENDSELECT.
EXIT.
ENDIF.
IF LOCK = 'X'.
UFLAGVAL = 64. "lock all users
LOCKSTRING = 'locked'.
ELSE.
UFLAGVAL = 0. "unlock all users
LOCKSTRING = 'unlocked'.
ENDIF.
SELECT * FROM USR02 WHERE BNAME <> 'SAP*' AND BNAME <> SY-UNAME.
IF USR02-UFLAG <> 0 AND USR02-UFLAG <> 64.
WRITE: 'User', USR02-BNAME, 'untouched; please handle manually.'.
CONTINUE.
ENDIF.
check that user has authority to make these changes
AUTHORITY-CHECK OBJECT 'S_USER_GRP'
ID 'CLASS' FIELD USR02-CLASS
ID 'ACTVT' FIELD '05'.
IF SY-SUBRC <> 0.
IF SY-SUBRC = 4.
WRITE: /'You are not authorized to lock/unlock user ',
USR02-BNAME, USR02-CLASS.
ELSE.
WRITE: /'Authorization error checking user ',
USR02-BNAME, USR02-CLASS, '(return code', SY-SUBRC, ').'.
ENDIF.
ELSE. "has authority
UPDATE USR02 SET UFLAG = UFLAGVAL WHERE BNAME = USR02-BNAME.
WRITE: / 'User', USR02-BNAME, LOCKSTRING, '.'.
ENDIF.
The SAP Lock Concept
Reasons for Setting Locks
Suppose a travel agent want to book a flight. The customer wants to fly to a particular city with a certain airline on a certain day. The booking must only be possible if there are still free places on the flight. To avoid the possibility of overbooking, the database entry corresponding to the flight must be locked against access from other transactions. This ensures that one user can find out the number of free places, make the booking, and change the number of free places without the data being changed in the meantime by another transaction.
Lock Mechanisms in the Database System
The database system automatically sets database locks when it receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program. Database locks are physical locks on the database entries affected by these statements. You can only set a lock for an existing database entry, since the lock mechanism uses a lock flag in the entry. These flags are automatically deleted in each database commit. Database locks are therefore never available longer than for only one database LUW. That means that in ABAP application programming, database locks can no longer exist than the duration of one dialog step.
The physical lock mechanisms in the database system are therefore insufficient for the requirements of an ABAP transaction. The locks must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and even different application servers. Consequently, each lock must not only apply on the application server that carries out the locking transaction, but on all installed servers of the SAP Web AS ABAP.
SAP Locks
To complement the SAP LUW concept, in which bundled database changes are made in a single database LUW, the SAP System also contains a lock mechanism, fully independent of database locks, that allows you to set a lock that spans several dialog steps. These locks are known as SAP locks.
The complete documentation on SAP locks can be found in The SAP Lock Concept. This is a short introduction within the environment of ABAP programming.
The SAP lock concept is based on lock objects. Lock objects allow you to set SAP locks for entire application objects. An application object consists of one or more entries in a database table, or entries from more than one database table that are linked using foreign key relationships.
Before you can set an SAP lock in an ABAP program, you must first create a lock object in the ABAP Dictionary. A lock object definition contains the database tables and their key fields on the basis of which you want to set a lock. When you create a lock object, the system automatically generates two function modules with the names ENQUEUE_Name and DEQUEUE_Name. You can then set and release SAP locks in your ABAP program by calling these function modules in a CALL FUNCTION statemenT.
Reward If Helpfull,
Naresh.

Migration of SAP From Windows to AIX

Gurus
I need information regrading migration of SAP ECC 6.0 on Oracle from Windows to AIX.
Thanks

Hi ,
You will find information in the System Copy Guide .
https://websmp104.sap-ag.de/instguidesNW70
SAP NetWeaver 7.0 (2004s) --> Installation ---> <download the suitable system copy guide>
You would also find lot of SAP Notes , go through them and let us know if you have any specific questions/concern.
Regards,
Neel

SAP PI FTP sender adapter not working with SAP ECC over Itanium

Hi,
We have been running normally SAP PI 7.0 SP14 with no issue for a while.
We are now in the process of migrate the SAP ECC system from PA risc to IA platform. We are performing some tests between SAP PI and SAP ECC to check that the platform migration is not affecting us in any way and we have found that FTP adapter sender is not working anymore (receiver is working as usual).
We place some files in the new ECC system and when PI goes to retreive the files it is like it can not read anything. It gives no error but it does not pick any file. This is not happening with the old platform.
Does anyone have any idea?
Thanks a lot for your help
Diana

Hi,
I am using FTP connection and for the receiver it is working fine.
Thanks
Diana

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
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 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
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 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Reg: An ABAP program has to run two SAP Queries via BG to Appl. server

Hi,
I have a requirement to develop an ABAP program to be able to run the two Z Queries respectively and be able to download to the file to the application server via background.
The selection is based on the Query Name, Usergroup and plant.How do we capture the data from the Queries and send it to the application server? Submit Statement is not working. There is a FM: RSAQ_REPORT_NAME from which we get the Query program name when Qery name and User group is given as an input.Through the above FM I have got the Query program name and used Submit statement with List_options to capture the Internal table data of that Query. As the Query program is dynamically generated and not available in TSTC, the Submit is not Working. Kindly suggest me is there any other approach to do it.
Please provide me the solution.
Thanks in advance.

Please refer to thread [Authorization Error|WDA adobe error] where various solution to the problem specified by you are described.
Regards
Rohit Chowdhary
Edited by: Rohit Chowdhary on Apr 7, 2009 9:41 PM

Queries related to ABAP Programs migration to SAP ECC 6.0

Similar Messages

Maybe you are looking for