Limits of maintenance plans (amount) in S4H on premise

[StefanMatthias]

My client has to manage at least 300.000 maintenance plans (strategy) in SAP S4H on premise.

Any recommendation / doubts /recommendation in managing this huge number of documents in S4H?

Are there limits to performance / scheduling jobs / call object creation?

[peter_atkin]

I've been on a few projects where the customer has had similar (or bigger) numbers of maintenance plans and had no issues.

However, this information should be passed to your Basis Team to ensure the system is sized correctly.

You may also need to carefully consider the way the "deadline monitoring" batch program(s) are scheduled (IP30H).

Furthermore, you may be able to rationalise the number of plans if your existing system uses a "single-cycle" approach for maintenance plans by using SAP's strategy-based plans.

PeteA

[StefanMatthias]

Hello Peter,

we will setup 300K maintenance plans the first time in S4H => we have no experience whether the system can manage the amount of documents.

I'm looking for expereince from another customer managing such huge amount of maintenance plans in SAP standard.

Stefan

[peter_atkin]

Stefan,

I'm assuming you already have SAP and are moving to S/4.

In that case, there is very little difference between ECC and S/4 in terms of the PM module.

So if your existing system handles 300K maintenance plans, then if S/4 is sized correctly it will also manage these plans.

FYI: There is a newer IP30H transaction that replaces IP30, and is more efficient at scheduling the plans. But you can get this transaction in ECC too..

PeteA