Quantcast
Channel: SCN: Message List - Data Warehousing
Viewing all articles
Browse latest Browse all 3366

Re: Missing Detail Records in PSA When Initializing Cube (PSA not matching RSA3)

$
0
0

It's unlikely to be that your code is running differently in RSA3 than via InfoPackage. More likely is that standard SAP stuff is screwing things up. Btw, you must have a check that C_T_DATA is not empty before selecting with FOR ALL ENTRIES. e.g. IF c_t_data[] IS INITIAL. RETURN. ENDIF. Forms are also considered obsolete since 7.3, so really you should use a Function Module instead of a form, if possible.

 

Now you need to do some debugging.

 

You can run in debug directly from RSA3 (set breakpoints first). To debug when running from your BW, you need to add this bit of code at the start of your routine.

 

DATA x.

WHILE x IS INITIAL.

ENDWHILE.


Then execute the infopackage. In SM50 identify the extraction job - it should say it's running ZBWIN_2LIS_04_P_ARBP. Select that thread in SM50, and then use the menu option "debug". This will start the debugger at the bit of code about. Change the value of x to anything (x for example), and then continue to step through your code.

 

Run from RSA3 in debug. Check the values in I_T_SELECT, C_T_DATA at the start and C_T_DATA at the end. Ensure all the data in C_T_DATA at the end matches all selection criteria that may exist in I_T_SELECT (and there may be some, even though you don't put them into the infopackage), Take notes of the values, then debug when running from the InfoPackage. Compare the values again. This might give you clues as to what is happening.


Viewing all articles
Browse latest Browse all 3366

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>