PC 3.0 SP5 - Control Rule Assignment dump

[Former Member]

Hi all,

On PC 3.0, SP05, we are having an issue when trying to assign a rule (rule BCSPPAR_01C1_01_A) to a control in Regulation SOX/ Automated test rules / Control Rule Assignment. Any help would be greatly appreciated

Please note that we have already checked that:

- script is assigned to the right connector

- Rule is in status "Released"

- Control has status "Automated" for both control automation and test automation.

Thanks for your help, and regards,

Sophie Planchais

NB: Will post dump and ST22 trace in following messages

[former_member196847 · Accepted solution]

Hi Sophie,

So to resolve this issue either you need to upgrade your SAP support package to SAPKB70106 or apply the attached SAP note: 1328786 to fix this issue.

Best Regards,

Jennifer

[Former Member]

associated ABAP ST22 trace reads:

09.06.2010      15:24:22        a03sap-grc01_PCA_00     OBER    200     C       ASSIGN_TYPE_CONFLICT                            0       15CA73DF9036F1C088A5A4BADBEA5213
Information on where terminated 
    Termination occurred in the ABAP program "CL_SCMG_CASE_QUERY_WIN========CP" - 
     in "QUERY". 
    The main program was "SAPMHTTP ". 
    In the source code you have the termination point in line 57 
    of the (Include) program "CL_SCMG_CASE_QUERY_WIN========CM004". 
 53   ENDIF. 
 54 *--PANDEP--cust.msg.0120025231 0000257854 2009------------ 
 55 *--in freak cases, attribute table may have entries while header may 
 56 *--not. This check will ensure that such entries are not picked up in query 
>>>   ASSIGN ch_output_table TO <lt_output_table>. 
 58   SELECT * INTO CORRESPONDING FIELDS OF TABLE  lt_case_header 
 59      UP TO im_max_num_selected ROWS 
 60      FROM scmg_t_case 
 61      FOR ALL ENTRIES IN <lt_output_table> 
 62      WHERE case_guid = <lt_output_table>-case_guid.

[Former Member]

dump:

Error when processing your request 
What has happened? 
The URL .../sap/bc/webdynpro/sap/GRPC_CTRL_RL_ASGN/ was not called due to an error.   
   
Note 
The following error text was processed in the system PCA : Type conflict with ASSIGN in program CL_SCMG_CASE_QUERY_WIN========CP . 
The error occurred on the application server a03sap-grc01_PCA_00 and in the work process 0 . 
The termination type was: RABAX_STATE 
The ABAP call stack was: 
Method: QUERY of program CL_SCMG_CASE_QUERY_WIN========CP 
Method: FIND_BY_HR_OBJECT of program CL_GRPC_ASSESSMENT============CP 
Method: CHECK_RELATED_OBJECTS of program CL_GRPC_MODEL_SETUP===========CP 
Function: GRPC_API_CONTROL_UPDATE of program SAPLGRPC_API_CONTROL 
Method: CREATE of program CL_GRPC_CTRL_RL_ASGN_ASSIST===CP 
Method: ADD_RULE of program /1BCWDY/888CG6KHMW7G5EXE3YJG==CP 
Method: IF_COMPONENTCONTROLLER~ADD_RULE of program /1BCWDY/888CG6KHMW7G5EXE3YJG==CP 
Method: ONACTIONOK of program /1BCWDY/888CG6KHMW7G5EXE3YJG==CP 
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/888CG6KHMW7G5EXE3YJG==CP 
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP 
  
What can I do? 
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system PCA in transaction ST22. 
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server a03sap-grc01_PCA_00 in transaction SM21. 
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server a03sap-grc01_PCA_00 . In some situations, you may also need to analyze the trace files of other work processes. 
If you do not yet have a user ID, contact your system administrator. 
Error code: ICF-IE-http -c: 200 -u: OBER -l: E -s: PCA -i: a03sap-grc01_PCA_00 -w: 0 -d: 20100609 -t: 152422 -v: RABAX_STATE -e: ASSIGN_TYPE_CONFLICT