Correcting Errors in the XPRAS Phase

Context

If errors occur in the XPRAS_AIMMRG phase during the execution of XPRA reports, the Software Update Manager stops and refers to the XPRASUPG.ELG log, which contains error messages with the following header:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in <file name>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code, then errors have occurred while the reports were being executed. In addition to the actual error lines, a separate line indicates the names of the reports that generated the preceding error messages.

You can display a detailed help text for each of these error messages in the SAP system. These texts usually contain all the information you need to correct the error.

Procedure

Find help texts for error messages
1. Search the XPRASUPG.ELG log to find the file name specified in the header.
  Note
  
  The file name that appears in the header of XPRASUPG.ELG is important for finding the help text. The file name always has the following format:
  SAPR<target_release>XPRA9<ID>.<SID> (where <ID> is a seven-digit number)
  The name of the relevant transport request can be derived from the two names. Replace the R with a K and delete the period and all characters that follow it. You have now SAPK<ID> as the name of the transport request.
2. Log on to the SAP system.
3. Call transaction SE09.
4. Choose Request/task Display individually and enter the name of the transport request SAPK<ID>.
5. Choose Goto Transport logs to display the individual transport logs.
6. Double-click the line Exec after put to navigate to the log display for this step. You can expand the log to view it in more detail. The error messages are visible as of the second level.
7. Position the cursor on the error message and choose Long text to display a help text.
Correct Errors
1. Follow the instructions in the help text to correct the error.
  If you are asked to implement an SAP Note, proceed as follows:
  1. Enter the following commands to unlock the SAP system:
    
    cd <update directory>/abap/bin
    
    ./SAPup unlocksys
  2. Log on to the system with a user other than DDIC and implement the SAP Note using the SAP Note Assistant (transaction SNOTE).
  3. Lock the SAP system using the following command:
    
    cd <update directory>/abap/bin
    
    ./SAPup locksys
2. After you have corrected all the errors, repeat the XPRAS phase.
3. Read the documentation of the report in question if you need more information, or if the report still results in errors when you repeat the XPRAS_AIMMRG phase. To access this information, log on to the SAP system. Call transaction SE38 and display the documentation for the report that is named in the error log.
4. Optionally, you can choose Accept non-severe errors and repeat phase XPRAS_AIMMRG.
  
  The Software Update Manager repeats the phase and accepts all error messages with the return code 8. The errors have to be removed after the update.
  
  You require a password for ignore all errors. The Software Update Manager then continues with the next phase, without executing the following XPRAs. Before you can choose ignore, you should have the approval from the SAP Support.
Correct errors after the update

If possible, correct errors immediately. However, you can correct some errors that occur during the execution of XPRA reports after you have completed the update.

This option makes sense, for example, when special measures in the SAP application areas are necessary to correct the errors, and the corresponding specialists are not available right now. To do this, you have to suppress the execution of the corresponding report before you repeat the update phase.

After the update, correct the error and run the report manually using transaction SE38.

For technical instructions on skipping an XPRA report, see SAP Note 122597 .

Caution

Skip an XPRA report only if you are sure that you can execute it later (for example, if an SAP Note tells you that this is allowed).
If you cannot execute an XPRA report later, and you still want to skip it, contact the SAP Support.
Consider special error situations
- The error "Name xyz has already been used". e065(fdt_core)" occurs in method FDT_AFTER_IMPORT.
  
  To solve the problem, proceed as follows:
  1. Continue the update with option Accept non-severe errors and repeat phase XPRAS_AIMMRG.
  2. Apply SAP Note 1301695 .
  3. Restart the after-import processing for method FDT_AFTER_IMPORT using report FDT_TRANS_Q_RESTART for S tables, T tables, and C tables.
- The following short dumps occur:
  - Runtime Errors COMPUTE_INT_PLUS_OVERFLOW
  - Exception CX_SY_ARITHMETIC_OVERFLOW
  - Date and Time [...]
  Check whether the short dump is the same as described in SAP Note 1243486 . If so, proceed as described there. Otherwise, contact the SAP Support.
- Error messages appear in log files
  - XPRAs are application reports that run at the end of an upgrade. Most XPRA reports have a report documentation that explains what the report does and how errors can be corrected. Call transaction SE38 in the SAP system, enter the report name, choose Documentation, and click Display. The names of the erroneous XPRAs are mentioned in the log file in messages of type PU132.
  - After-import methods are functions that are executed when a certain object type is part of the update. The name of the erroneous after-import method is mentioned in the log file in messages of type PU133. The corresponding component is mentioned in messages of type PU137.
  - In some cases, a hard error occurs that leads to abortion of the batch Job. In these cases, no error logs are written.