0% found this document useful (0 votes)
100 views

Dump Short EN

An ASSERTION_FAILED runtime error occurred in ABAP program CL_FINS_ML_CUSTOMIZING_UTIL===CP due to an ASSERT statement failing an expected condition. The ASSERT statement is located in the CHECK_CONSISTENCY method in include CL_FINS_ML_CUSTOMIZING_UTIL===CM004 at row 158. The error appears to be caused by a mismatch between CURTP values in tables FMLT_CURTP_ML and CKMLCT for a given company code.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
100 views

Dump Short EN

An ASSERTION_FAILED runtime error occurred in ABAP program CL_FINS_ML_CUSTOMIZING_UTIL===CP due to an ASSERT statement failing an expected condition. The ASSERT statement is located in the CHECK_CONSISTENCY method in include CL_FINS_ML_CUSTOMIZING_UTIL===CM004 at row 158. The error appears to be caused by a mismatch between CURTP values in tables FMLT_CURTP_ML and CKMLCT for a given company code.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

Category ABAP programming error

Runtime Errors ASSERTION_FAILED


ABAP Program CL_FINS_ML_CUSTOMIZING_UTIL===CP
Application Component CO-PC-ACT
Date and Time 02/01/2021 15:40:01 (EGYPT)
-----------------------------------------------------------------------------------
-----------------

-----------------------------------------------------------------------------------
-----------------
|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.
|
-----------------------------------------------------------------------------------
-----------------

-----------------------------------------------------------------------------------
-----------------
|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) "
|
-----------------------------------------------------------------------------------
-----------------

-----------------------------------------------------------------------------------
-----------------
|Trigger Location of Runtime Error
|
| (Program) CL_FINS_ML_CUSTOMIZING_UTIL===CP
|
| (Include) CL_FINS_ML_CUSTOMIZING_UTIL===CM004
|
| (Row) 158
|
| (Module Type) (METHOD)
|
| (Module Name) CHECK_CONSISTENCY
|
-----------------------------------------------------------------------------------
-----------------

-----------------------------------------------------------------------------------
-----------------
|Source Code Extract
|
-----------------------------------------------------------------------------------
-----------------
|Line |Code
|
-----------------------------------------------------------------------------------
-----------------
| 128|* SUBCHECK: There must be at least one ML relevant CURTP in table
FMLT_CURTP_ML for a co|
| 129|* with a ML productive valuation area.
|
| 130| READ TABLE lt_curtp_ml REFERENCE INTO DATA(lr_curtp_ml)
|
| 131| WITH KEY rbukrs = lr_t001k_v->bukrs.
|
| 132| ASSERT sy-subrc = 0.
|
| 133|* SUBCHECK: Set of CURTP in CKMLCT for a ML productive valuation area
and set of ML rele|
| 134|* CURTP in table FMLT_CURTP_ML for corresponding company code
must be identica|
| 135|* If not, there is a fundamental issue.
|
| 136|* Make working copy of CURTP for company code
|
| 137| DATA lt_curtp_ml_copy LIKE lt_curtp_ml.
|
| 138| REFRESH lt_curtp_ml_copy.
|
| 139| LOOP AT lt_curtp_ml REFERENCE INTO lr_curtp_ml
|
| 140| WHERE rbukrs = lr_t001k_v->bukrs.
|
| 141| APPEND lr_curtp_ml->* TO lt_curtp_ml_copy.
|
| 142| ENDLOOP.
|
| 143|* Look up CURTP from FMLT_CURTP_ML in CKMLCT. If found, clear respective
CURTP record in|
| 144|* Each CURTP must have been found. If not, there is a fundamental issue.
|
| 145| LOOP AT lt_curtp_ml_copy REFERENCE INTO DATA(lr_curtp_ml_copy).
|
| 146| READ TABLE lt_ckmlct REFERENCE INTO lr_ckmlct
|
| 147| WITH KEY bwkey = lr_t001k_v->bwkey
|
| 148| curtp = lr_curtp_ml_copy->curtp.
|
| 149| ASSERT sy-subrc = 0.
|
| 150| DELETE lt_ckmlct INDEX sy-tabix.
|
| 151| ASSERT sy-subrc = 0.
|
| 152| ENDLOOP.
|
| 153| CLEAR lr_curtp_ml_copy.
|
| 154|* All CURTP must have been matched. No CURTP must be left in CKMLCT.
|
| 155|* If not, there is a fundamental issue.
|
| 156| READ TABLE lt_ckmlct REFERENCE INTO lr_ckmlct
|
| 157| WITH KEY bwkey = lr_t001k_v->bwkey.
|
|>>>>>| ASSERT sy-subrc <> 0.
|
| 159| ENDLOOP.
|
| 160|
|
| 161|*we need to check whether the combination Company Code/Ledger in
FMLT_CURTP_ML does exist in|
| 162|*this check is necessary since it might happen, that customer after
productive start changes|
| 163|*that is, on the other hand, already frozen in FMLT_CURTP_ML
|
| 164|
|
| 165|
|
| 166| SELECT rbukrs, rldnr FROM fmlt_curtp_ml
|
| 167| INTO TABLE @DATA(lt_curtp_ml_ld)
|
| 168| WHERE rbukrs IN @rt_bukrs.
|
| 169|
|
| 170| SORT lt_curtp_ml_ld BY rbukrs rldnr.
|
| 171| DELETE ADJACENT DUPLICATES FROM lt_curtp_ml_ld COMPARING rbukrs rldnr.
|
| 172|
|
| 173|
|
| 174| SELECT bukrs, rldnr FROM finsc_ld_cmp
|
| 175| INTO TABLE @DATA(lt_finsc_ld_cmp)
|
| 176| WHERE bukrs IN @rt_bukrs.
|
| 177|
|
-----------------------------------------------------------------------------------
-----------------

-----------------------------------------------------------------------------------
-----------------
|Active Calls/Events
|
-----------------------------------------------------------------------------------
-----------------
|No. Ty. Program Include
Line |
| Name
|
-----------------------------------------------------------------------------------
-----------------
| 11 METHOD CL_FINS_ML_CUSTOMIZING_UTIL===CP
CL_FINS_ML_CUSTOMIZING_UTIL===CM004 158 |
| CL_FINS_ML_CUSTOMIZING_UTIL=>CHECK_CONSISTENCY
|
| 10 FUNCTION SAPLCKMV LCKMVU01
85 |
| CKMV_AC_DOCUMENT_CREATE
|
| 9 FORM SAPMM07M MM07MFF9_F_BELEG_ERGAENZEN
47 |
| F-BELEG_ERGAENZEN
|
| 8 FORM SAPMM07M MM07MFB9_BUCHEN_AUFBEREITEN
47 |
| BUCHEN_AUFBEREITEN
|
| 7 FUNCTION SAPLMBWL LMBWLU05
45 |
| MB_CREATE_MATERIAL_DOCUMENT
|
| 6 FUNCTION SAPLMBWL LMBWLU14
3454 |
| MB_CREATE_GOODS_MOVEMENT
|
| 5 METHOD SAPLMIGO LMIGOKD1
1396 |
| LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
|
| 4 METHOD SAPLMIGO LMIGOKD1
13 |
| LCL_MIGO_KERNEL=>DOCUMENT_POST
|
| 3 METHOD SAPLMIGO LMIGOST2
126 |
| LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
|
| 2 METHOD SAPLMIGO LMIGOFR2
172 |
| LCL_MIGO_FRAME=>OKCODE_DISPATCH
|
| 1 MODULE (PAI) SAPLMIGO LMIGOPAI
11 |
| PAI_OKCODE_DISPATCH
|
-----------------------------------------------------------------------------------
-----------------

You might also like