BAPI_NETWORK_MAINTAIN Massive mode

[vitek19]

Hello everyone,

we are using the BAPI_NETWORK_MAINTAIN for massive changes. We have an issue that we can't solve: when the BAPI encounters an error, it stops and doesn’t provide evidence of all other errors nor does it indicate the operation that caused the error (message CJ280). However, from CJ20N we get a log with all the precise errors. If you execute the BAPI for each individual operation, you do get error details. Unfortunately, this second approach has worse performance, so we can’t use it.

Do you have any advice?

Thank's,
Vito

[marcio_blos]

Hi Vito.

The BAPI_NETWORK_MAINTAIN requires the subsequent execution of the FM BAPI_TRANSACTION_COMMIT. This BAPI tends to have messages when the first one (BAPI_NETWORK_MAINTAIN) does not return clear messages.

Have you tried retrieving the messages in the BAPI_TRANSACTION_COMMIT?

Regards
Marcio Blos

[vitek19]

Hi, yes, I retrieve the messages. I debugged the standard, and this is exactly how it works: after about 10% of errors found, it no longer returns messages for the other operations and gives you the CJ 280 message. The constant used for calculating the percentage is hardcoded.

[vitek19]

Hi, yes, I retrieve the messages. I debugged the standard, and this is exactly how it works: after about 10% of errors found, it no longer returns messages for the other operations and gives you the CJ 280 message. The constant used for calculating the percentage is hardcoded. Regards