Read Master Data (Master Data Derivation) in SAP BW NW 7 is one of popular Transformation method to fill an InfoObject on a Cube or DSO. I think 99 percent of SAP BW architecture use this method.
Recently we have problem , an ABAP dump (error) occurs just after we finished a modification to a transformation. We are adding another read master data to new InfoObject. usually there is no any obstacle to perform this kind of modification.
The ABAB dump message (i have reduce the log file for important keyword only) :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
---------------------------------------------------------------------------------------------------- Runtime Errors GETWA_NOT_ASSIGNED Date and Time 12.11.2010 09:53:30 ---------------------------------------------------------------------------------------------------- What happened? The current ABAP program "CL_RSDMD_LOOKUP_MASTER_DATA===CP" had to be terminated because it has come across a statement that unfortunately cannot be executed. ---------------------------------------------------------------------------------------------------- What can you do? Using Transaction ST22 for ABAP Dump Analysis ---------------------------------------------------------------------------------------------------- Error analysis You attempted to access an unassigned field symbol ---------------------------------------------------------------------------------------------------- How to correct the error? If you have access to SAP Notes, carry out a search with the following keywords: "GETWA_NOT_ASSIGNED" " " "CL_RSDMD_LOOKUP_MASTER_DATA===CP" or "CL_RSDMD_LOOKUP_MASTER_DATA===CM003" "PREFETCH" ---------------------------------------------------------------------------------------------------- User and Transaction Program............. "CL_RSDMD_LOOKUP_MASTER_DATA===CP" ---------------------------------------------------------------------------------------------------- Information on where terminated Termination occurred in the ABAP program "CL_RSDMD_LOOKUP_MASTER_DATA===CP" - in "PREFETCH". The main program was "RSBATCH_EXECUTE_PROZESS ". In the source code you have the termination point in line 73 of the (Include) program "CL_RSDMD_LOOKUP_MASTER_DATA===CM003". ---------------------------------------------------------------------------------------------------- Source Code Extract 63|*Get reference to prefetched data 64|data l_lines type i. 65|data l_tabix like sy-tabix. 66|read table p_th_buffer assigning with table key iobjnm = i_iobjnm. 67|if sy-subrc = 0. 68| IF i_reset_prefetched_data = rs_c_true. 69| l_tabix = sy-tabix. 70| assign -r_data->* to . 71| describe table lines l_lines. 72| delete p_th_buffer index l_tabix. |>>>>>| clear . 74| unassign . 75| p_current_buffer_size = p_current_buffer_size - l_lines. 76| ENDIF. 77|ENDIF. ---------------------------------------------------------------------------------------------------- Active Calls/Events No: 7 Ty.Name : METHOD CL_RSDMD_LOOKUP_MASTER_DATA=>PREFETCH Program : CL_RSDMD_LOOKUP_MASTER_DATA===CP Include: CL_RSDMD_LOOKUP_MASTER_DATA===CM003 Line: 73 |
According to SAP NOTES , your system might have been implement:
SAP Note 1092539 – Master Data Lookup with prefetch
Which is a feature to speed up a read master data process by enabling “Master Data Lookup with Prefetch”. It can be turned ON by
maintaining a parameter named – MD_LOOKUP_PREFETCH_LOGIC in the table
RSADMIN. A value ‘X’ against this parameter causes the Transformation
program to switch to the new mode of Master Data look-up. It is turned ON
by default with SAP NetWeaver 7.0 BI support package 16.
Other Notes to read:
SAP Note 1175141 – Short Dump in Master Data Lookup in Transformations
SAP Note 1227788 – Reading master data with buffering returns incorrect values
SAP Note 1233535 – Reading master data with prefetch does not work correctly
SAP Note 1236970 – Reading master data returns incorrect data
SAP Note 1239269 – Error during Master Data Lookup in Transformations
Solution
1. Simply turn off the “Master Data Lookup with Prefetch” feature whic is a system-wide setting. Of course this will downgrade the ETL performace significantly
2. Update the BI patch to the latest release, or later than Release 19 . I think this is the best (recomended) option.
Good Luck