Enhancing Shuffler for SNP planning book - Performance issues

[former_member566926]

Hello Expert,

We have a business requirement to enhance shuffler for SNP planning book to include ‘Production planner’ code, giving schedulers an option to filter location product combinations based on it just like other SAP provided standard fields. To accomplish this, we implemented the BADI: /SAPAPO/SDP_SELECTOR and it works good as long as we use it in dev. Once its moved to quality, we observed performance issues and it takes almost indefinite time to hit the relevant methods of this BADI(due to the large number of combinations). The option to utilize freely-definable attributes  is also not available as they have already been exhausted for some other purposes.

Would like to know if you have faced something similar in the past and found some feasible solution to it. Any inputs around this will really be appreciated.

Thanks,

Rajat

[former_member199512]

Hi Rajat

We have a similar problem and issue. What was the solution for your question?

Best regards

[Former Member]

Hi Jose,

We have adopted a very simple way of improving the BADI performance by making the use of implicit enhancement(explained below) before system makes a call to it's method: LOC_PROD_VALUE_LIST.

- Navigate to the below routine and create an implicit enhancement at the start of the form

Include: /SAPAPO/LMSDP_SHFM1

Routine: matloc_get

- Based on the import parameter of this routine 'it_selection', we would be knowing what are the different production planners are passed to this BADI. Through these PP values, we can further restrict product/location combinations which would eventually be passed to the ct_value_list and filtered again using the method: LOC_PROD_VALUE_LIST. Essentially, we have tried to reduce the data volume before this method is invoked.

Let me know if you still need more details from my end.

Best Regards,

Rajat

[former_member199512]

Hi Rajat

Thank you for this advice.

We would like to add other plannerds, purchasing group and BESKZ to the selection. The crazy thing is that these selecction criteria are available in the interface for function /SAPAPO/DM_MATMODS_GET, but not called from teh perform matloc_get.

We have until now evaluated to use the BADI methd for userdefined selection, but we fear that it will force us to copy to large parts of the SAP standard code ( not recommened).

I understand what you did and we will evaluate this as a possibility.

Another possibility might be to make an implicit enhancement point at the beginning of the function and to append the wanted selection criteria to the interface parameters, after having them read from a global buffer of a static class that we filled in the BADI method to check the values.

Best regards