Skip to Content

Use the "Application Information"-Section of Dumps created by BOPF

While developing ABAP-based applications with the Business Object Processing Framework (BOPF), errors in your coding might lead to dumps. This is because neither ABAP nor BOPF can automatically handle a situation caused by a typical programming error (e.g. variable not bound). Thus the transaction will be rolled back and a dump containing some detailed information is written. In order to analyze the issue afterwards, the transaction st22 can be used to check the callstack and the values of variables.

Issue

However, in some cases it is a little cumbersome to check the callstack and a more precise dump analysis would be appreciated.

Example

In this example I use the Service Manager of the "Demo Customer" Business Object but invoking an action belonging to the "Sales Order" Business Object. This lead to a new dump.

Solution

In order to provide more precise error analysis, often the "Application Information" section of the dump is automatically filled by the BOPF during the crash. It often contains not only a description, but also a hint how to solve that issue. This additional information is available for the most common error pattern.

Example

The application information in transaction st22 describes that I am using the wrong Business Object. Changing my code to use the "Sales Order" Business Objects indeed solves the issue.

Conclusion

In case of dump caused by the BOPF check the application information section in transaction ST22. For typical error situations, BOPF creates a precise error description and often provides a hint for a solution.

  Hint: This article has been moved from a blog to the official BOPF content space

Former Member

No comments