JR31843: ABAP code does not stop processing if job is aborted

APAR status

• Closed as program error.

Error description

• The generated ABAP code continues sending data when a
  communication failure occurs,
  continuously producing error messages.
  
  This is causing problems because long ABAP
  reports are running after the job is terminated (by the user)
  and logging lots of SAP ABAP errors.
  

Local fix

Problem summary

• Users affected: ABAP stage, CPIC communication method, both
  generation methods (SQL Query and Extraction Object)
  The generated ABAP code continues sending data when a
  communication failure occurs, continuously producing error
  messages. This is causing problems because long ABAP
  reports are running after the job is terminated (by the user)
  and logging many SAP ABAP errors.
  

Problem conclusion

• Modified generated ABAP code (CPIC) to stop sending data after
  the first communication error. This avoids repeated error
  messages in the SAP system log.
  Version 2 of the fix corrects an issue where the check was not
  generated for EXtraction Object queries when using multiple
  tables.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IS PACK FOR SAP

• Fixed component ID

  5724Q5500

Applicable component levels

• R521 PSY

     UP

• R530 PSY

     UP

• R531 PSY

     UP

• R600 PSY

     UP

• R601 PSY

     UP

• R650 PSY

     UP

• R700 PSY

     UP