Solved: Error happened when maintained Rates Model - BPC 1...

Read only

368

SAP Managed Tags
SAP Business Planning and Consolidation, version for SAP NetWeaver

Dear experts,

when I want to change the CATEGORY dimension in Rates Model, I got the error below:

please help me to analyze it！ Thanks in advance.

my env:

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

It looks like issue is related to the fact that CATEGORY in a secured Dimension in that Model. Can you try removing that check mark, change Dimension and then secure it again?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Gersh,

Amazing! it works.

Removing the secured mark then save the model
Change Dimension, then save the model
Last secure the dimension, then save it works!

you can't do the 2 and 3 steps at the same time!

Could you please tell me why I have to execute like this sequence, is it because my environment or is it a standard way when we need to change a dimension in a model?

Thank you very much!

BR,

Jacob

Hi Jacob,

No, it's not standard way. I just saw in your dump that it fails while processing secure Dimension and thought it could help.

Also, I found that sometimes when you make changes to a secure Dimension without taking Env offline it fails. So, maybe taking it offline can help as well.

Regards,

Gersh

Answers (1)

Hi Jacob,

Check if there is any transaction data in rate mode, if yes, clear data and then try.

If not, do some changes in category dimension and process dimension.

Run UJA_REFRESH_DIM_CACHE.

P.S. Also check the dump in ST22.

May be helpful.

Shrikant

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Shrikant,

Thank you for your reply.

I followed what you suggest,the issue still exist. I checked the dump info. but I can not understand it,

I enclosed a part of dump info as Message is too large:

=============================================================================================================

Category ABAP Programming Error

Runtime Errors ASSERTION_FAILED

ABAP Program CL_UJA_APPLICATION============CP

Application Component EPM-BPC-NW-ADM

Date and Time 31.08.2015 08:03:30

----------------------------------------------------------------------------------------------------

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

----------------------------------------------------------------------------------------------------

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

| "CL_UJA_APPLICATION============CP" bzw. CL_UJA_APPLICATION============CM01Y |

| "MODIFY_BI_CONTENT" |

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

| |

| Application server... sapbpc |

| Network address...... 192.168.0.109 |

| Operating system... Windows NT |

| Release.............. 6.1 |

| Hardware type....... 2x AMD64 Level |

| Character length..... 16 Bits |

| Pointer length........ 64 Bits |

| Work process number... 9 |

| Shortdump setting. full |

| |

| Database server... sapbpc |

| Database type..... DB6 |

| Database name..... BPC |

| Database user ID SAPBPC |

| |

| Terminal.......... 192.168.0.103 |

| |

| Character set C |

| |

| SAP kernel....... 742 |

| Created on....... Sep 2 2014 15:11:05 |

| Created at....... NT 6.1 7601 x86 MS VC++ 16.00 |

| Database version DB6_81 |

| Patch level....... 17 |

| Patch text....... |

| |

| Database............. DB6 09.07.*, DB6 09.08.*, DB6 10.* |

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

| Heap.... 0 |

| Page.... 0 |

| MM used. 4212784 |

| MM free. 3635488 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client................. 001 |

| User.................. JACOB |

| Language key.......... E |

| Transaction......... |

| Transaction ID...... B4734FE53074F139840C000C29C57132 |

| |

| EPP whole context ID...... 000C29C571321ED593EE768E8124840C |

| EPP connection ID........ 000C29C571321ED593EE768E8124A40C |

| EPP call counter......... 1 |

| |

| Program.............. CL_UJA_APPLICATION============CP |

| Screen.............. SAPMHTTP 0010 |

| Screen line.......... 2 |

| Active debugger..... "none" |

----------------------------------------------------------------------------------------------------

|RFC Caller Information |

| Information on caller of "HTTP" connection: Plug-in type......... HTTP |

| Caller IP.............. 192.168.0.103 |

| Caller port............ 8000 |

| Universal resource ID /sap/bpcmodeling/cubes/FINA/Rates |

| |

| Program.............. CL_UJA_APPLICATION============CP |

| Screen.............. SAPMHTTP 0010 |

| Screen line.......... 2 |

| |

| Information on caller of "HTTP" connection: Plug-in type......... HTTP |

| Caller IP.............. 192.168.0.103 |

| Caller port............ 8000 |

| Universal resource ID "/sap/bpcmodeling/cubes/FINA/Rates" |

----------------------------------------------------------------------------------------------------

|Information on where terminated |

| The termination occurred in ABAP program "CL_UJA_APPLICATION============CP", |

| in "MODIFY_BI_CONTENT". The main program |

| was "SAPMHTTP". |

| |

| In the source code, the termination point is in line 103 of (Include) |

| program "CL_UJA_APPLICATION============CM01Y". |

----------------------------------------------------------------------------------------------------

|Source Code Extract (Source code has changed) |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

| 73| loop at it_appl_dim_src into ls_appl_dim_src. |

| 74| read table lt_appl_dim_tmp |

| 75| into ls_appl_dim_tgt |

| 76| with table key dimension = ls_appl_dim_src-dimension. |

| 77| if sy-subrc is initial. |

| 78| delete table lt_appl_dim_tmp from ls_appl_dim_tgt. |

| 79| if ls_appl_dim_src-secure ne ls_appl_dim_tgt-secure. |

| 80| read table lt_dim_list into ls_dim_list |

| 81| with key dimension = ls_appl_dim_tgt-dimension |

| 82| binary search. |

| 83| assert sy-subrc is initial. |

| 84| if ls_appl_dim_tgt-secure is not initial. |

| 85| lo_dim_dao->change_iobj_auth_flag( |

| 86| i_appl = is_appl_info-application_id |

| 87| i_dim = ls_appl_dim_tgt-dimension |

| 88| i_dim_tech_name = ls_dim_list-tech_name |

| 89| if_secure = 'X' ). |

| 90| else. |

| 91| lo_dim_dao->change_iobj_auth_flag( |

| 92| i_appl = is_appl_info-application_id |

| 93| i_dim = ls_appl_dim_tgt-dimension |

| 94| i_dim_tech_name = ls_dim_list-tech_name |

| 95| if_secure = space ). |

| 96| endif. |

| 97| endif. |

| 98| else. |

| 99| if ls_appl_dim_src-secure is not initial. |

| 100| read table lt_dim_list into ls_dim_list |

| 101| with key dimension = ls_appl_dim_tgt-dimension |

| 102| binary search. |

|>>>>>| assert sy-subrc is initial. |

| 104| lo_dim_dao->change_iobj_auth_flag( |

| 105| i_appl = is_appl_info-application_id |

| 106| i_dim = ls_appl_dim_tgt-dimension |

| 107| i_dim_tech_name = ls_dim_list-tech_name |

| 108| if_secure = 'X' ). |

| 109| endif. |

| 110| endif. |

| 111| endloop. |

| 112| loop at lt_appl_dim_tmp into ls_appl_dim_tgt. |

| 113| if ls_appl_dim_tgt-secure is not initial. |

| 114| read table lt_dim_list into ls_dim_list |

| 115| with key dimension = ls_appl_dim_tgt-dimension |

| 116| binary search. |

| 117| assert sy-subrc is initial. |

| 118| lo_dim_dao->change_iobj_auth_flag( |

| 119| i_appl = is_appl_info-application_id |

| 120| i_dim = ls_appl_dim_tgt-dimension |

| 121| i_dim_tech_name = ls_dim_list-tech_name |

| 122| if_secure = 'X' ). |

----------------------------------------------------------------------------------------------------

BR,

Jacob

Hi Jacob,

Try to apply the following notes.......

http://www.erpchamps.com/runtime-error-assertionfailed-happens-when-display-dump-det/

http://solveissue.com/note?id=1934121

Aravind

Hi Aravind，

Thank you for your reply!

I followed what you said, the issue still there.

BR,

Jacob

Ask a Question

Top Q&A Solution Author

User

Count

Error happened when maintained Rates Model - BPC 10.1

Know the answer?

Need more details?

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)