KBM Consulting Support
If you want to report errors for the KBM consulting solution, you can do so via the SAP ticket system.
- First check that you have imported the current build / current transport of your KBM version in the system. New builds/transports for the respective KBM cycle appear at regular intervals. The last build/transport contains all previous error corrections. It is possible that an error that you want to report has already been resolved. It is then sufficient to download and import the latest build/transport of KBM from the delivery platform.
You can find your currently imported KBM transport in the SCM Infocenter under transaction /n/SAPLOM/X_TRD.
First compare the version in your system with the version that is available for download on the delivery platform.
- Create an OSS incident under the component XX-PROJ-CON-KBM. For the priority of tickets, refer to the SAP Note.67739

- Make sure that the system connection is open and that credentials for logging on to the system are provided in the secure area of the incident. Check that it is possible to log on to the client of your choice. Also check that the provided user name has authorization for the transactions /n/SAPLOM/KBM, SE80, SE03, and for debugging in the system.
- Open the SCM Infocenter under transaction /n/SAPLOM/X_TRD and copy the output to the OSS incident.
- Describe the issue: What is the system behavior and what would you have expected?
- Provide a step-by-step description with an example of how to reproduce the error. An example includes:
- System name
- Client
- Variant
- Plant
- Material
- Any other relevant entries on the selection screen
Describe the example in a document and attach it to the incident.
- If an import error occurs, attach a screenshot of all imported SCM Consulting Solutions transports and the import sequence to the OSS incident, as well as a screenshot of the import error that occurred.
- In the case of a short dump, attach it to the OSS incident (for example, from transaction ST22).
Create an incident for each topic. Please do not mix topics in the incidents. See SAP Note 50048
.