on 09-22-2011 7:24 AM
When I start to import the system copy, can I create a database with the different name from the source system? Or I need to follow exactly the same name of the source system? Currently, I encounter this error 'DYNPRO_ITAB_ERROR' when try to login. Below is the error details:
Short text
Error in internal table in screen
What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.
Error analysis
The program "SAPMSYST" has terminated.
The following error occurred (short text of cause of error):
"FX099: Wrong fieldtype for CURSOR. Has to be binary/hex type."
The following elements are affected:
Screen name.............. "SAPMSYST"
Screen number............ 0020
This error is connected to the processing of an internal table with the
field or variable "TC_IUSRACL-CURRENT_LINE", and was triggered within in the
program.
Trigger Location of Runtime Error
Program SAPMSYST
Include SAPMSYST
Row 1.076
Module type (MODULE PBO)
Module Name D020_LOGON_WITH_SNC
Edited by: Swiber SAP on Sep 22, 2011 8:24 AM
Hi,
I've seen this error beign solved as follows:
logon into another system of your landscape and, in SM59, create an RFC connection to the system where you are getting the DYNPRO_ITAB_ERROR short dump. Now connect to that system through the RFC connection that you have created, go
to transaction SE80 and regenerate program SAPMSYST. After that the incidence will be solved.
Hope it helps,
Br,
Javier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, about generating the RFC you can guide from:
http://help.sap.com/saphelp_nw70/helpdata/en/22/04262b488911d189490000e829fbbd/frameset.htm
and the other part is pretty simple, once you are on the system thru the RFC created previously, just get into SE80 and regenerate SAPMSYST program
Br,
Javier
'OS release Windows NT 6.1 7601 Service Pack 1 2x AMD64 Level 6 (Mod 44 Step 2) is not supported with this kernel (700)'
Hello,
It means you need to upgrade SAP kernel patch.
Since the OS level is higher/newer, so it will be supported by higher patch level of kernel (As SAP might have released the correction in later kernel patch levels, for the same sap release).
Thanks
After I finished the import in the target system, I was able to login successfully. However, when I tried to access one transaction code. It is taking a long time compare to the normal system. Below there will show something like "compiling XXXXX in separate task". May I know how to solve this problem?
Yes, you can create a database with the different name from the source system.
Details will depend on your operating system and database.
Follow the system copy guide. You can find it on SAP marketplace.
Please read it carefully, and come back when you have got specific questions.
hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.