GRC PC 2.5, 3.0 Continuous Monitoring Question

[Former Member]

Experts,

We have purchased and would like to implement PC 3.0 at my company, but have had issues with change header data table (it is over 4 Terabytes).

Will PC be able to handle this size of a change header table that big? Approva could not.

Does anyone know how the continous monitoring works technically? It would have to use this table right?

Regards,

Curtis

[Former Member]

Hi,

This is aclassic case of Internal table overflow.In SAP you are not likely to encounter this problem.

Using PC we can monitor the changes that happens at the header level - in SAP it is BKPF Table- and also at the line item level - in SAP it is BSEG Table.

In PC we extract in a packet size of 1000 to avoid this problem.To a certain extent,with the help of "Table Index",this problem can be overcome.PC has functionalities like Report buffering,BAdIs to overcome this.

In PC the monitoring is done by means of Rules which use scripts and rule parameters.Through RFCs in case of SAP and using other interfaces in case of other ERPs they validate the individual transactions,picks up the exceptions and throw Reports on these.

Hope this helps.

Regards

Ramesh

[Former Member]

Good answer but just to be clear, I don't have to change anything with the implementation based on the header table being so large?

Since you said it is using BSEG and BKPF as well it won't have issues scanning through the 6.5 TB of data? Although those two tables look pretty large as well.

Or are you saying that it is monitoring all the transactions as they are entered so it is just scanning them as they come through and it doesn't need to scan the entire table (except maybe once to index the table)?

Just trying to understand if there are any additional actions besides the normal installation and sizing?

Regards,

Curtis

Edited by: Curtis Fincher on Jul 30, 2009 5:11 PM

[Former Member]

Hi,

While implementing PC 2.5 /3, we dont touch anything that is relevant with the Tables in the target ERP.PC is stand alone and works independently to your target ERP,so no changes required to the header table required.The deatiled installation procedures are given in SAP Service market place.Just follow these instructions.Except this,you need not to do any thing else.

Regards

Ramesh

[Former Member]

Thanks for your input, the tables we had trouble with during the implementation of Approva Process Insights were CDHDR, CDPOS, BKPF and BSEG. These tables are in excess of 6 Terabytes.

How does GRC PC monitor transactions for continuous monitoring if it does not read these tables?

Curtis

[former_member192417]

Hi Curtis

Automated controls in PC 3.0 does have different categories of rule scripts which can be used for the continious monitoring.

You can use GRC configurable rule and mention the table name and fields which you want to monitor,For ex BKPF,CDHDR

Though one limitation is that you can not use the pool tables in GRC configurable rules.For ex BSEG,CDPOS.The workaround is to write an ABAP program to monitor the changes in those tables and attach the program in GRC Programable rules (another category of rule).

Regards

Debraj