Here the list of inputs required to reproduce issue related to one particular object
Release | Yes/No |
|---|---|
| 8.0.x |  |
| 7.3.x | |
| 7.2.x | |
| 7.0.x |  |
The source code of faulty (or missing) object and other utilitarian files if necessary (see below).
Technology | Utilitarian files |
|---|---|
C++ | The include files used in the environment profiles is also necessary. For crash issues use the pre-processed file (..\Logs\Preprocessed). |
J2EE | XML and Jar files used n the environment profiles |
Please note For ABAP technology, if the faulty object is part of a Class Pool or a Function Pool, we need the code source of the Class Pool/ Function Pool which is usually splitted in many source file starting with same part. For example, the following list of files are the code code source the Class Poll ZCL_IM__FETCH_STORAGE_CAT:
ZCL_IM__FETCH_STORAGE_CAT=====CM001.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM002.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM003.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM004.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM005.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM006.abap
ZCL_IM__FETCH_STORAGE_CAT=====CM007.abap
Also, note that if objects other than the faulty object are involved in the violation, you will also need to get the source code of these objects. For instance, for diagnostics based on client/server links, you will need the participating base.