Performance VA* and VF*

[Former Member]

Hello,

I have a performance problem with transactions VA* and VF * with the transaction VA02 for example, an order of about 10 items to enter each have to wait about 3 minutes. By analyzing the transaction SE30 I see that as long to perform xkomv_bewerten PRICING_BUILD_XKOMV function.

Does anyone have a clue? The price is great, this would be the reason for the delay?

Thank you!

[Former Member]

Hi

It should know if your pricing is complex, I mean how many conditions are, but try to check if the bottleneck is in an exit or in some custom ruoitne of the pricing

Max

[yuri_ziryukin]

Hello Michely,

this subroutine belongs to pricing. Performance of pricing calculation depends on the complexity of your pricing procedure (access sequences, condition types, use of group conditions, etc.).

Another reason is something wrong that you could make in a user exit. I have faced several cases where the change in a user exit unnecessarily triggered new pricing.

Next possible performance optimization is "prestep".

See SAP Note 156230 for details on the prestep and requirements.

If you are using user exists or modifications to change the value of header fields (in structure TKOMK) during line item processing in pricing, this will cause multiple executions of the condition prestep. This can have a negative impact on pricing performance.

Regards,

Yuri

[Former Member]

Hello,

I did some testing with a Formula Price (VOFM) and noticed that passes through this many times foramula this in an application that has only 5 items.

I believe that by reporting on the condition that the value is tied to the precissonar enter this formula should be increased only once in the code, right?

Like where is generating this problem, have a tip?

Thank you.

[eduardo_hinojosa]

Hi

Check also if your formula do selects on tables. In tcode V/08 check all VOFM and if you have many subroutines in your range name. Other issue, check the size of your pricing conditions (number of records in tables A+++). Perhaps you have a huge table that never have the proper condition in the beginning of the access sequence (tcode V/07) and you can avoid this access.

I hope this helps you

Regards

Eduardo

[Former Member]

Hello,

I found that I do have cases where I have a huge list of tables in the access sequence and my condition is met only in the last table (for example), when he quoted what shall I avoid the previous access, you referre to it eliminates the previous tables, or there is another way to handle this?

Thank you for the tips!

Michely

[eduardo_hinojosa]

Hi

Then it's a question of functional analysis. Check in tcode V/06 for these conditions if the conditions can be deleted or they need to be archived. If you have a lot or records to be deleted archive it. How? With tcode TAANA do an analysis for table KONP and see how much records you have with LOEVM_KO = 'X'. Use the field KSCHL as a criteria in the filter. To archive this data use the archiving object SD_COND. Finally, I suggest you to do an analysis for pricing again. So, search a SD consultant for it, and check also pricing procedures (V/08) and all these VOFM subroutines.

I hope this helps you

Regards

Eduardo

[former_member376549]

HI,

Lots of good advice already. One option I did not see. Often the buffering options on the A+++ tables are not correct for their size. Check the table sizes (ST10 maybe) and set the appropriate buffering in SE11. That along with options above and you should be in good shape. Good Luck.

Allan Stone

EMC Solutions Design Center

[Former Member]

Hello Allan, thanks for the tip, I'm trying to make the adjustment mentioned, but with a doubt as regards the point is to adjust the size category, reported in the technical settings? Grateful for the attention.

[Former Member]

Hello Eduardo, I was able to perform the analysis, but could not make the archiving, the same with Tan? The archiving would be made ​​only for records with LOEVM_KO = 'X'? Grateful for the attention.

[former_member376549]

Hi,

It is not the size category but the buffering setting that needs to change. Try SE11, technical settings, then the buffering switched on and fully buffered. Save the changes and use transport. This is often the best for large pricing tables. Good Luck

[Former Member]

Hello, I have a doubt!

I have in my Princing a value formula would love just one condition, I put a breakpoint in this formula, and when I'm entering a Sales Order (VA01), with only one item, I end up stopping at a stop five times, this is correct?

Thank you,

Michely

[former_member196555]

Hi,

Can you put up your findings from the trace taken? What trace are you using? You can use ST12.

Thank you.

Regards,

Harshad.