Skip to Content
0
Aug 02, 2023 at 05:16 PM

S/4 GCP Job stays active while BODS job has already completed.

25 Views

hello,

we have random jobs in S/4 GCP that stay in active status even though the BODS job that is called finished successfully. Eventually the S/4 GCP job cancels itself with a broken pipe message in the log capture.

we dont have this issue with our on prem SAP ECC jobs.

We call the BODS job using a command call to a shell script that calls the AL_RWJobLauncher and passes GUID etc to BODS.

Any ideas ?

no signs of network hiccups but since it's not happening on our ECC onprem - im wondering if there is some sort of timeout config that is different in s/4 than ECC.

28 debug3: send packet: type 1

42 client_loop: send disconnect: Broken pipe

46 External program terminated with exit code 255

thanks in advance,

Armin