Submit and return silent skip in process inbound api

[Sandra_Rossi]

Dear Experts,

I have an issue sometimes data from the inbound REST API silently skips the process. When this happens, no data is processed, and absolutely no log is written into our custom logging table. Since this issue only happens occasionally in Production (and works fine in Development/Quality environments), I suspect it might be related to system load or session limitations. The submit program originally waiting time with default 12 second the code look like this.

  SUBMIT zxxx WITH v_wait = 12
              AND RETURN.

Any insights, experiences, or suggestions would be highly appreciated.

Thank you in advance!

[Sandra_Rossi]

I have no idea what the program ZXXX does, so I can't answer what the problem is.

[RaymondGiuseppi]

🔮must have left my crystal ball at home - how is this report structured? On a related note, SUBMIT and REPORT are suboptimal development patterns for this application.

[acetedi]

Hello Sandra, Basically the program running bapi and the there is no issue when we try on foreground

[acetedi]

Hello RaymondGiuseppi, because of this, I am considering a temporary solution by creating a Function Module or Class instead of using the SUBMIT program approach.

[Sandra_Rossi]

No need to do a fix that has no reason to fix the problem. Instead, change the program to log everything (at the places where there could be an issue) and identify what the problem is. Only after that, you can do a fix.

[acetedi]

Hello Sandra, Thanks for your advice

[sravan_aleshwaram]

Hello @acetedi 

Possible issue is with SUBMIT ... AND RETURN timing out or getting skipped under Production load.
Try increasing the wait time and add application logging before/after SUBMIT for traceability

SUBMIT zxxx WITH v_wait = 30
AND RETURN.

Thanks,
Sravan

[acetedi]

Hello Sravan,

I think increasing the wait time for the program is not the right solution. Also, adding logging after the SUBMIT is not fully traceable because some processes are being skipped silently. When I checked the SAP documentation for the SUBMIT syntax, I also found that there are several session handling limitations, especially when multiple executions are triggered simultaneously.

Kind Regards,

Tedi