BCS Release Request Short dump

Question

Hello,
I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
The description is as follows:
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED" " "
    "CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
    "UGMD_EXTRACT_SID_2"
Information on where terminated
    Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
     in "UGMD_EXTRACT_SID_2".
    The main program was "RDDM0001 ".
    In the source code you have the termination point in line 62
    of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
Source Code Extract
Line  SourceCde
   32   FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
   33   FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
   34   FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
   35 *  FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
   36
   37   ASSIGN io_itab->rd_wa->* TO <ls_wa>.
   38   IF i_value_sid IS NOT INITIAL.
   39     ASSIGN COMPONENT i_value_sid
   40            OF STRUCTURE <ls_wa>
   41            TO <ld_vsid>.
   42     CHECK sy-subrc = 0.
   43   ELSE.
   44     CREATE DATA lr_sid.
   45     ASSIGN lr_sid->* TO <ld_vsid>.
   46     CLEAR <ld_vsid>.
   47   ENDIF.
   48
   49   IF NOT i_fieldname_sid IS INITIAL.                  "Start hah160603.1
   50     ASSIGN COMPONENT i_fieldname_sid
   51            OF STRUCTURE <ls_wa>
   52            TO <ld_fsid>.
   53     CHECK sy-subrc = 0.
   54   ELSE.
   55     CALL METHOD ugmd_get_fieldname_to_table
   56       EXPORTING
   57         i_tabname = i_datainfo-tabname
   58       IMPORTING
   59         e_fieldname = ld_fieldname.
   60     lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
   61       ld_fieldname ).
   62  >>>>>     ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
   63     ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
   64   ENDIF.                                                "End hah160603.1
   65
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 1
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY TDR_FULL
SY-UCOMM REFR
SY-TITLE Transport organizer: ordens
SY-MSGTY I
SY-MSGID FINB_TR
SY-MSGNO 009
SY-MSGV1 &
SY-MSGV2 &
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080904
SY-UZEIT 200112
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
Will award points for valuable help.
Thank you

Answer 1

Hi Ricardo,
You tried to transport the BCS' configuration, right?
If in the request was the full set of settings from the start of the project, the it will definitely fail.
There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
"For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
During the transport of a new consolidation area, the following settings should be transported in the following sequence:
1. Data basis
2. Consolidation area
3. Special versions
After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
I usually transport the BCS setting in a little transport requests in this order:
- all BW objects and settings
- data basis (with source DB)
- cons area
- special versions
- versions
- master data
...etc.
Hope this helps.