JR50101: ABAP STAGE WITH RFC DATA TRANSFER: RE-INTRODUCE INDIVIDUAL TRANSACTIONS FOR THE ABAP PROGRAM TO ENABLE DS ROW EXTRACT

APAR status

• Closed as program error.

Error description

• ABAP stage with RFC data transfer: re-introduce individual
  transactions for the ABAP program  to enable DS row extraction
  as soon as the SELECT statement is completed in SAP
  

Local fix

Problem summary

• ABAP stage with RFC data transfer: re-introduce individual
  transactions for the ABAP program ("AS SEPARATE UNIT")
  to enable DS row extraction as soon as the SELECT statement is
  completed in SAP.
  

Problem conclusion

• The ABAP program statement "AS SEPARATE UNIT" was present in 70
  GA but later removed following JR48495.
  The intention with removing the statement was to clean up SAP
  transaction sm58, so just one transaction id is used for all
  packets.
  But, as we have found, a side effect in using just one
  transaction is that reading the data can only be started after
  all data is transferred.
  Code fix: reintroduce the "AS SEPARATE UNIT" statement. The fix
  affects affects both transfer methods (tRFC,qRFC), generation
  methods (SQL,EO),
  for both background and non-background jobs.
  
  *---------------------------------------------------------------
  ----*
  * Send data to RFC Transfer table
  *---------------------------------------------------------------
  ----*
  FORM RFC_CALL_SEND_DATA.
  CALL FUNCTION 'TRFC_SET_QUEUE_NAME'
  EXPORTING
  QNAME = 'ZIPSVM00273_ABAP_QRFC1'.
  
  CALL FUNCTION 'Z_DS_ABAP_TRANS'
  IN BACKGROUND TASK
  AS SEPARATE UNIT
    DESTINATION RFCDESTC
  TABLES
    ETLSTRSF = ETLTRSFTAB.
  

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