Updating SAP ABAP Systems on UNIX and Linux: IBM Db2 for Linux, Unix, and Windows

Correcting Problems When Processing ABAP Steps

Context

The following ABAP steps are performed in the SAP system:

  • ABAP Dictionary activation (A)

  • Distribution of ABAP Dictionary objects (S)

  • Table conversion (N)

  • Matchcode activation (M)

  • Import of application objects (D)

  • Update of version management (U)

  • Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP system. To trigger an ABAP step, tp writes control information to this table.

The JOB_RDDNEWPP phase schedules the event-driven background job.

For more information about the transport control program tp and the communication between tp and the SAP system, see the SAP Help Portal and follow the path according to your source release:

Release

Path in SAP Help Portal

  • SAP NetWeaver 7.3

  • SAP NetWeaver 7.3 incl. EHP 1

  • SAP NetWeaver 7.4

  • SAP NetWeaver 7.5

  • SAP NetWeaver AS for ABAP 7.51 innovation package

  • SAP NetWeaver AS for ABAP 7.52

Start of the navigation pathApplication Help Next navigation step SAP NetWeaver Library: Function-Oriented View Next navigation step Solution Life Cycle Management Next navigation step Software Logistics Next navigation step Change and Transport System Next navigation step Transport Tools (BC-CTS-TLS) Next navigation step Transport Control Program tpEnd of the navigation path

SAP NetWeaver 7.0 and EHPs up to 3

Start of the navigation pathApplication Help Next navigation step SAP NetWeaver by Key Capability Next navigation step Solution Life Cycle Management by Key Capability Next navigation step Software Life Cycle Management Next navigation step Software Logistics Next navigation step Change and Transport System Next navigation step Transport Tools (BC-CTS-TLS) Next navigation step Transport Control Program tpEnd of the navigation path

Procedure

  1. Make sure that the SAP system was started correctly. Log on in client 000 as user DDIC.
  2. Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled.

    In the or after event field, enter an asterisk (*) so that event-driven jobs are also displayed.

  3. Check when RDDIMPDP last ran and whether it ran without errors.
  4. Check whether the control information in table TRBAT has been entered correctly.

    The table should have one HEADER entry and should contain one entry for each transport request. While the ABAP Dictionary objects are being distributed (S) and the tables converted (N), table TRBAT may contain only one HEADER entry, since these steps are not carried out by transport request.

  5. Call transactions SM37 and SM50 to check whether RDDIMPDP has already started the background job that processes the ABAP step.