Debugging an extension

You can debug these types of extensions:

• Table extension

  To debug a table extension you must run a session that uses the table to which the extension belongs as a main table.

  You can also run a session for a different table, which does a dependent update in the table to which the extension belongs. For example, to debug a table extension for the inventory allocations table, you can run the sales order lines session to debug that extension.

• Report extension

  To debug a report extension, you must run the print session that produces the report.

• Session extension

  To debug a session extension, you must start the session you have extended. It can be necessary to start with another session if your session cannot be started directly from the menu.

• BOD extension

  To debug a BOD extension, you must start a session that publishes the BOD. This can be a session in the normal process flow, but you can also use the session that simulates the publishing of your BOD. In the LN menu structure, these sessions are located under Common > BOD Messaging > Publish BODs.

• Menu extension

  To debug a menu extension, expand the menu.

• Process extension

  To debug a process extension, you must run the session that uses the process extension.

You cannot debug the domain extension library.