preventing update to COPA tables for a particular Sales order type

[former_member590214]

Hi ,

We need to have incoming sales order transfer to COPA activated only for one particular sales order type activated.

Earlier we implemented note 571697 for user exit to allow COPA update only for particular sales order type.

This prevented the transfer of SO to actuals table, but off late the performance for VA01 and VA02 has decreased substantially.

Upon checking, we found this is happening because of other CE4XXXX tables (excluding CE1XXXX) which are getting updated during creation/ change of SO. as the data in these tables is huge .

If possible, please advise, right userexit to prevent update to these tables.

Thanks.

Neeraj

[ajaycwa1981 · Accepted solution]

Hi

COPA exit COPA0005 should be the right one to supress line items from getting posted in COPA

BR,Ajay M

[former_member590214 · Accepted solution]

Thanks Amit for your reply..

To explain my requirement more -

We had a requirement where in we wanted only a particular sales order type record being transferred to COPA tables.

We activated the incoming sales order in Flow of Actual values> Transfer incoming sales order. Further we implemented the note 571967 which helped us to allow update of COPA table CE1XXXX for only one order type.

Initially performance of VA01/ VA02 was ok, but as more & more documents got posted the peformance declined, as the other COPA tables (CE4XXXX) were getting updated for all sales orders and thus grew in size enormously.

We would like to know if COPA0005 / other user exit that can be used to allow updates only for particular sales order, and the overall impact on reporting (if this is achievable).

Thanks.

[ajaycwa1981 · Accepted solution]

Hi

If CE4 is getting updated, your 1st point of attack should be KEQ3.. Deselect sales order as Segment Level Char

Then COPA005 will be helpful if line items are getting written to CE1 table

BR,Ajay M

[waman_shirwaicar · Accepted solution]

Hi,

Just to add here i do not think COPA0005 will be accessed during VA01. This is because there is no accounting interface involved. You can clear the COPA line item in COPA0002.

regards

Waman

[Former Member · Accepted solution]

Hi, Neeraj

I am just curious, how many sales orders do you have each months that they can slow down the performance to such a noticeable rate? And do you activate 2 kinds of COPA or only 1?

Regards, Erwin

[former_member590214 · Accepted solution]

Thanks for your inputs..I have few more queries on same.

Initially we had incoming sales order activated in KEKF allong with implemented SAP note 571697, which helped us to update CE1XXXX only for a particular sales order type. This was initial requirement to have system updating COPA values only for one particular sales order type.Also, KEQ3 was also activated which resulted in updates to CE4XXXX. This was not a problem initially since we had few sales orders now that plant has grown old with more sales order (resulting in huge size of CE4XXXX) VA01 is impacted..

Currently ,since we have KEQ3 activated so, Segment is created the moment we create sales order.. and table CE4XXXX is updated..

As most of you have suggested to switch off sales order in KEQ3, i need to analyze the impact of this..

From what i understand CE1XXXX will continue with updation for that order type... and CE4XXXX won't be updated in future..Please correct me if i am wrong..

Also, please advise what all can be possible impacts on COPA reporting if I switch off from now onwards (client has been using this since long) , and what all should be the precautions that i should take while doing this.

Thanks

[ajaycwa1981 · Accepted solution]

Hi Neeraj

Your understanding is right.. CE1 will be updated, but not CE4

No impact as such of deactivating in KEQ3 and no precautions to be taken.. Just deselect sales order as a segment level char in KEQ3

Also, ask BASIS guy to archive COPA data so that your reporting performance increases

BR,Ajay M

[former_member590214 · Accepted solution]

Hi All,

Thanks for your inputs.. They have been quite helpful. Further , related to same, I have following understanding.

1. With KEQ3 off for sales order, updates to table CE4PI02 will not happen during sales order creation, but this table will continue to get updated during billling. Please correct me if my understanding is wrong.

2. If 1 is true, then I believe in future i might face performance issue during billing , as the table will get accessed at that time.

Please advise, if above all is correct, archiving table CE4PI02 can be considered as an option?

Thanks

Neeraj

[ajaycwa1981 · Accepted solution]

Hi

NO.. KEQ3 off for sale order will not update CE4 at any stage.... Neither SO nor Billing

Br, ajay M

[former_member590214 · Accepted solution]

Ajay,

In that case how will profitablity segments get updated? It would be kind if you can explain in detail,

When CE4XXXX gets updated ? If never, why?

Thanks

Neeraj

[ajaycwa1981 · Accepted solution]

Hi

KEQ3 - The chars you choose Define the Prof Segment...

Once you deselect "sale order" in KEQ3 - New sales order wont create any Prog Segment.. Hence wont update in CE4...

Billing will update CE1 table

CE4 will be updated only whenever new char value is found.. i.e. If you keep Customer / Product switched ON in KEQ3, CE4 will be updated only when a new customer / product combination comes into picture

Hope this clarifies

br, Ajay M

[former_member590214 · Accepted solution]

Hi All,

Thanks for help regarding KEQ3 ..

Now my prob is that this will help stop growing this table CE4XXXX in future for sales order & sales order item.

Currently there are 14 million records already in this table. Performance is still a issue as table is accessed to check /create profitablity segments.

Is there a way to delete the data in table CE4XXXX and redetermine the profitablity segments after the config of KEQ3 has been changed.

I believe if this is done, it would improve the performance to a great extent. Please advise.

Thanks.

Neeraj

[ajaycwa1981 · Accepted solution]

Hi

Archiving the data is your only option.. I said the same in my earlier replies as well

Search OSS notes.. There are some notes available on archiving.. or raise an OSS message to SAP

Br, Ajay M

[eduardo_hinojosa]

Hi Neeraj,

See Note 140880 - Long access times to table CE4xxxx. I suggest you to do a trace with ST05, analyze the output and create a secondary index. Search the help of a Basis and/or an ABAPer.

I hope this helps you

Regards

Eduardo

Edited by: E_Hinojosa on Mar 4, 2011 4:52 PM

[Former Member]

hi..

Again my view is to stop updating sale order data in KE4xxxx table by deselecting segment char in KEQ3.

This will help a lot for your performance. Then use appropriate user exit as suggested by Ajay.

kkumar

[Former Member]

hi..

Goto KEQ3 pl check wheather Sales order/items have been selected. If selected this will effect the performace.

As per standard this chracteristics should not be selected in KEq3.

kkumar