JR48495: WHEN MULTIPLE ABAP RFC STAGES RUN AT SAME TIME AND SAP SERVER IS UNDER LOAD, SOME OF THE STAGES MAY NOT EXTRACT COMPLETE DATA.

APAR status

• Closed as program error.

Error description

• When multiple ABAP RFC stages run at the same time and the SAP
  Server is under load, some of the stages may not extract
  complete data.
  

Local fix

• NA
  

Problem summary

• When multiple ABAP RFC stages run at the same time and the SAP
  Server is under load, some of the stages may not extract
  complete data (or no data at all).
  The affected ABAP stage does not detect any error, ending the
  execution. If using the background program mode, the normal
  cleanup at the end of execution will fail, since the background
  job is
  still running on the SAP Server. Example of warning messages
  generated:
  Warning: HR_TL_CAT_SAP_EXTRACT_ECC.PA0001:
  CleanBackgroundRunJob: BAPI_XBP_JOB_DELETE returns  Error:
  Delete a job: Unable to delete job table entry
  Message type:E Message class:XM                   Message
  number:080
  Warning: HR_TL_CAT_SAP_EXTRACT_ECC.Source:
  CleanBackgroundRunJob: ABAP job status as determined by
  BAPI_XBP_JOB_STATUS_GET is R (active) even after 20 retries,
  could not delete the job.
  Job Name=YETLTR33; Job Count=11513300
  

Problem conclusion

• Code fix - various ABAP program enhancements:
  SQL - SQL Builder; EO - Extraction Object
  1. exit if PING to DS RFC listener fails (meaning the job has
  aborted) - affects tRFC, SQL, EO
  2. use just one background task for all packets - affects tRFC,
  qRFC, SQL, EO
  3. extra selection criteria for table ARFCSDATA to avoid waiting
  for packets from previous runs (unrelated to the current
  transaction)  - affects tRFC, SQL, EO
  4. added space before FROM to correct an issue introduced by fix
  JR48669 (syntax check errors in se38)  - affects tRFC, qRFC, SQL
  
  After installing the patch, regenerate the ABAP programs for all
  ABAP stages in the affected jobs:
  1. open the ABAP stage GUI
  2. select the Output/ABAP program tab
  3. click "Clear program"
  4. click "Generate program". Answer "yes" to the question to
  upload.
  5. click "OK" to close the stage GUI
  6. save and recompile the job
  
  Note: if you want to avoid re-compiling the job and you are
  positive the columns in the job are synchronized with the
  existing ABAP query, you can just click "Cancel" at step 5.
  The ABAP program would still be uploaded and the job does not
  have to be recompiled.
  
  A quick way to verify if the programs are re-generated using
  this fix is to search for this function in the ABAP program:
  FORM RFC_CALL_SEND_DATA.
  
  Before the patch is would contain:
  CALL FUNCTION 'Z_DS_ABAP_TRANS'
  IN BACKGROUND TASK
  AS SEPARATE UNIT
    DESTINATION RFCDESTC
  
  After the current fix, the addition "AS SEPARATE UNIT" is
  dropped:
  CALL FUNCTION 'Z_DS_ABAP_TRANS'
  IN BACKGROUND TASK
    DESTINATION RFCDESTC
  

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

• R650 PSY

     UP

• R700 PSY

     UP