BOP Runtimes Understanding

[victorhugo_leao]

Hello Experts,

Do you know how to understand the BOP runtime details?

Why do we have more than one step for 'Initialization', 'Preparation', 'Check' and 'Send' even considering that we do not use parallel profiles?

Please, consider the screenshot below.

Thanks a lot!

Best Regards!

Victor Hugo

[victorhugo_leao · Accepted solution]

Thanks, R.Brahmankar!

It seems to be something standard for all BOP runs. But nobody knows why do we have different entries for the same step.

Do you run BOP in Parallel Mode?

Do you know if BOP Parallel can impact scenarios where we have orders consuming same PAL CVC, for example?

Do you have any recommendation to run it in parallel?

Thanks in advance!

Best regards!

Victor Leao

[rupesh_brahmankar · Accepted solution]

Hello Victor,

No we are not using parallel processing in back order processing.

Parallel processing may help to reduce the run time, apart from the split BOP variants will also help.

Please refer the useful SAP help document which suggested all the steps to setup the parallel processing in the BOP.

SAP Library - Backorder Processing

To optimize the total runtime of backorder processing, you can vary the group size and check its influence on the runtime in the runtime statistics. So all together trail and run scenario with same set of data.

My experience with BOP with PAC only is good however, when it comes to the PAL with PAC it has issue with runtime.

And if you have same CVC (example - mask ###) consuming PAL for most of the items runtime keeps on increasing.

I have an open incident for BOP performance with 2 steps PAL and PAC running forever for 20K demand/backlog.

If SAP come with any solution I will let you know and if you have it then please let me know.

Thanks

Best Regards,

R.Brahmankar

[victorhugo_leao]

Hello Brahmankar!

Deal!

Thanks a lot!

Best regards!

Victor

[rupesh_brahmankar]

Hello,

These are the steps inside the backorder processing

• Initialization
• Filters
• Split Items
• Sort
• Check
• Save
• Close

Even if you are using parallel processing system will execute all these steps inside the BOP.

If you are facing as issue with performance with BOP run you can use the parallel processing.

Before that you may try to split BOP variants limit your selection as per your backlog

If you are using custom filter and sort then check your development

Delete old BOP runs entries through report /SAPAPO/BOP_DELETE

Consult with one of your local DB experts, who can trace the execution of BOP runtime.

Also have a look on these SAP KBA,

1641525 - First steps in case of BOP performance issues - APO BOP (Please read consulting note inside the KBA carefully)

1962003 - Bad Performance running ATP check with Forecast in SCM system

Best Regards,

R.Brahmankar

[victorhugo_leao]

Hello R.Brahmankar!

Thanks a lot for your answer.

I attached the screenshot to explain better what I'm trying to undestand.

For example, "Preparation" has 4 counters. Why does it repeat?

Thanks in advance!

Best regards,

Victor Hugo

[rupesh_brahmankar]

Hello,

It looks like it works in packages during the BOP processing as we process a large data.

I could see the same in my BOP monitor too.

Best Regards,

R.Brahmankar