Hi Experts,
We are performing EWM system upgrade from 9.1 to 9.3, which is on SCM system with 7.0 EHP3. At XPRA_AIMMRG phase we are facing below error. Kindly help us to solve this.
We have already implemented the SAP Note 2196031 - ASSERTION_FAILED dump during client copy, install or upgrade manually by unlocking the system, but still we are facing the same.
Thanks in advance!!
XPRAUPG error
XPRA ERRORS and RETURN CODE in SAPR740XPRA90000090.E91
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP109 version and release : "380.28.39" "742"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK740XPRA90000090"
4 EPU111 on the application server: "CTSC005113289"
2 EPU122XPost-import method "/SCMB/DF_GENERATE_AFTER_IMPORT" started for "/SCMB/V_DF_DCTP" "V", date and time: "20151128215522"
1AETR012XProgram canceled (job "RDDEXECL", number "21552200")
1AEPU320 See job log"RDDEXECL""21552200""E91"
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 <<<
ST22:
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program /SCMB/CL_DF_DOCUMENT_TYPE=====CP
Application Component SCM-BAS-DF
Date and Time 28.11.2015 16:09:22
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short Text |
| The ASSERT condition was violated. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| The current application program has detected a situation with the |
| ASSERT statement that should not occur. |
| The reason for this runtime error was one of the following: |
| - For the checkpoint group specified with the ASSERT statement, the |
| activation mode is "abort". |
| - A system variant has been used to set the activation mode to "abort" |
| globally for all checkpoint groups in this system. |
| - The activation mode is set to "abort" at program level. |
| - The ASSERT statement is not assigned to any checkpoint groups. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| 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 checkpoint group was used: No checkpoint group specified |
| |
| If the FIELDS addition was used in the ASSERT statement, you can find |
| the content of the first 8 fields specified in the following overview: |
| (not used) |
| (not used) |
| (not used) |
| (not used) |
| (not used) |
| (not used) |
| (not used) |
| " (not used) " |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| - |
| If the error occurs in a non-modfied SAP program, you might be able to |
| find a solution in the SAP Notes system. If you have access to the SAP |
| Notes system, check there first using the following keywords: |
| |
| "ASSERTION_FAILED" |
| "/SCMB/CL_DF_DOCUMENT_TYPE=====CP" bzw. /SCMB/CL_DF_DOCUMENT_TYPE=====CM004 |
| "TABLE_CREATE" |
| If you cannot solve the problem yourself, please send the following |
| information to SAP: |
| |
| 1. This description of the problem (short dump) |
| To do this, choose System -> List -> Save -> Local File (unconverted) |
| on the screen you are in now. |
| |
| 2. A suitable system log |
| To do this, call the system log in transaction SM21. Restrict the time |
| interval to ten minutes before the short dump and five minutes after |
| it. In the display, choose System -> List -> Save -> Local File |
| (unconverted). |
| |
| 3. If these are programs of your own, or modified SAP programs: Source |
| code of these programs |
| To do this, choose More Utilities -> Upload/Download -> Download in |
| the Editor. |
| |
| 4. Details regarding the conditions under which the error occurred or |
| which actions and input caused the error. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|System environment |
| SAP Release..... 740 |
| SAP Basis level 0010 |
| |
| Application server... CTSC005113289 |
| Network address...... 10.155.140.125 |
| Operating system... Windows NT |
| Release.............. 6.3 |
| Hardware type....... 4x AMD64 Level |
| Character length..... 16 Bits |
| Pointer length........ 64 Bits |
| Work process number... 11 |
| Shortdump setting. full |
| |
| Database server... CTSC005113289 |
| Database type..... MSSQL |
| Database name..... E91 |
| Database user ID e91 |
| |
| Terminal.......... |
| |
| Character set C |
| |
| SAP kernel....... 742 |
| Created on....... Mar 24 2015 16:58:40 |
| Created at....... NT 6.1 7601 x86 MS VC++ 16.00 |
| Database version SQL_Server_9.00 |
| Patch level....... 101 |
| Patch text....... |
| |
| Database............. MSSQL 9.00.2047 or higher |
| SAP database version. 742 |
| Operating system... Windows NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT |
| 6.3 |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 7221168 |
| Heap.... 0 |
| Page.... 40960 |
| MM used. 1125232 |
| MM free. 724240 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client................. 000 |
| User.................. DDIC |
| Language key.......... E |
| Transaction......... |
| Transaction ID...... 48BC95E5CDFCF1E180F6005056BA4CFE |
| |
| EPP whole context ID...... 00000142004F00550050003100200020 |
| EPP connection ID........ 00000000000000000000000000000000 |
| EPP call counter......... 0 |
| |
| Program.............. /SCMB/CL_DF_DOCUMENT_TYPE=====CP |
Regards,
Preetha Balan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.