Error in pharse XPRAS_UPG
Hello,
I got an error in phase XPRAS_UPG. i paste the log LONGPOST.LOG :
UPGRADEPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR700WG4.R46" <
Long text:
Cause
During the upgrade, a message relevant for postprocessing was written
to a log file. This message is not dealt with until the end of the
entire upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the
original log file, this message is generated by R3up.
What to do
Note the messages following this message and proceed according to the
instructions.
A2PESEEF_BADI 152 CMOD " " for SMOD "V56LDELI" has yet to be migrated
Long text:
Cause
Migrate CMOD implementation " " using transaction SPAU
System Response
What to do
To migrate the CMOD implementation to a new BAdI, you must call up
transaction SPAU, and then select "Migration Objects" under the tab
"Modifications".
You will find your SMOD implementation under Migration Objects -> SAP
Enhancements. To start the migration, select your CMOD implementation by
clicking on it.
Tasks for system administration
1PEPU203X> Messages extracted from log file "SAPR700ZG1.R46" <
Long text: see above
A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
Thanks,
Roy
Hi Roy,
Its is usaully done by the ABAP team.
The modifications or changes will be done by the ABAPer.
You will be able to see this customer exit in SMOD transaction.
1.go to SMOD, Enter V56LDELI enhancement name
2. click components
3. Click display button
4. In the function module exits heading you will be able to the function module EXIT_SAPLV56L_002 specified there.
5. Double click on it, so that the function module code will be opened.
6. In the last but before line of the function module EXIT_SAPLV56L_002 code you will see an line INCLUDE ZXV56U25.
7. Double click on include name ZXV56U25.
8. If you have find any code in this include then you need to migrate this customer exit to BAdi.
9. If suppose it is asking for you to create the include for the first time, then you can skip the step of migrating this BAdi.
If you not using this Badi, then you can go ahead with your upgarde by selecting continue and revision completed.
Do it with the help of your ABAP consultant.
regards,
chandru.
Similar Messages
-
Upgrade with XPRA ERRORS message at xpras_upg
Hi,all
I am upgrading sap ERP 4.72 (win2Ksql2K_sp3) to ECC6(win2003sql2K+sp4). Prepare is sucess.When the upgrade process is running xpras_upg,I got error message below.
XPRA ERRORS and RETURN CODE in SAPR700ZE1.PRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A2EESMMSS_ANALYZE 000 SQL error "446": "Cannot resolve collation conflict for concatenatio" "n operation." " "
2EEPU133 Errors occurred during post-handling "MSS_SDBP_AFTER_IMP" for "SDBP" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly
before this message. First read these error messages and the respective
long texts. You will find further information there on correcting the
errors.
If this information is not sufficient, look for error notes in the
SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-DB-MSS" ("Microsoft SQL Server")
Long text:
Cause
During the upgrade or import of a transport request, errors occurred in
the component
"BC-DB-MSS" ("Microsoft SQL Server").
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I have searched in sap notes and SDN,but no help to me.
Can give me solution?
Thanks a lot.Sorry,I have solved this problem.
The version of my sql is sql2k with sp3 before,but sp3 only support CP850_BIN. After sp3,microsoft support CP850_BIN2 and BIN.
The default installation of the sql2k sp4 software from sap is supported CP850_BIN2 .
So,the versionof the sql server is BIN,and database is BIN in my ERP 4.72. Then I install sql2k with sp4 with BIN2,and database is BIN.
I must change the BIN&BIN2 with instcoll.exe.
More information,please read note 505906,600027.
Thanks.
Wensent Lee -
XPRAS_UPG Error Messages
Dear All,
While performing an upgrade from 4.6c to ECC6.0. I have received 10 errors in the XPRAS_UPG Phases.
As per the upgrade guide I following to find the name of the error messages
as SAPK700ZG2 and checked the error message in SE09.
Transport Logs:
5 SAPK700ZG2 Rel. 700 AFTER_IMP objects: SOBJ/PDWS
5 DV2 DV2 - HPUX System
Import 12/17/2007 19:55:20 (0) Successfully Completed
5 Method Execution 12/17/2007 21:28:56 (8) Ended with errors
12/17/2007 20:43:05 (8) Ended with errors
12/17/2007 21:28:56 (8) Ended with errors
4 Import steps not specific to transport request
When I clicked on the long text for the above error message it gives the general help.
Execution of programs after import (XPRA)
Transport request : SAPK700ZG2
System : DV2
tp path : /usr/sap/DV2/SYS/exe/run/tp
Version and release: 372.03.35 700
Execution of programs after import (XPRA)
End date and time : 20071217212856
Ended with return code: ===> 8 <===
Can anyone help to solve this issue.
I am enclosing the error file XPRASUPG.ELG:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG2.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEOL555 Object type '"BUS20370"' could not be generated
Long text:
Cause
The object type could not be activated.
What to do
Select the function 'Check' in the object type and correct the error
found. Then try to activate the object type again.
2EEOL555 Object type '"BUS20350"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20300"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20360"' could not be generated
Long text: see above
2EEPU133 Errors occurred during post-handling "SWO_OBJTYPE_AFTER_IMPORT" for "SOBJ" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly
before this message. First read these error messages and the respective
long texts. You will find further information there on correcting the
errors.
If this information is not sufficient, look for error notes in the
SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-DWB-TOO-BOB" ("Business Object Builder")
Long text:
Cause
During the upgrade or import of a transport request, errors occurred in
the component
the component
&V#& (&V#&).
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INFICA.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPRGPGD07.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INISUT.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007ININSURANC.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INFICAX.DV2
so on.
The error message doesn't give enough information neither the upgrade guide. Can anyone help me to overcome this error.
Thanks & Regards
SenthilThe basic problem here is that the affected SWO1 objects depend on an Enhancement Spot containing a type group which is in-active and therefore not available for generation from SWO1.
You have to activate the type group concerned.
The following process should achieve activation of the SWO1 objects:
1. TCODE: SE18
Display PLM_AUDIT_LIST_ITEM in enhancement spot.
Activate this object.
2. TCODE SE80
Package: PLM_AUDIT
Find the PLM_BUS203* function groups and activate them. (same as generating from SWO1)
You might want to try step 2 first, and only activate the object in step 1 if Step 2 fails.
Hope this helps others who will prefer to fix rather than ignore this error.
Best Regards
Andre Rainsford-Alberts -
Urgently Upgrade Stop In XPRAS_UPG Phase
Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
<b>Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:</b>
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
Remaining change request found in buffer TVD.
Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
<b>XPRASUPG.ECO and R3up.ECO</b>
the problem is with the <b>RDDEXECL</b> JOB. Which is in the status <b>CANCELED</b>
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
<b>Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
</b>
The conversion of some code pages is not supported.
<b>What happened? </b>
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
<b> 'CX_SY_CODEPAGE_CONVERTER_INIT'</b>, was neither
caught nor passed along using a RAISING clause, in the procedure <b>"READ_TEXTLINES" "(FORM)"</b>.
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
<b>We saw this note:</b>
<b>122597</b> Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
<b>676135</b> Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
<b>This are the logs:</b>
<b>XPRASUPG.ECO</b>
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
<b>R3up.ECO:</b>
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree CardenasHi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
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.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
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_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
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
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas -
XPRA_EXECTION MSS_SDBP_AFTER_IMP for SDBP L Error
Hello everybody,
I'm trying to implement these patches in our DEV ERP system. The import process stopped at phase XPRA_EXECUTION with this message:
The following details help you to analyze the problem:
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPKB70030, tp step "R", return code
0008
In the Action and Import Logs can be found this records:
This is the error on the log:
2 EPU122XPost-import method "MSS_SDBP_AFTER_IMP" started for "SDBP" "L", date and time: "20140307103739"
4 E0Q045 Starting processing of SQL scripts (R3TR SDBP)...
4 E0Q043 SQL script "sap_dbcoll" " " " " being executed
4 E0Q043 SQL script "sap_get_table_size_info" "9.0" "A" being executed
4 E0Q041 SQL script "sap_get_table_size_info" "A.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_get_table_size_info" "B.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_get_table_size_info" "C.0" "A" will be ignored (incorrect release)
4 E0Q043 SQL script "sap_mon_sqlsetup" "9.0" "A" being executed
4 E0Q041 SQL script "sap_mon_sqlsetup" "A.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_mon_sqlsetup" "B.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_mon_sqlsetup" "C.0" "A" will be ignored (incorrect release)
4 E0Q043 SQL script "sap_p_snapshot" "9.0" "A" being executed
4 E0Q041 SQL script "sap_p_snapshot" "A.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_p_snapshot" "B.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_p_snapshot" "C.0" "A" will be ignored (incorrect release)
4 E0Q042 Deletion request for SQL script "sap_tabstats" " " " "
4 E0Q041 SQL script "sap_tabstats" "8.0" "A" will be ignored (incorrect release)
4 E0Q043 SQL script "sap_tabstats" "9.0" "A" being executed
A2EESMMSS_ANALYZE 000 SQL error "156": "'object_schema_name' is not a recognized built-in" "function name.Incorrect syntax near the keyword 'A" "S'.Incor
4 E0Q041 SQL script "sap_tabstats" "A.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_tabstats" "B.0" "A" will be ignored (incorrect release)
4 E0Q041 SQL script "sap_tabstats" "C.0" "A" will be ignored (incorrect release)
3 E0Q044 SQL scripts executed / deleted / ignored: "5" / "1" / "13"
2EEPU133 Errors occurred during post-handling "MSS_SDBP_AFTER_IMP" for "SDBP" "L"
3 EPU135 "MSS_SDBP_AFTER_IMP" belongs to package "SMSS_TOOLS"
2EEPU136 The errors affect the following components:
2EEPU137 "BC-DB-MSS" ("Microsoft SQL Server")
3 EPU123 Post-import method "MSS_SDBP_AFTER_IMP" completed for "SDBP" "L", date and time: "20140307103748"
any idea?
thanks in advance,
CarlosHi Deepak,
I have seen this notes:
738950 SPAM error in "Method Execution" on Microsoft SQL Server
1719979 SPAM/SUM: SQL error 208: Invalid object name 'sap_get_para'
928915 DB privileges lacking when applying support package
769842 SQL errors occur in XPRAS_UPG phase
1832133 * SQL Server 2000: Importing SAPKB70028 fails with "SQL Error 170 Line 1 Incorrec
1045797 Upgrade error in phase XPRAS_UPG
1131766 Error in XPRA on sap_tabstats_job_update
927614 MSSQL : Empty log entries in MSSPROCS / "Start all"
but i dont find the solution.
any idea?
thanks -
SAINT import of TU/SPS gets error 207 Invalid Column name 'area'
Hi,
I have installed a EHP5 ECC 6 system, Windows 2008 SQLServer 2008R2. Have used SolMan MaintOpz to download the additional Technical Usages (TU) like HCM and SPS to be imported into the system using transaction SAINT.
I am using the stack.xml file for the Saint import.
IMPORT phase have completed, but now I am getting an SQL error 207 duing the XPRA_EXECUTION phase when doing method execution. This stops the SAINT import and when I click on Continue button i will et the same error and SAINT will stop again.
The error is for the support package SAPKB70204 Basis Support Package 04 for 7.02.
The return code for method execution is RC 8.
When I check the log file, the errors are
SQL Error 207 Invalid colun name 'area'
Errors occurred during post-handling MSS_SDBP_AFTER_IMP for SDBP L
The error affects the following components: BC-DB-MSS
Further analysis find that it is trying to run a SQL script and the script fails due to the above error.
I read the script, it contains statements to create a table with a field name 'area' and select statements to this table.
I have tried patching the SAPEXE and SAPEXEDB kernels to the latest but still the same error. Already on the latest kernel level and dbmssslib.dll and tp and r3load and r3trans files due to the patch.
Without fixing this error, my SAINT import will never complete and I will not have a functioning ERP system. The entire team is waiting for me so plese can anyone help me? I am desperate.
Thank you for any advise or help.Check
Note 769842 - SQL errors occur in XPRAS_UPG phase
Markus -
升级到ECC6过程中,XPRAS_UPG出现错误
环境是WIN2003 X64 + SQL 2005 X64, SAP 46C 61补丁,升级到ECC 6 .,我的SID:C11 ( SAP- APPLICATION + DATABASE:SQL2005同一机器上 )
问题如何解决?
前面一切都是正常的,提示这个错误:
============================================================
ERROR: 6 ERRORS detected during XPRAS_UPG.
Analyze summary error logfile XPRASUPG.ELG
and remove all error conditions in the way
it is described in the upgrade manual. Repeat
this phase until it is error free.
Additional hints may be given in logfiles
SLOG700 and F:\usr\sap\put\log\R3up.ECO
============================================================
错误日志XPRASUPG.ELG:
============================================================
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700WG3.C11
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EENR397FThe subobject value table "TFK_NUMGR_IT" contains invalid key fields
2EENR893INumber range object "FKKEXBL_IT" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB" for "NROB" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly
before this message. First read these error messages and the respective
long texts. You will find further information there on correcting the
errors.
If this information is not sufficient, look for error notes in the
SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text:
Cause
During the upgrade or import of a transport request, errors occurred in
the component
&V#& (&V#&).
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
====================================================================
Edited by: mo ziyou on Dec 24, 2010 1:23 PM -
XPRAS_UPG error in DOWNTIME phase in EHP4
Hi,
I am getting the below error in XPRAS_UPG in DOWNTIME phase of EHP4 installation in ERP 6.0 on HP-UNIX and Oracle.
XPRA ERRORS and RETURN CODE in SAPRW70104.HD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10302400")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""10302400""HD1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I was successfully able to umlock the system and in SM37 I could see the job log pointing to ST22. In ST22 we have many dumps related to error PXA_NO_FREE_SPACE. I found many notes in marketplace but all are referring the parameter abap/buffersize which needs to increased. I am a bit apprehensive about the fact that since we are in DOWNTIME phase and in the middle of XPRA execution phase should we increase the parameter and restart the system and then continue with the upgrade???
I have also tried to run the phase many times but the same error persists.
Please can anyone help me to come out of this problem.....
Thanks & regards,
RozalHello Rozal,
You are correct XPRAS is a downtime 2 phase, but actually your system is up and running. It was started way back in phase "STARTSAP_NBAS" its just that you cannot use your system productively. XPRAS executes the XPRAS methods in the running system.
Its absolutely safe, you can change the parameter take a restart and continue further.
- Niraj -
XPRAS_UPG error. Do ABAPers fix these?
Experts,
The XPRAS_UPG phase is failing, because the program SAPLSDHI has syntax error in with SHLP_DESCR_TAB_T type missing or not defined. I checked all the underlying data types that define SHLP_DESCR_TAB_T and all are OK. What could possibly be the cause? Did anyone come across a similar situation? BTW, I am upgrading from 4.0B to ECC 6.0.
Do ABAPers enter the scene in this phase to fix errors?
Thanks in advance. Points will be gratefully awarded.
Edited by: NW on May 19, 2008 8:49 AMHi Raj,
for problems during XPRASS_UPG or any other phase refer to the upgrade manual according to the source and target release
this will give you notes that contains solution to general errors such as this
Thanks and Regards
Abdul Hadi -
Upgrade From 46B to ECC6 SR3 - XPRAS_UPG errors
Hello,
I ugrade a system from 46B to ECC6 SR3.
Windows 2003 SP1 32bits / MSSQL 2000 SP4.
During the XPRAS_UPG phase, i have an error in the post-import method RS_SHIP_AFTER_IMPORT for the transport SAPK700ZH1.
The log is the RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxx were synchronized
Incorrect input for activating transported shadow IPacks
Job cancelled after system exception ERROR_MESSAGE
Have you already encountered this problem?
Thanks,
AlexandreThe problem is solved.
It was due to an empty entry in table rsbasidoc.
Alex -
Hi;
We are trying to uprade from 4.6C to EHP4 SR1. When we are in XPRAS_UPG
phase, upgrade gives the errors below:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-603DWINEAAPPL.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397CThe subobject value table "TCACS_APPLDEF" contains invalid key
fields
2EENR893INumber range object "CRD_AS_ID" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly before this message. First read these error messages and the
respective
long texts. You will find further information there on correcting
the
errors.
If this information is not sufficient, look for error notes in the SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message
number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors
occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text:
Cause
During the upgrade or import of a transport request, errors
occurred in
the component
&V#& (&V#&).
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-604DWINEAAPPL.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397CThe subobject value table "TCACS_APPLDEF" contains invalid key
fields
2EENR893INumber range object "CRD_AS_ID" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-604DWINSAPHR.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397HThe subobject value table "T591A" contains invalid key fields
2EENR893INumber range object "HR_ZA_LABR" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR701WG3.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397FThe subobject value table "TFK_NUMGR_IT" contains invalid key
fields
2EENR893INumber range object "FKKEXBL_IT" " "
2EENR397HThe subobject value table "T591A" contains invalid key fields
2EENR893INumber range object "HR_ZA_LABR" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
Best regards
NoyanHello Noyan,
Please refer to note '1484591 - NK: Error message NR 397 after import'
and check whether it helps you.
Please apply the note 1484591 manually
as it is not possible to use SNOTE during upgrade.
Make sure the Req. Corr. Instructions from note
'1467470 - NR: Check of subobject value table'
are also implemented if not done yet.
In order to apply the note manually (as SNOTE is blocked due to the
upgrade), you need to unlock the system:
1. In order to unlock the system, you must execute these commands:
/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/
abap/bin/DEFAULT.TPP unlocksys <SID>
/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/
abap/bin/DEFAULT.TPP unlock_eu <SID>
2. Now you should be able to logon into the system with a user
different from DDIC.
3. Apply the note's changes manually. Please take into account the
note's prerequisites' corrections from note 1467470 have to be
applied also.
4. Lock the system with the following commands:
tp locksys <SAPSID> pf=<transport profile>
tp lock_eu <SAPSID> pf=<transport profile>
5. Repeat the failing phase.
Regards,
Paul -
Error in XPRAS_UPG Phase for report RSR_VARIANT_XPRA
Upgrade from 4.6C to SAP ERP 2005 SR2 with all support packs
During execution of background job for RSR_VARIANT_XPRA, TP terminates with exit code "12" and halts the upgrade process.
On manual execution report throws error message Program class RSR_RECHERCHE does not exist. The TRKORR number for this is SAPR700XP4.
Any help on this will be really appreciated. I have tried to set the lock value to 2 /7 but same result.
Regards
Rohit ChowdharyHi,
We've faced the same problem during upgrade to ECC6.0.
Since i've read your message (I couldn't find out which was the program), debugging RSR_VARIANT_XPRA i've found there's a missing entry in table RSSGTPCLAT. If you included it the phase runs again.
The fields are:
PROGCLASS: RSR_RECHERCHE
CLIDEP: (blank)
GENFLAG: X
SUBC : 1
TEMPLATE : RSRDUMMY
TITLE :
Hope this help you.
Regards. -
Error in XPRAS_UPG phase on SCPR_FLDV_TAB
Hi,
Has anyone experienced this error before when upgrading to ECC 6.0?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZDA.FR1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "00273700")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
etc.etc.
When I then go to SM37 to look at the job log i find an ABAP syntax error message that generated a short dump:
Runtime error SYNTAX_ERROR
Datum en tijd 16.11.2007 00:24:27
Korte tekst
Syntaxfehler im Programm "%_CSCPR ".
Wat is er gebeurd?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Im Programm "%_CSCPR " ist im Include "%_CSCPR " in Zeile 17
der folgende Syntaxfehler aufgetreten:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary control structure introduced with "CLASS" . . . . . ."
| Autor und letzter Änderer des Includes sind:
Autor "SAP "
| Letzter Änderer "SAP "
So for some reason this type SCPR_FLDV_TAB is defined in two places and SAPup won't allow me to ignore it.
I have opened a message with SAP on this problem as well, but this system is due to go live on Monday so any help that would speed up the resolution process will be very much appreciated.
Kind Regards,
SanderHi ,
Please refer to note 122597 and 816057 i request you to check the job logs in sm37 as well.
Regards,
iqbal -
Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative
Hi Gurus,
am upgrading from ecc 6.0 to ehp5 on dual stack system OS:Windows 2003 DB:oracle 10.2.0.2
i got below error in the MAIN_NEWBAS/XPRAS_UPG phase
XPRASUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-500AGINCPRXRPM.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14152200")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""14152200""IJE"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server admin0001 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
Dump at ST22:
Error analysis
The following syntax error was found in the program
CL_DPR_TASK_O=================CP :
"Formal parameter "IV_PLANSTART" does not exist."
please help me solve
Thanks,
VenkatHi Sunny,
here is dump details..
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_DPR_TASK_O=================CP
Application Component PPM-PRO-STR
Date and Time 06.12.2011 16:34:41
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transaction ID...... "04FA1FE12F6DF16DB7E400145E69764F"
EPP Whole Context ID.... 34454438393637453445443839363745
EPP Connection ID....... 34454442374143323445444237414332
EPP Caller Counter...... 1
Program............. "CL_DPR_STATUS_CHANGE_OBSERVER=CP"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_DPR_TASK_O=================CP " in include
"CL_DPR_TASK_O=================CM021 " in
line 74:
"Formal parameter "IV_PLANSTART" does not exist."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program
CL_DPR_TASK_O=================CP :
"Formal parameter "IV_PLANSTART" does not exist."
Information on where terminated
Termination occurred in the ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" -
in "SET_HANDLER".
The main program was "R_DPR_PROJECT_ROLES_XPRA ".
In the source code you have the termination point in line 12
of the (Include) program "CL_DPR_STATUS_CHANGE_OBSERVER=CM00A".
The program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Thanks in advance
Venkat -
XPRA_UPG ERRORS UPGRADING TO ECC6
Hello Gurus
i am getting some errors during XPRAS_UPG.Ugrading from 4.7 to ECC6sr2 on Win2k3 64,SQL2005
I have checked R3up.ECO logs entries:
STARTSAP continues...
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 9616 terminated with status 12
Deleting file c:\usr\sap\put\log\XPRASUPG.ELG
Moving file c:\usr\sap\put\log\PROT.TMP to c:\usr\sap\put\log\SAPR700ZEA.NTP
Moving file c:\usr\sap\put\log\XPRASUPG.ELG to c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\tmp\MSGIN.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LST
Deleting file c:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file c:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file c:\usr\sap\put\log\TP.ECO
Deleting file c:\usr\sap\put\bin\TRLIST.DMP
Deleting file c:\usr\sap\put\tmp\upalert.log
Deleting file c:\usr\sap\put\tmp\upalert.log
Copying file c:\usr\sap\put\buffer\NDP to c:\usr\sap\put\buffer\AFTXPRAS.BUF
Then i checked ACTUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG700.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG701.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG702.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAD70024.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60008.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60009.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60010.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60011.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60012.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60013.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60014.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPAE60015.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "4"
and
XPRASUPG.ELG:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZEA.NDP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "16371300")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""16371300""NTP"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I tried to execute the job RDDEXECL as DDIC in client 000 and it doesn`t run it quickly cancels with an ABAP dump SYNTAX_ERROR.I checked notes 980194,905029,821032,813658
So i went and checked in SE09 ,request/task,display individually,the transport logs
c:\usr\sap\put\log\*SAPLA70010.NDP* and discovered what might be the source of the problem:in SAPKA70010
different nametabs for table SEOCLASSDF (field CLSSHAREDMEMORY).
different nametabs for table SEOCLASSDF (field WITH_UNIT_TESTS).
different nametabs for table SEOCLASSDF (field DURATION_TYPE).
different nametabs for table SEOCLASSDF (field RISK_LEVEL).
in all the listed transport requests/support packs by ACTUPG.ELG log so how do i fix this problem in order to finish the upgrade?
Any ideas are most welcomeHi Attached is the dump:
Runtime Errors SYNTAX_ERROR
Date and Time 19.04.2008 16:47:26
Short text
Syntax error in program "%_CSCPR ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "%_CSCPR " in include "%_CSCPR "
in
line 17:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "%_CSCPR ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program %_CSCPR :
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary . control structure introduced with "CLASS" . . . . ."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "BDX1-sap02"
Network address...... "10.50.74.207"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "BDX1-SAP02"
Database type..... "MSSQL"
Database name..... "NDP"
Database user ID.. "ndp"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Feb 3 2008 22:36:38"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 146
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16128
EM...... 29329328
Heap.... 0
Page.... 32768
MM Used. 12958608
MM Free. 3797776
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "E384EEDB5E10F1EC892B001A64C1074E"
Program............. "SAPLSCPRPR"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSCPRPR" - in
"SCPR_DB_ATTR_GET_LIST".
The main program was "RDDEXECU ".
In the source code you have the termination point in line 1
of the (Include) program "LSCPRPRU17".
The program "SAPLSCPRPR" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 16472600
Source Code Extract
Line
SourceCde
>>>>>
FUNCTION SCPR_DB_ATTR_GET_LIST.
2
3
""Lokale Schnittstelle:
4
*" IMPORTING
5
*" VALUE(CATEGORY) TYPE SCPRATTR-CATEGORY DEFAULT SPACE
6
*" VALUE(COMPONENT) TYPE SCPRATTR-COMPONENT OPTIONAL
7
*" VALUE(RELEASE) TYPE SCPRATTR-MAXRELEASE OPTIONAL
8
*" VALUE(MAX_COUNT) TYPE I OPTIONAL
9
*" EXPORTING
10
*" REFERENCE(SEL_COUNT) TYPE I
11
*" TABLES
12
*" PROFS STRUCTURE SCPRXPROF OPTIONAL
13
*" VERSIONS STRUCTURE SCPRXVERS OPTIONAL
14
*" PROFTYPES TYPE SCPR_XPTYPES OPTIONAL
15
*" CLI_DEPS STRUCTURE SCPRXCLDEP OPTIONAL
16
*" CLI_CASS STRUCTURE SCPRXCLCAS OPTIONAL
17
*" REFTYPES STRUCTURE SCPRXRTYPE OPTIONAL
18
*" REFERENCES STRUCTURE SCPRXREF OPTIONAL
19
*" MODDATES STRUCTURE SCPRXDAT OPTIONAL
20
*" MODIFIERS STRUCTURE SCPRXMOD OPTIONAL
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
2
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
CORR
SY-MSGV2
MERG
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080419
SY-UZEIT
164726
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
7 FUNCTION SAPLSCPRPR LSCPRPRU17 1
SCPR_DB_ATTR_GET_LIST
6 FUNCTION SAPLSCPRPR LSCPRPRU19 60
SCPR_DB_ATTR_GET_ADDITIONAL
5 FUNCTION SAPLSCPRCRITICAL ??? 0
SCPR_SCP2_AFTER_IMPORT
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 342
CALL_IMP_METHODS_IN_CLIENT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 168
START-OF-SELECTION
Chosen variables
Name
Val.
No. 7 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_LIST
CATEGORY
S
5
3
COMPONENT
222222222222222222222222222222
000000000000000000000000000000
MAX_COUNT
0
0000
0000
RELEASE
2222222222
0000000000
SEL_COUNT
0
0000
0000
CLI_CASS[]
Table[initial]
CLI_DEPS[]
Table[initial]
MODDATES[]
Table[initial]
MODIFIERS[]
Table[initial]
ORGIDS[]
Table[initial]
PROFOUT[]
PROFS[]
PROFTYPES[]
REFERENCES[]
REFTYPES[]
VERSIONS[]
CONTEXT_CLASSIC
2
0
CF_SOL_MANAGER
M
4
D
RTYPE_CUSTREC
CREC
4544
3253
RTYPE_TRANSPORT
TRAN
5544
421E
RTYPE_COPY
COPY
4455
3F09
ACT_DELETE
06
33
06
ACT_SHOW
03
33
03
OTYPE_TABLE
S
5
3
OTYPE_TLOGO
L
4
C
OTYPE_SPECIAL
T
5
4
OTYPE_UNKNOWN
U
5
5
RTYPE_NO_REFTYPE
2222
0000
ACT_MODIFY
02
33
02
OTYPE_VIEW
V
5
6
OTYPE_CLUSTER
C
4
3
ACT_CREATE
01
33
01
COL_BLUE
1
0000
1000
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSCPRPR
5454545555222222222222222222222222222222
310C330202000000000000000000000000000000
ICON_CLI_DEP
@0V@
43542222222222222222
00600000000000000000
CFLAG_ANY
VAL
544
61C
No. 6 Ty. FUNCTION
Name SCPR_DB_ATTR_GET_ADDITIONAL
CATEGORY
S
5
3
READ_ATTR
X
5
8
READ_DOCU
2
0
READ_SWITCH
2
0
READ_TADIR
2
0
READ_TEXT
2
0
REMOVED_BCSETS
Table[initial]
PROFLIST[]
Table IT_44[10683x298]
FUNCTION=SCPR_SCP2_AFTER_IMPORTDATA=BCSETS
Table reference: 27
TABH+ 0(20) = 50C21557FE070000B0C21557FE07000000000000
TABH+ 20(20) = 1B0000002C000000BB2900002A010000FFFFFFFF
TABH+ 40(16) = 04570000080D000010000000C1248001
store = 0x50C21557FE070000
ext1 = 0xB0C21557FE070000
shmId = 0 (0x00000000)
id = 27 (0x1B000000)
label = 44 (0x2C000000)
fill = 10683 (0xBB290000)
leng = 298 (0x2A010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FA6557FE070000
pgHook = 0x70FD6657FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 33 (0x21000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10704 (0xD0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x60176657FE070000
collHook = 0x0000000000000000
ext2 = 0xB0416257FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0xF0C11557FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
SY-SUBRC
0
0000
0000
FC_CANCEL
RW
5522
2700
FC_TAKE_NEW
TAKN
5444
41BE
<%_TABLE_SCPRSATTR>
FC_VALUE_HELP
VHLP
5445
68C0
BCSET_RANGE
IEQV1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
4455354544555455555554555554544544422222222222222222222222222222222
95161F93852F250F0153091F53FE338F45700000000000000000000000000000000
FC_DEL_SUBP
DELS
4445
45C3
%_DUMMY$$
2222
0000
%_ITAB_DELETE_LIST
Table[initial]
<WA_PROFLIST>
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
BCSET_RANGES
Table IT_45[10683x67]
FUNCTION=SCPR_DB_ATTR_GET_ADDITIONALDATA=BCSET_RANGES
Table reference: 28
TABH+ 0(20) = 60436257FE070000000000000000000000000000
TABH+ 20(20) = 1C0000002D000000BB29000043000000FFFFFFFF
TABH+ 40(16) = 045900003011000010000000C1248001
store = 0x60436257FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 28 (0x1C000000)
label = 45 (0x2D000000)
fill = 10683 (0xBB290000)
leng = 67 (0x43000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000068
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40176757FE070000
pgHook = 0x50D89357FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 34 (0x22000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16304 (0xB03F0000)
lineAlloc = 10800 (0x302A0000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
BCSETS_ATTRS
Table[initial]
SYST
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
ICON_CLI_CAS
@0V@
43542222222222222222
00600000000000000000
TCATEGORY_CUSY
CUSY
4555
3539
No. 5 Ty. FUNCTION
Name SCPR_SCP2_AFTER_IMPORT
IT_E071
Table IT_42[10683x180]
FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
Table reference: 26
TABH+ 0(20) = 90EF1457FE07000020444C57FE07000000000000
TABH+ 20(20) = 1A0000002A000000BB290000B4000000FFFFFFFF
TABH+ 40(16) = 044C0000080D000010000000C9248001
store = 0x90EF1457FE070000
ext1 = 0x20444C57FE070000
shmId = 0 (0x00000000)
id = 26 (0x1A000000)
label = 42 (0x2A000000)
fill = 10683 (0xBB290000)
leng = 180 (0xB4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC01B6757FE070000
pgHook = 0x20276757FE070000
idxPtr = 0xD0B58457FE070000
shmTabhSet = 0x0000000000000000
id = 31 (0x1F000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 10736 (0xF0290000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0xD0F75357FE070000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
IT_E071K
Table[initial]
IV_IS_UPGRADE
X
5
8
IV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
IT_CLIENT
Table IT_39[1x4]
FUNCTION=TRINT_CALL_AFTER_IMP_METHODDATA=LS_SPEC_PARS-CLIENTS
Table reference: 18
TABH+ 0(20) = A0B91557FE070000000000000000000000000000
TABH+ 20(20) = 12000000270000000100000004000000FFFFFFFF
TABH+ 40(16) = 044C00002813000019000000C1248001
store = 0xA0B91557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 18 (0x12000000)
label = 39 (0x27000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000077
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x40F75357FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 28 (0x1C000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
<WA_E071>
SAPK700ZEA 010684R3TRSCP2V1_ISHER_REP_PQUSPIQ_US_NSCH_DEG
5454333544222222222233333353555453535454455545555555455555454454442222222222222222222222222222
310B700A5100000000000106842342330261F93852F250F0153091F53FE338F4570000000000000000000000000000
<%_L001>
<%_L001>-PGMID
TTYPE_R3TR
R3TR
5355
2342
SYST-REPID
SAPLSCPRCRITICAL
5454545545454444222222222222222222222222
310C33023294931C000000000000000000000000
<%_L001>-OBJECT
OBJECT_TYPE_SBCSET
SCP2
5453
3302
CONTEXT_CLASSIC
2
0
ACT_STOP_ICON
@3U@
4354
0350
SCPR_AUTHORITY_CHECK
X
5
8
FLD_STATUS_FLD_NM_KEY
FLD_NM_KEY
44454454452222222222
6C4FEDFB590000000000
BCSETS
Table IT_44[10683x298]
BCSET
V1_ISHER_REP_PQUSPIQ_US_NSCH_DEGN00000000000000
5354544555455555554555554544544443333333333333322222222222222222222222222222222222222222222222
61F93852F250F0153091F53FE338F457E0000000000000000000000000000000000000000000000000000000000000
REMOVED_BCSETS
Table[initial]
PCAT_SWITCH
S
5
3
INFO_SEL_REC
4
0000
4000
INFO_NAMESPACE
7
0000
7000
INFO_EQUALIZE
8
0000
8000
INFO_COMMIT
5
0000
5000
INFO_SHOW
6
0000
6000
INFO_SEL_PROFS
9
0000
9000
INFO_COMMIT_SET
10
0000
A000
CFLAG_ANY
VAL
544
61C
T_MESSAGES
Table[initial]
T_MESSAGE
0
3222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SWITCH_BC_SET_ICON
@C1@
4434
0310
LTYPE_FIELD
FLD
4442
6C40
T_MESSAGE-LEVEL
0
3
0
No. 4 Ty. FORM
Name CALL_IMP_METHODS_IN_CLIENT
PS_SPEC_PARS-WITH_ASYNCH_MODE
2
0
SY-XPROG
SAPLSYST
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
PS_METHOD_CALL-METHOD_FB
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
GC_SCP2_AFTER_IMP
SCPR_SCP2_AFTER_IMPORT
545555453544545544545522222222
3302F3302F16452F9D0F2400000000
PS_SPEC_PARS-ASYNCH_MODE
2
0
GC_PARTNRPR_BACK_TO_STNDRD
1A&1B&1H&1I&2I&3R
34234234234234235
11612618619629632
PV_IS_UPGRADE
X
5
8
PS_CLIENT-CLIENT
222
000
GC_GNS_NO_DIFF
/0*/
2322222222
F0AF000000
LT_E071
Table IT_42[10683x180]
GC_GNS_NO_SPECIFIC
2222222222
FAF0000000
LT_E071K
Table[initial]
RELSET
RNO
544
2EF
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
SYST-REPID
SAPLSCTS_EXE_EXP
5454545554545455222222222222222222222222
310C3343F585F580000000000000000000000000
DEVC_PREFIXNS
N
4
E
PS_SPEC_PARS-CLIENTS
Table IT_39[1x4]
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 3 Ty. FORM
Name CALL_IMP_METHODS
PV_TRKORR
SAPK700ZEA
54543335442222222222
310B700A510000000000
PV_NO_WORK_FOUND
2
0
GC_XPRA_COMPLETED
C
4
3
PT_CLIENT
Table IT_21[1x4]
PROGRAM=RDDEXECUDATA=GT_CLIENT
Table reference: 16
TABH+ 0(20) = 00AD1557FE070000000000000000000000000000
TABH+ 20(20) = 10000000150000000100000004000000FFFFFFFF
TABH+ 40(16) = 040000003808000019000000C1248001
store = 0x00AD1557FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 16 (0x10000000)
label = 21 (0x15000000)
fill = 1 (0x01000000)
leng = 4 (0x04000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000027
occu = 25 (0x19000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70AC1557FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 19 (0x13000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 25 (0x19000000)
lineAlloc = 25 (0x19000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LS_CLIENT_H
2222
0000
TTRA
T
5
4
SY
000000000000B200000000000000000000000000000000000000000000000000000000000000200000000000000000
000000001000B900000000000000000000000000100020001000000010000000000000000000A10000000000000000
PV_UPDATE_LOCKFLAG
X
5
8
PV_CTC
2
0
PV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL
AFTER_IMP SCPR_SCP2_AFTER_IMPORT #######È#######É###########ÿÿÿÿ
445455445254555545354454554454552222222220000000C0001000C00010000000FFFF
16452F9D003302F3302F16452F9D0F24000000000000000080007000900060000000FFFF
PV_IS_UPGRADE
X
5
8
PV_TOP_LEVEL
2
3
2
PS_SPEC_PARS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL-CLIDEP
2
0
PS_SPEC_PARS-WITH_CL_RESULTS
X
5
8
%_VIASELSCR
0
4
No. 2 Ty. FUNCTION
Name TRINT_CALL_AFTER_IMP_METHOD
IS_E070
SAPK700ZEA PRSAP SYSTSAPUSER 20080418120004
5454333544222222222255545222222255555455545222223333333333333322222222222222222222
310B700A51000000000002310000000039343105352000002008041812000400000000000000000000
IT_E071
Table IT_15
Maybe you are looking for
-
Problem in using output type for purchase order
Hi experts, I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :- 1) Going to tcode NACE->Selected the row u201CEF Purchase Orderu201D and clicked on u201CProcedures". 2
-
I`m experiencing wierd thing. I have simple scenario using BPM [ async iFlow1 ] -> [ BPM ] -> [ async iFlow2 ] All SI are asynchronous, including one which I call from BPM through Automated Activity. But if I look in the message log of that outgoing
-
Anyone Successfullly installed 7.4.3 on Vista Premium?
I have been resisting the upgrade due to all the posts with problems. I wanted to find out if anyone has been successful in upgrading. I would like to do ringers. thanks!
-
SOAP:14 - Unexpected element
Hi, while trying to consume an external WS from our ECC 6.4 ABAP system, I'm getting the following error message: CODE - SOAP:14 ERRORTEXT - Unexpected element -el=script ns= More detailed information from RFC-Trace: XRFC> INFO 16:41:40: SOAP SESSION
-
Which is better? iPad Smart Cover. Polyurethane or Leather?
Same