Skip to main content
insightsoftware Docs insightsoftware Docs
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Configuration Extensions

You can add configuration extensions to some of the modules and object types defined in the standard content.

  • In Configuration Extensions navigation mode, you can inspect the defined configuration extensions (see Inspecting the configuration extensions).
  • In Modules navigation mode, if at least one configuration extension type is supported for a module or object type, the edit page of that entity will have an enabled Configure button: WB_button_configure.

Currently, two types of configuration extensions are supported:

  • Restructure configuration extensions

    With restructure configuration extensions you can easily add fields to existing object types without having to manually create or edit content. The following restructure configuration extensions are supported:

    • Long texts

      Long texts are the container for long texts in SAP systems that are usually attached to business objects. They enable users to freely enter comments.

    • Partner roles

      Partners roles are used to classify a business partner in business terms and reflect the functions it has and the business transactions in which it is likely to be involved.

    • Statuses

      Statuses on documents are affected or updated by business transactions to avoid inconsistencies by restrictions based on the current status and allow control. There are system statuses and user statuses.

      • System statuses are set by the system and cannot be deleted or changed directly.
      • User statuses are activated by the user and can be created as an addition to the existing system statuses.
    • Classifications

      Classifications can be thought of as heavily customizable attributes to describe the related objects.

  • Templating configuration extensions

    Templating configuration extensions can be used to generate specific content without having to repeat content manually. The following templating configuration extensions are supported:

    • Financial statement version

      Financial statement versions are ‘trees’ that organize and group general ledger accounts.

    • Conditions tables

      Condition tables are used for customer specific material prices, e.g. to give discounts for privileged customers.

    • Controlling hierarchies

      Finally, controlling hierarchies are trees that map the organizational structure onto an accounting structure of which Angles for SAP currently supports cost centers, cost elements and profit centers.

In the Modeling Workbench, both types of configuration extensions are supported and they work in a similar fashion.

Related topics

Published:

Configuration Extensions

You can add configuration extensions to some of the modules and object types defined in the standard content.

  • In Configuration Extensions navigation mode, you can inspect the defined configuration extensions (see Inspecting the configuration extensions).
  • In Modules navigation mode, if at least one configuration extension type is supported for a module or object type, the edit page of that entity will have an enabled Configure button: WB_button_configure.

Currently, two types of configuration extensions are supported:

  • Restructure configuration extensions

    With restructure configuration extensions you can easily add fields to existing object types without having to manually create or edit content. The following restructure configuration extensions are supported:

    • Long texts

      Long texts are the container for long texts in SAP systems that are usually attached to business objects. They enable users to freely enter comments.

    • Partner roles

      Partners roles are used to classify a business partner in business terms and reflect the functions it has and the business transactions in which it is likely to be involved.

    • Statuses

      Statuses on documents are affected or updated by business transactions to avoid inconsistencies by restrictions based on the current status and allow control. There are system statuses and user statuses.

      • System statuses are set by the system and cannot be deleted or changed directly.
      • User statuses are activated by the user and can be created as an addition to the existing system statuses.
    • Classifications

      Classifications can be thought of as heavily customizable attributes to describe the related objects.

  • Templating configuration extensions

    Templating configuration extensions can be used to generate specific content without having to repeat content manually. The following templating configuration extensions are supported:

    • Financial statement version

      Financial statement versions are ‘trees’ that organize and group general ledger accounts.

    • Conditions tables

      Condition tables are used for customer specific material prices, e.g. to give discounts for privileged customers.

    • Controlling hierarchies

      Finally, controlling hierarchies are trees that map the organizational structure onto an accounting structure of which Angles for SAP currently supports cost centers, cost elements and profit centers.

In the Modeling Workbench, both types of configuration extensions are supported and they work in a similar fashion.

Related topics

For an optimal Community experience, Please view on Desktop
Powered by Zendesk