What's New Viewer - SAP S/4HANA

Detail Improvements

The following features describe detail improvements:

  • PMQ.Designer

    • Improvements for Breakpoints

      The PMQ.Designer debugger now also supports breakpoints for creating and deleting product module instances, relation instances, structure instances and messages.

      In addition, the following functions have been added to the existing breakpoints:
      • Condition at exceptions

      • Using breakpoints as trace points (console output instead of pausing)

      • Using breakpoints as trigger points (preventing hitting of breakpoints until more trigger breakpoints hit)

      • Freely selectable names for context variables in conditions and console outputs of watch points, exception breakpoints and instance breakpoints.

    • Deleting Objects via Search View

      It is now possible to delete objects from the Search view in the view type Tree and List. The deletion takes place in the same way as deleting in other views and editors, that means, references to the object to be deleted are also removed.

    • Improvements for the Legacy Mode

      The PMQ name check can be (de)activated using the project setting Legacy mode (context menu Start of the navigation pathProject Next navigation step Properties Next navigation step PMQ Settings Next navigation step Project SettingsEnd of the navigation path in the group Compability). The name check of msg.PMQ is more restrictive than in msg.PM 3.x. Only the letters A-Z, the numbers 0-9 and underscores are allowed.

      The project settings Legacy mode and C runtime support can now be switched independently. Customers who use C runtime as their runtime environment can now also use PMQ name validation. Problems in downstream application systems due to the use of special characters in names can thus be avoided.

      The legacy mode contains further validations. These validations have been fundamentally revised.

      For more information, refer to the PMQ.Designer User Guide, section 'Legacy Mode (Compatibility to msg.PM 3.x)'

    • Improvements for the Product Data Update
      The dialog for updating the product data (context menu Start of the navigation pathProject Next navigation step Update Product DataEnd of the navigation path) has been adapted. The previous options
      • Update old product data to the current data version (including add/update GUIDs for stable object referencing)

      • Reformat all product data XMLs

      • Delete history in the product data

      are an integral part of the product data update as of this release. The user now has the possibility to update either all files or only files with outdated data versions. The option Activate automatic naming for product module relations is retained and can only be activated in connection with updating all files.

      Furthermore, a new headless command UpdateProductData is introduced. In the course of this a new flag -allFiles is provided, which extends the scope of the update to all files.

      The parameter -updateProductData can now be set for the already existing headless command ImportExistingContentProject - as for the headless command ImportContentArchive. If the parameter -updateProductData is specified, the data version of the imported objects is updated to the data version used by PMQ.Designer, otherwise the data version is not adjusted.

      For the command ImportExistingContentProject, the original boolean parameter -ignoreExisting was renamed to -skipExisting and converted to a flag. If the flag -skipExisting is specified, existing projects are skipped during import. If the option is not set, the import of an existing project is terminated with an error.

Technical Details



Functional Localization

Not applicable

Scope Item

Not applicable

Application Component

FS-MPM (msg.PMQ)

Available As Of

SAP S/4HANA 1909