Any Problems w/Financial ESUs JK18022 or JK21476?

Are there any issues w/Financial ESUs JK18022 or JK21476? JK18022 is a financial baseline ESU for E812. I need JK21476. CFO worried about way too many objects being updated - concerned about too much risk. Any thoughts or counter arguments? Thanks...

Well that will depend on what you need the change for.

Is it a business critical change or is it something that the user have lived with?

Is it a single object that you can do a manual code change for or is it several objects you need?

At some point you will have to take the baseline ESU for any future ESU's so you and your CFO has to determine at what point it is best to take the baseline. Is there a time when you business slows down and you can get users to run their test scripts?

Think about it

The problem to be solved by the ESU is this:
When there is an error in the first batch (or middle batch) processed by R04110ZA (A/P Z Processor creating Vouchers), then all subsequent batches are not processed even though good. The good batches do not even appear on the report and a null pointer message shows for them in the workcenter. The work around is to process by (EDI) batch. It is a problem because it requires manual intervention (looking for good unprocessed batches, then submitting them one by one to be vouchered). Data flows hourly from an external system (GDS) and vouchering time is very important. The users want to approve on the GDS system and have the vouchers show up on JDE an hour later for payment. The manual step adds about 90 minutes to this process.