Skip to Content
0

ABAP Dump when activating BI content in BW 7.4

Sep 21, 2017 at 06:30 AM

98

avatar image
Former Member

Hi Experts,

Have similar issue as below forum Question

https://archive.sap.com/discussions/thread/3769281

(problem was resolved in this thread)

Error Message:

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

When activating a Info Object in BI Content: 0BPARTNER.

Receiving below ABAP Dump error:

Category ABAP Programming Error Runtime

Errors MESSAGE_TYPE_X

ABAP Program SAPLRSDG_IOBJ_DB_READ

Application Component BW-WHM-MTD

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

SOURCE CODE:


Information on where terminated                                                                   |
|    The termination occurred in ABAP program "SAPLRSDG_IOBJ_DB_READ", in                          |
|     "REGULAR_IOBJ_GET_FOR_META". The main program                                                |
|    was "RSAWBN_START".                                                                           |
|                                                                                                  |
|    In the source code, the termination point is in line 31 of (Include)                          |
|    program "LRSDG_IOBJ_DB_READF40".                                                              |
----------------------------------------------------------------------------------------------------


----------------------------------------------------------------------------------------------------
|Source Code Extract (Source code has changed)                                                     |
----------------------------------------------------------------------------------------------------
|Line |SourceCde                                                                                   |
----------------------------------------------------------------------------------------------------
|    1|*----------------------------------------------------------------------*                    |
|    2|*   INCLUDE LRSDG_IOBJ_DB_READF40                                      *                    |
|    3|*----------------------------------------------------------------------*                    |
|    4|                                                                                            |
|    5|                                                                                            |
|    6|*---------------------------------------------------------------------*                     |
|    7|*      Form  REGULAR_IOBJ_GET_FOR_META                                                      |
|    8|*---------------------------------------------------------------------*                     |
|    9|*    read a regular InfoObject as Meta InfoObject                                           |
|   10|*---------------------------------------------------------------------*                     |
|   11|*   --> I_INFOCUBE   InfoCube                                                               |
|   12|*   --> I_IOBJNM     InfoObject                                                             |
|   13|*   <-> C_T_COB_PRO  InfoCube specific InfoObject properties                                |
|   14|*---------------------------------------------------------------------*                     |
|   15|FORM regular_iobj_get_for_meta USING    i_infocube   TYPE rsinfocube                        |
|   16|                                        i_iobjnm     TYPE rsiobjnm                          |
|   17|                               CHANGING c_t_cob_pro  TYPE rsd_t_cob_pro.                    |
|   18|                                                                                            |
|   19|  DATA: l_s_cob_pro  TYPE rsdcobpro.                                                        |
|   20|                                                                                            |
|   21|  CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'                                                 |
|   22|    EXPORTING                                                                               |
|   23|      i_iobjnm       = i_iobjnm                                                             |
|   24|      i_objvers      = rs_c_objvers-active                                                  |
|   25|    IMPORTING                                                                               |
|   26|      e_s_cob_pro    = l_s_cob_pro                                                          |
|   27|    EXCEPTIONS                                                                              |
|   28|      iobj_not_found = 1                                                                    |
|   29|      illegal_input  = 2.                                                                   |
|   30|  IF sy-subrc <> 0.                                                                         |
|>>>>>|    MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'                                        |
|   32|                             'REGULAR_IOBJ_GET_FOR_META'.                                   |
|   33|  ENDIF.                                                                                    |
|   34|                                                                                            |
|   35|* time charact --> time dimension / In BEX not visible                                      |
|   36|  IF i_iobjnm = rsd_c_chanm-date OR                                                         |
|   37|     i_iobjnm = rsd_c_timnm-calday.                                                         |
|   38|    l_s_cob_pro-chasel     = rsd_c_chasl-not_allowed.                                       |
|   39|    l_s_cob_pro-chanav     = rsd_c_chanv-not_allowed.                                       |
|   40|                                                                                            |
|   41|**   from 3.0 these InfoObjects are marked as META objects                                  |
|   42|*    l_s_cob_pro-iobjtp     = rsd_c_objtp-meta.                                             |
|   43|*    the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -       |
|   44|*    therefore it has to be in the cobpro                                                   |
|   45|*    but it must not be of type META, since then day of validity logic                      |
|   46|*    does not work                                                                          |
|   47|*    solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine         |
|   48|*    if 0DATE / 0CALDAY is part of the infocube                                             |
|   49|                                                                                            |
|   50|*   leave dimension empty                                                                   |
----------------------------------------------------------------------------------------------------

**************** SOURCE CODE ENDS ********************

Have already activated the infoobjects 0DATE, 0CALDATE, 0HIER* infoobjects.

However, the ABAP Dump error still comes when I try to install the InfoObject: 0BPARTNER

Attached is the detailed Error Log

Needs your suggestions.

Regards,

AK

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

avatar image
Former Member Sep 21, 2017 at 12:43 PM
0

Hi All,

The above issue is resolved now.

However, getting different error while simulating the Infocube activation.

Error:

Exception 'An exception with the type CX_SY_REF_IS_INITIAL oc' in progrmm 'CL_RSD_MDOB_VERS==============CP,CL_RSD_MDOB_VERS=' when passing type 'InfoCube' CUBE

Looked into the SCN blog: https://archive.sap.com/discussions/thread/3654592#

error-in-program.jpg

Error:

Regards,

AK


Share
10 |10000 characters needed characters left characters exceeded
Andras Margitics
Oct 18, 2017 at 02:36 PM
0

Hi Amil,

Check this KBA:

1942562 - 0CMM_C0* - Error when collecting/activating the infocube from Business Content

Br, Andras

Share
10 |10000 characters needed characters left characters exceeded