Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Issue with Code inspector ( SCI ) using BDC ??

Former Member
0 Likes
460

We have a requirement to run Code inspector (SCI ) using BDC.

We are facing an issue when the inspection is run.

The inspection is created, but it is not run.

I can find an entry for the inspection in table SCIINS_INF, but no entries in SCIREST_PS.

Even when i displayed the inspection, it shows the status as "Not Yet Executed".

I even tried saving the inspection first and running it, but even that didn't work.

Herez the code :

PERFORM bdc_dynpro USING 'SAPLS_CODE_INSPECTOR' '0200'.

PERFORM:

bdc_field USING

'SCI_DYNP-X_I_OBJS_0' 'X',

bdc_field USING

'SCI_DYNP-I_OBJ_T' 'PROG',

bdc_field USING

'SCI_DYNP-I_OBJ' i_pgm-name,

bdc_field USING

'SCI_DYNP-I_CHKV' 'YGLOBAL_VAR',

bdc_field USING

'BDC_OKCODE' '=OK'.

PERFORM bdc_dynpro USING 'SAPLS_CODE_INSPECTOR' '0200'.

PERFORM:

bdc_field USING

'BDC_OKCODE' '=RUN'.

Appreciate if anyone can help me through this

2 REPLIES 2
Read only

tushar_shukla
Active Participant
0 Likes
404

I'm not sure why are you recording BDC for SCI tcode. If you are creating it for purpose of running it in background, you can refer the programs of package 'S_CODE_INSPECTOR' .

Read only

0 Likes
404

We are having a QA Tool and we would like to integrate SCI to that tool.

For that case we would like to run Code inspector using BDC.

As i mentioned earlier, the inspection is saved, but the control is moved to the BDC program once it encounter the commit statement after saving the inspection.

There is a Commit Work Statement with in the method RUN in class CL_CI_INSPECTION.

That statement is available after the Inspection has been saved.

When running SCI directly, we are passing through this statement and then going to Run the inspection. But when run through BDC, the control is moved back to the bdc program once we encounter the Commit statement during debug.